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

[GEMPAK #QEJ-861814]: GEMPAK - Date/Time Ranges in GDGRIB



Chris,

I would suggest using the gddiag binary from the 5.10.3 binary distribution and 
see if that works for you.
The gddiag program does not connect to a gplt process, so it will be OK to run 
that program in your 5.10.2 environment
as a test.

If you are unable to run the program, then you can try building the 5.10.3 
version from source, but I'd
like to determine if the problem is with the program itself, compile flag 
differences between your system and
what I have to build on here, or something else. Generally the problem you 
decribe with the text string
being corrupt is either a byte swapping issue, or c to fortran string 
conversion problem, but I havdn't
seen it here.

Steve Chiswell
Unidata User Support



> Steve,
> 
> The version of GEMPAK that I am running is 5.10.2 compliled from source. I 
> have spoken with Brendon Hoch, our IT contact at PSU and he is willing to 
> upgrade to 5.10.3 if you feel that will solve this issue.
> 
> --Chris
> 
> 
> ----- Original Message -----
> From: "Unidata GEMPAK Support" <address@hidden>
> To: address@hidden
> Cc: address@hidden
> Sent: Friday, September 21, 2007 6:14:10 PM (GMT-0500) America/New_York
> Subject: [GEMPAK #QEJ-861814]: GEMPAK - Date/Time Ranges in GDGRIB
> 
> Christopher,
> 
> What version are you running? It sounds like a GDDIAG bug in creating the name
> since it should be TMXK.
> 
> I ran it here and got TMXK and nothing like "    E", so I think you are there 
> if we
> can get this knocked out.
> 
> Steve Chiswell
> Unidata User Support
> 
> 
> > Steve,
> >
> > I feel like I am ever so close. Here is what I have for GDDIAG and GDGRIB 
> > for my NARR-A files.
> >
> > GDDIAG:
> >
> > GDFILE    Grid file                         
> > stat_north_sector_1000_tmpk_t0.grid
> > GDOUTF    Output grid file                  
> > time_north_sector_1000_tmpk_t0.grid
> > GFUNC     Scalar grid                       MAXTMPK
> > GDATTIM   Grid date/time                    971116/1200F000:060224/1200F000
> > GLEVEL    Grid level                        1000
> > GVCORD    Grid vertical coordinate          PRES
> > GRDNAM    Grid parameter name               tmxk^060224/1200
> > GRDTYP    Diagnostic grid type (Scalar/Vec  S
> > GPACK     Packing type/number of bits       none
> > GRDHDR    Grid Header Flags
> > PROJ      Map projection/angles/margins|dr  LCC
> > GRDAREA   Area covered by grid
> > KXKY      Number of grid points in x;y
> > MAXGRD    Maximum number of grids
> > CPYFIL    Grid file whose navigation is to  narra_221_20001230_1800.grid
> > ANLYSS    Grid analysis block               4/2;2;2;2
> > Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> > GRDTYP,GPACK,GRDHDR,PROJ,GRDAREA,KXKY,MAXGRD,CPYFIL,ANLYSS.
> > GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> 
> > GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> 
> > GEMPAK-GDDIAG> GEMPAK-GDDIAG>
> > TIME1             TIME2         LEVL1 LEVL2   VCORD PARM
> > 060224/1200                          1000          PRES TMXK
> > Enter a new grid parameter name, <cr> to accept or type EXIT: Parameters 
> > requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> > GRDTYP,GPACK,GRDHDR,PROJ,GRDAREA,KXKY,MAXGRD,CPYFIL,ANLYSS.
> > GEMPAK-GDDIAG> GEMPAK-GDDIAG>Creating process: gplt for queue 1422032896
> >
> >
> > GDGRIB:
> >
> > GDFILE    Grid file                         
> > time_north_sector_1000_tmpk_t0.grid
> > GFUNC     Scalar grid                       TMXK
> > GDATTIM   Grid date/time                    060224/1200
> > GLEVEL    Grid level                        1000
> > GVCORD    Grid vertical coordinate          PRES
> > GBTBLS    Input GRIB decoding tables        wmogrib131.tbl
> > GBFILE    GRIB data file name               finished.grb
> > VERCEN    PDS byte_4/byte_5/byte_6/byte_26
> > PDSVAL    GRIB PDS grid identifier overrid  tmxk^20060224/1200
> > PRECSN    Packing precision
> > WMOHDR    WMO_ID/Origin_ID/DDHHMM
> > CPYFIL    Grid file whose navigation is to  narra_221_20001230_1800.grid
> > PROJ      Map projection/angles/margins|dr  LCC
> > GRDAREA   Area covered by grid
> > KXKY      Number of grid points in x;y
> > Parameters requested: GDFILE,GFUNC,GDATTIM,GLEVEL,GVCORD,GBTBLS,GBFILE,
> > VERCEN,PDSVAL,PRECSN,WMOHDR,CPYFIL,PROJ,GRDAREA,KXKY.
> > GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> 
> > GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> GEMPAK-GDGRIB> 
> > GEMPAK-GDGRIB> [DG -7]  Input grid TMXK ^060224/1200 @1000 %PRES cannot be 
> > found.
> > Parameters requested: GDFILE,GFUNC,GDATTIM,GLEVEL,GVCORD,GBTBLS,GBFILE,
> > VERCEN,PDSVAL,PRECSN,WMOHDR,CPYFIL,PROJ,GRDAREA,KXKY.
> >
> > I have used GDINFO to look at the grid file after running GDDIAG and it 
> > produces this result:
> >
> > GDINFO:
> >
> > Number of grids in file:     1
> >
> > Maximum number of grids in file:    400
> >
> > NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
> > 1     060224/1200                           1000         PRES       E
> > Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
> >
> >
> > If you notice, the PARM does not seem to show up correctly and instead had 
> > "four spaces" then E. When I replace gdfunc in GDGRIB from TMXK to "four 
> > spaces" and E a grib file is produced, however it contains no data. Am I 
> > defining something incorrectly or using GDDIAG incorrectly? If you have a 
> > chance let me know. Thanks.
> >
> > --Chris
> >
> >
> > ----- Original Message -----
> > From: "Unidata GEMPAK Support" <address@hidden>
> > To: address@hidden
> > Cc: address@hidden
> > Sent: Wednesday, September 19, 2007 4:19:04 PM (GMT-0500) America/New_York
> > Subject: [GEMPAK #QEJ-861814]: GEMPAK - Date/Time Ranges in GDGRIB
> >
> > > Steve,
> > >
> > > I have managed to convert individual NARR-A GEMPAK grid files to grib 
> > > format and it loads perfectly in IDV. However, my goal is to convert 
> > > GEMPAK grids that have been averaged using GDSTAT and convert those files 
> > > to gribs. These averaged files as you know have a date/time range to them 
> > > indead of a single data/time period. Here are the two approaches I have 
> > > used to define the date/time:
> > >
> > > GDATTIM= 971116/1200F000-060224/1200F000
> > >
> > > GDATTIM= 971116/1200F000:060224/1200F000
> > >
> > >
> > > Here is my output from GDINFO showing the times.
> > >
> > > NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
> > > 1     971116/1200F000   060224/1200F000     1000         PRES MAXTMPK
> > > 2     971116/1200F000   060224/1200F000     1000         PRES MINTMPK
> > > 3     971116/1200F000   060224/1200F000     1000         PRES AVETMPK
> > > 4     971116/1200F000   060224/1200F000     1000         PRES SDVTMPK
> > > 5     971116/1200F000   060224/1200F000     1000         PRES CNTTMPK
> > > Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
> > >
> > >
> > > Is there another way of listing date/time ranges for GDGRIB?
> > >
> > >
> > > --Chris Warren
> > >
> > >
> > > Christopher Warren
> > > Graduate Research Assistant
> > > Plymouth State University
> > > Plymouth, NH 03264
> > > Email: cjwarren1@mail.plymouth
> > >
> > >
> > Chris,
> >
> > The PDSVAL parameter can be used to set the parameter name, level, time to 
> > be used,
> > however, the time interval for your average if much largetr than an hourly 
> > value
> > like P06M for example.
> >
> > The easiest solution to get the parameter to grib would be to use GDDIAG and
> > convert the MAXTMPK for that time interval to the TMXK parameter
> > (as defined in $GEMTBL/grid/wmogrib2.tbl parameter #15) such as:
> > GFUNC    = maxtmpk
> > GDATTIM  = 971116/1200f000:060224/1200f000
> > GLEVEL   = 1000
> > GVCORD   = pres
> > GRDNAM   = tmxk^060224/1200
> > GRDTYP   = s
> > GPACK    = none
> > GRDHDR   =
> >
> >
> > Then use GDGRIB to convert the TMXK to grib.
> >
> > I don't have a good way to encode the time period of gdtat into the grib
> > without doing some direct bit writing in the PDS block. The above use of
> > the single time in GRDNAM in gddiag gets around having to work
> > with the time ranges.
> >
> > Steve Chiswell
> > Unidata User Support
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: QEJ-861814
> > Department: Support GEMPAK
> > Priority: Normal
> > Status: Closed
> >
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: QEJ-861814
> Department: Support GEMPAK
> Priority: Normal
> Status: Closed
> 
> 
> 


Ticket Details
===================
Ticket ID: QEJ-861814
Department: Support GEMPAK
Priority: Normal
Status: Closed