New Use Case: International Soil Moisture Network (ISMN)

[anewman89]

Describe the Enhancement

The capability to read in International Soil Moisture Network (ISMN) formatted ASCII files was recently implemented into the MET ASCII2NC tool.

We need to develop a use case that can demonstrate the use of the ISMN data ingest in ASCII2NC through an example model forecast verification.

We could develop a use case that reads soil temperature and moisture from ISMN data and verifies NOAA UFS output from sample GFS data, specifically the HR3 data available on NCAR HPC which is a prototype configuration for GFSv17, using the MET pointstat tool. It could be good to include quick-look plotting capabilities of the pointstat matched pair output as well, either spatially or as a scatter plot of model versus obs, or model error versus model value.

Use Case Name and Category

Model soil moisture and temperature verification using ISMN data
This should be in the Land-surface category

Input Data

UFS GFS prototype model data focusing on soil moisture and temperature output
ISMN data focused on CONUS

Acceptance Testing

Verify conversion of ISMN data using ASCII2NC
Verify output of pointstat for example cases for soil moisture and temperature verification

Time Estimate

2-3 days

Sub-Issues

• Collect observations and model example data
• Develop use case scripts
• Develop description of use case
• See associated issues and ISMN data documentation need (below)

Relevant Deadlines

05/31/2024

Funding Source

7790111 (CLASP)

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)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Along with this use case, there is a related documentation issue for ISMN data, METplus #2448

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.
• Add any new Python packages to the METplus Components Python Requirements table.
• 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 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 and merge your changes.
• Delete your fork or branch.
• Close this issue.

[anewman89]

@DanielAdriaansen I started this issue for the ISMN use case per our discussion on 04/01/2024. I believe we will be adding someone, likely Bri, to take the lead here, but I think it'd be good to have you in a support role for help.