Benjamin Kirk writes: > > I've done like this after building a mesh object: > > > > // Partition the mesh with ParMetis package. > > ParmetisPartitioner pmetis; > > pmetis.partition(mesh, 4); // Partition the mesh on 4 processors > > > > // Print information about the mesh to the screen. > > mesh.print_info(); > > > > I get the following output which shows that I have only 1 subdomain: > > > > Mesh Information: > > mesh_dimension()=3 > > spatial_dimension()=3 > > n_nodes()=29791 > > n_elem()=3375 > > n_local_elem()=843 > > n_active_elem()=3375 > > n_subdomains()=1 > > n_processors()=4 > > processor_id()=0 > > > > > > So, what's wrong ? > > > Absolutely nothing ;-) > > The partitioners in libMesh set the elem->processor_id() flag. The > subdomain_id() is reserved for user purposes and is not touched by > partitioners. > > If you write the mesh in a format that can understand the partitioning (GMV > is my favorite) then you'll see four different processor domains -- > unfortunately the terminology is a bit overloaded and can be confused with > more material-specific subdomains.
Just wanted to add: if you want to find out the current number of partitions, use mesh.n_partitions(). I guess we could add this to our standard print_info() call as well. -J ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
