On Wed, 23 Mar 2011, Andrea Hawkins-Daarud wrote:
Search through the svn logs for libHilbert, which we use to get
partitioning-independent node numbering in mesh files. There was a
bug in our earlier interface to libHilbert which was actually creating
corrupted outputs in some cases. IIRC we switched the renumbering off
to avoid triggering the bug, then switched it back on once the bug was
tracked down and fixed. If you've got files that read fine with an
older libMesh version but get scrambled today, they were probably
written with libHilbert disabled. If you've got files that don't read
fine with any libMesh version, you probably got hit by the bug...
although I think in this case the mesh doesn't read correctly either
so you're probably in the previous case.
Ok. Does knowing that it did work back in August guarantee that I
didn't get hit by the bug? =)
If you were able to load a mesh and solution in dbg mode without
triggering an assert failure (or if you know you were able to load
them in opt mode without inaccuracy) then you didn't get hit by the
bug.
I will try a few versions and see what happens.
Try configuring the svn head with --disable-libHilbert and see if
things read properly.
---
Roy
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
