added feature snapping criteria to snappyHexMeshDict and changed decomposition method #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SiHubb
changed the title
SiHubb
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think the issue was not snapping correctly around the features. There are some inputs into shmDict that control feature snapping that were missing, so I grabbed them from the template dict (foamGetDict snappyHexMeshDict). The .eMesh file input is only for resolution control, not snapping.
FYI I ran this on v2206, but worked fine.
Ignore the constant/polyMesh/boundary file update, I just didn't clean up well enough afterwards...
After a closer look there was still some unpleasantness around the boundaries. I tweaked blockMeshDict and the writePrecision (probably doesn't affect the result, just habit) and changed the decomposition from hierarchical to scotch. I generally use scotch as it has good processor face sharing. You have to be careful with hierarchical when choosing the x y z decomposition relative to the geometrical extent in each direction.