auto_write cellLevel_, pointLevel_, and level0Edge_ #9
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
|
There are a couple of different constructors for the hexRef class. When the levels and level0Edge fields are not provided they are set to READ_IF_PRESENT. Only when the lists are provided are the fields set to NO_READ. You should be able to restart simulations and have the refinement continue as expected. I just double checked with the Riemann2D case. |
|
The fields are also written by explicitly calling cellLevel_.write(), pointLevel_.write(), and level0Edge_.write() in the hexRef::write() function. If you look in the timeName/polyMesh folder everything will be there. |
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.
Dear developers,
In the
hexRef.C, the variables cellLevel_, pointLevel_, and level0Edge_ are set toNO_READandNO_WRITE. While that set will cause the refined mesh can not be unrefined when recalculating from the breakpoint, because of missing the level message. If you think my opinion is reasonable, you can consider this pull request.Best wishes.