On Thu, 6 Oct 2011, Cody Permann wrote: > I'm running into a serious regression with this patch. If you > declare a Mesh variable with the default constructor arguments you > end up with a mesh with dimension=1 (mesh_base.h:80). If you then > make a call to mesh::read(...) -> ExodusII_IO::read(...), you'll > immediately trip the new error check at exodus_io.C:110 when it > tests for the dimension of the mesh and fails if it equals 1. The > ExodusII interface was updated by Roy some time ago to set the > dimension of the mesh "after" reading the ExodusII header > information. This new error check simply needs to be postponed > until after the header is read and the mesh dimension has been set. > > I'm happy to make the change or you can. Let me know,
Can you? Thanks; sorry we missed that. --- Roy ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
