[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #RQD-888533]: pqact errors after upgrade to 6.13.0



Hi Dave,

re:
> Everything also seems to work if i run the PIPE entries through 'csh -c'
> (although I'm waiting to confirm the MEX, MAV and LAMP data)
> 
> 
> # METAR's
> WMO     ^S[AP].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9])        PIPE    csh 
> -c "metar2nc -t 30 -l logs -d data/dec_data/obs/metar etc/metar.cdl"
> #
> #
> # Synoptic reports
> WMO     ^S[IMN][^V].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9])   PIPE    csh 
> -c "syn2nc -t 120 -l logs -d data/dec_data/obs/synoptic etc/syn.cdl"
> WMO     ^S[IMN]V[GINS].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9])        PIPE  
>   csh -c "syn2nc -t 120 -l logs -d data/dec_data/obs/synoptic etc/syn.cdl"
> #
> # AVN MOS (MAV)
> WMO     ^FOAK3[7-9] KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])     PIPE    csh 
> -c "mos2nc -l logs/mav2nc.%Y%m%d.asc etc/mav_mos.cdl 
> data/dec_data/mos/mav_mos/(\1:yyyy)(\1:mm)\1/mav_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> WMO     ^FOPA20 KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])         PIPE    csh 
> -c "mos2nc -l logs/mav2nc.%Y%m%d.asc etc/mav_mos.cdl 
> data/dec_data/mos/mav_mos/(\1:yyyy)(\1:mm)\1/mav_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> WMO     ^FOUS2[1-6] KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])     PIPE    csh 
> -c "mos2nc -l logs/mav2nc.%Y%m%d.asc etc/mav_mos.cdl 
> data/dec_data/mos/mav_mos/(\1:yyyy)(\1:mm)\1/mav_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> #
> # Eta MOS (MET)
> WMO     ^FOUS4[4-9] KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])     PIPE    csh 
> -c "mos2nc -l logs/met2nc.%Y%m%d.asc etc/met_mos.cdl 
> data/dec_data/mos/met_mos/(\1:yyyy)(\1:mm)\1/met_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> #
> # MRF MOS (MEX)
> WMO     ^FEAK3[7-9] KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])     PIPE    csh 
> -c "mos2nc -l logs/mex2nc.%Y%m%d.asc etc/mex_mos.cdl 
> data/dec_data/mos/mex_mos/(\1:yyyy)(\1:mm)\1/mex_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> WMO     ^FEPA20 KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])         PIPE    csh 
> -c "mos2nc -l logs/mex2nc.%Y%m%d.asc etc/mex_mos.cdl 
> data/dec_data/mos/mex_mos/(\1:yyyy)(\1:mm)\1/mex_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> WMO     ^FEUS2[1-6] KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9])     PIPE    csh 
> -c "mos2nc -l logs/mex2nc.%Y%m%d.asc etc/mex_mos.cdl 
> data/dec_data/mos/mex_mos/(\1:yyyy)(\1:mm)\1/mex_mos.(\1:yyyy)(\1:mm)\1.\2.nc"
> #
> # GFS LAMP MOS
> WMO     ^FOUS11 KWNO ([0-3][0-9])([0-2][0-9][0-5][0-9]) PIPE    csh -c 
> "mos2nc -l logs/lamp2nc.%Y%m%d.asc etc/lamp_mos.cdl 
> data/dec_data/mos/lamp_mos/(\1:yyyy)(\1:mm)\1/lamp_mos.(\1:yyyy)(\1:mm)\1.\2.nc"

Yup, there are many ways of working around the problem at hand :-)

PIPEing the product to a Shell which then runs the decoder has the attraction
of not having to maintain scripts.  Nice catch!

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


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.