Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Use Case: Satellite verification of sea surface salinity: AVISO vs RTOFS output HYCOM climo #1318

Closed
23 tasks
mrinalbiswas opened this issue Dec 16, 2021 · 0 comments · Fixed by #1440
Closed
23 tasks
Assignees
Labels
METplus: Marine and Cryosphere priority: high High Priority requestor: NOAA/EMC NOAA Environmental Modeling Center requestor: NOAA/OPC NOAA Ocean Prediction Center required: FOR OFFICIAL RELEASE Required to be completed in the official release for the assigned milestone type: new use case Add a new use case
Milestone

Comments

@mrinalbiswas
Copy link
Contributor

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

AVISO: https://resources.marine.copernicus.eu/product-detail/SEALEVEL_GLO_PHY_L4_NRT_OBSERVATIONS_008_046/INFORMATION

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.
@mrinalbiswas mrinalbiswas added alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle type: new use case Add a new use case labels Dec 16, 2021
@j-opatz j-opatz linked a pull request Feb 17, 2022 that will close this issue
12 tasks
@georgemccabe georgemccabe changed the title Add a use case to demonstrate the satellite verification of sea surface salinity: AVISO vs RTOFS output HYCOM climo New Use Case: Satellite verification of sea surface salinity: AVISO vs RTOFS output HYCOM climo Feb 17, 2022
@georgemccabe georgemccabe added this to the METplus-4.1.0 milestone Feb 17, 2022
@TaraJensen TaraJensen added requestor: NOAA/EMC NOAA Environmental Modeling Center requestor: NOAA/OPC NOAA Ocean Prediction Center METplus: Marine and Cryosphere priority: high High Priority required: FOR OFFICIAL RELEASE Required to be completed in the official release for the assigned milestone and removed alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle labels Feb 22, 2022
@jprestop jprestop modified the milestones: METplus-4.1.0, METplus-5.0.0 Feb 28, 2022
@j-opatz j-opatz modified the milestones: METplus-5.0.0, METplus-4.1.0 Feb 28, 2022
@j-opatz j-opatz closed this as completed Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
METplus: Marine and Cryosphere priority: high High Priority requestor: NOAA/EMC NOAA Environmental Modeling Center requestor: NOAA/OPC NOAA Ocean Prediction Center required: FOR OFFICIAL RELEASE Required to be completed in the official release for the assigned milestone type: new use case Add a new use case
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants