Skip to content

Add TC-Gen configuration file options for init_inc, init_exc, and basin_mask. #1626

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

We've been revamping the TC-Gen tool in several ways for the MET 10.0.0 release. The updates include an overhaul to the matching logic, a new gridded NetCDF output file, and a new genesis matched pair (GENMPR) output line type. During the development process, we realized that adding 3 more configuration file options for TC-Gen would be very useful:

init_inc = [ ]; // Strings in YYYYMMDD[_HH[MMSS]] format
init_exc = [ ]; // Strings in YYYYMMDD[_HH[MMSS]] format
basin_mask = [ ]; // Strings with basin_name values

The first 2 options explicitly specify which model initialization times should be included or excluded from the processing logic. If the inclusion list is non-empty, only those times explicitly listed will be included. If the exclusion list is non-empty, any initialization times listed will be excluded.
The basin_mask entry is an array of strings of basin name values. They should match the basin_name variable values defined in met/data/tc_data/basin_global_tenth_degree.nc. If multiple basins are listed, their union will be used. If both vx_mask and basin_mask are specified, their intersection will be used.

Time Estimate

2 days.

Sub-Issues

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

Relevant Deadlines

None.

Funding Source

7790901

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: John HG
  • Select scientist(s) or no scientist required: Kathryn

Labels

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

Projects and Milestone

  • Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
  • Select milestone to next major version milestone 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), Project(s), Milestone, and Linked issues
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Labels

requestor: NCARNational Center for Atmospheric Researchtype: enhancementImprove something that it is currently doing

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions