-
Notifications
You must be signed in to change notification settings - Fork 120
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
[develop] Reorganize verification tasks (rename tasks and files; split tasks into two) #618
[develop] Reorganize verification tasks (rename tasks and files; split tasks into two) #618
Conversation
… for Hera and modify run_WE2E_tests.py so that this location is obtained in a platform-independent way.
…ation of staged forecast files; modify code to correctly set VX_FCST_INPUT_BASEDIR in WE2E experiments.
…o that it is exactly consistent with the one used in run_WE2E_tests.py.
…t each task has its own values for NNODES, PPN, MEM, WTIME, MAXTRIES.
…t the DTC team wants.
…ks; Add ensemble member name (if running ensemble vx) to the names of the vx tasks in the ROCOTO xml.
…t convention; fix bugs in the two ex-scripts exregional_run_met_pointstat_ens[mean|prob].sh that call METplus twice.
@MichaelLueken @gspetro I just created Issue #630 for updating the vx documentation. |
Thank you very much, @gsketefian, for creating issue #630! |
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.
@gsketefian Thanks for making the changes, approving now.
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.
@gsketefian Thank you very much for addressing @danielabdi-noaa's concerns! Following the renaming of the ex- scripts to be lower case, per NCO guidelines, these changes look good to me. I will go ahead and approve these changes now.
@danielabdi-noaa @MichaelLueken Thanks for the approvals! I am retesting now on Hera to make sure all the fundamental tests pass. Also, I'd like to wait until tomorrow (morning, let's say) to get some feedback on Issue #619 (so far I haven't gotten any) before proceeding further. Assuming my tests pass and there is no or minor feedback on #619 by tomorrow, could @MichaelLueken launch the automated tests then? Thanks. |
@gsketefian After I gave my approval, I went ahead and submitted the Jenkins tests. If any additional changes are pushed to your |
@MichaelLueken Ok, thanks for letting me know. One question -- does the automated testing system first merge |
@gsketefian Yes, the first thing that the automated Jenkins tests do is merge the latest develop branch into the branch associated with the PR. So, no worries with that. If discussion from issue #619 leads to additional modifications, then the tests will need to be rerun, but you don't need to worry about the PR being up-to-date with develop until just before merging. |
Machine: hera |
@MichaelLueken Ok, thanks! |
@MichaelLueken All the fundamental tests I ran locally on Hera passed. |
…leStat for point-obs, ensure that METplus is called only once and for the correct variable (instead of for both SFC and UPA).
@MichaelLueken FYI unfortunately I found bugs in a couple of the vx ex-scripts. They only affect verification. I fixed them and reran the three vx tests ( |
@MichaelLueken A couple of people are going to take a look at Issue #619 by COB today, so could you hold off on rerunning the automated tests until then? I can let you know when the PR is ready for the re-testing. Thanks! |
@gsketefian I'm on PTO today, so if it is okay with you, I will resubmit the automated tests first thing tomorrow morning. They should run fast enough so that this work can be merged early in the day. Thanks! |
@MichaelLueken Yes, that sounds good. |
@gsketefian I have just resubmitted the automated Jenkins tests. Are there any other changes that you will be making, or will these changes be ready to be merged once the tests successfully pass? |
@MichaelLueken No more changes, so please go ahead and merge it if the tests pass. Thanks! |
@gsketefian Great! I will move forward with these changes once they pass the automated tests. |
DESCRIPTION OF CHANGES:
config_defaults.yaml
with its own resource variables (WTIME_...
,PPN_...
, etc).Type of change
TESTS CONDUCTED:
I have run the following fundamental WE2E tests on Hera with the Intel compiler. All were successful. Also, all task names and log file names are as described in Issue #619.
DOCUMENTATION:
This PR requires changes to the documentation. However, I have not yet made changes to the documentation. There will likely be further changes required to the documentation due to several upcoming vx PRs. I prefer to make all the documentation changes in one go after all the vx PRs have been merged.
ISSUE:
This resolves Issue #619.
CHECKLIST
LABELS (optional):
A Code Manager needs to add the following labels to this PR:
CONTRIBUTORS (optional):
@michelleharrold @JeffBeck-NOAA @willmayfield @mkavulich