Skip to content
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

New Use Case: TCDiag Seasonal Analysis Use Case #2360

Open
6 of 40 tasks
jvigh opened this issue Sep 20, 2023 · 0 comments
Open
6 of 40 tasks

New Use Case: TCDiag Seasonal Analysis Use Case #2360

jvigh opened this issue Sep 20, 2023 · 0 comments

Comments

@jvigh
Copy link
Contributor

jvigh commented Sep 20, 2023

Describe the New Use Case

The goal of this use case is to provide a use case for EMC that illustrates an end-to-end workflow that analyzes pre-existing real-time diagnostic runs for an an entire season accomplishes the following steps:

  • Run TCPairs to generated matched pair output for a season's worth of diagnostics output
  • Stratify the diagnostic values by intensity
  • Stratify the intensity performance conditioned by errors (e.g., track) or by a thresholded diagnostic value (e.g., low vertical shear)
  • Generate summary plots for a retrospective evaluation of model performance:
    • spatial plot of the stratified errors
    • display the distributions of diagnostics by storm, by season, by model
    • performance diagram (stratifying by diagnostic value of shear low/med/high or for different models)
    • scatter diagram (?)

NOTE: This is an elaborated use case that will be housed in the TCDiag-Realtime repo.

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.

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here

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: Early 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)
  • Select privacy

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.

New Use Case 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 your changes. Merge branch into develop.
  • Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
  • Delete your fork or branch.
  • Close this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment