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

20000104: Garp defaults

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: 20000104: Garp defaults
  • Date: Wed, 05 Jan 2000 09:35:05 -0700
Pete,

you can rename the durectories under fdf/scalar and fdf/vector to
match your naming conventions.

The reason I had to change the names here is because while I'm working
on NMAP for GEMPAK6.0, I have to make the file names compatible
with both releases of GEMPAK. The fdf directort names don't get bui;t-
they are just unpacked from the distribution tarfile. 

When you run garp, if the model key doesn't match the name of a
subdirectory under the fdf, then it uses the subdirectory "default"
which is pretty basic.

Steve Chiswell
Unidata User Support


>From: Rahe Peter J MSgt AFIT/ENP <address@hidden>
>Organization: .
>Keywords: 200001051453.HAA03677

>Steve,
>
>I've checked the $GARPHOME/fdf/scalar/ directory, and I think that's where
>the problem lies.  At what point do the subdirectories in
>$GARPHOME/fdf/scalar/ get built, because in the previous garp release
>(garp2.02) those subdirectories matched my file naming convention
>(eta_grid211) while they now show as simply eta211.  Do I rename the
>directories to match my naming convention, or change my naming convention to
>match the directories? 
>
>Pete Rahe
>Contractor, ICES Ltd
>Weather Lab Unix System Administrator
>Air Force Institute of Technology
>Wright-Patterson AFB OH
>
>??address@hidden       
> ?  (DSN 785-3636 x4646  COMM (937) 255-3636 x4646
>       Fax:  DSN 785-2921    COMM (937) 255-2921
>
>
>>Steve,
>>
>>I applied the latest patches for Garp yesterday (to take care of y2k bugs)
>>and noticed several changes and/or problems.  The biggest problem is that
>>any changes I make in the $GARPHOME/config/Garp_defaults files aren't being
>>picked up when Garp is run.  For instance, if I change the color scheme for
>>lines, the same default settings continue to show up.
>>
>>I also noticed that when under the HAS button, MSLP (mb) is listed, but
>>there is no more MSLP with eta reduction as in the previous release.  
>>
>
>
>Pete,
>
>The MSLP with eta reduction is in the $GARPHOME/fdf/scalar/eta211/HAS.
>You may have to change the model keys in the Garp_defaults to match your
>file naming however. Here, I have 2000010412_eta211.gem,
>so my model keys that I sent out in the Garp_defaults have
>eta211, and that is the directory that is being looked for in the fdf/scalar
>
>tree.
>
>In the previous distribution, I may have had eta_211 or something, so check
>how your $HDS directory files are named and change Garp_defaults
>accordingly.
>
>If you don't see changes in your Garp_defaults that you make, you might need
>to check to see if your GARPHOME environmental variable is pointing
>to the correct directory (and not the previous distribution).
>
>Steve Chiswell
>