Damn - this sounds subtle, and good catch. I'll have a look but it may be mid week before I can do anything useful.
-Ben On May 18, 2012, at 6:39 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > Todd Oliver found and partially tracked down an ugly bug; I think I've > got it pinned down to a libHilbert interface issue. > > A test code which breaks is attached. Originally we had to do some > refinement to trigger the problem but now literally all it does is > generate a 1D mesh and write it out. The first argument is the number > of elements. 1 through 3071 work. 3072 (and many other larger mesh > sizes, sparsely scattered...) fails. > > Todd triggered the bug at a tot_val_size assertion in the I/O code, > but the underlying problem turns out to be duplicate HilbertIndices > leading to duplicate renumbered node ids. I've updated the svn head > to test for duplicate HilbertIndices and print them out as soon as > they're found in MeshCommunication::assign_global_indices(). > > I'm still not sure *why* the duplicate indices are occuring, and I'm > at the point where more eyes might be helpful. > --- > Roy > <refinement_test.C> ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
