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

20040929: Gempak-Garp fails

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20040929: Gempak-Garp fails
  • Date: Thu, 30 Sep 2004 10:32:36 -0600
Mynul,

This is likely a problem with your data file, or your
path to locate the data as defined in $GARPHOME/config/Garp_defaults
in matching the data template name, which you should typically
have your surface data named $GEMDATA/surface/YYYYMMDD_sao.gem
to use the default configuration as provided.

Steve Chiswell

>From: mynul khan <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200409292314.i8TNETUE029326

>When I try to see Surface Observation data using Garp
>program it throws the following error messages.
>meteor% garp
>G A R P - v2.1 starting...
>  Warning: keylist   is null
>           Cannnot set option menu default button
>  Warning: keylist   is null
>           Cannnot set option menu default button
>  Warning: keylist   is null
>           Cannnot set option menu default button
>  Warning: keylist   is null
>           Cannnot set option menu default button
>ilio: [1010] Unknown error
>lately: reading sequential formatted internal IO
>part of last string: 1.0|
>Abort (core dumped)
>
>What do you think the problem is? And how do I fix it?
>Thanks,
>-Mynul
>
>
>               
>_______________________________
>Do you Yahoo!?
>Declare Yourself - Register online to vote today!
>http://vote.yahoo.com
>
--
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.