new here but I think I might be coming back a few times.
When I run the command line version of mmg (linux debug build from github master branch
mmg2d_Os -hmax 0.1 -v 10 sweet.msh
on a simple square input with four vertices, I get the following output https://pastebin.com/ue95vb8V which is fine.
However, when I run the same mesh through the API, setting hmax to 0.1 using
MMG2D_Set_dparameter(mesh, met, MMG2D_DPARAM_hmax, 0.1)
, I get the debug output
It ignores the hmax option and only generates one additional vertex. So, I wanted to track down on what point the two outpus diverge. The first point of divergence is when it says “8 corners, 0 singular points and 0 non manifold points detected” which appeared in the command line output but not in the API output, and then there are more divergences. How does that information help me to find out what is wrong with my API usage? Or do you recommend another way of debugging to find out why it ignores hmax? What is the recommended mechanism to make sure the API usage and the command line usage are the same? Even if the reason is some setting in mesh->info, why does the API ignore the hmax?
Thanks for help, Mathias