Skip to content

Stat-Analysis fails when aggregating ECNT lines. #1706

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Problem

This issue was raised by a user via met-help:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=98979

The user did send us data to test, but we were also able to replicate the data that created by running "make test".
Running Stat-Analysis to aggregate the ECNT line type results in the following error:

ERROR  : 
ERROR  : CRC_Array::operator[](int) const -> range check error ... index = 0, Nelements = 0, Nalloc = 0
ERROR  :

Confirmed that this problem exists for both MET version 9.1 and the development versions for MET version 10.0.0. Recommend that we include a fix in version 10.0.0. Also, be sure to add a new job to the unit test which exercises this functionality.

Expected Behavior

Stat-Analysis should be able to aggregate the ECNT line type.

Environment

Describe your runtime environment:
1. Machine: Replicated this functionality on kiowa (Linux) and my Mac laptop
2. Software version number(s): at least MET version 9.1 and later

To Reproduce

Describe the steps to reproduce the behavior:
1. Go to a build of MET for which 'make test' has already been run.
2. Run the following command:

bin/stat_analysis -lookin out/ensemble_stat/ensemble_stat_SKIP_CONST_20120410_120000V.stat -job aggregate -line_type ECNT

3. See error:

ERROR  : 
ERROR  : CRC_Array::operator[](int) const -> range check error ... index = 0, Nelements = 0, Nalloc = 0
ERROR  :

Relevant Deadlines

met-10.0.0

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

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions