-
Notifications
You must be signed in to change notification settings - Fork 249
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
flexible output hour for history files and and update MOM6 to GFDL 20210723 #691
flexible output hour for history files and and update MOM6 to GFDL 20210723 #691
Conversation
Fix for new ECFlow requirements on hera
Machine: hera |
Looks like the BL tag was added by accident. Colors are too close I guess. Fixed that. |
Machine: jet |
Both job failures on jet were |
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.
Changes look good. I do think we need good documentation to allow users to take advantage of the feature.
@@ -0,0 +1,37 @@ | |||
total_member: @[ENS_NUM] |
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.
Not used anymore. Can be removed in one of the future PRs.
I reran the two tests, both passed on jet. Compile 001 elapsed time 259 seconds. -DAPP=NG-GODAS-NEMSDATM -DMPI=ON -DCMAKE_BUILD_TYPE=Release -DSIMDMULTIARCH=ON -DMOM6SOLO=ON baseline dir = /lfs4/HFIP/h-nems/emc.nemspara/RT/NEMSfv3gfs/develop-20210722/INTEL/datm_control_gefs 0: The total amount of wall time = 118.220097 baseline dir = /lfs4/HFIP/h-nems/emc.nemspara/RT/NEMSfv3gfs/develop-20210722/INTEL/datm_cdeps_bulk_gefs 0: The total amount of wall time = 191.770578 |
@@ -57,7 +61,7 @@ export SYEAR=2021 | |||
export SMONTH=03 | |||
export SDAY=22 | |||
export SHOUR=06 | |||
export RESTART_INTERVAL=12 | |||
export RESTART_INTERVAL="12 -1" |
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.
I didn't read the code carefully, it seems. Does -1
mean at the end of the forecast run?
Is the second element is "-1", it means the first element is a restart
frequency.
RESTART_INTERVAL="12" means writing out restart at fh=12.
…On Tue, Jul 27, 2021 at 10:09 AM Dom Heinzeller ***@***.***> wrote:
***@***.**** approved this pull request.
------------------------------
In tests/tests/control
<#691 (comment)>
:
> @@ -57,7 +61,7 @@ export SYEAR=2021
export SMONTH=03
export SDAY=22
export SHOUR=06
-export RESTART_INTERVAL=12
+export RESTART_INTERVAL="12 -1"
I didn't read the code carefully, it seems. Does -1 mean at the end of
the forecast run?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#691 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TOVG23TQ6FERFD74S3TZ24XLANCNFSM5ANZIJOA>
.
|
PR Checklist
Ths PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR
are specified below.
[] If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
Instructions: All subsequent sections of text should be filled in as appropriate.
The information provided below allows the code managers to understand the changes relevant to this PR, whether those changes are in the ufs-weather-model repository or in a subcomponent repository. Ufs-weather-model code managers will use the information provided to add any applicable labels, assign reviewers and place it in the Commit Queue. Once the PR is in the Commit Queue, it is the PR owner's responsiblity to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
In this PR, model is allowed to output history files at flexible (random) forecast hours.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
Dependencies
If testing this branch requires non-default branches in other repositories, list them. Those branches should have matching names (ideally).