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

20041101: dcacars



Donna,
From the command line:

>[ chinook-weasw ] /lsw/wea/gempak/bin/linux/dcgunzip 200411011800.nc.gz
>200411011800.nc.gz: Permission denied.

should be:

cat 200411011800.nc.gz | /lsw/wea/gempak/bin/linux/dcgunzip \
        /lsw/wea/gempak/bin/linux/dcacars \
        -e GEMTBL=/lsw/wea/gempak/gempak/tables \
        -l /var/wea/gempak/dcacars.log   \
        gempak/acars/YYYYMMDDHH_acars.gem

Two things above, remove the "-b 30" since we aren't using NN in
the file name template, and 2, the dcacars line is the argument
to the script with the gz file as piped input.

Perhaps we should set the environmental variabled in the dcgunzip
script and clean up the pqact.conf entry.

Try the following in dcgunzip:

echo "$argv" | logger -t "$0 [$$]" -p local0.notice
setenv PATH ${PATH}:/lsw/wea/gempak/bin/linux        <<--- add this line
setenv GEMTBL /lsw/wea/gempak/gempak/tables          <<--- add this line
cat | /usr/bin/gunzip -c | $argv

Then change your pqact.conf to be:

PCWS <tab> ^FSL\.CompressedNetCDF\.MADIS\.acars\.
<tab>   PIPE <tab> -close <tab> /lsw/wea/gempak/bin/linux/dcgunzip dcacars 
<tab>   -l /var/wea/gempak/dcacars.log gempak/acars/YYYYMMDDHH_acars.gem


It could be something as simple as an extra "space" or "tab" character following
the filename in your pqact.conf. If you send me your pqact.conf file
as an attachment, I can see if there are any stray unprintable characters
in it.

Steve Chiswell
Unidata User Support



>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200411012125.iA1LPevV020898

