-
Notifications
You must be signed in to change notification settings - Fork 6
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
[0.25deg config] MINIMUM_DEPTH & MASKING_DEPTH in MOM_grid_init #177
Comments
Thanks for the detailed description @minghangli-uni. To be pedantic, the min depth in the OM2 0.25° 50-level grid is actually 11.805749893188477 m - will that matter? If this needs to match exactly, it seems like we should have an automatic way to set |
Thank you for pointing this out @aekiss. As long as |
Yes, I was just about to post that :-) So when we change to 75 levels we'll need to adjust |
Actually, it would be simpler to set
and set the minimum depth when we generate |
Yes, I agree. Setting Bur it appears that if if (mask_depth == -9999.*US%m_to_Z) mask_depth = min_depth Since the default value of |
That would be even simpler, so I'm tempted to omit both parameters from |
Sounds good. I'll update the PR and include a note about the modifications. |
ACCESS-NRI/access-om3-configs#78 is merged. |
MINIMUM_DEPTH
is a need-to-change parameter that was discussed in namelist discussion.However instead of setting it to zero, it is prefered to to adjust another parameter,
MASKING_DEPTH
to zero, and setMINIMUM_DEPTH
to the minimum value defined bytopog.nc
, here is 11.8m.When only
MINIMUM_DEPTH
is set andMASKING_DEPTH
remains at its default value (-9999), the depth is calculated as ,The above calculation using
0.5*min_depth
is considered obscure according to inline comments. On the other hand, settingMASKING_DEPTH
is encouraged.MINIMUM_DEPTH
is strictly to be larger than zero, whileMASKING_DEPTH
can be negative to enable negative depths and to enable for example flooding. SettingMASKING_DEPTH
is more robust and will be adjusted as follows:The text was updated successfully, but these errors were encountered: