Describe the Problem

This issue arose via a Slack discussion with @mpm-meto. Investigation revealed a slight discrepancy in MET's handling of the accumulation interval value when it is not specified or does not apply. See below for detail.

Expected Behavior

When the accumulation interval does not apply to a given dataset, its value should be stored/reported consistently by MET, regardless of the input file type.

Environment

Describe your runtime environment:
*1. MacOS

To Reproduce

Describe the steps to reproduce the behavior:
1. Run pcp_combine on a GRIB input file:

bin/pcp_combine -add data/sample_fcst/2005080700/wrfprs_ruc13_12.tm00_G212 'name="RH"; level="Z2";' rh.nc

2. Run plot_data_plane with -v 4 on the GRIB input:

bin/plot_data_plane data/sample_fcst/2005080700/wrfprs_ruc13_12.tm00_G212 rh_grib.ps 'name="RH"; level="Z2";' -v 4

3. Run plot_data_plane with -v 4 on the NetCDF output:

bin/plot_data_plane rh.nc rh_nc.ps 'name="RH_Z2"; level="Z2";' -v 4

4: Observe the difference in accumulation interval reported:

DEBUG 4:    accum time: 000000

vs

DEBUG 4:    accum time: NA

These should be consistent.

Only need to fix this in the develop branch, not main_v10.1.

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 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 PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

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

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.
• 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 Linked 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 Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.