Skip to content

Bugfix: PointStat support multiple observations files #2567

@georgemccabe

Description

@georgemccabe

Currently if multiple observation input template paths are specified, the PointStat wrapper creates a text file with a list of file paths to process. However, the point_stat tool does not support passing a file list file as the observation input file. Additional point observation files are passed to point_stat using the -point_obs argument.

Describe the Problem

PointStat wrapper should be modified to provide additional observation files using the -point_obs argument.

Expected Behavior

Multiple observation files can be read into PointStat

Environment

Describe your runtime environment:
1. Machine: casper
2. Software version number(s): METplus 6.0.0-beta3

To Reproduce

Describe the steps to reproduce the behavior:
1. Log into casper
2. Load METplus 6.0.0-beta3
3. Run use case /glade/u/home/mccabe/i-wrf/use_cases/Hurricane_Matthew/METplus/PointStat_matthew.conf using the commented value for OBS_POINT_STAT_INPUT_TEMPLATE that includes multiple values

OBS_POINT_STAT_INPUT_TEMPLATE = metar/netcdf/met_{valid?fmt=%Y%m%d_%H%M}.nc, raob/netcdf/met_{valid?fmt=%Y%m%d_%H%M}.nc

4. See error in log file

WARNING: process_obs_file() -> can't open observation netCDF file: /glade/u/home/mccabe/out_test2/stage/file_lists.20240426183014/20161006000000_36_point_stat_obs.txt

Relevant Deadlines

6.0.0

Funding Source

I-WRF

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 Organization level Project for support of the current coordinated release
  • Select Repository level Project for development toward the next official release or add alert: NEED CYCLE ASSIGNMENT label
  • Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

Bugfix 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 main_<Version>.
    Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
  • Fix the bug 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 main_<Version>.
    Pull request: bugfix <Issue Number> main_<Version> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Organization level software support Project for the current coordinated release
    Select: Milestone as the next bugfix version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Complete the steps above to fix the bug on the develop branch.
    Branch name: bugfix_<Issue Number>_develop_<Description>
    Pull request: bugfix <Issue Number> develop <Description>
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions