> On 25 Oct 2018, at 23:08, Jeremy Theler <jer...@seamplex.com> wrote: > > Hi all > > I see in contrib/HighOrderMeshOptimizer/OptHomRun.cpp:686 that if the > higher-order optimizer cannot make all the jacobian non-negative, then > an error is raised. > > Why is this a hard error and not a warning? I have seen cases where the > optimizer cannot make all of then non-negative, yet the results are > reasonable. Moreover, if not optimizing high order, they still are (and > the general quality is worse). So I do not get why this is an error. > > Any comment?
The goal of the optimization is to produce all-valid elements... But indeed we could downgrade the failure to a warning -> it's changed in git. > > Thanks > -- > jeremy > www.seamplex.com > > > > > _______________________________________________ > gmsh mailing list > gmsh@onelab.info > http://onelab.info/mailman/listinfo/gmsh — Prof. Christophe Geuzaine University of Liege, Electrical Engineering and Computer Science http://www.montefiore.ulg.ac.be/~geuzaine Free software: http://gmsh.info | http://getdp.info | http://onelab.info _______________________________________________ gmsh mailing list gmsh@onelab.info http://onelab.info/mailman/listinfo/gmsh
