New Use Case:Ocean fronts demonstrating modified Hausdorff

[j-opatz]

Describe the New Use Case

This is the final use case that was being tracked by the umbrella issue #800 to bring marine verification into the METplus suite.

This use case will replicate the verification work done for ocean fronts. While this largely relies on plotting output and will be completed at a later time in METplotpy, the focus will remain largely on figuring out how to replicate the modified Hausdorff.

Use Case Name and Category

Use case name will be determined once input sources are identified.

This use case will reside in the marine_and_cryosphere category

Input Data

List input data types and sources.
Provide a total input file size, keeping necessary data to a minimum.

Acceptance Testing

This use case will be successful if it replicates the modified Hausdorff values with the same input data as the website.
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

• 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.

[georgemccabe]

@j-opatz , @mrinalbiswas, has this work been completed?

[mrinalbiswas]

@georgemccabe No, this work is not completed. I will let @j-opatz comment on the limitations of MET that is needed for the use case.

[georgemccabe]

Thanks @mrinalbiswas . @j-opatz , I noticed this issue has the "priority:high" and "required: FOR OFFICIAL RELEASE" labels but is not assigned to a release milestone. Could you adjust the labels/milestones as needed?