Skip to content

Enhancement: Allow TC_STAT_LOOKIN_DIR setting to accept multiple entries, update documentation #3265

@j-opatz

Description

@j-opatz

Describe the Enhancement

In a recent Discussions topic, the TC_STAT_LOOKIN_DIR setting was discussed. Two issues were discussed, and this issue is to correct and enhance the setting:

  1. First, the METplus wrappers documentation says the TC_STAT_LOOKIN_DIR is only for the directory that TC-Stat will look in for files. However, this setting is a wrapped extension of the -lookin flag for MET's TC-Stat tool, which can accept a file or a top-level directory that contains the files. This should be tested to ensure the behavior is as expected, and then update the METplus wrappers documentation to show the dual behavior capability.
  2. The -lookin flag can accept multiple entries. This is a desired behavior in the METplus wrapped tool version. We should confirm that this behavior is currently unavailable, and then enhance the wrapped tool to add this behavior.

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

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as a METplus-Wrappers-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a METplus-Wrappers-X.Y.Z version, select the METplus-Wrappers-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

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.
  • For any new datasets, an entry to the METplus Verification Datasets Guide.
  • 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 issue
    Select: Milestone as the next official version
    Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    🩺 Needs Triage

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions