Describe the Enhancement

The TC-Diag tool in MET is being updated considerably for MET version 12.0.0. Some of these enhancements impact the TC-Diag METplus wrapper. This issue is enhance that wrapper as needed, and described below. Rather than creating separate issues for each change, I'm bundling them together into this single issue and assigning it to the beta3 development cycle. If it is more convenient to actually make the changes as we go, please feel free to close this issue, and I'll create a new one for additional changes.

List of changes:

1. PR Feature #2609 tc_diag_missing_data MET#2680 for issue Refine TC-Diag logic for handling missing data MET#2609:

• Adds new one_time_per_file_flag boolean option to the TC-Diag configuration file. Default is TRUE.
• Modifies the TCDiagConfig_default from using "all" lead times found in the tracks (lead = [];) to explicitly listing the expected ones:

lead       = [   "0",   "6",  "12",  "18",  "24",
                "30",  "36",  "42",  "48",  "54",
                "60",  "66",  "72",  "78",  "84",
                "90",  "96", "102", "108", "114",
               "120", "126" ];

Time Estimate

1 day?

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2770043

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.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  No additional impacts.

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.