Skip to content

Add Scatter Index to the CNT line type. #1843

@j-opatz

Description

@j-opatz

Describe the New Feature

As work continues in the marine and coastal verification area, the variable Scatter Index has been used more and more in the user Python code. As MET is already producing 99% of the variables calculated for marine and coastal verification, the addition of Scatter Index seems appropriate.

Scatter Index (SI) is calculated by

SI = 100.0*[ (avg((fcst-obs)^2)^0.5) - (avg(fcst-obs)^2) ] / avg(obs)

Acceptance Testing

Input data types and formats vary, but this should be first tested against ice cover data (netCDF4 format). A sample forecast and obs file are on Kiowa:

Fcst file: /d1/projects/MET/MET_test_data/ice_cover_ScatterIndex/20210305_rtofs_glo_2ds_n024_ice.nc
Obs file: /d1/projects/MET/MET_test_data/ice_cover_ScatterIndex/2021030512_UKMO_L4.nc
Python embedding: /d1/projects/MET/MET_test_data/ice_cover_ScatterIndex/ice_code_hera.py

Python script requires the following arguments to run:
Fcst_file Obs_file hemisphere file_indicator

Depending on the file indicator, the script will either pass the forecast field or observation field in memory for MET to utilize. Success of this issue is the return of the Scatter Index by MET in the CNT line type.

Time Estimate

Need estimate from engineer

Sub-Issues

Consider breaking the new feature down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

None

Funding Source

2788881

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

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.

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

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions