Currently when we sync a BoundaryMesh for the entire boundary, we give the boundary elements subdomain_ids and processor_ids that correspond (after mapping them to be sequential starting with 0) to the boundary condition ids their corresponding interior elements' sides had... unless we're sync'ing a limited set of requested boundary ids, in which case we make the subdomain_ids and processor_ids match the interior elements.
Would anyone mind if we just made the latter behavior the default for *any* BoundaryInfo::sync? The former seems kind of useless, except maybe for visualization-only purposes, and it would be nice to refactor the two implementations, since adding ParallelMesh support is making the sync() a bit more complicated. --- Roy ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
