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 Dave, Based on discussions that Steve and I have been having regarding your report of several netCDF Perl decoders not running under LDM.6.13.x, I decided to try a simple experiment aimed at determining where the problem might lie. The experiment was to wrap the invocation of the netCDF perl decoder in a simple shell script, and change the LDM pattern-action file entry that executes 'metar2nc' via a PIPE to run the shell script instead. The problem I ran into was the need to install the PDL package(s) needed by your version of 'metar2nc'. Instead of continuing to march down this road for testing here, I decided to see if you would be willing to try the same test in your setup. The (very simple) idea is to create a shell script, say 'metar2nc.sh', in a directory in the PATH of the user running your LDM, and have it run 'metar2nc'. This is the very simple script that I created yesterday afternoon to run the test: #!/bin/sh # Announce script startup echo "metar2nc.sh: Starting up at `date -u +'%b %d %T'`" >> logs/metar2nc.log # Write the input product to a disk file. This makes sure that the # PIPE from 'pqact' will be emptied so that 'pqact' will not retry to # run the action if there is a failure suffix=`date -u +'%Y%m%d%H%M' cat > /tmp/metar2nc_input.$suffix # Run 'metar2nc' on the product received and saved mkdir -p data/dec_data/obs/metar cat /tmp/metar2nc_input.$suffix | metar2nc -t 30 -l logs -d data/dec_data/obs/metar etc/metar.cdl # Cleanup and exit rm -f /tmp/metar2nc_input.$suffix echo "metar2nc.sh: Exiting at `date -u +'%b %d %T'`" >> logs/metar2nc.log exit The before and after LDM pattern-action file actions to be used are: #----------------------------------------------------------------------------- # # PIPE actions for observational data and MOS # #----------------------------------------------------------------------------- # # METAR's #WMO ^S[AP].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9]) # PIPE metar2nc -t 30 -l logs -d data/dec_data/obs/metar etc/metar.cdl WMO ^S[AP].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9]) PIPE metar2nc.sh If you are willing to try this out under LDM-6.13.x, please let us know your results. Just so you know, Steve is still trying to figure out why your 'metar2nc' decoder runs under LDM-6.12.14 and not 6.13.x. 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: RQD-888533 Department: Support LDM Priority: Normal Status: Closed