v12: Update c12 and c24 timesteps#715
Merged
sdrabenh merged 1 commit intofeature/sdrabenh/gcm_v12from Apr 15, 2025
Merged
Conversation
sdrabenh
approved these changes
Apr 15, 2025
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
2 participants
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.
Recently, many of my nightly tests for c12 and c24 have been failing. Working with @atrayano, we found they all had hallmarks of "instability". So, in this PR we change the default time steps for c12 and c24:
More complete testing is ongoing, but this seems to fix the issues we are seeing.
I am marking non-zero-diff as it is for these resolutions, but only those.