Skip to content

Enhance the MET statistics tools to read and process range/azimuth data from the TC-RMW and RMW-Analysis tools #3064

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the New Feature

As discussed during the HAFS project meeting on Jan 27, 2025 (see meeting notes), the MET statistics tools should be enhanced to read the range/azimuth grid output written by the TC-RMW and RMW-Analysis tools.

This requires adding range/azimuth as a new "projection type" to be supported. Generally, we could treat range as the "x" dimension and azimuth as the "y" dimension. The goals are:

  • enable Grid-Stat to compare R-A data on the same grid
  • enable Point-Stat to interpolate points to the R-A grid

Acceptance Testing

Development tasks:

  • Enhance the vx_grid and vx_data2d_nc_met libraries to support the TcrmwGrid directly. DONE as of 2/27/25.
  • Fix some SonarQube code smells in these libraries to drive the overall number down.
  • Consider renaming TcrmwGrid as RngAziGrid since its a range/azimuth grid that may or may not be defined relative to the radius of maximum winds.
  • Confirm that regridding from lat/lon to range/azimuth and then back to lat/lon produces sane results. DONE (see this comment) as of 2/27/25.
  • Add unit test for plot_data_plane (without plotting map data since that doesn't work well).
  • Add unit test for grid_stat that uses auto-regridding (e.g. to_grid = FCST) to verify a range/azimuth forecast.
  • Add unit test for point_stat

Migrated additional work to a new #3096 issue.

Time Estimate

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

Sub-Issues

Consider breaking the new feature down into sub-issues.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2783604 2025 NOAA R2O HAFS

Define the Metadata

Assignee

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

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a MET-X.Y.Z version, select the MET-X.Y.Z Development project

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 Development issue
    Select: Milestone as the next official version
    Select: MET-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions