Skip to content

Bugfix: Fix the PARUSR BUFRLIB failure when PB2NC is compiled with -O2 optimization #3054

@georgemccabe

Description

@georgemccabe

While testing the MET conda recipe for dtcenter/METplus#2863, I discovered that pb2nc crashes when using bufrlib 12.1.0, which is the version that is provided via NCEPLIBS-bufr in conda-forge. This version of bufrlib also supports the Intel OpenAPI compilers (see release notes).

The following error is output:

 ***********BUFR ARCHIVE LIBRARY ABORT**************
 BUFRLIB: PARUSR - INPUT STRING () HAS

                   NO STORE NODES

 ***********BUFR ARCHIVE LIBRARY ABORT**************

Describe the Enhancement

Update calls to bufrlib for pb2nc to prevent this error.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Split between AF optimization (2771024) and conda build (base)

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a MET-X.Y.Z version, select the MET-X.Y.Z Development project

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 Development issue
    Select: Milestone as the next official version
    Select: MET-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Type

Projects

Status

🏁 Done

Relationships

None yet

Development

No branches or pull requests

Issue actions