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

20000630: GARP search keys


Devin,

sfc_keys shouls have a corresponding "key"_dir and "key"_parms entry for
each entry.

So, if you choose to replace the default suggested "sao" with "sf", you
should also change sao_dir and sao_parms to sf_dir and sf_parms respectively.


Also, you may want to upgrade to PL16 which contains Garp 2.1 and several Y2K
fixes.

Steve Chiswell
Unidata User Support




On Fri, 30 Jun 2000, Devin Kramer wrote:

> I am attempting to get GARP v2.02 up and running fully  and I find
> myself  deep into the Garp_defaults file.
> After fixing up all the path info and some of the "keys" variables, I
> have our Satellite, Radar,  Upperair and Gridded data working fine, but
> I am stumped on the surface stuff.  It seems the sfc_keys do not work
> the same as say the modelkeys variable.  We, of course, use a different
> naming convention for all of our files then that suggested by UNIDATA
> but since it did not impact the use of our upper air data with GARP I
> figured it would not matter with the surface files either as long as
> I fixed up the sfc_keys parameter properly.  Here is an example filename
> for our METAR data:
> 
> sf0005w5.dat  -> this corresponds to the 5th week of May in the year
> 2000 a week being defined as Sat-Fri (GMT)
> 
> Here is the lines I tried to use in Garp_defaults:
> 
> sfc_keys : "sf,sywd,sh,amos,mmos,nmos,ffg,nldn"
> sfc_labels : "METAR,Synoptic,Ship / Buoy,AVN MOS,MRF MOS,NGM MOS,Flash
> Flood,Lightning"
> 
> After some trial an error with different file names, it appears that the
> only "key" that will work for this data is "sao", which was actually the
> setting defined in the Garp_defaults file from the original s/w
> distribution.  Basically I can call the file just about anything as long
> as it has sao in it  and it works fine. This is the behavior I would
> actually expect, however, if I try to change the sfc_keys to look for my
> configurations string "sf", or any other string for that matter, instead
> of "sao" it does not work.   This appears to hold true for all of the
> sfc_keys. As long as I have the strings defined in the original
> Garp_defaults for sfc_keys  in my  filenames it works flawlessly.  Are
> these strings somehow hardcoded even though it appears they should be
> changeable.
> Note that I use nearly the same naming convention for my uperair files
> (e.b. ua0006w1.dat) and they work fine with the key set to "ua".
> 
> Suggestions, Ideas, etc. etc.????
> 
> Thanks in advance!
> Devin
> 
> 
> --
> --------------------------------------------------------
> Programmer Analyst    Department of Atmospheric Science
> University of California Los Angeles
> PH:(310)825-2418 FAX:(310)206-5219
> http://www.atmos.ucla.edu/geninfo/comp/how_to.html
> --------------------------------------------------------
> 
> 
> 
>