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

[McIDAS #JRF-883135]: problem: old data showing on mcidas 2006

Hi Steve,

re: check ADDE setup for RTIMAGES to see where you are looking for the images

> This showed my problem. My initial config. of ldm and mcidas was that I used 
> the ldm-
> mcidas-pqact.conf.all example that came with ldm which had data being 
> decompressed to
> data/mcidas and to several gempak subdirectories. I had then modified 
> slightly the
> LSSERVE.BAT to look in those gempak directories.
> I then later took out the entries in the pqact.conf that were putting data in 
> the gempak
> subdirs.

OK, I thought the problem might be something like this.

> I tried changing the RTIMAGES section in LSSERVE.BAT to use 
> /usr/local/ldm/data/mcidas/
> but this had the effect of showing all types of images when I went to see a 
> GE-VIS image
> loop.

The key is in creating a regular expression for the DIRFILE= keyword that
includes just the images you are interested in for a particular dataset.

> My guess is that I have to put a file pattern with the appropriate AREA file 
> and number
> wildcard but I couldn't find an example or list of the AREA files that go 
> with each type of
> image.

If you are currently filing the UNIWISC images using the McIDAS routing table
(ROUTE.SYS) concepts, the simplest way to configure ADDE datasets is to _not_
use the DIRFILE= keyword syntax.  Instead, you would use a DSSERVE invocation
that listed the beginning and ending AREA file numbers to include in a set.
I have attached a McIDAS BATCH file that contains the DSSERVE commands you
can use to define all of the RTIMAGES datasets using the AREA file numbers

> I would like to just have all the images decompress in /usr/local/ldm/mcidas
> (as it is now) and have McIDAS read from there but if that is not the 
> recommended
> or preferable way anymore then I would like to stop the data being 
> decompressed
> to ldm/data/mcidas but then what would I put in the LOCAL.NAM ?

The "typical" setup anymore when using routing table concepts is to configure
the LDM to decompress the UNIWISC images into the ~ldm/data/mcidas directory.
Here is the single action ~ldm/etc/pqact.conf action that will do this for

# Example of decoding UW datastream imagery (GOES and CIMSS products) using
# McIDAS-X routing table for product naming and possible execution of ROUTE
# PostProcess BATCH files.

UNIWISC ^pnga2area Q. (..) (.*) (.*) (.*) (.*) (........) (....)
        PIPE    -close
        pnga2area -vl logs/ldm-mcidas.log
        -a etc/SATANNOT
        -b etc/SATBAND
        -d data/mcidas -r \1,\2

For this to work, you must copy ROUTE.SYS and SYSKEY.TAB from your McIDAS
distribution to the ~ldm/data/mcidas directory.  Of course, this directory
must be readable and writable by both 'ldm' and 'mcidas'.

After copying the files, you need to "teach" McIDAS how to find the routing
table and system key table (SYSKEY.TAB):

<as 'mcidas'>
cd ~mcidas/workdata
cp ROUTE.SYS ~ldm/data/mcidas
cp ~mcidas/data/SYSKEY.TAB ~ldm/data/mcidas

redirect.k ADD ROUTE.SYS \"/usr/local/ldm/data/mcidas
redirect.k ADD SYSKEY.TAB \"/usr/local/ldm/data/mcidas

You have the option of either running these REDIRECT commands by hand,
or including them in your ~mcidas/data/LOCAL.NAM file.  I recommend
the latter approach.

The next thing you must do is "teach" McIDAS how to find the AREA files
that the LDM actions will create.  This is also done using the REDIRECT
command, or, better yet, by including the appropriate entries in
your ~mcidas/data/LOCAL.NAM file.

By the way, McIDAS v200[56] comes with shell scripts that you can run
to configure McIDAS and McIDAS-XCD:

mcxconfig -> configure McIDAS
xcdconfig -> configure McIDAS-XCD

I recommend using these scripts as they lead you through the process.
You may still need to edit ~mcidas/data/LOCAL.NAM, ~mcidas/data/LSSERVE.BAT,
and ~mcidas/data/LOCDATA.BAT, but the rest of the steps (copying, etc.) will
be done for you.

> Right now I have the data being decompressed in both the ldm/data/mcidas dir.

Very good.

> (the
> syskey.tab and route.sys are being updated and they are readable and 
> writeable to the met
> group which mcidas is a member of)


> and I have the data being decompressed in the gempak subdirs also.

OK.  The reason I added the two different ways of decoding the images in the
ldm-mcidas-pqact.conf example files was for the convenience of both McIDAS
and GEMPAK users.  Also, since McIDAS does not care about how a file is
named, one can more easily setup stores of more than 10 files of each
type of image (e.g., GOES-East VIS, IR, 3.9, etc.) using the DIRFILE=
approach of DSSERVE.  The only downside to using this approach is the
inability to use the routing table to kick off processing of an image
after it is received.  The typical PostProcessing is compositing the
East and West images of the same type, and compositing VIS and IR images
with topography images.  If you are not interested in these composite
images, then filing of the images under the ~ldm/data/gempak directory
tree and creation of ADDE datasets using the DIRFILE= approach with
DSSERVE is the best option.  This is why the DSSERVE.BAT file in the
McIDAS distribution is setup the way that it is.

> FYI, the LOCAL.NAM was configured to use /usr/local/ldm/data/mcidas and
> dmap.k AREA
> did show the proper listing.

Editing LOCAL.NAM entries is the first step in "teaching" McIDAS how
to find the images.  The second mandatory step is using the REDIRECT
command to make those settings active:

<as 'mcidas'>
cd ~mcidas/workdata
-- after editing ~mcidas/data/LOCAL.NAM if needed
redirect.k REST LOCAL.NAM

> Thanks for the help.

No worries.  Please check the attached McIDAS BATCH file, OLDDSSERVE.BAT
and let me know if you have any questions.


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: JRF-883135
Department: Support McIDAS
Priority: Normal
Status: Closed

Description: Binary data

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.