Describe the Task

This is a very small change. Adjust the STAT-Analysis GO Index configuration file by changing PRMSL/Z0 to PRMSL/L0. When applying the GO Index and newly developed CBS Index to recent Air Force datasets, it was determined that while "L0" works, "Z0" does not. This necessitated that a separate config file be created for this minor change. This task is to make this small change to the default.

Note that any GRIB records matching PRMSL/Z0 will ALSO match PRMSL/L0 since L0 does generic level value matching rather than enforcing the level type be considered to be a "vertical level", as the Z0 setting does.

Time Estimate

1 hour.

Sub-Issues

Consider breaking the task down into sub-issues.
No sub-issues needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2712221

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: @JohnHalleyGotway
• Select scientist(s) or no scientist required: No scientist needed. Have @michelleharrold review the PR to approve the change.

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
  No impacts.

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