Skip to content

Add gridded output fields from tc_gen in NetCDF format #1430

@DanielAdriaansen

Description

@DanielAdriaansen

Describe the Enhancement

TC genesis can be summarized in various ways, including the computation of the seasonal-to-sub-seasonal (S2S) metrics Track Density Function (TDF) and Genesis Density Function (GDF). To compute these metrics, it would be useful to have the following information from tc_gen written to a gridded (see NOTE1) NetCDF output file:

  1. Total count of observed genesis events
  2. Total count of unique forecast genesis events (see NOTE2)
  3. Total count of genesis hits
  4. Total count of genesis misses
  5. Total count of genesis false alarms
  6. Total count of forecast track points (see NOTE3)
  7. Total count of observed track points (see NOTE3)

NOTE1: It would be preferable to have a user configurable global grid to produce output on.

NOTE2: In order to not "double count" forecast genesis events (i.e. only include unique forecast genesis events), care will need to be taken to consider whether there are multiple forecasts of genesis at the same location (grid cell). For example, a model run a 00, 06, 12, and 18 UTC each day could produce 4 forecasts valid at 12 UTC two days in advance. The lead times from these forecasts would be 60, 54, 48, and 42. If all of those forecasts produced a genesis event at the same location (grid cell) and same valid time then these should only be counted as one genesis forecast and not 4.

NOTE3: It would be useful to include a user configurable boolean flag/option in the tc_gen config file to include track points before or after the genesis point in both the forecast and observed tracks. Something like INCLUDE_TRACK_BEFORE_GENESIS, with the default set to FALSE.

Time Estimate

Estimate the amount of work required here.
Approximately 1-2 days.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

  • Add support for user configurable global grid
  • Add support for writing NetCDF output file
  • Add support for keeping track of requested output fields
  • Add support for duplicate forecast genesis event ID and removal
  • Add user configuration to include track points before genesis or only after genesis

Relevant Deadlines

NONE

Funding Source

Split: 7790971, 2785051

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: John Halley-Gotway
  • Select scientist(s) or no scientist required: Dan Adriaansen

Labels

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

Projects and Milestone

  • Review projects and select relevant Repository and Organization ones
  • Select milestone

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.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • 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>
  • 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