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.
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
Nodal modulation #725
base: dev/gfdl
Are you sure you want to change the base?
Nodal modulation #725
Changes from all commits
211cab5
405213a
7a64956
59211b6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
These 4 parameters would need to have default arguments if they are to be properly logged in the correct MOM_parameter_doc files.
It may be that we need to add support for a default array of integers to
get_param_integer_array()
, analogously to what we recently added forget_param_real_array()
.If we were to get community buy-in on the idea of moving to use the non-OBC parameters for these tidal parameters, we might deal with this by storing the values set above, adding
do_not_log=.true.
to theseget_param()
calls, and then directly adding a warning if variables likeOBC_TIDE_ADD_EQ_PHASE
are set differently fromTIDE_USE_EQ_PHASE
. I will try to raise this at this evening's MOM6 dev call, and then provide further guidance depending on how that conversation goes.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.
The default arguments for these parameters are already set by
TIDE_USE_EQ_PHASE
,TIDE_ADD_NODAL
,TIDE_REF_DATE
andTIDE_NODAL_REF_DATE
, so they will always be properly logged. I've tested this.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.
It would be more complicated if we want to add a warning if the old variables (e.g.,
OBC_TIDE_ADD_EQ_PHASE
) are set differently from the new ones (e.g.,TIDE_USE_EQ_PHASE
), but I don't think this should happen if both astronomical and OBC tidal forcings are turned on (and this is the reason for obsoleting the old variables). I did not add ado_not_log
option because these parameters were used by OBC tidal forcing only, and I think it would be easier to just remind everyone who uses OBC tidal forcing that these parameters will be obsolete.