>From: Eirh-Yu Hsie <address@hidden> >Organization: CU/CIRES >Keywords: 200409071813.i87IDevq001014 ldm-mcidas pnga2area Hsie, >Beginning from last week, the image decoder "pnga2area" and "old McIDAS decoder >with ROUTE PostProcess BATCH files" generate different file size. From the >/home/ldm/etc/pqact.conf: > ># ># Example of decoding UW datastream imagery (GOES and CIMSS products) using ># McIDAS-X routing table for product naming and possible execution of ROUTE ># PostProcess BATCH files. ># >MCIDAS ^pnga2area Q. (..) (.*) (.*) (.*) (.*) (........) (....) > PIPE > -close pnga2area > -l logs/ldm-mcidas.log > -a decoder/etc/SATANNOT > -b decoder/etc/SATBAND > -d data/mcidas -r \1,\2 >... >... ># UW Mollweide composite (IR & WV) >MCIDAS ^pnga2area Q. (UX) (.*) (.*)_IMG (.*) (.*) (........) (....) > PIPE -close > pnga2area -vl logs/ldm-mcidas.log > -a decoder/etc/SATANNOT > -b decoder/etc/SATBAND > data/sat/mcidas/MOLLWEIDE/24km/IR/IR_\6_\7 > >MCIDAS ^pnga2area Q. (UY) (.*) (.*)_IMG (.*) (.*) (........) (....) > PIPE -close > pnga2area -vl logs/ldm-mcidas.log > -a decoder/etc/SATANNOT > -b decoder/etc/SATBAND > data/sat/mcidas/MOLLWEIDE/24km/WV/WV_\6_\7 > >... >meiyu:[53]% ls -l /wrk/data/sat/mcidas/MOLLWEIDE/24km/WV/WV_20040907_1500 >-rw-r--r-- 1 ldm unidata 225088 Sep 7 10:35 >/wrk/data/sat/mcidas/MOLLWEIDE/24km/WV/WV_20040907_1500 >meiyu:[54]% areaInfo /wrk/data/sat/mcidas/MOLLWEIDE/24km/WV/WV_20040907_1500 >/wrk/data/sat/mcidas/MOLLWEIDE/24km/WV/WV_20040907_1500 >WV_20040907_1500 GOES-8 1km >meiyu:[55]% ls -l /wrk/data/mcidas/AREA0114 >-rw-rw-r-- 1 ldm unidata 33556032 Sep 7 10:35 /wrk/data/mcidas/AREA01 > 14 >meiyu:[56]% areaInfo /wrk/data/mcidas/AREA0114 >/wrk/data/mcidas/AREA0114 >WV_20040907_1500 GOES-8 1km > >They are more than 10 times bigger with the old way of decoding??? I just verified that the same thing is happening on two different kinds of systems maintained by the UPC: Sun Solaris SPARC 5.9 and Fedora Core Linux 1. The cause of the problem is unknown to me at this time. I will need to dig into pnga2area as soon as I am able. This may not be for a few days, however, since I am currently in Sao Paulo, Brazil, and getting the time to review code and come up with a fix will be hard to find until I return to Boulder. The really strange thing about the big files is that they seem to be OK, or at least I can list out information from them with no problems!? Thanks for bringing this problem to my attention! I will attempt to get to the problem as soon as I am able. Cheers, 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.
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.