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.
Douglas, One likely cause in would be the change in the data set naiming from "eta" to "nam". I mentioned in the release notes that the decoders and datatype.tbl were set up to refer to the data sets as "nam" now: http://www.unidata.ucar.edu/software/gempak/GEMPAK/whats_new.html#5.9.3 The $GARPHOME/config/Garp_defaults file has a section: # Widget defaults model : eta I left the default model in Garp to be "eta" because the Garp FDF files are located in subdirectory names by the modelkey. The $GEMTBL/config/datatype.tbl will locate the "eta" data set as a synonym for the NAM80: ETA $MODEL/nam YYYYMMDDHH_nam211.gem If your NAM80 files are not named as above, you will need to configure your datatype.tbl accordingly. Alternatively, if you change the modelkey in the Garp_defaults file to "nam", then you should copy the "eta" FDF directories for each of the plot types to directories named "nam". Steve Chiswell Unidata User Support On Tue, 2006-08-22 at 15:06 -0500, Douglas Tilly wrote: > Gembuds, > > I recently installed GEMPAK5.9.3 ( I used the precompiled binaries and > libraries ) on a machine running on FC2. Everything appears to working > fine, except for garp. > > Garp starts up fine, and I can choose to display any observed data, > e.g., metar, sat, etc. However, when I click on a button to display > model data, garp crashes. It doesn't matter if it's model data in plan > view, cross section, etc. Has anyone seen this before? If so, what > fixed this problem? > > Thanks for your help. > > Doug -- Steve Chiswell <address@hidden> Unidata