New use case: TCDiag Single Init Use Case

[jvigh]

Describe the New Feature

The goal of this use case is to provide a use case to NHC that illustrates an end-to-end workflow that runs the TCDiag suite for a single initialization and accomplishes the following steps:

• Call the TC-Diag tool to generate diagnostics output for one initialization
• Load the resulting data into TC-Pairs to generate TCMPR output
• Call the TCMPR plotter on the TCMPR output
  • Call METdataio reformatter to reformat output from TCDiag tool
  • Time series of diagnostic values for forecasts (a real-time type of plot for forecasters)
    (Similar to what CIRA is producing. Representing what is in the current diagnostic file.)
  • Additional brainstorming: Another option could be short-term retrospectives (e.g., last 5 runs, or the storm history).
    • Recommend that when using this use case, decide whether this enhancement should be done as part of this use case or a new use case. (NOTE: Probably would not be an end-to-end use case, but rather use existing data).
• Call the Skew-T diagram using the CIRA ASCII data

NOTE: This is not the basic use case (e.g., TCDiag-only use case that is tool-specific). Rather, this is the elaborated use case that will go under the model applications under the TC and Extra TC section.

NOTE: Jon Martinez is working on setting up a verification workflow with METplus that mimics the NHC verification workflow.
So in the future, there may be a workflow to pattern after. This may require some separate meetings with Jon Martinez, Kathryn Newman, Kate, etc.

Use Case Name and Category

This use case will live in the TCDiag-Realtime repository.

Input Data

List input data types and sources.
Provide a total input file size, keeping necessary data to a minimum.

Time Estimate

3 days

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

Goal: December (subject to v12.0.0 release schedule).

Funding Source

TCDiag Project (2770043)

Define the Metadata

Assignee

• Engineer: George McCabe and Minna Win-Gildenmeister
• Scientist: Jonathan Vigh

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus
• MET
• METdataio
  - [ ] Support reformatting the TCDIAG line type written by the TC-Pairs tool  METdataio#240
• METviewer
• METexpress
• METcalcpy
• METplotpy
  • Enhance TCMPR plotter to read TCDiag lines and filter by one column and plot another column METplotpy#342
  • Create documentation and testing for TCMPR plotting code  METplotpy#383

New Feature Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.