The MTD met_tool_wrapper does not produce useful output

[DanielAdriaansen]

Replace italics below with details for this issue.

Describe the Problem

When attempting to use the output from this use case in #641, none of the output looked reasonable in ncview.

Two ideas:

1. Double check thresholds being used to define objects in MTD in the METplus conf file
2. Make sure the time range of input data is long enough to track objects through time

Expected Behavior

MTD should produce coherent objects.

Environment

Describe your runtime environment: 1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop) 2. OS: (e.g. RedHat Linux, MacOS) 3. Software version number(s)

To Reproduce

Describe the steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error Post relevant sample data following these instructions: https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2700042

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 Organization level Project for support of the current coordinated release
• [ ] Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
• [ ] Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

• [ ] METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Bugfix 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 main_\. Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• [ ] Fix the bug 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 main_\. Pull request: bugfix <Issue Number> main_<Version> <Description>
• [ ] Define the pull request metadata, as permissions allow. Select: Reviewer(s) and Linked issues Select: Organization level software support Project for the current coordinated release Select: Milestone as the next bugfix version
• [ ] Iterate until the reviewer(s) accept and merge your changes.
• [ ] Delete your fork or branch.
• [ ] Complete the steps above to fix the bug on the develop branch. Branch name: bugfix_<Issue Number>_develop_<Description> Pull request: bugfix <Issue Number> develop <Description> Select: Reviewer(s) and Linked issues Select: Repository level development cycle Project for the next official release Select: Milestone as the next official version
• [ ] Close this issue.

[DanielAdriaansen]

John says to consider high/low pressure centers if we need a simple demo.