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

20000925: Use of GEMPAK with case studies, RUC2 etc.

Glenn,

There is an example of ntl.case in the 5.4 distribution as:
$NAWIPS/scripts/soosac/ntl.case.
This isn't my script, but you can use it as a guide.
ntl.case is just a script to set environmental
variables for data locations (specific to each case) rather than
the realtime data locations- before launching ntl. Typically,
for the Unidata distribution, the environmental variables referenced
in $GARPHOME/config/Garp_defaults are: $GEMDATA, $SAT, $NIDS, $HDS.
Generally these are set when you source Gemenviron....however, since you 
would probably have each case in its own data tree, you would
want to reset those locations for an ntl session- whereafter all the 
application launched from that ntl would inherit those values.
You may want a separate ntl.case for each separate case study.

RUC2 is not broadcast on NOAAPORT. Only the RUC 80km grid 211 is on NOAAPORT.
The RUC2 grids are on the OSO ftp server in the /ncepe directories.

All fdf functions which appear in the Garp pulldowns are defined in
the $GARPHOME/fdf/scalar and vector directories. These functions are specific to
the individual model names and the modelkeys used in 
$GARPHOME/config/Garp_defaults file.
In the $GARPHOME/fdf/scalar(and vector) directories are modelkey specific 
directory
names, eg:
$GARPHOME/fdf/scalar/ruc211/general/MSLPress_mb_MAPS_Reduction

The ruc211 directory is specific to the ruc211 modelkey used in
$GARPHOME/config/Garp_defaults. If you name your grids something
other than ruc211, then those directory names will have to
reflect the model keys you are using. If there is no subdirectory under fdf
for the modelkey you are using, then the "default" directory is used-
which won't have the MAPS specific macros.

You can decode archived data into individual case trees for each data set. 
The locations that you chose to decode the data into should follow the
same structure for each case, so that the $GARPHOME/config/Garp_defaults
file locations can be represented by environmental variables I mentioned above.
It is possible to use a different Garp_defaults file if necessary. THis
file location is defined in the $NAWIPS/Gemenviorn files as GARP_PATH.
If you need different data set names (model keys etc), then you could use your n
tl.case script to redefine that variable as well for garp menus specific
to that case.

Steve Chiswell





>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200009251809.e8PI9bb15032

>
>
>Steve,
>Finally got the systems config right around here and garp is running.
>Several questions:
>
>1) I thought there was a MAPS sfc mapping function for use with the RUC.
>Only a SLP options is displayed on my system.  Do I have to set anything to
>have it as an option in the model plan projection?
>2) where is ntl.case?  Is that part of your distribution.  I can't seem to
>find it.
>3) Speaking of the RUC. is there not a grib 236 or 7 grid now avbl. at 40km
>I've included that grid KWBH (i believe) in my paqct but it is not being
>found.  Thanks
>
>4) I'm going to grab  raw NOAAPort data from our archives (yes, we are now
>finally archiving ALL noaaport NWS TG data), and I will send them to the
>decoders for display in garp. (I'll set the clock with ntl.case).  Would I
>call the dc style decoders?  Or, which should I call (i.e., what
>directories are they located?)    Thanks for your patience......
>
>Thanks,  Glenn
>
>