20020410: updating McIDAS and installing the ADDE remote server (cont.)

>From: Chris Herbster <address@hidden>
>Organization: Embry-Riddle University
>Keywords:  200203251603.g2PG36a11520 McIDAS ADDE LDM

Chris,

>Wow!  This would have taken me a year to get done, and it still
>wouldn't have worked right!  (-:

The procedure for getting things working seems really complicated, but
it is basically only three steps (I mused about this after sending
you the email yesterday):

1) you have to get the data first  (LDM)
2) you have to decode the data next (LDM pqact actions coupled with some
   McIDAS rules)
3) finally, you have to serve the data (McIDAS rules coupled with setting
   up an ADDE server in the OS)

So, the big picture is pretty simple.  The dirt is in the details :-)

>I'll reply to a few questions below....

Ready.

re: setting up ADDE

>I didn't realize how far off things were from what they are needed to
>be!  I can see a number of changes that you made that were
>show-stoppers for the server!  Thanks!

No problem.  The good news is that the remote ADDE server needs to be
setup once.  After that, everything is downhill.

re: LDM side setup

>Thanks again!  These are details that make perfect sense when I read
>them, but would have taken me forever to get complete (and correct!) -
>very cool.

I didn't mention that I found several typos in ~ldm/etc/pqact.conf that
I corrected.  These would have prevented the decoding of several types
of images that were being received by your machine.

>>   NOTE:  the cron file entry for 'ldm' says:
>>
>> # DO NOT EDIT THIS FILE - edit the master and reinstall.
>> # (/tmp/crontab.20792 installed on Tue Apr  9 19:29:26 2002)
>> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)

>I don't know of any master file myself.  I assume you used "crontab -e"
>which is what I use.

Yes, exactly.  I got worried when I saw the warning (which is in the
cron file) and didn't see any scouring actions.

>I generally keep a copy of the current crontab in
>the user's home directory just to be safe.  As best I can tell, this is
>a feature in Linux.  (-:  I'm sure there is a location on the disk that
>holds the "master", but I haven't found it yet....

I didn't find any master file either, and I did spend time looking (and
using the 'locate' utility).

re: data scouring

>As part of a research project we have been moving data to another disk
>(with a script I wrote), and have tried not to scour data.

AH HA!  This explains the mystery.

>We are then
>trying to make a backup, but this may be more work than necessary as we
>have been trying to focus on the case studies instead .... We did get
>pretty close to full just this morning (but we new that was happening
>and now there is plenty of room again).

OK.

re: I can't access supercell using ADDE from my UPC machine on either
ports 500 (ADDE uncompressed data transfers) or 503 (ADDE compressed
data transfers).

>I had thought that this machine was open through the firewall, but
>perhaps not all ports.  I'll follow up on this with our network folks,
>thanks.

OK, thanks.  It would be useful to be able to "look in" on supercell
from time-to-time.  This is the beauty of ADDE!

>Tom, thanks again for all this work!  This is very exciting to have
>this fixed!

No worries.

>We move to our new facilities next week.  Two new 30
>workstation classrooms (2GHz P4, 512 MB RAM), plus a new weather center
>with another 20+ of these systems!

Wow, muscle machines!  Excellent, especially for using the MetApps IDV!

>(Perhaps a spring break - beach -
>site visit is in order! (-:  Though most of the college kids have left
>town now.)

Yes sir!  For now, I will have to content myself with going skiing.
We should be heading up for the last time this season tomorrow.  Closing
for Winter Park (the resort several of us have season passes for) is
Sunday.  The really sad/scary thing is that the snowfall has been _way_
below "normal" this year.  It makes me start to worry about the coming
forest fires.

>Best to you and the rest!

Later...

Tom