-
Notifications
You must be signed in to change notification settings - Fork 88
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
Convert verification to solely use METplus configuration files (feature/ens_design_RRFS) #695
Merged
JeffBeck-NOAA
merged 7 commits into
ufs-community:develop
from
michelleharrold:feature/ens_design_RRFS
Mar 22, 2022
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1439830
Create feature/ens_design_RRFS branch and move original MET and METpl…
michelleharrold 7d89b94
Updated METplus conf files to remove dependency on project-based MET …
michelleharrold 49a9922
Sync with develop.
michelleharrold bc2bf09
Updates to METplus conf files and run scripts for transitioning away …
michelleharrold ed84f7d
Merge remote-tracking branch 'upstream/develop' into feature/ens_desi…
michelleharrold 7d3d358
Removed MET configuration files; changed envar ACCUM back to acc in s…
michelleharrold 26b61ec
Removed old METplus conf files and removed OBS PROB info from Grid-St…
michelleharrold File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@michelleharrold I know we discussed error checking in a meeting before, but I wanted to understand the details (which I've forgotten) of why we don't want to use error-checking here. By error-checking, I mean adding to this call a
print_err_msg_exit
statement if it fails, e.g.I and other reviewers are now encouraging use of error-checking so the ex-script doesn't exit with a false success status. But for some of the verification ex-scripts, I remember you and/or @jwolff-ncar said we should not have the script fail even if the return code from METplus is nonzero. Can you explain again the reason for that? Also, are some of the other vx sripts well-behaved in the sense that we can do error-checking with them? Thanks.
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 - good question. I agree not having the error checking for the verification can cause some frustration when a job fails but is called successful by the workflow. @jwolff-ncar and I decided not to implement error checking for the vx jobs because we run all the forecast lead times through the verification in one job, and there are circumstances where some observations may not present (which is okay). This would cause the verification job to error out prematurely if a forecast/obs combo was not present. I am definitely open to brainstorming ways around this because having more robust error checking would certainly make testing and monitoring easier.