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

20050802: Problem with cross sections with GEMPAK5.8.2a



Bob,

I suspect the problem is caused by garp calling GEMPAK program routines
as subroutines, and the gempak routines have all changed the grid access
since 5.8.1.

I'll go through each of these plot types to verify the plotting.

Steve Chiswell


>From: "Robert J. Ballentine" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200508021908.j72J80jo020427

>Steve:
>   We are running GEMPAK5.8.2a on a Dell Desktop under linux
>Fedora Core 4.  We are also ingesting data with LDM-6.0.14.
>Everything runs OK for us except vertical cross sections,
>time-height cross sections, and model soundings in GARP.
>   When we try to plot a vertical cross section using the
>current ETA file (or any other file), we always get the error:
>
>  [GDCROSS -12]  No levels--check input for GDATTIM and GVCORD.
>
>We do not get this error on other machines running GEMPAK5.7.2p2
>or on the Fedora machine using GEMPAK5.7.2p2.
>   I get the same error message when I run GDCROSS manually
>in GEMPAK5.8.2a if I use gdattim=050802/1200, but it works
>when I use gdattim=050802/1200F00.  But I cannot make this fix
>in GARP where we just click on the desired date/forecast time.
>   We even tried creating subdirectories for eta and other models
>in data/gempak/model.  When we try to do cross sections in GARP,
>it finds the file in the subdirectory, but still fails to create
>the cross section and gives the GDCROSS error message above.
>   When we try doing the time-height cross section or the model
>soundings in GARP, we get a blank screen with no error message.
>Never had these problems with GEMPAK5.7.2p2.
>   Can you suggest a fix for the cross sections?
>   Thanks,
>   Bob Ballentine
>
--
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.