It appears that there is a regression in the XDA format reader. The mesh in example 10 that contains two subdomains of different element types loses it's subdomain information some time during the read stage. The error can easily be repeated by running that mesh through example 1 and viewing the printed information about the mesh. If you try to convert the mesh to Exodus through example 1 you'll see an additional flaw in the Exodus writer. The Exodus writer fails in a poor way since the two element types are both in the single subdomain. There isn't an explicit check in the ExodusII writer for two element types in a single subdomain so it seg faults in optimized mode and fails on a somewhat misleading assert in debug mode.
Cody ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
