If you're just going to do it once... just do it in the same way on all the processors.
In general, this is "the way" with libMesh... do a little redundant computation to keep from doing communication. Anything you're going to do a limited number of times is a good candidate for this. Derek On Sun, Apr 7, 2013 at 2:58 PM, Ataollah Mesgarnejad <[email protected] > wrote: > Roy, > > Since I only need to this once in the beginning of my program can't I do > it on the head node and then broadcast the mesh using: > MeshCommunication::broadcast ? > > Thanks, > Ata > > On Apr 7, 2013, at 12:01 AM, Roy Stogner <[email protected]> wrote: > > > > > On Sat, 6 Apr 2013, Ataollah Mesgarnejad wrote: > > > >> One more question: do I need to broadcast this or will it be set for > >> all the copies of the mesh? > > > > You'll need to communicate it yourself. > > Parallel::sync_dofobject_data_by_id() might be useful for doing so. > > --- > > Roy > > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users > ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
