-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
+Add option to fix z-file layer initialization bug #1266
+Add option to fix z-file layer initialization bug #1266
Conversation
Added a new runtime flag, LAYER_Z_INIT_IC_EXTRAP_BUG, to allow for the correction of a vertical indexing bug when initializing a layer-mode configuration from a Z-space temperature and salinity file with nominally unstable density profiles in the bottommost points in the z-space file. Also corrected some spelling errors in MOM_state_initialization.F90. By default, all solutions are bitwise identical, but there is a new entry in some MOM_parameter_doc files.
I assume this would have affected CM2G63L initial conditions? Might explain that initial bottom warming Toni asked us about... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conflict needs resolving as a result of ice_shelf PR.
Codecov Report
@@ Coverage Diff @@
## dev/gfdl #1266 +/- ##
============================================
- Coverage 45.78% 45.78% -0.01%
============================================
Files 225 225
Lines 71455 71458 +3
============================================
Hits 32714 32714
- Misses 38741 38744 +3
Continue to review full report at Codecov.
|
Added a new runtime flag, LAYER_Z_INIT_IC_EXTRAP_BUG, to allow for the
correction of a vertical indexing bug when initializing a layer-mode
configuration from a Z-space temperature and salinity file with nominally
unstable density profiles in the bottommost points in the z-space file. Also
corrected some spelling errors in MOM_state_initialization.F90. By default, all
solutions are bitwise identical, but there is a new entry in some
MOM_parameter_doc files.