20010504: 20010504: RUC 236

Glen,

The output below I showed was from "GDINFO".

As for gribkey.tbl, the line that will file the RUC is:
007   x   105       @@@    data/gempak/model/YYYYMMDDHH_ruc@@@.gem    7500

This is for Center 7 (aka NCEP), model number 105 (aka RUC). 
The @@@ is a wildcard cor any grid identifier that matches 7 & 105,
so this will work for both the RUC 211 and RUC 236.

Steve Chiswell
Unidata User Support





>From: "Glenn Rutledge" <address@hidden>
>Organization: NCDC
>Keywords: 200105041758.f44HwJp19719

>Thanks Steve,
>How did you ascertain the info about that grid?
>
>No doubt you are correct about the grib2.  It's much cleaner and less
>mainatenance.  I'll get to that one day (I can never seem to get to my n-awips
>stuff...).  Any other changes I'll need to make when I do the grib2?  I did no
> t
>have 236 in my gribkey table 'Ya know.  (or soimehow it was deleted.??).
>
>Thx, Glenn
>
>Unidata Support wrote:
>
>> Glenn,
>>
>> I looked at your file. It has 1 grid:
>>  Number of grids in file:     1
>>
>>  Maximum number of grids in file:   1500
>>
>>   NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
>>     1     010401/0000F001                        550         PRES HGHT
>>
>> I pulled this up in Garp (Using the RUC II model type which
>> I have defined in the $GARPHOME/config/Garp_defaults file as ruc236).
>>
>> I set the pressure level to 550 and the gfunc to hght and produced
>> a plot. Everything looks fine. Eg, this is not what
>> I would call surface rucs.
>>
>> Did you expect other than 1 grid in the file?
>>
>> Also, I created the gribkey.tbl file for dcgrib2 so that you
>> would not have to worry about WMO header changes etc such
>> as the KWBC vs KWBG, or all the different models.
>>
>> I just pipe the entire grid data stream to dcgrib2 and let it
>> assign the file names for all the different data sets it finds,
>> eg:
>> # Global GRIB decoding action.
>> # Products stored maintained in $GEMTBL/grid/gribkey.tbl
>> HDS|NMC2|NOGAPS ^(/u/ftp/gateway|[HOYZ]|US058).*
>>         PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib.log
>>         -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
>>
>> By not giving a file name output, dcgrib2 will use the path and names
>> given in gribkey.tbl.
>>
>> Otherwise, you should be able to display the data in the file you just sent
>> me if your model keys have ruc236 for the associated model button.
>>
>> Steve Chiswell
>> Unidta User Support
>>
>> >From: "Glenn Rutledge" <address@hidden>
>> >Organization: NCDC
>> >Keywords: 200105041619.f44GJ6p16397
>>
>> >This is a multi-part message in MIME format.
>> >--------------B6582309137CE0F15CD5D78D
>> >Content-Type: text/plain; charset=us-ascii
>> >Content-Transfer-Encoding: 7bit
>> >
>> >Steve-
>> >I figured out that rucs are now KWBG and W grids are the 236's.  It's
>> >working operationally.
>> >
>> >On a related note- (the reason I wnet after the 40km rucs), is a file
>> >our archive group puts on the archive.  I took the grib, and did a
>> >dcgrib 'YYYYMMDDHH_ruc@@@.gem' < [fn] on it and get the attached file.
>> >
>> >When I go to plot it, GARP does not opeperate on it.   Any clues?
>> >
>> >Thx, again, Glenn
>> >
>> >--------------B6582309137CE0F15CD5D78D
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8644                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service                        http://www.unidata.ucar.edu/     
>> ****************************************************************************
>