20000119: MCIDAS NLDNPLT command error (cont.)

>From: Michael Voss <address@hidden>
>Organization: SJSU
>Keywords: 200001181849.LAA08980 McIDAS-X NLDNPLT

Mike,

re: ~mcidas/.mcenv entries
>I did this yesterday...?

I see the contents of ~mcidas/.mcenv being:

umask 002
MCDATA=/export/home/mcidas/workdata
MCPATH=${MCDATA}:/export/home/mcidas/data:/export/home/mcidas/help
MCGUI=/export/home/mcidas/bin
MCTABLE_READ="${MCDATA}/MCTABLE.TXT;/export/home/mcidas/mcidas/data/ADDESITE.TXT"
MCTABLE_WRITE="/export/home/mcidas/mcidas/data/ADDESITE.TXT"
PATH=${MCGUI}:/usr/openwin/bin:/opt/SUNWspro/bin:/usr/ccs/bin:/usr/bin:/usr/local/bin:/usr/ucb
XCD_disp_file=$MCDATA/DECOSTAT.DAT
export MCDATA MCPATH MCGUI MCTABLE_READ MCTABLE_WRITE PATH XCD_disp_file
cd $MCDATA

MCTABLE_READ and MCTABLE_WRITE should be:

MCTABLE_READ="/export/home/mcidas/mcidas/data/MCTABLE.TXT"
MCTABLE_WRITE="/export/home/mcidas/mcidas/data/MCTABLE.TXT"

You have an extra path in your MCTABLE_READ: ${MCDATA}/MCTABLE.TXT;

re: LSSERVE.BAT
>OK, I did that. I must have missed something in the last email.

OK.

>question: If these AREA's were not defined correctly, how come the data was
>filling up the AREA's, i.e., 5200-5225, and I could access them from my user
>(not mcidas) F-Key menu?
>(oh, I guess because these definitions are for ADDE)

Right.  These definitions are for ADDE.  The name space for the AREA
files decoded by the ldm-mcidas AREA decoder, lwtoa3. 'lwtoa3' reads
the McIDAS routing table, ROUTE.SYS, IF IT EXISTS to find out how it
should name its output files.  If ROUTE.SYS does not exist (or is not
readable by the user running the LDM), then the output files will be
named with defaults.  The defaults are such that a system would keep
only 6 of the Manually Digitized Radar products and 4 each of all other
images in AREA format.

Right now, the setup for McIDAS is rather klunky: 'mcidas' has to
manage both the routing table AND the ADDE data set resolution table
(~mcidas/workdata/RESOLV.SRV).  The management of ROUTE.SYS is, as you
know, done by ROUTE; the management of RESOLV.SRV is done by DSSERVE.

>><edit batch.k and set MCDATA, etc. like you did in mcscour.sh and xcd_run)
>>
>
>batch.k is some strange format (binary?), how can I  edit it????

My stupidity!  ~mcidas/bin/batch.k is the actual McIDAS BATCH executable.
The script batch.k that you want to edit is distributed with the ldm-mcidas
pacakge.

>From address@hidden  Wed Jan 19 13:09:57 2000

>RE: batch.k file: I edited the old one which was in ~ldm/ldm-5.0.2/bin
>(old ldm).

OK.  In order to protect this file from disappearing when you do an LDM
upgrade, I recommend moving it to ~ldm/decoders.

>We'll see if this works. Not sure why the one from
>~mcidas/bin is of strange format, isn't just a script?

Again, my stupidity (I should stop answering emails late at night).

>Feel free to log in and see what else I've mangled (:

I did logon to check out the .mcenv contents.  While on, I verified
that ROUTE PostProcessing is also taking place as it did before:

vortex:~/workdata>route.k LIST
S Pd         Description         Range       Last      Received  Post Process C
- -- ------------------------- --------- ------------ ---------- ------------ -
  CI GOES-8/9 IR Composite       80-89   AREA0088     00019 2039     none     3
  CV GOES-8/9 VIS Composite      90-99   AREA0099     00019 2040     none     3
  CW GOES-8/9 H2O Composite      70-79   AREA0072     00019 2039     none     3
  LD LIGHTNING DATA             default  MDXX0079     00019 2036 NLDN.BAT     3
s MA Surface MD data            default  MDXX0010     99182  630 SFC.BAT      3
  N1 GOES-8 IR/TOPO Composite   220-229  AREA0221     00003 2237     none     3
  N2 GOES-8 VIS/TOPO Composite  230-239  AREA0234     00003 2239     none     3
  N3 GOES-9 IR/TOPO Composite   240-249  AREA0242     00003 2217     none     3
  N4 GOES-9 VIS/TOPO Composite  250-259  AREA0250     00003 2218     none     3
  N5 MDR/TOPOGRAPHY Composite   260-269  AREA0268     00003 2206     none     3
  N6 Mollweide/Topography comp  270-279  AREA0275     00003 2231     none     3
  N7 GOES-8/9 IR/TOPO Composit  280-289  AREA0287     00019 2039     none     3
  N8 GOES-8/9 VIS/TOPO Composi  290-299  AREA0297     00019 2041     none     3
 ...

The other thing I did was to exercise your remote ADDE server installation.
I did this as follows:

<in a McIDAS-X session here at Unidata>
DATALOC ADD RTIMAGES VORTEX.SJSU.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           25    GOES-West Western US IR
GW-IRTOPO       10    GOES-West IR/TOPO Composite
GW-VIS          26    GOES-West Western US VIS
GW-VISTOPO      10    GOES-West VIS/TOPO Composite
GW-WV           25    GOES-West Western US H2O
MDR             10    Manually Digitized Radar
MDRTOPO         10    MDR/TOPO Composite
MOLL-IR         24    Mollweide Composite IR
MOLL-IRTOPO     10    Mollweide IR/TOPO Composite
MOLL-WV         24    Mollweide Composite H2O
RESFLOATER      10    Research Floater

DSINFO -- done

IMGLIST RTIMAGES/GE-VIS.ALL
Image file directory listing for:RTIMAGES/GW-VIS
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
   1  G-10 IMG      18 JAN 00018  19:00:00    24  137 1
   2  G-10 IMG      18 JAN 00018  20:00:00    24  137 1
   3  G-10 IMG      18 JAN 00018  21:00:00    24  137 1
   4  G-10 IMG      18 JAN 00018  22:00:00    24  137 1
   5  G-10 IMG      18 JAN 00018  23:00:00    24  137 1
   6  G-10 IMG      19 JAN 00019  00:00:00    24  137 1
   7  G-10 IMG      19 JAN 00019  01:00:00    24  137 1
   8  G-10 IMG      19 JAN 00019  02:00:00    24  137 1
   9  G-10 IMG      19 JAN 00019  03:00:00    24  137 1
  10  G-10 IMG      19 JAN 00019  14:00:00    24  137 1
  11  G-10 IMG      19 JAN 00019  15:00:00    24  137 1
  12  G-10 IMG      19 JAN 00019  16:00:00    24  137 1
  13  G-10 IMG      19 JAN 00019  18:00:00    24  137 1
  14  G-10 IMG      19 JAN 00019  19:00:00    24  137 1
  15  G-10 IMG      19 JAN 00019  20:00:00    24  137 1
  16  G-10 IMG      17 JAN 00017  22:00:00    24  137 1
  17  G-10 IMG      17 JAN 00017  23:00:00    24  137 1
  18  G-10 IMG      18 JAN 00018  00:00:00    24  137 1
  19  G-10 IMG      18 JAN 00018  01:00:00    24  137 1
  20  G-10 IMG      18 JAN 00018  02:00:00    24  137 1
  21  G-10 IMG      18 JAN 00018  03:00:00    24  137 1
  22  G-10 IMG      18 JAN 00018  14:00:00    24  137 1
  23  G-10 IMG      18 JAN 00018  15:00:00    24  137 1
  24  G-10 IMG      18 JAN 00018  16:00:00    24  137 1
  25  G-10 IMG      18 JAN 00018  17:00:00    24  137 1
  26  G-10 IMG      18 JAN 00018  18:00:00    24  137 1
IMGLIST: done

IMGDISP RTIMAGES/GW-VIS EU=IMAGE STA=KLAX MAG=2 SF=YES REFRESH='EG;MAP X 5 
COUNTY=ALL;MAP VH 1 WID=2'

Looking good!  Then I checked out your McIDAS surface data:

DATALOC ADD RTPTSRC VORTEX.SJSU.EDU
SF 1
SFCPLOT T OLAY FRAME

Also looks good!

Tom

>From address@hidden  Wed Jan 19 14:43:02 2000

re: MCTABLE_READ, MCTABLE_WRITE
>Yes, thanks, I think I finally see the changes.....doh!!

re: move the script batch.k to ~ldm/decoders
>done...

re: looks good!

Thanks a bunch for all your help, I really appreciate it!! It looks
like were in business for awhile, at least until I mangle something
else.

Cheers,
Mike