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

Re: metar2nc.new behavior

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.

  • Subject: Re: metar2nc.new behavior
  • Date: Mon, 9 Aug 2004 12:46:20 -0600 (MDT)
Tom,

Have you installed the latest decoders release?  There are fixes in it for
the mentioned problems.

robb...



On Mon, 9 Aug 2004, Tom Baltzer wrote:

> Hey Robb,
>
>
>
> I noticed some unusual behavior out of metar2nc.new on lead1 recently.
> First I noted these in ldmd.log:
>
> Aug 09 10:10:43 lead1 pqact[4803]: pbuf_flush 7: time elapsed   3.919847
>
>
>
> Next I noted that 4803 is the process id associated with surface metar.  It
> is still running both the old and the new metar decoders.  The metar.new log
> file showed a bunch of the following messages:
>
>
>
> ncvarget: ncid 3; varid 1: Edge+start exceeds dimension bound
>
> NetCDF::recget status = -1
>
>
>
>
>
> Perhaps these two are correlated...
>
>
>
> Thanks for looking into it.
>
> Tom.
>
>
>
>
>
>
>
>
>
> Tom Baltzer
>
> Software Engineer
>
> UCAR Office of Programs
> Unidata Program Center
> P.O. Box 3000
> Boulder, CO 80307-3000
>
>
>
> E-mail: address@hidden
>
> Phone: 303-497-8637
>
>
>
>

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================