Skip to content

Add tmp_dir configuration option to the Plot-Point-Obs tool #2237

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

During development of a METplus wrapper for the Plot-Point-Obs tool, @georgemccabe noted two issues:

  1. The Plot-Point-Obs config file currently lacks the tmp_dir configuration option. This is an oversight, and it should be added.
  2. He also found that passing an empty configuration file to the MET tools results in a runtime error. This can be demonstrated using the test_config utility:
touch empty_file ; internal/test_util/basic/vx_config/test_config empty_file
...
ERROR  : yyerror() -> syntax error in file "/tmp/met_config_3387_0"

This task is to fix both issues. While 1. is a mandatory, the fix for 2. is only desired.

Time Estimate

1 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.
Non needed.

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

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

Metadata

Metadata

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions