-
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_fhr24snow #460
bugfix_fhr24snow #460
Conversation
Hi @malloryprow ! I have cloned your fork and checked out branch |
Sounds good! |
The runs are underway! |
I got some missing data emails
This would make sense since global_det atmos prep doens't run until 1815Z. |
OH ok! Let me run again w/ an earlier date. I forgot about that. |
I forgot too! |
I got the missing emails as well as was about to write in! Thanks, all! An earlier date sounds good! |
Re-runs are underway w/ VDATE=20240327.
|
No missing file emails so far! |
Everything looks good! |
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.
The code change yields the expected results.
Pull Request Testing
Set-up
✔️ global_det atmos stat
Has the code been checked to ensure that no errors occur during the execution? Yes
Do these updates/additions include sufficient testing updates? Yes
Please complete this pull request review by 4/28/2024.
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.