-
Notifications
You must be signed in to change notification settings - Fork 27
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
Bugfix/nfcens wafs #391
Bugfix/nfcens wafs #391
Conversation
I have cloned your fork and checked out branch |
The wafs changes look good. I ran wafs processing. I grepped on
The WARNING was removed is no longer part of the if test. ✔️ stats processing completed successfully. |
The AQM change looks fine and align with NCO SPA suggestion. I do not believe I can test it since our dev driver scripts override COMIN and COMOUT default settings. |
dev/drivers/scripts/plots/nfcens/jevs_nfcens_wave_grid2obs_plots.sh
Outdated
Show resolved
Hide resolved
The ecf changes can't be tested. But @SamiraArdani-NOAA checked that the equivalent dev driver scripts had the appropriate #PBS -N naming convention. prep and stats looked good already. plots needed updating. I ran nfcens plots. The job is now the proper name, as born out in the name of the logfile: plots processing completed successfully. ✔️ |
I was trying to find the See lines 99-102 of
I think the following line needs to be put after each call to run the USHevs scripts: Do you agree? If so, I think we need to do this as something that was missed in the EE2 checklist. |
I ran nfcens plots w/ SENDDBN set up for FAKE dbn_alert. The new for loop works correctly for the FAKE dbn_alert set up. ✔️ |
The re-run of nfcens plotting to include err_chk worked correctly. From the logfile (
The plots tar files are generated and match closely with emc.vpppg. |
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.
All tests yielded expected results. I approve this PR for merge.
@AliciaBentley-NOAA, @PerryShafran-NOAA , I recommend this PR for merge. However, I will not merge it yet, allowing the chance for your review. |
@SamiraArdani-NOAA @ShelleyMelchior-NOAA I have looked over this PR and think it is good to go! Thank you! |
Pull Request Testing
Describe testing already performed for this Pull Request:
clone my EVS repository in your local, then find the driver scripts located at: EVS/dev/drivers/scripts
Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
for NFCENS:
To run prep: dev/drivers/scripts/prep/nfcens/jevs_nfcens_wave_grid2obs_prep.sh
To run stats: dev/driver/scripts/stats/nfcens/jevs_nfcens_wave_grid2obs_stats.sh
To run plots: dev/driver/scripts/plots/nfcens/jevs_nfcens_wave_grid2obs_plots.sh
for WAFS:
To run stats: dev/driver/scripts/stats/wafs/jevs_wafs_atmos_stats.sh
Has the code been checked to ensure that no errors occur during the execution? [Yes]
Do these updates/additions include sufficient testing updates? [Yes or No]
Please complete this pull request review by [Fill in date].
Pull Request Checklist
Review the source issue metadata (required labels, projects, and milestone).
Complete the PR description above.
Ensure the PR title matches the feature branch name.
Check the following:
Instructions provided on how to run
Developer's name is replaced by ${user} where necessary throughout the code
Check that the ecf file has all the proper definitions of variables
Check that the jobs file has all the proper settings of COMIN and COMOUT and other input variables
Check to see that the output directory structure is followed
Be sure that you are not using MET utilities outside the METplus wrapper structure
After submitting the PR, select Development issue with the original issue number.
After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
Close the linked issue.