On Tue, Dec 2, 2008 at 5:44 PM, Roy Stogner <[EMAIL PROTECTED]> wrote: > On Tue, 2 Dec 2008, Roy Stogner wrote: > >> On Tue, 2 Dec 2008, John Peterson wrote: >> >>> Use the BoundaryInfo object to Sync with a boundary mesh and write to >>> GMV. Set each element's processor_id to its boundary ID to color them >>> independently. >> >> Nice idea! Thanks! >> >> It looks like meshtool already does the former (with the -b option) >> but I hadn't thought about tricking it into doing the latter. I'll >> commit that to the SVN version once I'm sure I've got it working. > > Ah, it appears we've got a regression in that feature - > BoundaryInfo::sync *already* sets processor_id values to boundary > ids... but then calls prepare_for_use, which repartitions. I'll dig > through old code and figure out how things were working before... but > I think it might be worthwhile to have a "dont_repartition_me" flag > that users (and in this case, the library) can turn off in MeshBase. > Or better yet - instead of creating a Parmetis or Metis partitioner > deep in mesh_base.C, let's leave it up to the Mesh constructor to > create a partitioner, then give the user the ability to destruct the > default and replace it with their own (including "Null") Partitioner > subclass. > > Any thoughts?
Fine with me as long as mesh.partition(n) still does what it always has. -- John ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
