Re: [Libmesh-users] Bug in ExodusII_IO::read

[Derek G. <fri...@gm...>]

I don't think there is a bug with ExodusII_IO.  Just make sure that your mesh doesn't contain any blocks, sidesets or nodesets that are _0_.

This is done on purpose so the numbering matches what gets generated with Cubit.

What are you using to generate your meshes?

Derek

This is 
On Feb 8, 2010, at 12:14 PM, Rahul Sampath wrote:

> Hi:
> 
> I believe that there is a bug in the function ExodusII_IO::read(). I
> have attached a sample program and the input file to demonstrate this.
> The ASCII version of the exodus file was generated using the tool
> ncdump. You can see the ExodusII uses a 1-based numbering scheme.
> However, when trying to add nodes to boundary_info using nodesets the
> ExodusII_IO::read()  function assumes a 0-based numbering scheme. As a
> result an assertion error is thrown at line 108 in serial_mesh.C in
> function SerialMesh::node_ptr, which is called from
> BoundaryInfo::add_node, which is in turn called from
> ExodusII_IO::read.
> 
> Regards,
> 
> Rahul
> <cubeMesh.txt>------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com_______________________________________________
> Libmesh-users mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-users