Skip to content

New Use Case: Buoy wave heights to wave watch model III output via GFSv16 #1482

@j-opatz

Description

@j-opatz

Describe the New Use Case

This use case will look at Altimeter wave heights, comparing their output to the wave watch model. This is timely, as the next wave watch model upgrade is integrated in the GEFS and GFS.

Use Case Name and Category

Use case name is unknown for now, but should follow:
PointStat_fcstGFS_obsNDBC_WaveHeight

Note that WaveWatch output, the model of focus, is included in GFS and GEFS.

This use case can reside in the Marine_and_Cryosphere category, as it deals with wave heights.

Input Data

Fcst source: wave watch model data (need size, type)
Obs source: NDBC buoy Altimeter data (ASCII, ranging in size from 600KB to 2.5KB)

Work to ingest the Altimeter wave height data was previously accomplished by Jake Campbell, who graciously provided his scripts to us for use. This work included taking the above data sources and combining them into a conglomerate netCDF, which this use case will be provided.

George pulled copies onto Seneca, under: /d1/projects/METplus/METplus_Data/development/WW3_data.

Acceptance Testing

Success of this use case will be two things: a successful run through METplus with the datasets listed above, and meaningful output for OPC that their center can utilize.

As use case develops, provide a run time here

Time Estimate

1-3 days
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the new feature down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

None

Funding Source

Define the source of funding and account keys here or state NONE.

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)
  • Select privacy

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 Use Case 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 your changes. Merge branch into develop.
  • Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions