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

20040928: 20040927: converting WRF grib output to GEMPAK



Michale,

Yes, they are compiletime defined in 
$GEMPAK/source/programs/gd/gdvint/viprm.prm.

You should be able to redefine and compile just gdvint.

Steve Chiswell


>From: Michael Brennan <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200409282143.i8SLhPHP017603

>Hi Steve,
>
>Thanks, your suggestions were very helpful.
>
>The conversion to GEMPAK from grib was pretty straightforward from that 
>point.
>
>Now I'm trying to use gdvint to try and interpolate from this WRF eta 
>level data to pressure level data.  I've had some partial success, but 
>I'm running into some hard limits for:
>
>1) the number of eta levels that I can process
>2) the number of pressure levels I can write output to
>3) the number of parameters I can interpolate
>
>Are these hardwired somewhere in the source code for gdvint?
>
>Thanks,
>Mike
>
>Michael J. Brennan
>Graduate Research Assistant
>Department of Marine, Earth and Atmospheric Sciences
>North Carolina State University
>Email: address@hidden
>Phone: (919) 515-1447
>
>Unidata Support wrote:
>> Michael,
>> 
>> The vcrdgrib1.tbl provides for the ETA level and Layer coordinate.
>> 
>> Your output below: WMO parameter table to wmogrib200.tbl
>> shows that your grib is using parameters in table 200.
>> This is not a table that exists in the current NCEP grib
>> documentation so you will have to create that table for parameters 1-127, 
>> as well as the local (xxxxgrib200.tbl) file  for parameters 128-255.
>> What model center is being used? The model center number will have to
>> be defined in cntrgrib1.tbl (if you aren't using an existing number),
>> and that will define the string used for your local table name.
>> 
>> Without those tables, you wont have any defined parameters to decode,
>> so you won't have anything in your output file..
>> 
>> Steve Chiswell
>> 
>> 
>>>From: Michael Brennan <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200409271712.i8RHC5nJ025022
>> 
>> 
>>>Steve,
>>>
>>>I've been able to get WRF model output in grib format by using an grib 
>>>output module from Todd Hutchinson at WSI.  I'd like to try and convert 
>>>the grib files to GEMPAK.  However, the WRF output is in the WRF's "Eta" 
>>>vertical coordinate, and I think that trips up dcgrib2.  I don't get an 
>>>error message when I run dcgrib2, but the GEMPAK file doesn't get created.
>>>
>>>[mjbrenna@compute-2-35 mjbrenna]$ dcgrib2 wrf_test.gem < wrfout.grb
>>> Changing center table to cntrgrib1.tbl
>>> Changing vertical coord table to vcrdgrib1.tbl
>>> Changing WMO parameter table to wmogrib200.tbl
>>>
>>>Do you have any thoughts or suggestions?
>>>
>>>Thanks,
>>>Mike
>>>-- 
>>>Michael J. Brennan
>>>Graduate Research Assistant
>>>Department of Marine, Earth and Atmospheric Sciences
>>>North Carolina State University
>>>Email: address@hidden
>>>Phone: (919) 515-1447
>>>
>> 
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support 
>> ----------------------------------------------------------------------------
>> 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.
>
--
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.