[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20040525: help with dcacars
- Subject: Re: 20040525: help with dcacars
- Date: Tue, 25 May 2004 16:53:00 -0500 (CDT)
Yes! That was it. Thanks a bunch.
-Eric
On Tue, 25 May 2004, Unidata Support wrote:
>
> Eric,
> This seems to say that the dcgunzip script isn't able to find "gunzip"
> on your system, such that the input to dcacars
> isn't uncompressed and not recognized as a netcdf file.
>
> Check the location for where gunzip exists on your system, and
> see if decoders/dcgunzip has the correct path. Edit that accordingly.
>
> Steve Chiswell
> Unidata User SUpport
>
>
>
>
>
> >From: Eric Nelson <address@hidden>
> >Organization: UCAR/Unidata
> >Keywords: 200405252016.i4PKGOtK024754
>
> >
> >I've just installed gempak 5.7.2p2 and I'm having trouble getting acars
> >data correctly decoded. I'm seeing the following errors in my ldm log...
> >
> >May 25 15:12:18 climate decoders/dcgunzip [24551]: decoders/dcacars -e
> >GEMTBL=/home/gempak/GEMPAK5.7.2p2/gempak/tables -l
> >data/gempak/logs/dcacars.log data/gempak/acars/YYYYMMDDHH_acars.gem
> >May 25 20:12:18 climate pqact[1666]: pbuf_flush (8) write: Broken pipe
> >May 25 20:12:18 climate
> >pqact[1666]: pipe_dbufput:
> >-closedecoders/dcgunzipdecoders/dcacars-eGEMTBL=/ho
> > me/gempak/GEMPAK5.7.2p2/gempak/tables-ldata/gempak/logs/dcacars.logdata/gempa
> > k/acars/YYYYMMDDHH_acars.gem
> >write error
> >May 25 20:12:18 climate pqact[1666]: pipe_prodput: trying again
> >May 25 15:12:18 climate decoders/dcgunzip [24582]: decoders/dcacars -e
> >GEMTBL=/home/gempak/GEMPAK5.7.2p2/gempak/tables -l
> >data/gempak/logs/dcacars.log data/gempak/acars/YYYYMMDDHH_acars.gem
> >May 25 20:12:19 climate pqact[1666]: pbuf_flush (8) write: Broken pipe
> >May 25 20:12:19 climate
> >pqact[1666]: pipe_dbufput:
> >-closedecoders/dcgunzipdecoders/dcacars-eGEMTBL=/ho
> > me/gempak/GEMPAK5.7.2p2/gempak/tables-ldata/gempak/logs/dcacars.logdata/gempa
> > k/acars/YYYYMMDDHH_acars.gem
> >write error
> >
> >and the following errors in my dcacars log...
> >
> >May 25 20:02:18 dcacars[14623]: could not decode data -1
> >May 25 20:12:18 dcacars[24557]: Could not open
> >data/gempak/acars/.tmp_netcdf.3mOMu0
> >May 25 20:12:18 dcacars[24557]: could not decode data -1
> >May 25 20:12:19 dcacars[24587]: Could not open
> >data/gempak/acars/.tmp_netcdf.16uRD7
> >May 25 20:12:19 dcacars[24587]: could not decode data -1
> >
> >I made sure I have all the dc bins and scripts in the ldm decoders dir but
> >I can't figure out what I'm doing wrong. (With me it's probably something
> >painfully obvious!)
> >
> >Any help is appreciated.
> >
> >-Eric
> >
> >--
> >________________________________________________________________________
> >Eric Nelson |
> > |
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
> >+ College of Dupage Meteorology Dept. + Research Applications Prog. + |
> >+ Weather Data Manager + UCAR/NCAR + |
> >+ http://weather.cod.edu + http://www.rap.ucar.edu + |
> >+ address@hidden + address@hidden + |
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
> > |
> >"Sometimes I think the surest sign that intelligent life exists |
> >elsewhere in the universe is that none of it has tried to contact us." |
> > |
> >--Calvin (of Calvin and Hobbes) |
> > |
> >________________________________________________________________________
> >
> --
> **************************************************************************** <
> 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 publically 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.
>