fixing auto dt sizing function#116
Merged
Merged
Conversation
WPringle
requested changes
Sep 12, 2020
Collaborator
There was a problem hiding this comment.
Hey, yes the fix seems correct.
There is this case where you choose obj.dt to be length 2 and maxCr will be infinity. I think this is mainly user problem but maybe we could have an error for length(obj.dt) = 2 and dt == 0? Saying that dt = 0 is only intended for restricting the upper bound of Cr?
elseif length(obj.dt) == 2
% minimum Courant number bound
minCr = obj.dt(2);
maxCr = inf;
```
Collaborator
Author
|
like this? |
Collaborator
|
Yeah except that wouldn't work because it would go into the elseif length(obj.dt) == 2 above, so like this:
|
Collaborator
Author
|
ah yea. cool. |
WPringle
approved these changes
Sep 12, 2020
Jiangchao3
added a commit
to Jiangchao3/OceanMesh2D
that referenced
this pull request
Sep 13, 2020
fixing auto dt sizing function (CHLNDDEV#116)
This file contains hidden or 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
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.
The automatic selection of the numerically stable timestep for which to CFL limit the mesh sizing function should be based on the
max_crnot themin_cr.This appears to fix #114 with a mesh that should be numerically stable at a timestep of roughly 1.34 seconds because of the high resolution zone near New York, e.g.,
The outer patch by itself is theoretically stable with: