20000927: AREA composite files for MCIDAS

>From: alan anderson <address@hidden>
>Organization: St. Cloud State
>Keywords: 200009271415.e8REFMb15528 ROUTE post processing

Alan-

>OK Don,  my first suspicions were that the composites were created 
>locally, but seeing them as a separate product in the routing table
>changed my mind.  

Yeah, that's sort of tricky.  You can use the ROUTEing table for things
other than the products in the datastream. The C1, C2, C3 and N* products 
are such beasts.  None of these were updating on your system.

>The products CI, CV and CW are not suspended, and the appropriate 
>.BAT files are listed in the post-process column of ROUTE LIST for
>the Goes E & W products.  

Okay.

>Those same .BAT files, (*-IR.BAT, *-VIS.BAT,  and *-WV.BAT) are found
>in the /home/mcidas/work directory of user mcidas.
>Their file dates show no evidence of recent editing, also, looking at 
>one of them, GW-VIS.BAT, shows just the two active lines for 
>NORTMAPR  and   GOESCOMP.

Okay, this is as it should be.

>The only thing I have done in the last few days was to set up the 
>BLIZZARD group of files in the ADDE system, so that our terminals
>could access them from our server rather than from your place.
>Tom sent me a note on how to set it up and I also looked at the 
>instructions on your web.  That part, the tutorial lessions which
>access the BLIZZARD files now works fine.

I saw the instructions Tom sent and this should not affect the
product creation.

>I suspect I must have done something else, but am at a loss. 

me, too. ;-)

>We are still running MCIDAS v. 7.503 on this machine (our ingest
>and ldm box) but we seldom run any MCIDAS sessions on it since
>we just use it for ingestion and decoding.  I know I need to 
>upgrade, but again, not sure why this problem should have just
>popped up.

Okay, I logged on to your machine and found that the file ROUTEPP.LOG
in ~mcidas/workdata was non-existant.  This is the file that output
from ROUTE PostProcess (PP) BATCH files get written to.  I'm not sure
why it disappeared, but I stopped and restarted your LDM and it was
created when the next McIDAS product arrived.  It looks like all your
post processing stopped on the 25th about 21Z so maybe that's when the
file went away.  It looks like the LDM was stopped and restarted since
then, so I'm surprised that ROUTEPP.LOG didn't get created again.

I'll let Tom know about this when he returns next week and he can
investigate further if need be.

Don