← Back to team overview

dolfin team mailing list archive

Re: MeshDomain

 

On 11 February 2013 10:05, Johan Hake <hake.dev@xxxxxxxxx> wrote:
> On 02/11/2013 10:44 AM, Garth N. Wells wrote:
>> On 11 February 2013 08:00, Johan Hake <hake.dev@xxxxxxxxx> wrote:
>>> I am adding some functionality to MeshDomains, (actually to SubMesh,
>>> which soon also propagates MeshDomains to the new mesh), and wonder if
>>> there where any good reasons why a MeshDomain does not have a pointer to
>>> the parent mesh?
>>>
>>
>> Not that I recall. Will adding a pointer to a Mesh cause a problem
>> when reading MeshDomain files which do not contain a Mesh?
>
> MeshDomain does not read any files. It is just a collection for
> MeshValueCollections, which indeed can be created from file. But I am
> not suggesting putting a Mesh into a MeshValueCollection.
>

OK, I was confusing the two.

Garth

> Johan
>
>> Garth
>>
>>> If such was provided during construction we could skip the annoying mesh
>>> argument in:
>>>
>>>   facets_domains = mesh.domains().facet_domains(mesh)
>>>
>>> Johan
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dolfin
>>> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dolfin
>>> More help   : https://help.launchpad.net/ListHelp
>


References