Enhancement: Add config option to write MET log output to terminal

[georgemccabe]

Currently MET log output is not written to the terminal (screen) when METplus is run. The output is captured and written to the METplus log file output.

Describe the Enhancement

Look into enhancing the logic so that the MET log output can be output to the screen if desired.

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

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

[georgemccabe]

The LOG_METPLUS variable can be set to empty to send all log output (including MET log output) to the terminal. I am adding a config variable LOG_TO_TERMINAL_ONLY to make this easier to configure. This should be sufficient for the NOAA EVS requirement to be able to capture MET errors in their job logs.

I didn't find an easy way to send the MET output (or output from any command run by the METplus wrappers) to both the terminal and the log file, but this may not be necessary since the above solution solves the original issue.