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

Re: Decoders Success

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: Decoders Success
  • Date: Tue, 18 Jul 2000 10:48:26 -0600
Matthew Maschmann wrote:

> Anne,
>
>         I think we finally have our decoders working!  The logging error
> was overcome by simply creating a log file in the decoded directory with
> the name of the file that supposedly could not be read (uaLog.181618.log).
> From that point on, it has been making its own log files.  Thank you for
> your help and patience with me.  It has been very appreciated.
>
> Matt

Cool!  My pleasure!

For my own information, is it making many log files or just using one?

Anne

--
***************************************************
Anne Wilson                     UCAR Unidata Program
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************