Hi Alessandro,
If I am understanding you correctly, you can already accomplish this yourself
as a user by calculating the number of nodes you need to specify for a given
progression to get a desired first element size.
From a CFD perspective, what would make the most sense intuitively would be
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
It might be useful having the possibility to specify the number of intervals
and the length of the first element, rather than the progression…
A.
Da: gmsh [mailto:gmsh-boun...@ace20.montefiore.ulg.ac.be] Per conto di Ruth
Vazquez Sabariego
Inviato: mercoledì 24 ottobre 2018 16:28
A: Nathan J.