-
Notifications
You must be signed in to change notification settings - Fork 7
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
Consistent formatting of MOM_input, matching MOM_parameter_doc.short #200
Comments
Sounds good to me |
@minghangli-uni will this be an annoying disruption to your parameter-tuning workflow? It could make for messy merges of parameter changes. |
Hi @aekiss , my understanding is that the proposed consistent formatting is only applied once for each repo. Following tests will then use this established format, is that correct? The current technique for tuning parameters is through MOM_override, hence it is not necessarily to modify MOM_input, unless we want to merge the override parameters into MOM_input. But it is still good to have an ordered MOM_input file. I believe this script COSIMA/om3-utils#17 can do the match properly. One issue might exist if we add a new parameter, such as |
The position of the 'new' parameter and its associated comment can be fixed by aligning MOM_input with MOM_parameter_doc.all, ensuring that they are properly positioned. |
Yep, the idea is to establish a new standard way of arranging these files. The content would simply be copied from
|
We should be able to enforce this through a "QA" check in the repro CI, I think |
After |
Looks good to me. Thanks both! |
We need a consistent
MOM_input
format so we can easily compare across branches usinggit diff
and also avoid merge conflicts when cherry-picking across branches.I propose we use an order and format that matches
MOM_parameter_doc.short
so it will also be easy to see whether anything inMOM_input
is redundant (e.g. a default value) by comparingMOM_input
toMOM_parameter_doc.short
. Note that this differs from the previous layout we inherited from CESM - e.g. see here. I've already done this forMOM6-CICE6/1deg_jra55do_ryf
and propose doing this for our other branches.Also note that there will need to be some hand-additions of the parameters not included in
MOM_parameter_doc.short
- see #121Any objections?
The text was updated successfully, but these errors were encountered: