Skip to content

New Use Case: Read in Argo profile data netCDF files for use in METplus with python embedding #1977

@GwenChen-NOAA

Description

@GwenChen-NOAA

Replace italics below with details for this issue.

Describe the New Use Case

Provide a description of the new feature request here.

To create a new use case and python code to read Argo profile data into PointStat using python embedding.

Use Case Name and Category

Provide use case name, following Contributor's Guide naming template, and list which category the use case will reside in.
If a new category is needed for this use case, provide its name and brief justification

PointStat_fcstRTOFS_obsArgo_netCDF_temp_sali
In the Model Applications/Marine and Cryosphere category

Input Data

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

The netCDF files are available on WCOSS2 at /lfs/h1/ops/dev/dcom/$YYYYMMDD/validation_data/marine/argo.

Acceptance Testing

Describe tests required for new functionality.

Use python embedding and PointStat to read in Argo profile data for RTOFS ocean temperature and salinity verifications, then the functionality will be successfully created. Utilize available python packages on WCOSS2 and test run on WCOSS2.

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.

1-2 week time is sufficient.

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.

EVS Alpha Test was due on December 1, 2022 and Beta Test deadline is to be determined.

Funding Source

Define the source of funding and account keys here or state NONE.

2773542

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
    @JohnHalleyGotway
  • 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.

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

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions