Skip to content
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

Fix bug in limiting cull distance #787

Merged

Conversation

trhille
Copy link
Collaborator

@trhille trhille commented Mar 8, 2024

This merge removes an unnecessary assertion about the value of cull_distance, since it is handled by other logic.

The assertion and the error message did not agree. We want to make
the assertion match the error message, limiting cull_distance to
be less than 3.0 * max(high_dist, high_dist_bed).
@trhille trhille requested a review from matthewhoffman March 8, 2024 21:00
@matthewhoffman
Copy link
Member

@trhille , looking at this again, I think the proper thing to do is delete the assertion and its message. What this bit of code was meant to do was stick coarse resolution out past the boundary of the culled mesh so that jigsaw runs faster by not having the highest resolution over a huge area that later gets thrown away. This bit of code does that automatically by setting the coarsest resolution at a (hopefully) safe distance beyond the specified cull_distance. That logic has nothing to do with the relation between cull_distance and the high_dist, so no check actually needs to happen related to that. I'm not sure what I was thinking when I wrote the assertion, but I don't think it makes sense, and we should just remove it.

Remove unnecessary assertion about cull_distance, as this is
handled by the logic that follows.
@matthewhoffman matthewhoffman merged commit a9d4b53 into MPAS-Dev:main May 22, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants