20000803: McIDAS-X ADDE and LDM installation at Western Michigan(cont.)

>From: "John D. Tucker" <address@hidden>
>Organization: Western Michigan
>Keywords: 200007181435.e6IEZAT22632 McIDAS-X -XCD ADDE LDM install

Elen,

>Thanks Tom!

You are welcome.

>I don't need those areas on home7/ldm/mcidas/mcidas/data.  But how can I
>access the areas on s418/ilya2/mcidas/data by opening mcidas from the
>~/ldm/mcidas/mcidas?

I am not quite sure of exactly what you are asking.  When you are doing
your work, who are you logging in as?  If the answer is the user 'mcidas'
then the account is already setup to access the files in /ilya2/mcidas/data.
I set this up through file REDIRECTions:

REDIRECT ADD AREA6* "/ilya2/mcidas/data

If you are running McIDAS from some other account on s418, then you
would need to setup the same REDIRECTion from a running McIDAS-X session.

>Do I still need to use mcadde if I am using archived (not real time) data?

No, not at all.  If your login account has access to the directory in
which images exist (i.e., you can do an 'ls' and see the image files),
then you can "teach" McIDAS how to find them through a file REDIRECTion.
If this is your situation, you should make the REDIRECTion very specific.
For instance, do the following:

REDIRECT ADD AREA6* "/ilya2/mcidas/data

Do NOT do:


REDIRECT ADD AREA* "/ilya2/mcidas/data

as that tells McIDAS that it should look for ALL AREA files in this
directory.  This is typically NOT what you want, so be specific in your
REDIRECTions.

Before I delete the AREA files in ~mcidas/mcidas/data, I need to make
sure that you can access the ones in /ilya2/mcidas/data, AND that those
files are the ones you really want to work with.  The reason I say this
is that AREA6241 in /ilya2/mcidas/data is a different size from the
one in ~mcidas/mcidas/data.

Tom