Re: [Libmesh-users] Status of MeshData in parallel?

[Mengda Wu <ph...@gm...>]

Thanks for your reply!

What if I have a smoothly varying properties, i.e. The properties are
generally differently between neighboring elements.
Can I use subdomain_ids to do that?

Could you please list some packages that can generate Exodus meshes? I only
found that CUBIT can do this, but
it is not free to use. Or if there is a documentation about Exodus file
format. That will be even better.

Besides, how xda supports subdomain? I have not found the information in the
following document:
http://libmesh.sourceforge.net/xda_format/xda_format.pdf

Thanks,
Mengda

2009/6/2 Derek Gaston <fri...@gm...>

> And if all you want to do is assign different properties to different sets
> of elements I highly recommend setting subdomain_ids on elements and then
> just using those to infer what material properties should be used on each
> element.
>
> If you build your meshes with something that outputs Exodus meshes... you
> can create element "Blocks" that are assigned subdomain_ids... which will
> automatically get read in and assigned when you read the mesh.  I'm not sure
> if any of our other mesh formats (besides xda obviously) support that.
>
> Derek
>
>
> On Jun 2, 2009, at 6:34 AM, Roy Stogner wrote:
>
>
>> On Tue, 2 Jun 2009, Mengda Wu wrote:
>>
>>   I am trying to use the MeshData structure in parallel. It seems
>>>  that there are some discussions on this issue. I am wondering what
>>>  is the status of MeshData in parallel.
>>>
>>
>> Unmaintained in general, not working in parallel.  None of the current
>> libMesh developers are MeshData users/developers or have been for
>> quite some time, so nobody's had the knowledge to work on or extend
>> the class.
>>
>>  How to handle the meshdata such as material parameters in parallel
>>> if this feature is not available.
>>>
>>
>> A separate solution field in a separate ExplicitSystem can be used to
>> store scalar material parameters easily; an equal order LAGRANGE field
>> for nodal data or a 0th order MONOMIAL field for cell data, for
>> example.  Those would get extended properly though mesh
>> refinement/coarsening.
>>
>> Alternatively, you could be the one to fix MeshData.  We'd happily
>> accept patches from an active user of it.
>> ---
>> Roy
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libmesh-users mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libmesh-users
>>
>
>