From: John P. <jwp...@gm...> - 2015-05-05 18:30:54
|
On Tue, May 5, 2015 at 12:20 PM, David Knezevic <dav...@ak...> wrote: > On Tue, May 5, 2015 at 10:27 AM, John Peterson <jwp...@gm...> > wrote: > >> >> >> On Tue, May 5, 2015 at 7:10 AM, David Knezevic < >> dav...@ak...> wrote: >> >>> [0] /home/dknez/software/libmesh-src/src/fe/fe_map.C, line 618, compiled >>> May 5 2015 at 08:08:28 >>> ERROR: negative Jacobian: -1.79627e-07 in element 7051 >>> >> >> Is your fe_map.C not the version in master? Line 618 doesn't have a >> libmesh_error_msg() on it for me. >> >> In any event, we have the Elem* available, so we should probably just be >> helpful and print the stuff that Roy requested before erroring out... >> > > > I added some print statements to the test code I was running before (with > libMesh git hash 1a6a549f26219f462ac4ceef87c3c03e9eafa836) and I get the > info printed below for the failing element. > > When I update to the git HEAD, I now get a segfault with no stack trace > when I just loop over the elements and call fe->reinit(elem). I'm wondering > if maybe ExodusIO isn't reading this mesh in properly, or something. > That, or a dirty build? I don't suppose this is another cubit bug where it's outputting TRISHELL elements with a different connectivity than we are expecting? -- John |