New Use Case: Land-Atmosphere verification with Scorecards and Bowen Ratio

[DanielAdriaansen]

Describe the New Use Case

This use case will use Python embedding to read Latent and Sensible heat flux fields from NY State Mesonet observations and GFS/HR* model forecasts to compute the Bowen Ratio. The Bowen Ratio is defined as the ratio of the sensible heat flux (numerator) to the latent heat flux (denominator). Additional standard forecast variables will be included in the point_stat configuration. Forecasts out to 5 days (120h) every 24h at 00 UTC will be processed for two versions of the GFS model- HR1 and HR2.

Use Case Name and Category

model_applications/land/PointStat_fcstUFS_obsNYSM_BowenRatio

Input Data

NY State Mesonet observation data containing standard and flux sites
GFS/UFS Model Forecasts for two versions to compare models

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here

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.

• 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

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

Milestone and Projects

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

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, 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.
• Add any new Python packages to the METplus Components Python Requirements table.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• 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: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
• 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.

[DanielAdriaansen]

@anewman89 here is the stub issue for the scorecard work @briannen is doing, to document creating a new use case to demonstrate that. I've added it to the Land Project board as "in progress" but we will need to fill out more information. Can you do that? Or, we can do it together at the next land meeting on 4/28. Thanks.

[anewman89]

@DanielAdriaansen Since we don't have a cycle defined - we can plan for 6.2, let's try to define this use case at one of the upcoming land meetings. As we discussed yesterday, the 6.1 release is top priority, so perhaps we can do this in July?