Support reformatting the TCDIAG line type written by the TC-Pairs tool

[bikegeek]

Describe the Enhancement

The TCDIAG line type is written by the TC-Pairs MET tool when the -diag command line argument is used. When diagnostic data is provided and matched to track data, each TCMPR line is followed by a TCDIAG line containing the diagnostic values corresponding to that point.

This issue is to parse/reformat this TCDIAG data, as needed, so that it can be used by the tcmpr plotter code in METplotpy.

A sample TC-Pairs output file containing TCDIAG lines can be found in:
seneca:/d1/projects/MET/MET_regression/develop/NB20240228/MET-develop/test_output/tc_pairs/al092022_20220926_DIAGNOSTICS.tcst

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

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

TCDiag Project (2770043)

Define the Metadata

Assignee

• Select Minna Win
• 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

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.