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.
Dave, The "Couldn't execute decoder..." message means that the execvp(2) system-call failed and returned back to the pqact(1) process. This usually indicates that it couldn't find the program (pnga2area) or that the format of the program wasn't recognized. I'll have to think some more. > On Oct 31, 2014, at 2:27 PM, Unidata LDM Support > <address@hidden<mailto:address@hidden>> wrote: > > Dave, > > Does the pnga2area(1) log file "logs/ldm-mcidas.log" indicate anything? > > Steve, > > Lots of unalarming messages like this: > > Oct 31 20:10:18 pnga2area[85533] NOTE: Starting Up > Oct 31 20:10:18 pnga2area[85533] INFO: output file pathname: > 1410311900_sve.mca > Oct 31 20:10:18 pnga2area[85533] NOTE: unPNG:: 1480762 4724568 3.1906 > Oct 31 20:10:18 pnga2area[85533] NOTE: Exiting > > — Dave Regards, Steve Emmerson Ticket Details =================== Ticket ID: JMJ-890556 Department: Support LDM Priority: Normal Status: Closed