EDIT: This issue originally covered both adding documentation for new config variables and updating all wrappers to consistently find input files using RuntimeFreq's functions. The new development work is out of the scope for the 6.0.0 release, so I created issue #2757 to update the documentation for the 6.0 release. Then I renamed this issue and moved it to 6.1 development.

The functionality for #2460 has been added and works as expected. However, there are some additional changes that should be done before the official release.

Describe the Task

• Update logic to find files to be consistent and use RuntimeFreq's functions

• Ensure unit tests still pass after above changes

• Add documentation for new config variables for allow missing input logic -- moved to issue Documentation: Add allow missing input variables to glossary #2757

Time Estimate

Assess time and only work if less than 3 days

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2771024

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

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