Fix to mesher error in very specific cases #1325
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warn when structures are too small compared to the generated mesh.
Also realized that e.g. placing a thin
MeshOverrideStructure
of size dl and mesh step dl will not place boundaries on both sides of that structure (i.e. a single mesh step) because of the way theisclose
check is done. Changed tolerances a bit to fix this as it should be expected behavior.I also added more docstrings explaining how that part of the mesher works. I must admit it's still a bit of a mess, but I don't have time for a complete overhaul (and it's not clear what that might look like).