On Dec 9, 2008, at 7:56 PM, David Fuentes wrote: > thanks ben, > > in > > exodusII_IO::read > > the element subdomain_id gets set to the block id > > elem->subdomain_id() = subdomain_id;
This is my assumption.... and might not always be true... but I couldn't come up with a better way to relate subdomain_ids to something in an Exodus file. There is something else to be aware of when you use element blocks (especially generated by Cubit). You need to make sure that nodes from both element blocks along the interface between them _exactly_ correspond to eachother. If you don't... you will end up with "holes" in your mesh when you read it into libMesh. There are methods within Cubit for helping with this.... if you need to know let me know. In Sierra if there were two element blocks you had to do something special on the interface between them (like "tied thermal contact"). Assuming you don't want to write routines like that it's best to make sure the nodes perfectly align... then libMesh will happily stitch the two blocks together for you when it reads the mesh. This will allow you to have two subdomains in physically the same geometric entity (we use this for varying material properties). Derek ------------------------------------------------------------------------------ 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
