[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #ADX-952588]: dcgrib2 unable to decode GEFS grid

Hi,

First, I separated the GEMPAK portion of your last email into a separate
support inquiry...

re:
> And the Gempak challenge. I am not a Gempak person. I modify GARP code for
> you any day, but GEMPAK is a challenge.

I understand.  I am a novice when it comes to GEMPAK also.

re:
> So, I try to convert gefs to gem. Maybe I am not even getting the right
> files from nomad, but I am trying my best here.
> 
> This is what I am trying to do kind of copy pasted from pqact files:
> 
> /home/gempak/GEMPAK7/os/linux64/bin/dcgrib2 -v 5 -d dcgrib.log -e
> gep01.t12z.pgrb2a.0p50.f111
> 
> It generates an output, but I am not even sure it is right.
> 
> Is there something like ncdump for gem files?

I am sure that there is some sort of a GEMPAK routine that can be used to
list values from a grid file.  I am not sure what it is unfortunately.

re:
> In dcgrib.log I see this:
> 
> [2213] 201018/2104[DCINIT 3] Version 7.5.1
> [2213] 201018/2104[DCINIT -11]
> [2213] 201018/2104[DC 2] Interrupt Signal
> [2213] 201018/2104[DC 5] Normal termination.
> [2213] 201018/2104[DC 2] Number of bulletins read and processed: 0
> [2213] 201018/2104[DC 6] Shutting down.
> [2508] 201018/2106[DCINIT 3] Version 7.5.1
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 0 1 [6]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 2 
> 224 1 [1498169936]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 2 
> 22 1 [1498169936]
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 20 1 [1]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 234 1 [1]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 20 1 [1]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 234 1 [1]
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 20 1 [1]
> [2508] 201018/2106[GB 1] No GEMPAK parameter name defined for this grid.
> [2508] 201018/2106[DECODE_GRIB2 -34] Could not determine parameter name 0 19 
> 234 1 [1]
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -4] Cannot read file ....
> [2508] 201018/2106[FL -5] Cannot write to file ....
> [2508] 201018/2106[DM -6] Write error.

The lines that have 'Could not determine parameter name' I believe are indicting
that the GEMPAK tables being used do not have the appropriate entries for the
fields that are in the GEFS file(s) you are trying to process.  I will take a
look to see what may need to be added to which table, but I will not be able
to get to this until tomorrow (or, perhaps, later tonight).

Aside: the reason I suspect the GEMPAK grib2 tables is these are also included
in the LDM releases (for NOAAPort ingest support), and we routinely see that
new fields are being added to the NOAAPort SBN that are not accounted for in
the GEMPAK GRIB tables, and this requires us to look up the GRIB2 definitions
and update the table(s) in the LDM release.  If I find that the GEMPAK grib2
tables in the LDM release have been updated to include the field(s) that are
not being found by dcgrib2, I will point you to where you can find them.  If
the fields are not (yet) included, I will try and figure out what the entry(ies)
need to look like and send you the change(s).

re:
> I appreciate any help, idea, anything.

No worries.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ADX-952588
Department: Support GEMPAK
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.