-
Notifications
You must be signed in to change notification settings - Fork 258
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
Add valid time to the 6 tile cubed sphere grid history files #1265
Conversation
By default the calendar type will be 'gregorian'
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.
Thanks for updating the code, the changes look good to me.
I had to revert commit that changes the calendar type from 'julian' to 'gregorian' because some restart (warm start) tests have calendar type set to julian in the input data:
Changing calendar will require new input data directory. |
@DusanJovic-NOAA Brian wants a bit more time with AQM PR. Can we start working on this PR to create new BL? |
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
Automated RT Failure Notification |
WCOSS_Dell_P3 on baseline creation: + echo 'Test cpld_debug_noaero_p8 007 failed in run_test failed '
|
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
Automated RT Failure Notification |
@BrianCurtis-NOAA we need to copy over two BL files on jet. @DeniseWorthen all test passed. You can leave final comments and approve the PR. |
@DusanJovic-NOAA we are ready to merge fv3atm PR. |
@jkbk2004 What did you mean when you told Brian "we need to copy over two BL files on jet"? |
I recreated two BL files on jet (control_ras rrfs_v1beta) and passed ok now. |
Everything ready to merge the fv3atm PR and update pointers. |
@jkbk2004 So the initial baselines for those two tests were not reproducible when we first ran the verification RT? Do we know why? |
fv_core.res.tile4.nc ............ALT CHECK......NOT OK ? |
nccmp tells some of variables do not exist in those initial BL files. Somehow jet got trouble to correctly finish up writing out files. |
@DeniseWorthen can we merge in Dusan's fv3atm PR? we need one more approval there. |
Ready for merge. |
PR Checklist
This 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.
Results for one or more of the regression tests change and the reasons for the changes are understood and explained below.
New or updated input data is required by this PR. If checked, please work with the code managers to update input data sets on all platforms.
Description
Add 'time_iso' variable to cubed sphere grid output when ESMF write routines are used. This variable has already been added to the parallel version of the netcdf write routine.
This PR includes changes from NOAA-EMC/fv3atm#515
New regression test has been added that outputs history files with all 6 cubed sphere tiles in a single file.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues must always be created before starting work on a PR branch!)
Testing
How were these changes tested? Yes.
What compilers / HPCs was it tested with? Intel. Hera
Are the changes covered by regression tests? Yes.
Have the ufs-weather-model regression test been run? On what platform?
Will the code updates change regression test baseline? Yes. New netcdf variable has been added to the history files.
Dependencies
If testing this branch requires non-default branches in other repositories, list them. Those branches should have matching names (ideally).
Do PRs in upstream repositories need to be merged first? Yes.
If so add the "waiting for other repos" label and list the upstream PRs