New Use Case: Scatterometer wind data

[j-opatz]

Describe the New Use Case

To start OPC's verification process in METplus, the priority has been for ASCAT winds. While we concurrently develop a use case for the altimeter wave heights in #1482, focus will remain on this use case.

OPC has warned in previous meetings that scatterometer winds can have many dead ends, and this use case will need to utilize a script from Frances to get the ASCAT data in a MET-accessible format. Those files are attached.
convert_altimeter_hdf5_to_ascii.py.txt
get_sentinel_data.pl.txt
MGDRlite2ascii.py.txt

Use Case Name and Category

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

This use case can reside in the Marine_and_Cryosphere category, as it deals with winds over oceans.

Input Data

Fcst source: GDAS 10m winds
Obs source: Scatterometer data (need size, type) link to webpage that showcases the data. Obs data will require preprocessing via Python script.

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

List relevant project deadlines here or state 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.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

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.

[j-opatz]

The following is new guidance from OPC with regards to the verification process:

start with a PointStat verification case for the ASCAT winds versus the GFS forecast winds. We're looking to verify the ocean winds over these two basins (separately):
N. Pac: Equator to 67N, and 180 to the coast of S. America
N. Atl: Equator to 67N, and from the coast to 35W

As such, the new name for this use case will be

PointStat_fcstGFS_obsASCAT_satelliteWinds

And will utilize the masking option for the two regions indicated. Further, the WATERSF message type will be changed to add SATWND and WDSATR, which will allow the land_mask dictionary to also be used for only water gridpoints.

[j-opatz]

While the Atlantic verification area should be straightforward via a self-created poly file, the N. Pacific region indicated will require the creation of a new mask. This mask can be made by creating the borders as described by EMC, then subtracting out the CAR.poly and GLF.poly files. The land that is left will be ignored by the use of the land_mask dictionary.