Describe the Enhancement

This is a request from NOAA/MDL that arose during a telecon on 3/29/2021. Here's the correspondence:

From NOAA/MDL:
When we run stat_analysis, all of the stat output lines are written to the logs as well. Is there a way to turn that off?

Response:
Stat-Analysis originally just wrote its output to log files. Then we added the "-out" option to write the output to a separate file instead. When "-out" is used, the output is written to the "-out" file INSTEAD OF the log file.

Then we added the "-out_stat" option to format and write the output to a true .stat file including all the header columns. But specifying "-out_stat" DOES NOT prevent the output from being written to the log file.

It does make sense to me that when "-out" or "-out_stat" is provided, Stat-Analysis should NOT write its output to the log file.

This task is to suppress the logging of job output when the "-out_stat" option is provided. It is already suppressed when "-out" is used.

Time Estimate

1/2 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.
No sub-issues required.

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: John HG
• Select scientist(s) or no scientist required: no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy
  No impacts.

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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.