Skip to content

Update the time offset (by yyyymmdd_hhmmss) at the unit_plot_data_plane.xml #1677

@hsoh-u

Description

@hsoh-u

Describe the Problem

The time reference was updated with #1657 if "bounds" attribute exist. The time should match with the values at the "bounds" attribute. The unit test need to be updated.

/d1/projects/MET/MET_regression/develop/NB20210223/MET-develop/met/share/met/../../bin/plot_data_plane \
       /d1/projects/MET/MET_test_data/unit_test/model_data/easm/pr_day_MPI-ESM-MR_rcp85_r1i1p1_20060101-20091231.nc \
       /d1/projects/MET/MET_regression/develop/NB20210223/MET-develop/test_output/plot_data_plane/EaSM_CMIP5_pr_day_MPI-ESM-MR_rcp85_r1i1p1_20060101_12_time.ps \
       'name="pr"; level="(20060101_120000,*,*)";' \
       -v 4

ERROR  :
ERROR  : plot_data_plane -> trouble getting field "name="pr"; level="(20060101_120000,*,*)";" from file "/d1/projects/MET/MET_test_data/unit_test/model_data/easm/pr_day_MPI-ESM-MR_rcp85_r1i1p1_20060101-20091231.nc"
ERROR  :

Expected Behavior

The time comes from the "time_bnds" variable instead of the "time" variable. There is a half day off between two times. The time variable is the mid-point of the time_bnds variable. So the referenced time "20060101_120000" should be updated to "20060102_000000" (in time_bnds variable).

Environment

Describe your runtime environment:
1. Machine: (Linux Workstation - kiowa)
2. OS: (Debian)
3. Software version number(s)

To Reproduce

Describe the steps to reproduce the behavior:
1. Login to kiowa
2. /d1/projects/MET/MET_regression/develop/NB20210223/MET-develop/test/perl/unit.pl /d1/projects/MET/MET_regression/develop/NB20210223/MET-develop/test/xml/unit_plot_data_plane.xml
3. See error

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 (None)

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 relevant 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.
  • 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), Project(s), Milestone, and Linked issues
  • 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>
  • Close this issue.

Metadata

Metadata

Assignees

Labels

type: bugFix something that is not working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions