Re: Level II error messages

I think a good compromise would be for you to just discard all logging 
messages. I _think_ this will do it:

 java.util.logging.Logger.getLogger("").setLevel(Level.OFF);

Don Murray wrote:
> John-
>
> John Caron wrote:
>
> > It would probably be more robust to capture the log messages of at 
> > least ERROR, and maybe WARN, for error tracking.
>
>
> The issue is that a user sees these messages spewing out, but that
> the display works just fine.  If they do not cause a problem with
> accessing/displaying the data, then they shouldn't be shown to the
> user.
>
> You and Yuan can run with logging levels set appropriately and
> fix the source of the problems if they are indeed problems.  If
> they are not problems, then there's no need to print them out.
>
> Don
>
> > Don Murray wrote:
> >
> > > John-
> > >
> > > John Caron wrote:
> > >
> > > > It indicates damaged records in the file. Not sure what to do about 
> > > > it. I could put the log level to WARN. Are you setting the log level?
> > >
> > >
> > >
> > > No.  I would prefer that these only print out if some debugging
> > > is set so I guess WARN is as good as any other.
> > >
> > > Don
> > >
> > > > Don Murray wrote:
> > > >
> > > > > Hi Yuan-
> > > > >
> > > > > When I read in some KFTG data this morning, I got the
> > > > > following messages printing out to my console:
> > > > >
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: *** segment = -25974/3 message(780 1896984)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: ****780 HAS bad velocity offset= -31100 message(780 1896984)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: ****780 HAS spectWidth AND NOT velocity!! message(780 1896984)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: *** message date = 2049 : 23816784 message(780 1896984)
> > > > >  data date = -31868 : -2037610104
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: *** no reflect or dopplar =  message(780 1896984)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: *** segment = 26208/26983 message(795 1933464)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: ****795 HAS bad reflect offset= 28000 message(795 1933464)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: ****795 HAS bad velocity offset= 22642 message(795 1933464)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: ****795 HAS bad spwidth offset= 28000 message(795 1933464)
> > > > > Jul 25, 2006 7:09:03 AM ucar.nc2.iosp.nexrad2.Level2Record checkOk
> > > > > SEVERE: *** message date = 3948 : 1802398058 message(795 1933464)
> > > > >  data date = 257 : 1216446331
> > > > > CRC Error
> > > > > CRC Error
> > > > >
> > > > > These seem to be debug messages more than anything else. Can
> > > > > these be turned off by default?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Don
> > > > > *************************************************************
> > > > > Don Murray                               UCAR Unidata Program
> > > > > address@hidden                        P.O. Box 3000
> > > > > (303) 497-8628                              Boulder, CO 80307
> > > > > http://www.unidata.ucar.edu/staff/donm
> > > > > *************************************************************