Skip to content

Enhancement: Enhance the MODE wrapper to handle updated multivar configuration options #2210

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

PR dtcenter/MET#2569 for issue dtcenter/MET#1283 slightly modifies the configuration options to support multivariate MODE logic. This task is to update the METplus wrapper for MODE to handle the change.

According to the METplus Configuration Glossary, the following are supported:

  • MODE_FCST_MULTIVAR_UNITS
  • MODE_OBS_MULTIVAR_UNITS

These options are no longer used and should be replaced with:

  • MODE_FCST_MULTIVAR_LEVEL
  • MODE_OBS_MULTIVAR_LEVEL

The are used to set the values of fcst.multivar_level and obs.multivar_level respectively.

Recommend also testing the MODE wrapper with MET's develop branch after the MET-11.1.0-rc1 release has been created.

Please see @davidalbo with any questions about multi-variate MODE.

Time Estimate

3 hours?

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None needed.

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)

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)

Consider the impact to the other METplus components.

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.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions