19991124: ADDE Server on Hurri

>From: "charles h. murphy" <address@hidden>
>Organization: Kean University
>Keywords: 199911241457.HAA14944 McIDAS ADDE

Charlie,

>I don't know if you remember when I was out for the User's
>Committee meeting and we were talking in your office about
>making images from datafiles or  something like that and
>you requested a radar image from my machine via ADDE and
>it issued an error.

I vaguely remember something like that, but you know that those brain
cells are pretty worn :-)

>We were both puzzled and then
>were were interrupted and then "beer" so it just
>slipped by.

There are way too many times when Friday afternoon impinges on
something interesting.  Oh, the social pressures.

>Well I think the problem was that this
>summer we had all our ip addresses changed and 
>althought I asked about proper procedure for the
>LDM I never thought about our ADDE server.

Right off to the top of my head, I can't see how changing IP addresses
would affect the ADDE setup.  As a general comment, if the LDM works,
then the ADDE remote server should work.

>       Just to give you an idea of the kind of fall
>I'm having it has taken two months for me to remember
>and figure out what was going on.  Any way the ip address
>for hurri.kean.edu is   131.125.22.20

OK.  I just pointed to your machine and verified that I can look at
GOES imager from it:

DATALOC ADD RTIMAGES hurri.kean.edu
DSINFO IMAGE RTIMAGES

        Dataset Names of Type: IMAGE in Group: RTIMAGES

Name         NumPos   Content
------------ ------   --------------------------------------
ANTARCTIC       10    Antarctic IR Composite
EDFLOATER-I     10    Educational Floater
EDFLOATER-II    10    Educational Floater II
GE-IR           10    GOES-East North America IR
GE-IRTOPO       10    GOES-East IR/TOPO Composite
GE-VIS          10    GOES-East North America VIS
GE-VISTOPO      10    GOES-East VIS/TOPO Composite
GE-WV           10    GOES-East North America H2O
GEW-IR          10    GOES-East/West IR Composite
GEW-IRTOPO      10    GOES-East/West IR/TOPO Composite
GEW-VIS         10    GOES-East/West VIS Composite
GEW-VISTOPO     10    GOES-East/West VIS/TOPO Composite
GEW-WV          10    GOES-East/West H2O Composite
GW-IR           10    GOES-West Western US IR
GW-IRTOPO       10    GOES-West IR/TOPO Composite
GW-VIS          10    GOES-West Western US VIS
GW-VISTOPO      10    GOES-West VIS/TOPO Composite
GW-WV           10    GOES-West Western US H2O
MDR             10    Manually Digitized Radar
MDRTOPO         10    MDR/TOPO Composite
MOLL-IR         10    Mollweide Composite IR
MOLL-IRTOPO     10    Mollweide IR/TOPO Composite
MOLL-WV         10    Mollweide Composite H2O
RESFLOATER      10    Research Floater

DSINFO -- done
IMGLIST RTIMAGES/GE-IR.ALL
Image file directory listing for:RTIMAGES/GE-IR
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
   1  G-8 IMG       24 NOV 99328  15:15:00    23   71 4
   2  G-8 IMG       24 NOV 99328  08:15:00    23   71 4
   3  G-8 IMG       24 NOV 99328  09:15:00    23   71 4
   4  G-8 IMG       24 NOV 99328  10:15:00    23   71 4
   5  G-8 IMG       24 NOV 99328  11:15:00    23   71 4
   6  G-8 IMG       24 NOV 99328  12:15:00    23   71 4
   7  G-8 IMG       24 NOV 99328  13:15:00    23   71 4
   8  G-8 IMG       24 NOV 99328  14:15:00    23   71 4
   9  G-8 IMG       24 NOV 99328  14:15:00    23   71 4
  10  G-8 IMG       24 NOV 99328  15:15:00    23   71 4
IMGLIST: done

I then loaded the latest image and had no problems.

I next decided to look at point source data, and this is what I found:

PTLIST RTPTSRC/PTSRCS.ALL FORM=FILE
Pos      Description                        Schema  NRows NCols  Date
------   --------------------------------   ------  ----- ----- -------
     7   SAO/METAR data for   23 NOV 1999   ISFC       72  4500 1999327
     8   SAO/METAR data for   24 NOV 1999   ISFC       72  4500 1999328
    17   Mand. Level RAOB for 23 NOV 1999   IRAB        8  1300 1999327
    18   Mand. Level RAOB for 24 NOV 1999   IRAB        8  1300 1999328
    19   Mand. Level RAOB for 25 NOV 1999   IRAB        8  1300 1999329
    27   Sig.  Level RAOB for 23 NOV 1999   IRSG       16  6000 1999327
    28   Sig.  Level RAOB for 24 NOV 1999   IRSG       16  6000 1999328
    29   Sig.  Level RAOB for 25 NOV 1999   IRSG       16  6000 1999329
    37   SHIP/BUOY data for   23 NOV 1999   ISHP       24  2000 1999327
    38   SHIP/BUOY data for   24 NOV 1999   ISHP       24  2000 1999328
    47   NGM MOS for day      23 NOV 1999   FO14       38   600 1999327
    48   NGM MOS for day      24 NOV 1999   FO14       38   600 1999328
    57   SYNOPTIC data for    23 NOV 1999   SYN         8  6000 1999327
    58   SYNOPTIC data for    24 NOV 1999   SYN         8  6000 1999328
    67   PIREP/AIREP data for 23 NOV 1999   PIRP       24  1500 1999327
    68   PIREP/AIREP data for 24 NOV 1999   PIRP       24  1500 1999328
    77   NLDN data for        23 Nov 1999   NLDN     1000  1000   99327
    78   NLDN data for        24 Nov 1999   NLDN     1000  1000   99328
    87   Hourly Prof data for 23 Nov 1999   WPRO       48    35   99327
    88   Hourly Prof data for 24 Nov 1999   WPRO       48    35   99328
    97   6-min Prof data for  23 Nov 1999   WPR6      480    35   99327
    98   6-min Prof data for  24 Nov 1999   WPR6      480    35   99328
PTLIST: Done

The listing shows that the lightning and wind profiler data decoders
are not current: the Date format is YYDDD instead of CCYYDDD.  I would
advise you to upgrade to the most recent version of the ldm-mcidas
decoders when you get a chance (before Dec. 31).  This date format is
not Y2K compatible.

>       I also have a question - when I installed McIDAS-X
>at home under Solaris X-86 the installation process put
>actual copies of all the executables in mcidas/bin, but
>on out Sparc machine they are hard links to the files
>in the installation directory.  Is this normal on the 
>X-86 machine?

No.  The only time that the files in ~mcidas/bin should not be links
are when ~mcidas/bin lie on a file system that is different from the
one where ~mcidas/mcidas7.6/src lives.  The other way that this can
happen if using gcc/f2c/mcfc to build the distribution is:

<login as 'mcidas'>
cd mcidas7.6/src
make mcx
make install.mcx
make clobber
make mcx

If ~mcidas subdirectories are all on the same file system, then this is
the way that the executable files in ~mcidas/bin can end up to be not
links.

One last thing.  The links that are made are hard links, not soft links.
Is it possible that you were expecting soft links and since you did not
see them that you assumed that the files were separate?

>Thanks,

I got your phone mail yesterday (working from home for the morning);
thanks for the good wishes.  We are having a dinner for 14 up at
Sugarloaf -- it promises to be a good time with lots of food, beer,
wine, and champagne.  The good thing is that we have enough space
(counting floor space) so that people can stay if they are not in shape
to drive back down the road.  I know that at least Mike and Tammy will
be staying.  Last year the day after Thanksgiving was so warm that we
could all go hiking up Bald Mountain in shorts and Tee shirts.  This
year doesn't promise to be so nice since there is currently a little
less than a foot of snow up at the house.

By the way, I just got back from 3 weeks in Australia.  It was _fantastic_!!

Have a great Thanksgiving!

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/*
+-----------------------------------------------------------------------------+