Currently the climatology field can be set by using {TOOL}_CLIMO_[MEAN/STDEV]_FIELD i.e. GRID_STAT_CLIMO_MEAN_FIELD. However, the format of the value must match the format that is expected by the MET tool:

GRID_STAT_CLIMO_MEAN_FIELD = {name="TMP"; level="(*,*)";}

Describe the Enhancement

It would be easier for users if the climatology field info can be set in the same way that forecast and observation fields are specified. Add support for setting {TOOL}_CLIMO_[MEAN/STDEV]_VAR_[NAME/LEVELS]. The above example would be set using:

GRID_STAT_CLIMO_MEAN_VAR1_NAME = TMP
GRID_STAT_CLIMO_MEAN_VAR1_LEVELS = "(*,*)"

Time Estimate

~1-2 days

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

5.0.0

Funding Source

2792541

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

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 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 and merge your changes.
• Delete your fork or branch.
• Close this issue.