> Not really a problem, but does
>
> MeshBase::n_subdomains()
>
> affect the mesh partition later on or anything?
> Would it cause any problems
> if the corresponding variables of
>
> ExodusII::get_num_elem_blk() & MeshBase::n_subdomains()
>
> were set equal?
That should not cause any problem. The mesh has the notion of a subdomain
mapping which is separate and distinct from the parallel decomposition. So,
the Exodus reader may choose to set the subdomain flag to something
reasonable, but it could just as well ignore it. For that matter, the user
can change it as well without affecting anything.
Now, what you don't want to do is mess with MeshBase::n_partitions().
Looking at the documentation, I can see the confusion:
/**
* Returns the number of subdomains in the global mesh. Note that it is
* convenient to have one subdomain on each processor on parallel machines,
* however this is not required. Multiple subdomains can exist on the same
* processor.
*/
unsigned int n_subdomains () const
{ return _n_sbd; }
That is at best confusing, and probably misleading. I'll change that to say
the subdomain mapping is independent of the partitioning.
-Ben
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
