[Met_help] [rt.rap.ucar.edu #90402] History for Use of GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

John, I know I am pushing my quota but I am trying to get our MET software running in production.
As you recall, our ensemble files can contain both probability data and deterministic data.  When running my code I get:

SEED=959967324
DEBUG 1: Forecast File: /h/data/global/ENSEMBLE/data/post/GEPS/global/2019042500/grib2.2019042500.0018.EPOSTOUT
DEBUG 1: Observation File: /h/data/global/WXQC/data/met/nc_obs/precip/2019042518.nc
WARNING:
WARNING: MetGrib2DataFile::data_plane_array() -> Using the first of 2 exact matching records for "PROB(APCP_06>0.010)/A006/PROB":
WARNING: record 102 field 1: ipdtmpl[36] = 1, 8, 5, 0, 99, 0, 255, 1, 12, 1, 0, 0, 255, 0, 0, 0, 0, 1, 0, 0, 3, 10, 2019, 4, 25, 18, 0, 0, 1, 0, 1, 2, 1, 6, 255, 0
WARNING: record 218 field 1: ipdtmpl[29] = 1, 8, 2, 0, 99, 0, 255, 1, 12, 1, 0, 0, 255, 0, 0, 2019, 4, 25, 18, 0, 0, 1, 0, 1, 2, 1, 6, 255, 0
WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and "GRIB2_ipdtmpl_val" config file options to select one.
WARNING:

Luckily, the first record is the correct one.  How do I use the GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val to select one?  The manual does not mention this.

Thanks
Bob


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Use of GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val
From: John Halley Gotway
Time: Mon Jun 03 11:29:16 2019

Bob,

Thanks for letting me know that we forgot to add an explanation for
those
settings.  I'll add the following to the documentation for the next
release:

//       - The "GRIB2_ipdtmpl_index" and "GRIB2_ipdtmpl_val" entries
are
arrays
//         that specify product description template values to be
used.  The
//         indices are 0-based.  For example, use the following to
request a
//         GRIB2 record whose 9-th and 27-th product description
template
values
//         are 1 and 2, respectively:
//            GRIB2_ipdtmpl_index=[8, 26]; GRIB2_ipdtmpl_val=[1, 2];

Many of these GRIB2 filters are handled by other configurable entries
(GRIB2_ltab, GRIB2_disc, GRIB2_parm_cat, GRIB2_parm, GRIB2_pdt,
GRIB2_process, GRIB2_cntr, GRIB2_der_type, GRIB2_stat_type).  The
GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val entries are meant as a
catch-all
in case there are multiple matching records that aren't handle by the
existing filters.

I'd suggest looking at the output of wgrib2 to see how your two
matching
records differ.  And then use one of the GRIB2_... filters to grab the
one
you want.

Thanks,
John

On Thu, May 30, 2019 at 2:16 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Thu May 30 14:15:39 2019: Request 90402 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Use of GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90402 >
>
>
> John, I know I am pushing my quota but I am trying to get our MET
software
> running in production.
> As you recall, our ensemble files can contain both probability data
and
> deterministic data.  When running my code I get:
>
> SEED=959967324
> DEBUG 1: Forecast File:
>
/h/data/global/ENSEMBLE/data/post/GEPS/global/2019042500/grib2.2019042500.0018.EPOSTOUT
> DEBUG 1: Observation File:
/h/data/global/WXQC/data/met/nc_obs/precip/
> 2019042518.nc
> WARNING:
> WARNING: MetGrib2DataFile::data_plane_array() -> Using the first of
2
> exact matching records for "PROB(APCP_06>0.010)/A006/PROB":
> WARNING: record 102 field 1: ipdtmpl[36] = 1, 8, 5, 0, 99, 0, 255,
1, 12,
> 1, 0, 0, 255, 0, 0, 0, 0, 1, 0, 0, 3, 10, 2019, 4, 25, 18, 0, 0, 1,
0, 1,
> 2, 1, 6, 255, 0
> WARNING: record 218 field 1: ipdtmpl[29] = 1, 8, 2, 0, 99, 0, 255,
1, 12,
> 1, 0, 0, 255, 0, 0, 2019, 4, 25, 18, 0, 0, 1, 0, 1, 2, 1, 6, 255, 0
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
> WARNING:
>
> Luckily, the first record is the correct one.  How do I use the
> GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_val to select one?  The manual
does
> not mention this.
>
> Thanks
> Bob
>
>

------------------------------------------------