This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: address@hidden (Chris Hennon) >Organization: Ohio State >Keywords: 200009111601.e8BG1gb11030 ldm-mcidas Chris, >Here's my pqact.conf entry that works for CIMSS sounder imagery: > ># CIMSS Cloud Top Pressure - McIDAS product code CA >MCIDAS ^pnga2area Q. CA .... (.*) (.*) (.*) (........) (....) > PIPE -close /usr/local/ldm/decoders/pnga2area > -a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT > -b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND > data/goes_sounder/\3/ctp/CTP_\4_\5 OK, this looks acceptable for the Cloud Top Pressure CIMSS product. >Here is my pqact.conf entry that doesn't work (i.e. nothing is written to >the directory I specified) for Unidata/Wisconsin GOES imagery: > ># Regular Unidata-Wisconsin Imagery >MCIDAS ^pnga2area Q1 .. .... (.*) (.*) (.*) (........) (....) > PIPE -close /usr/local/ldm/decoders/pnga2area > -a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT > -b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND > data/images/test/\3/\4_\5 This looks OK as well assuming that the directory data/images/test is writable by the user running the LDM. How about specifying that you want verbose logging so we can what pnga2area has to say for itself: # Regular Unidata-Wisconsin Imagery MCIDAS ^pnga2area Q1 .. .... (.*) (.*) (.*) (........) (....) PIPE -close /usr/local/ldm/decoders/pnga2area -a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT -b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND -vxl /usr/local/ldm/logs/satarea.log data/images/test/\3/\4_\5 >Here is my pqact.conf entry for LWTOA3: > >MCIDAS ^LWTOA3 (...) .* > PIPE -close > /usr/local/ldm/decoders/lwtoa3 -d /usr/local/ldm/data/satarea -l >/usr/local/ldm/logs/satarea.log -v I used the logging location from this in the suggestion to add logging to the pnga2area invocation. >I just tried dumping the images into a test directory but nothing gets >written there. Let me know if you need any more information. We need to know if pnga2area is exiting early. If it is, you would see 'broken pipe' messages in ~ldm/logs/ldmd.log. If that is not happening, I will be very suprised to say the least since a notifyme to your machine shows that you are receiving the PNG compressed GOES images from the Unidata-Wisconsin stream: notifyme -vxl- -o 3600 -f MCIDAS -h twister.sbs.ohio-state.edu Sep 12 21:05:23 notifyme[15060]: Starting Up: twister.sbs.ohio-state.edu: 20000912200523.902 TS_ENDT {{MCIDAS, ".*"}} NOTIFYME(twister.sbs.ohio-state.edu) returns OK Sep 12 21:05:23 notifyme[15060]: NOTIFYME(twister.sbs.ohio-state.edu): OK Sep 12 21:05:25 notifyme[15060]: d540b89b422cf7635a02ff7b1f2798f4 466648 20000912203155.534 MCIDAS 000 LWTOA3 160 DIALPROD=UA 256 203152 Sep 12 21:05:25 notifyme[15060]: c51ea02121d625a6d860dd7e50f4ecb3 347850 20000912203206.137 MCIDAS 000 pnga2area Q1 UA 160 GOES-8_IMG 0.65um 1km 20000912 2015 Sep 12 21:05:25 notifyme[15060]: fa343961b6514a95883c619e516b206b 444332 20000912203409.543 MCIDAS 000 LWTOA3 60 DIALPROD=UC 256 203357 Sep 12 21:05:25 notifyme[15060]: 2a7bde507a7b799928fe7238feef4fa9 338598 20000912203450.964 MCIDAS 000 pnga2area Q1 UC 60 GOES-8_IMG 0.65um 1km 20000912 2015 Sep 12 21:05:25 notifyme[15060]: bccd66f8f09a895a433086f085d40caf 1473104 20000912203548.014 MCIDAS 000 LWTOA3 150 DIALPROD=UI 256 203527 After we verify that there are 'broken pipe' messages in ldmd.log, we need to examine verbose pnga2area log output to find out why it is exiting early. Tom