>From: weather <address@hidden> >Organization: NMSU/NSBF >Keywords: 199906301819.MAA16164 McIDAS LDM ROUTEPP Robert, >The Goes E/W composites are not being produced by the RoutePP >on psnldm.nsbf.nasa.gov. Everything is working fine on wxmcidas.nsbf.nasa.gov. >I can't find what the problem is on psnldm, I have checked batch.k >and it is correct, it is executable, the top files can be found via >the redirect and there is output being written to ROUTEPP.LOG, >with no apparent errors. However, no images are present. It >is probably something dumb again, but I am at a loss here. >Help! I logged onto psnldm as the user running your LDM and did the following: o edited your copy of batch.k and added a 'cd $MCDATA'; this is needed for things to work correctly but was not the cause of your problems I then logged in as 'mcidas' and did the following: cd workdata dmap.k SYSKEY.TAB WARNING: cannot examine directory /var/data/xcd: No such file or directory PERM SIZE LAST CHANGED FILENAME DIRECTORY ---- --------- ------------ ---------- --------- -rw- 24000 Jun 30 20:01 SYSKEY.TAB /var/data/ldm/mcidas 24000 bytes in 1 files dmap.k ROUTE.SYS WARNING: cannot examine directory /var/data/xcd: No such file or directory PERM SIZE LAST CHANGED FILENAME DIRECTORY ---- --------- ------------ --------- --------- -rw- 14080 Jun 30 19:39 ROUTE.SYS /var/data/ldm/mcidas 14080 bytes in 1 files route.k LIST route.k LIST S Pd Description Range Last Received Post Process C - -- ------------------------- --------- ------------ ---------- ------------ - s CI GOES-E/W IR Composite 80-89 none none none 3 s CV GOES-E/W VIS Composite 90-99 none none none 3 s CW GOES-E/W H2O Composite 70-79 none none none 3 LD NLDN Lightning Flashes 71-71 none none none 3 s MA Surface MD data default none none SFC.BAT 3 s N1 GOES-East IR/TOPO Composi 220-229 none none none 3 s N2 GOES-East VIS/TOPO Compos 230-239 none none none 3 s N3 GOES-West IR/TOPO Composi 240-249 none none none 3 s N4 GOES-West VIS/TOPO Compos 250-259 none none none 3 s N5 MDR/TOPO Composite 260-269 none none none 3 s N6 Mollweide IR/TOPO Composi 270-279 none none none 3 s N7 GOES-E/W IR/TOPO Composit 280-289 none none none 3 s N8 GOES-E/W VIS/TOPO Composi 290-299 none none none 3 NF Global Initialization Gri 101-102 none none GLOBAL.BAT 3 NG Early Domestic Products 1-2 none none ADDGRID.BAT 3 ... U1 Antarctic IR Composite 190-199 AREA0199 99181 1811 none 3 U2 FSL2 hourly wind profiler default none none none 3 U3 Manually Digitized Radar 200-209 AREA0204 99181 1906 MDR.BAT 3 U5 GOES-West Western US IR 130-139 AREA0131 99181 1918 GW-IR.BAT 3 U6 FSL2 6-minute Wind profil default none none none 3 U9 GOES-West Western US VIS 120-129 AREA0120 99181 1920 GW-VIS.BAT 3 UA Educational Floater I 160-169 AREA0163 99181 1931 none 3 UB GOES-West Western US H2O 170-179 AREA0173 99181 1917 GW-WV.BAT 3 UC Educational Floater II 60-69 AREA0066 99181 1934 none 3 UI GOES-East North America I 150-159 AREA0152 99181 1937 GE-IR.BAT 3 UR Research Floater 180-189 none none none 3 US Undecoded SAO Data default none none none 1 UV GOES-East North America V 140-149 AREA0144 99181 1939 GE-VIS.BAT 3 UW GOES-East North America H 210-219 AREA0210 99181 1937 GE-WV.BAT 3 UX Mollweide Composite IR 100-109 AREA0107 99181 1930 MOLL.BAT 3 UY Mollweide Composite H2O 110-119 AREA0118 99181 1936 none 3 The redirect.k was done to examine your set of REDIRECTions to make sure that you would be able to find SYSKEY.TAB and ROUTE.SYS. The dmap.k invocations were to make sure that SYSKEY.TAB and ROUTE.SYS could be found. The 'route.k LIST' was to find out if the generation of the composites was enabled: they were not! To correct the problem, I simply did: route.k REL N route.k REL C The process of generating the composites is: o an image is received by the LDM o the ldm-mcidas decoder, lwtoa3, is run to turn the compressed data into a McIDAS AREA file o the ldm-mcidas decoder looks in the routing table and sees that it is supposed to run PostProcess BATCH files (e.g. MDR.BAT, GW-IR.BAT, GW-VIS.BAT, etc.). The BATCH file _is_ run as is demonstrated by the log file, ~mcidas/workdata/ROUTEPP.LOG, having output from the various BATCH files. o The compositing routine, GOESCOMP, gets as input the routing table product code for the ouput data file (i.e. the composite), so it checks the routing table to make sure that it is, in fact, supposed to create the product. Since the routing table entries for composite images were SUSpended (product codes N1-N8 and C1-C3), no composites were created. o RELeasing these entries will tell GOESCOMP that the composites are to be created. After releasing the N and C entries in the routing table and waiting until new images arrived, I reran: route.k LIST CI GOES-E/W IR Composite 80-89 AREA0080 99181 2018 none 3 CV GOES-E/W VIS Composite 90-99 none none none 3 CW GOES-E/W H2O Composite 70-79 AREA0070 99181 2016 none 3 LD NLDN Lightning Flashes 71-71 none none none 3 s MA Surface MD data default none none SFC.BAT 3 N1 GOES-East IR/TOPO Composi 220-229 none none none 3 N2 GOES-East VIS/TOPO Compos 230-239 none none none 3 N3 GOES-West IR/TOPO Composi 240-249 AREA0240 99181 2018 none 3 N4 GOES-West VIS/TOPO Compos 250-259 none none none 3 N5 MDR/TOPO Composite 260-269 AREA0260 99181 2005 none 3 N6 Mollweide IR/TOPO Composi 270-279 none none none 3 N7 GOES-E/W IR/TOPO Composit 280-289 AREA0280 99181 2018 none 3 You can see that a number of the composites have now been created, so the compositing is now working as it should. >Thanks, Later... Tom >From address@hidden Wed Jun 30 14:28:16 1999 I must be losing it. I looked in my redirects and never saw the error with SYSKEY.TAB and ROUTE.SYS. I certainly know you can't have the products suspended. I think they come suspended by default and I never released them. The scary thing is I looked at this for three days before e-mailing you. Thanks for the help, Robert
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.