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

20021122: running RSMAS IMGLIST/IMGCOPY scripts from 'mcidas' account (cont.)

>From: Angel Li <address@hidden>
>Organization: U Miami/RSMAS
>Keywords: 200211150406.gAF46PL16731 McIDAS LDM ldmd.conf RTNEXRAD NEXRCOMP

Angel,

re: setup sapodilla to ingest/decode NEXRAD, NEXRCOMP images
>That would be nice. I would like to get away from software someone else 
>wrote to deal with the NNEXRAD images.

OK.

>For now, we are just interested in the Miami and Key West radars.

I logged onto sapodilla and set it up to ingest all products for
all Florida NEXRADs (JAX, EVX, MLB, BYX, TLH, AMX, and TBW).  This was
done through the following request line in your ldmd.conf file:

request NNEXRAD "/p...(AMX|BYX|EVX|JAX|MLB|TBW|TLH)" f5.aos.wisc.edu

I also setup your machine to ingest/decode all of the composites in the
FNEXRAD datastream:

request FNEXRAD "^pnga|rad/"    atm.geo.nsf.gov

(I had to configure atm.geo.nsf.gov to allow you to get FNEXRAD products)

I added corresponding processing entries to your pqact.conf file:

#########################################################################
#
# NEXRAD Level III products
#
NNEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        data/radar/NEXRAD/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

#########################################################################
#
# FNEXRAD NEXRAD composites
#

# NEXRCOMP 6 km National BREF mosaic
FNEXRAD ^pnga2area Q5 (RL) (.*) (.*) (.*) (.*) (........) (....)
        PIPE    -close
        decoders/pnga2area -v
        data/radar/NEXRCOMP/6KN0R-NAT/\4_\6_\7

# NEXRCOMP 10 km National RCM mosaic
FNEXRAD ^pnga2area Q5 (RN) (.*) (.*) (.*) (.*) (........) (....)
        PIPE    -close
        decoders/pnga2area -v
        data/radar/NEXRCOMP/10KRCM-NAT/\4_\6_\7

# NEXRCOMP 1 km Regional BREF mosaic
FNEXRAD ^pnga2area Q5 (RO) (.*) (.*) (.*) (.*) (........) (....)
        PIPE    -close
        decoders/pnga2area -v
        data/radar/NEXRCOMP/1KN0R-FLT/\4_\6_\7

# PNG compressed radar composites in GINI format
FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....)
        PIPE    -close
        decoders/pngg2gini -v
        data/radar/NEXRCOMP/\1/\2/\2_\3_\4


I setup scouring of these data files through two crontab actions for 'ldm':

# Scour NEXRAD Level III products
#
15 * * * * util/prune_nexrad.csh /ldm/data/radar/NEXRAD 20 >/dev/null 2>&1
#
# Scour NEXRCOMP composites
#
11,30 * * * * util/prune_nexrcomp.csh /ldm/data/radar/NEXRCOMP 20 >/dev/null 
2>&1

The scouring scripts that are being run, prune_nexrad.csh and
prune_nexrcomp.csh, were grabbed from the UPC and put in the ~ldm/util
directory (which I also added to the PATH of the user 'ldm').  I then
edited these scripts to match the setup on sapodilla:

o the top level directory for all IDD radar products is /ldm/data/radar

o the top level directory for the NEXRAD Level III products is
  /ldm/data/radar/NEXRAD

o the top level directory for the NEXRAD Level III composites is
  /ldm/data/radar/NEXRCOMP

I setup the scours to keep 20 of each NEXRAD Level III product for each
station except Miami (AMX) which will have 60.  I also setup scouring
of the composite images to keep 20 each.  Changing the number of images
that are kept is easily done by modifying the second parameter in each
crontab entry.

Finally, I setup McIDAS to be able to look at all of the data through
ADDE.  I did this by:

<as 'mcidas'>
cd data

edited LSSERVE.BAT and incorporated new definitions for the v2002 DSSERVE.BAT
file:

o added definition for the CIMSS dataset (images already in the
  Unidata-Wisconsin broadcast)

o added definitions for the RTNEXRAD dataset.  Modified these entries to
  use the configuration file UMNEXR.CFG which I created in ~mcidas/workdata.

o added definition for the NEXRCOMP dataset and modified the DIRFILE= 
  to match where data is being written on your system

o comment out definitions for the RTNIDS and RTNOWRAD datasets
  (these are from WSI and are not free)

cd ~/workdata

made the entries in LSSERVE.BAT active for 'mcidas':

batch.k LSSERVE.BAT

Now, you have local access to all of the NEXRAD products and composites
that are in the Unidata IDD.  To give these a whirl, try doing the
following as 'mcidas':

<login as 'mcidas'>
cd workdata

mcidas -config

Through the GUI that will popup, select the size of the frames you want
in your McIDAS session, select that you want the MCGUI to start
automatically, and select the radiobutton that says to save these
settings.  A McIDAS-X session should now start with the MCGUI
interface.

In the MCGUI, click on the ADDE Client Routing Config button (the
button just to the right of the one with the big red Z.  This pops up
an interface that lets you point at a variety of machines for a variety
of data types.  If you click on the IMAGE tab, you should select
LOCAL-DATA for all of the datasets: CIMSS, NEXRCOMP, RTNEXRAD, and
TOPO.  Choose the only non-LOCAL-DATA option for the AMRC and ME7
datasets.  Finally, choose one of the servers in the list for GINICOMP,
GINIEAST, and GINIWEST.  Leave the POINT and TEXT selectors to
LOCAL-DATA, and change the RTGRIDS to point at one of the servers in
the list (like papagayo.unl.edu).  When finished, click on the Update
and Exit button.

Now try loading images from one of your local datasets:

Click on:

  Display
     |___ Imagery

and select NEXRCOMP as the type of image data you want to look at.
Try loading any of the NEXRCOMP images from the list.

From the same Display -> Imagery selection, move to RTNEXRAD.  From
three try plotting images/loops from any of the NEXRADs you are now
ingesting.

etc.

Note: any of the products being ingested can be turned off either in
ldmd.conf or in pqact.conf.  I setup everything so you could get a good
idea of what was possible.

Last thing: have you considered installing the ADDE remote server?
This would make remote access to your datasets possible.  This can be
very useful for ADDE-enabled access to data from other machines on your
network and, if you decided to participate in the set of cooperating
servers across the US, others in the Unidata community.

Tom