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.
Hi Mike, As you likely know, I am logged onto the FIT LDM machine and am actively investigating why the ldm-mcidas 'pnga2area' decoder is not being run from the pattern-action file action: MCIDAS ^pnga2area Q. UI (.*) (.*) (.*) (.*) (........) (....) PIPE -close pnga2area -vl /home/ldm/data/gempak/logs/dcsat.log -a /home/ldm/etc/SATANNOT -b /home/ldm/etc/SATBAND /home/ldm/data/gempak/images/sat/goes13/\4/IR/IR_\5_\6 To test whether the 'pnga2area' binary (/home/ldm/decoders/pnga2area) works, I modified the pattern-action file (/home/ldm/etc/pqact.conf) to include FILEing of the original product in /home/ldm/data/gempak/images/sat/goes13/4km/IR (the directory that the action above is supposed to write into. As soon as I saw the receipt of a new GOES-13 IR image (I was running 'notifyme' to watch for the arrival of new MCIDAS (aka UNIWISC) image products), I ran the following by hand: cat data/gempak/images/sat/goes13/4km/raw/IR/IR_20120806_1945 | pnga2area -vl /home/ldm/data/gempak/logs/dcsat.log -a /home/ldm/etc/SATANNOT -b /home/ldm/etc/SATBAND /home/ldm/data/gempak/images/sat/goes13/4km/IR/IR_20120806_1945 This _correctly_ resulted in: - the creation of the log file /home/ldm/data/gempak/logs/dcsat.log with an entry that looks like it should: Aug 06 20:01:30 pnga2area[27118] NOTE: Starting Up Aug 06 20:01:30 pnga2area[27118] INFO: output file pathname: /home/ldm/data/gempak/images/sat/goes13/4km/IR/IR_20120806_1945 Aug 06 20:01:30 pnga2area[27118] NOTE: unPNG:: 1076666 4724488 4.3881 Aug 06 20:01:30 pnga2area[27118] NOTE: Exiting - the creation of the correctly decoded output file: -rw-r--r-- 1 ldm ldm 4724488 Aug 6 15:59 IR_20120806_1945 This experiment unequivocally demonstrates that there is no problem with the ldm-mcidas 'pnga2area' decoder. Now the question is why the standard GEMPAK action for decoding the image using 'pnga2area' is not working! To figure this out, I am implementing a new pattern-action file action that will log things like the PATH in-scope during the execution of the action; etc. I will get back to you and Steven when I learn more. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: KHY-214172 Department: Support ldm-mcidas Priority: Normal Status: Open