-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expensive gmi_is_point_in_region called during ma::adapt #444
Comments
for reference, can you add details on the adaptation inputs you're using? or a the link to the main function if available |
This are the inputs we're using. ma::Input* in;
in = ma::makeAdvanced(ma::configure(apfMesh, mdsScaleField, mdsFrameField));
in->shouldSnap = true;
in->shouldTransferParametric = true;
in->shouldFixShape = true;
in->shouldForceAdaptation = true;
if (apfMesh->getDimension() == 2)
in->goodQuality = 0.04; // this is mean-ratio squared
else // 3D meshes
in->goodQuality = 0.027; // this is the mean-ratio cubed
in->maximumIterations = 10; We are calling it from a file similar to capstone_clis/capStoneAnisoAdapt.cc |
For reference, this commit 4b51494 added the check. |
I believe this is closed by #446? |
Yeah. It should be all set. |
I'm reporting an issue in ma::adapt where an unnecessarily expensive call (depending on geometric complexity) is made to gmi_is_point_in_region.
Call stack (from gdb):
I'm not particularly well-versed in the adapt code, but this should be avoidable during adaptation.
The text was updated successfully, but these errors were encountered: