After some searching and testing, I found deleting a few lines in
src/mesh/mesh_data.C will solve
the parallel of MeshData in xdr format.
Basically, in MeshData::read, we can allow all processors to read. From the
file mesh_data_xdr_support.C (unchanged),
one processor has data for all nodes, but only elements it owns.
I have not tested if this will cause problems for another formats MeshData
can read: unv and tetgen. But I think
they will be fine at least one processor has data for all nodes and
elements.
I attach this little patch in case you would like to commit it into the
repository.
Thanks a lot for your help!
Mengda
2009/6/3 Roy Stogner <[email protected]>
>
> On Tue, 2 Jun 2009, Mengda Wu wrote:
>
> Adding parameters as variables is a good idea. I will try that first.
>> For now, I have already had my serial version code working using MeshData
>> format .xta. I am wondering if you can give some hints on how to load that
>> data
>> in a parallel setting.
>>
>
> Your best bet is to do the transformation in serial: write a serial
> program that loads the MeshData and writes it out to a new vector in a
> new ExplicitSystem. Then you can write that system out in serial and
> load it up again in parallel.
>
> (2) Should I use add_vector instead of add_variable() to avoid increasing
>> the number of dofs. Right?
>>
>
> I'd add_system() first - create a new ExplicitSystem and just use its
> solution vector for the parameter.
> ---
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
