>From: Michael Voss <address@hidden> >Organization: SJSU >Keywords: 200009112351.e8BNpwb26866 ldm-mcidas Mike, >My first problem was that I left out the first 'a' in pnga2area...(see >below)...oops! :) Oops, I didn't see that in your previous email either. >Now I'm getting some of the areas decoded, but not all of them it >seems. My lastest entry in pqact.conf is: > >MCIDAS ^pnga2area Q. (..) (....) (.*) (.*) (.*) (........) (....) > PIPE -close > pnga2area > -a /usr/local/ldm/etc/SATANNOT -b /usr/local/ldm/etc/SATBAND > -d /data3/mcidas -r \1,\2 OK. This looks good if you copied SATANNOT and SATBAND to /usr/local/ldm/etc. >although, since I have mcidas in /export/home/mcidas/data, and I see >SATANNOT and SATBAND there I could look for them there with the -a and >-b. Yes, exactly. If your McIDAS installation was such that the HOME directory for 'mcidas' was /home/mcidas, you wouldn't need to specify the '-a' and '-b' flags at all. This was a semi-arbitrary decision on my part based on my recommendations for installing McIDAS-X under /home/mcidas. >I guess my question is should my old routing work with the new >decoder...it seems like it from the messages I've read in the support >archives? Yes, it should work correctly. One thing that I have found, however, is that IF you are decoding the CIMSS images (Q0 time indicator), and you are using routing concepts to name the files, you MUST add routing table entries for those products. Here is what to do to test your situation: <login as 'mcidas'> make sure that you have a REDIRECTion that points to the copy of ROUTE.SYS and SYSKEY.TAB that is located in the directory into which you are going to decode images cd workdata route.k LIST Is the routing table OK or is it munged? If it is OK, and if you don't have routing entries for the CIMSS products then you should add the entries: ftp ftp.unidata.ucar.edu <user> anonymous <pass> your email address cd pub/mcidas get CIMSS.BAT quit batch.k CIMSS.BAT If your routing table is munged, you can do one of two different things: o regenerate it from DROUTE.BAT o use the copy contained in the ldm-mcidas distribution If you use the one in the ldm-mcidas distribution, it should already have CIMSS product entries. If you regenerate a new one, then you should: cd workdata batch.k LROUTE.BAT <- the copy of DROUTE.BAT you should have made at McIDAS-X installation batch.k CIMSS.BAT >Here is a listing of my /data3/mcidas directory. I started the new >pqact.conf at 9:15 am. So, you can see the area files I would typically >get are not showing up, and I see nothing in the ~ldm/logs to indicate >any errors...? > >> Sat >total 510196 >-rw-rw-r-- 2 mcidas data 24000 Sep 12 09:54 SYSKEY.TAB >-rw-rw-r-- 2 ldm data 15104 Sep 12 09:54 ROUTE.SYS >-rw-r--r-- 1 ldm data 309280 Sep 12 09:50 AREA1150 >-rw-rw-r-- 1 ldm data 11909 Sep 12 09:49 ASUS1256 >-rw-r--r-- 1 ldm data 322320 Sep 12 09:49 AREA1140 >-rw-r--r-- 1 ldm data 242720 Sep 12 09:33 AREA1130 >-rw-r--r-- 1 ldm data 242800 Sep 12 09:31 AREA1110 >-rw-rw-r-- 1 ldm data 3669 Sep 12 09:20 FSUS2256 >-rw-r--r-- 1 ldm data 309200 Sep 12 09:15 AREA1100 >-rw-rw-r-- 1 ldm data 225088 Sep 12 09:06 AREA0206 >-rw-rw-rw- 1 ldm data 714096 Sep 12 08:19 AREA0097 >-rw-rw-rw- 1 ldm data 2439056 Sep 12 08:19 AREA5205 >-rw-rw-rw- 1 ldm data 714096 Sep 12 08:18 AREA0085 >-rw-rw-rw- 1 ldm data 2439056 Sep 12 08:18 AREA5003 >-rw-rw-rw- 1 ldm data 613456 Sep 12 08:16 AREA5103 This shows that you are getting the CIMSS images and that they are either correctly named from a routing table entry, or they are named using default AREA file numbers. Are your regular images numbered in the 5000s? >I'm not sure where to go from here. Given the pqact.conf action you included above, and given that you are receiving PNG compressed images, I suspect the routing table. Please do a route.k LIST from ~mcidas/workdata to see if the table is munged. If it is, follow the instructions above. Tom
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.