In general I think it may be dangerous to add dofs at the wrong time - we don't currently build up a list of processors we need to communicate with, but I could see that being a useful optimization. In that case the list needs to be constructed after all dofs are added to the list.
I'd think the best way to go is an API where the user can provide a vector list of dofs to add, and internally we could then do error checking as appropriate? Raw writeable access to the list just feels dangerous. -Ben On Feb 8, 2011, at 11:04 AM, "Derek Gaston" <[email protected]> wrote: > Is there a currently accepted way to add dofs to the send_list? > > I see that you can get the send_list from the dof map but it is const. > Should I add another method where you can pass in dofs to add to the send > list (maybe in an std::vector) or should I change the accessor so I can get a > non-const send_list? Is there a reason it's const? > > Thanks, > Derek > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
