Enhance ExtractTiles using MTD input to properly match times

[georgemccabe]

While developing a new feature relative use case, @hertneky discovered that the logic for ExtractTiles using MTD data to match fcst and obs objects assumes that the times slices match up 1-to-1 in order. However, this is not the case in some MTD output.

Describe the Enhancement

Modify the logic to loop through the times for either fcst or obs and find the corresponding time in the other. Only process if there is a time for both inputs. Also, skip the 000 clusters.

Also consider adding an option to filter which objects to use.

Time Estimate

~1 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add support for explicitly setting file list file paths in wrappers that support multiple input files #1289
• Add support for setting INIT_LIST and VALID_LIST for irregular time intervals #1286

Relevant Deadlines

4.1.0-beta5

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