>Chiz,
>
>Thanks for the info on the model soundings.
>
>Yes, I still do not get the decoded acars soundings.  I am getting the
>raw files.  I can decode the raw files manually but would like to 
>get the decode done automatically.  I don't know if the following 
>information will help but it shows how difficult this problem is.
>Note that the profiler data from FSL are decoded and written just fine.
>From my pqact.conf file
>
>FSL2    ^FSL\.NetCDF\.NOAAnet\.windprofiler\.(01hr)\.
>        PIPE    -close
>                /lsw/wea/gempak/bin/linux/dcncprof
>                -e GEMTBL=/lsw/wea/gempak/gempak/tables
>                -l /var/wea/gempak/dcncprof.log
>                gempak/profiler/YYYYMMDD_pro.gem
>
>PCWS    ^FSL\.CompressedNetCDF\.MADIS\.acars\.
>        PIPE    -close
>        /lsw/wea/gempak/bin/linux/dcgunzip
>        /lsw/wea/gempak/bin/linux/dcacars -b 30
>        -e GEMTBL=/lsw/wea/gempak/gempak/tables
>        -l /var/wea/gempak/dcacars.log
>        gempak/acars/YYYYMMDDHH_acars.gem
>
>The gempak directory looks like
>
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:59 acars
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 15:00 acft
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:47 airm
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:10 csig
>drwxr-xr-x    2 weasw    weasw        4096 Oct 31 06:00 drops
>drwxr-xr-x    2 weasw    weasw       12288 Nov  1 15:01 hrs
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:37 isig
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 10:44 mos
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:24 ncon
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:31 nldn
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 15:04 profiler
>drwxr-xr-x    2 weasw    weasw        8192 Nov  1 15:03 radar
>drwxr-xr-x    2 weasw    weasw        4096 Nov  1 14:06 rdf
>drwxr-xr-x    2 weasw    weasw        4096 Oct 31 17:51 scd
>drwxr-xr-x   10 weasw    weasw        4096 May 27 17:18 storm
>drwxr-xr-x    2 weasw    weasw        4096 Oct 31 17:32 surface
>drwxr-xr-x    2 weasw    weasw        4096 Oct 31 17:22 taf
>drwxr-xr-x    2 weasw    weasw        4096 Oct 31 17:46 upperair
>
>Note that all the directories have the same permissions.  I don't know
>why the LDM will write to all these other directories and not the
>acars one.  Note that the software and the data reside on separate 
>filesystems.  One thing that does seem strange when decoding the raw
>files.
>
>[ chinook-weasw ] /lsw/wea/gempak/bin/linux/dcgunzip 200411011800.nc.gz
>200411011800.nc.gz: Permission denied.
>
>
>[ chinook-weasw ] gunzip 200411011800.nc.gz
>
>It does not like the first command.  The second command unzips fine.
>The same user runs both commands.  dcacars also runs fine from the
>command line and will write to /data/wea/gempak/acars.   
>
>
>
>For review the dcacars.log file looks like
>
>
>^@Oct 29 19:23:36 dcacars[21807]: Could not open gempak/acars/.tmp_netcdf.T9Jl
> 7A
>^@Oct 29 19:23:36 dcacars[21807]: could not decode data -1
>^@Oct 29 19:23:36 dcacars[21813]: Could not open gempak/acars/.tmp_netcdf.VFXD
> 4C
>^@Oct 29 19:23:36 dcacars[21813]: could not decode data -1
>^@Oct 29 19:23:49 dcacars[21820]: Could not open gempak/acars/.tmp_netcdf.jOaw
> pW
>^@Oct 29 19:23:49 dcacars[21820]: could not decode data -1
>^@Oct 29 19:23:49 dcacars[21826]: Could not open gempak/acars/.tmp_netcdf.pQrv
> 7W
>^@Oct 29 19:23:49 dcacars[21826]: could not decode data -1
>^@Oct 29 19:23:53 dcacars[21832]: Could not open gempak/acars/.tmp_netcdf.XOSI
> MJ
>^@Oct 29 19:23:53 dcacars[21832]: could not decode data -1
>^@Oct 29 19:23:53 dcacars[21838]: Could not open gempak/acars/.tmp_netcdf.91lR
> cK
>^@Oct 29 19:23:53 dcacars[21838]: could not decode data -1
>^@Oct 29 19:33:36 dcacars[21971]: Could not open gempak/acars/.tmp_netcdf.tauO
> 6c
>^@Oct 29 19:33:36 dcacars[21971]: could not decode data -1
>
>
>Donna Tucker                      1475 Jayhawk Blvd.
>Associate Professor               213 Lindley Hall 
>address@hidden                     Department of Geography
>(785) 864-4738                            University of Kansas                
>  
>(785) 864-5378 (fax)               Lawrence, KS  66045-7613                   
>  
>
>
>
>
>
>
>
>
>
>
>> >From: address@hidden
>> >Organization: UCAR/Unidata
>> >Keywords: 200410291937.i9TJbIvV018585
>> 
>> >Does CONDUIT or another data stream contain the NCEP model soundings.
>> >I know that GEMPAK will generate soundings at the grid points from
>> >the gridded data but I had a request for the NCEP produced soundings.
>> >Is that in any of the Unidata data streams?
>> >
>> >Donna Tucker                           1475 Jayhawk Blvd.
>> >Associate Professor            213 Lindley Hall 
>> >address@hidden                     Department of Geography
>> >(785) 864-4738                         University of Kansas                
>> >  
>> >(785) 864-5378 (fax)               Lawrence, KS  66045-7613                
>    
>> >  
>> >
>> --
>> 
>> Donna,
>> 
>> No, the NCEP bufr files aren't part of the Unidata IDD. They can be
>> downloaded (via FTP) and decoded into GEMPAK using namsnd into a surface 
>> (for meteorogram) and upper air file (for sounding) for plotting.
>> 
>> Also, back to dcncprof where I'm still scratching my head.... now
>> after the workshop is over I can scratch harder again.
>> The log message you had was that the temporary file couldn't be created.
>> Is it still the case that you get no output? Can you run as the account that
>> runs the LDM using the pqact arguments? Just for clarification, your
>> failed path is:
>> gempak/acars/.tmp_netcdf.p8dsYD
>> Whereas our usual path is a data/gempak directory under the LDM account tree
> .
>> I know your don't have a ~ldm user account, but where is your $GEMDATA tree
>> in relation to that location of $LDMHOME?
>> 
>> 
>> Steve Chiswell
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support 
>> ----------------------------------------------------------------------------
>> 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.
>> 
>
--
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.