Replace italics below with details for this issue.

Describe the Problem

Provide a clear and concise description of the bug here.

Expected Behavior

Provide a clear and concise description of what you expected to happen here.

The latest build should produces the same outputs with the reference build

1. test_output/ioda2nc/odb_sonde_16019_all.nc
   main_v10.0-ref: hdr_typ_table = "\001" ;
   main_v10.0: hdr_typ_table = "pNj.\374\177" ;

2. test_output/pb2nc/nam.20210311.t00z.prepbufr.tm00.pbl.nc
   main_v10.0-ref: nobs = 293 ;
   main_v10.0: nobs = 245 ;
   this difference was detected 03-17-2022 (did not happen before)

Environment

Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop): senaca
2. OS: (e.g. RedHat Linux, MacOS): linux
3. Software version number(s) 10.0 bugfix

To Reproduce

Describe the steps to reproduce the behavior:
1. Compare unit test outputs (by nightly build)
2. See error: /d1/projects/MET/MET_regression/main_v10.0/NB2022031?/test_regression_2022031?.log
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

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: None
• Select scientist(s) or no scientist required: None

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, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

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.