New Use Case: Satellite verification of sea surface salinity: AVISO vs RTOFS output HYCOM climo #1318
Description
Replace italics below with details for this issue.
Describe the New Use Case
This new use case will duplicate the efforts of Todd Spindler's VLab-Redmine code, specifically its calculations for satellite verification of sea surface salinity using AVISO as obs, RTOFS output as model forecasts, HYCOM as climatology to calculate anomaly and OSTIA ice for masking.
It still needs to be determined if the graphical output currently produced and displayed at the site listed below need to be produced in this use case.
As a final step, these new data sources will be logged in the METplus Verification Datasets Guide.
This is part of the larger Marine layer Verification package integration, which is tracked in #800.
Useful weblink : https://polar.ncep.noaa.gov/global/class-1/
Use Case Name and Category
GridStat_fcstRTOFS_obsAVISO_climHYCOM_ssh under marine_and_coastal
Input Data
Provide a total input file size, keeping necessary data to a minimum.
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
2788881
Define the Metadata
Assignee
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.