-
Notifications
You must be signed in to change notification settings - Fork 17
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
update how UFS names restarts #109
update how UFS names restarts #109
Conversation
DeniseWorthen
commented
Feb 3, 2023
- write all restarts as YYYYMMDD.HHMMSS.MOM.resX
- includes stoch restarts
- write final restart with timestamp
- change nems=>ufs
* write all restarts as YYYYMMDD.HHMMSS.MOM.resX * includes stoch restarts * write final restart with timestamp * change nems=>ufs
edb8a4f
to
6c69e61
Compare
@DeniseWorthen let's work in the following orders: |
@jiandewang That all sounds fine. Thanks. |
@jiandewang We need approval before we start the UFS RT testing. |
@jiandewang We're ready for the MOM6 merge. Thanks. |
done |
* Fix non-standard white space Made widespread corrections to indentation and other white space issues to conform to the MOM6 standards, as documented in the white space section of the MOM6 style guide, at https://github.com/mom-ocean/MOM6/wiki/Code-style-guide. - MOM6 code uses a 2-point indent scheme. - There should be a space around all assignment (" = ") operators. - The names of optional arguments do not use whitespace, to differentiate them from assignments. - There is a space around the semicolons for stacked enddo statements. After this change, greping for '^ [a-zA-Z]', '^ [a-zA-Z]' or '^ [a-zA-Z]' does not find any lines in the MOM6 src or config_src/infra code. All answers and output are bitwise identical.