StatAnalysis - Allow processing of time ranges other than daily

[georgemccabe]

Currently StatAnalysis wrapper truncates the INIT/VALID_BEG/END times to only use YYYYMMDD. The hours are subset using the lists in the config file, i.e. FCST_VALID_HOUR, OBS_VALID_HOUR, FCST_INIT_HOUR, OBS_INIT_HOUR. Users may want to run the tool on a more specific time range.

Describe the Enhancement

Enhance the wrapper to use the full time specified with INIT/VALID_BEG/END. To preserve previous behavior, if only YYYYMMDD is specified, then set the time range to include the full day of the end date, e.g. if VALID_END = 20221018, then set valid_end = "20221018_235959"

Time Estimate

~1-2 days

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

5.0.0

Funding Source

None

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