-
Notifications
You must be signed in to change notification settings - Fork 121
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
Rename vx tasks so they follow METplus-tool based convention #619
Labels
enhancement
New feature or request
Comments
37 tasks
37 tasks
@michelleharrold @JeffBeck-NOAA @willmayfield @mkavulich Couple of questions:
Thanks. |
@gsketefian, I would prefer capitalized acronyms when possible for ease of comprehension, so long as it doesn't interfere with NCO requirements. |
MichaelLueken
pushed a commit
that referenced
this issue
Mar 1, 2023
…t tasks into two) (#618) 1. Rename verification tasks and corresponding j-jobs, ex-scripts, and log files as described in issue #619. 2. Separate combined METplus vx tasks for surface and upper air into separate tasks. This is so that there is only one call to a METplus tool per ROCOTO task and helps simplify the workflow and debugging. 3. Ensure that each vx task has a separate section in config_defaults.yaml with its own resource variables (WTIME_..., PPN_..., etc).
26 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
To avoid various sorts of file conflicts (e.g. multiple workflow tasks writing to the same output file), the eventual goal for the verification (vx) tasks in the ROCOTO workflow is for each task to only call one METplus tool (e.g.
GridStat
,PointStat
,EnsembleStat
, etc) and operate on one field or group of fields (see Issue #620 ). For clarity, we would like the task names along with the corresponding j-job, ex-script, and log file names to reflect this.Solution
In this issue, I propose that each item (task or file name) be renamed so that it contains the name of the METplus tool the task runs as well as the name of the field or group of fields on which it is run (e.g. 1-hour precip (APCP01h), reflectivity (REFC), etc).
I propose to rename the j-job scripts as follows (note that NCO requires that all j-job names be in upper case):
I propose to rename the ex-scripts as follows (note that NCO requires that all ex-script names be in lower case):
I propose to rename the METplus configuration files as follows (some aren't renamed):
Finally, I propose to rename the tasks and log file names for each of deterministic and ensemble verification as follows (e.g. for the 2019061500 cycle):
Deterministic Verification
Rename the ROCOTO tasks as follows:
Rename the corresponding log file for each task as follows:
Rename the corresponding METplus log files as follows:
Ensemble Verification
Rename the ROCOTO tasks as follows:
Rename the corresponding log file for each task as follows:
Rename the corresponding METplus log files as follows:
Acceptance Criteria (Definition of Done)
WE2E verification tests run without changing results.
Alternative Solutions (optional)
If you have other ideas for a naming convention, please suggest in the discussion below.
The text was updated successfully, but these errors were encountered: