Skip to content

Upcoming MOM6 PR changes defaults #17

@mathomp4

Description

@mathomp4

This is mainly to serve as a "warning" to @sinakhani as he looks to test mom-ocean#1670

In my testing of mom-ocean#1670 (to see if it builds, runs, etc.) I found that in order to get zero-diff to current GEOS coupled c12, I had to set in MOM_override:

#override USE_DIABATIC_TIME_BUG = False
#override EQN_OF_STATE = "WRIGHT"
#override USE_WRIGHT_2ND_DERIV_BUG = False
#override VISC_REM_BUG = True
#override VISC_REM_TIMESTEP_BUG = True
#override TIDES_ANSWER_DATE = 20230630
#override MASS_WEIGHT_IN_PRESSURE_GRADIENT_TOP = False
#override BETTER_BOUND_KH = True
#override BETTER_BOUND_AH = True
#override BACKSCATTER_UNDERBOUND = True
#override FRICTWORK_BUG = True
#override CFL_BASED_TRUNCATIONS = True
#override VISC_REM_BT_WEIGHT_BUG = True
#override LOTW_BBL_ANSWER_DATE = 20190101
#override NDIFF_ANSWER_DATE = 20240101

Note that this is in addition to the:

#override USE_HUYNH_STENCIL_BUG = True
#override EPBL_ANSWER_DATE = 20231231

we currently set which were needed for https://github.com/GEOS-ESM/MOM6/releases/tag/geos%2Fv3.2 for zero-diff.

I suppose the question for @sinakhani is: what to do? Perhaps it is time to accept non-zero-diff and just remove all these overrides? 🤷🏼

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions