New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove limitation when applying GRIB ensemble filter configuration options. #1604
Closed
8 of 21 tasks
Closed
8 of 21 tasks
Labels
MET: Library Code
reporting: DTC NOAA R2O
NOAA Research to Operations DTC Project
requestor: NOAA/EMC
NOAA Environmental Modeling Center
type: enhancement
Improve something that it is currently doing
Projects
Milestone
Comments
JohnHalleyGotway
added
type: bug
Fix something that is not working
component: library code
requestor: NOAA/EMC
NOAA Environmental Modeling Center
labels
Dec 9, 2020
JohnHalleyGotway
changed the title
Remove limitation for when GRIB ensemble filter configuration options are checked.
Remove limitation when applying GRIB ensemble filter configuration options.
Dec 9, 2020
JohnHalleyGotway
added a commit
that referenced
this issue
Dec 9, 2020
…IB1 data. Instead of only processing the ensemble config options for NCEP data (center = 7, subcenter = 2), apply them anytime the user has supplied them.
JohnHalleyGotway
added
type: enhancement
Improve something that it is currently doing
and removed
type: bug
Fix something that is not working
labels
Dec 14, 2020
Switched from a bugfix type issue to an enhancement. Binbin confirmed that including this fix in met-10.0.0-beta3 is sufficient. We do not need a met-9.1.2 bugfix release for this change. |
JohnHalleyGotway
added a commit
that referenced
this issue
Dec 14, 2020
JohnHalleyGotway
added a commit
that referenced
this issue
Dec 14, 2020
…warning message when multiple matching records are found, even for pressure or vertical level types.
8 tasks
jprestop
pushed a commit
that referenced
this issue
Dec 14, 2020
JohnHalleyGotway
added a commit
that referenced
this issue
Dec 15, 2020
…the introduction of a memory leak and a variable that was set but never used. Minor updates to address these findings.
JohnHalleyGotway
added a commit
that referenced
this issue
Dec 15, 2020
8 tasks
jprestop
pushed a commit
that referenced
this issue
Dec 15, 2020
* Per #1604, removing the ensemble GRIB filtering limits for the develop branch. * Per #1604, update logic in MetGrib1DataFile::data_plane() to print a warning message when multiple matching records are found, even for pressure or vertical level types. * Per #1604, the Fortify run revealed two issues with these changes... the introduction of a memory leak and a variable that was set but never used. Minor updates to address these findings.
TaraJensen
added
the
reporting: DTC NOAA R2O
NOAA Research to Operations DTC Project
label
Mar 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
MET: Library Code
reporting: DTC NOAA R2O
NOAA Research to Operations DTC Project
requestor: NOAA/EMC
NOAA Environmental Modeling Center
type: enhancement
Improve something that it is currently doing
Describe the Enhancement
This requested change to the logic arose via met-help:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97769
Binbin is trying to filter out a single record from a GRIB1 ECMWF data file. MET does include a GRIB_ens configuration option which should be used in this case. However, the GRIB_ens logic is currently only applied to NCEP produced data. This task is to remove the check in data2d_grib_utils.cc that prevents this filtering logic from applied to non-NCEP behavior.
In met-9.1, whenever the user specifies the "GRIB_ens" option, apply it to the data regardless of the center and subcenter numbers.
I was also surprised not to see a warning message about matching multiple records. Compare the GRIB1 log messages with those from GRIB2 and make them consistent when you unexpectedly match multiple records.
Also ensure that this change does not change the output from the nightly build.
Describe the steps to demonstrate this:
1. Pull sample data:
2. With met-9.1, run:
3. Note that it matched 51 records, but should only match 1 of them... record 26.
Time Estimate
2 days to test and fix.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
No sub-issues required.
Relevant Deadlines
Include in met-10.0.0.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
None.
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s), Project(s), Milestone, and Linked issues
The text was updated successfully, but these errors were encountered: