Skip to content

Enhance METviewer to plot SS_INDEX from the new SSIDX STAT line type. #327

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

The pull request dtcenter/MET#1892 for issue dtcenter/MET#1788 adds a new STAT line type that is created by Stat-Analysis. The SSIDX line type is documented in the Stat-Analysis MET User's Guide chapter on the feature branch. After that PR is approved/merged, please see the develop branch instead.

The SS_INDEX column contains the key statistic. However, there is no way to aggregate this across multiple cases. Instead, we'd just plot this using the summary method (e.g. mean or median). We should also be able to plot it as a boxplot. @michelleharrold and @hertneky can provide additional data for testing and validate the resulting plots.

The columns for FCST_MODEL, REF_MODEL, N_INIT, N_TERM, and N_VLD are purely information and do not need to be plotted.

Please ask @JohnHalleyGotway any questions about how to handle the data.

A sample data file is provided here:
ssidx_sample.tar.gz

One file with FCST_VAR = OBS_VAR = GO_INDEX.
One file with FCST_VAR = OBS_VAR = SS_INDEX.
Another option is CBS_INDEX but no example is provided here.
Note that strings in the header columns can get long. For example, MODEL = fcst model name, reference model name. By default, when multiple strings are encountered in the input, their unique values are written to the output as a comma-separated list.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.
No sub-issues needed.

Relevant Deadlines

To be included in the coordinated METplus version 4.1.0 release.

Funding Source

Funded via the DTC AF project (2712221). See @michelleharrold.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: Tatiana
  • Select scientist(s) or no scientist required: no scientist needed

Labels

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

Projects and Milestone

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

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement 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.
  • 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 Linked 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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions