19991026: Fkey menu GRID items and XCD decoding of GRIDded data (cont.)

>From: Myron Kowalski <address@hidden>
>Organization: Moravian College
>Keywords: 199910262043.OAA26544 McIDAS Fkey

Myron,

>I'll try it with the cron job first.
>
>should cron run out of mcidas or root or ldm?

I would run it out of the mcidas or ldm accounts, NOT root.

>Is it ok to run it once an hour (definitely before class starts)
>like so
>
>0 * * * * /users/mcidas/workdata/uwgrid.sh NG
>0 * * * * /users/mcidas/workdata/uwgrid.sh NF
>
>and now it looks like to files came in.

The way that UWGRID works (uwgrid.sh is a wrapper around the McIDAS
routine like mcscour.sh is a wrapper around routines needed to do data
scouring).  I would try running the script by hand a few times to get
the hang of it.  Also, if your McIDAS routing table has an entry for
products NF and NG (products that used to be in the Unidata-Wisconsin
datastream), UWGRID will determine whether or not it is supposed to do
the conversion based on whether or not the products are SUSpended.  If
they are not SUSpended (i.e. are RELeased), and if they have a ROUTE
PostProcess associated with them, then the PostProcess will be run.
This provides the same kind of action(s) that were available when the
grids came in in the Unidata-Wisconsin datastream.

>catwoman% grdlist.k RTGRIDS/ALL.ALL FORM=FILE
>DATASET NAME: RTGRIDS/ALL
> Dataset Position  Creation Date Max Grids         Directory Title
> ----------------  ------------- --------- -------------------------------
>...
>       80             1999300       2000   ALL  12Z NGM 0  HR<=VT<=24 HR
>       90             1999300       2000   ALL  12Z NGM 24 HR< VT<=48 HR

The NGM stuff should be in.  I would start by playing around with uwgrid.sh
for product NG:

<login as mcidas>
cd workdata
<edit uwgrid.sh and set McIDAS environment variables to match your
setup (just like was done for mcscour.sh)>
sh ./uwgrid.sh NG

The conversion process will use the notion of McIDAS file naming
and the cylinder range specified in the routing table for the product
that you are trying to produce.  I believe that your system is setup
like our default, so that the NGM grids will be put into GRID0001 and
GRID0002 and the AVN grids will be put into GRID0101 and GRID0102.
Running the script once-per-hour will cause the current GRID file
to change once-per-hour, but this should not matter given that
the System Key Table entry used by the Fkey menu will be changed to
reflect which file has the current model run.  The thing you lose is
having the previous model run available in the other GRID file.

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+