Fix layerNormalVelocity bug in Runge-Kutta loop #130
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
Update layerNormalVelocity in each RK stage. While velocity was being solved for each stage, layerNormalVelocity was not being updated based on the updated velocity, which is a major bug.
Use layerNormalVelocity instead of normalVelocity to calculate layerThicknessEdge.
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.
Even though we do a velocity solve during each Runge-Kutta stage, those updated velocities were not being used for advection because
layerNormalVelocitywas not being updated after each velocity solve. This merge fixes that major bug in RK time integration.