[McIDAS #NZQ-510524]: RTNEXRAD Feed from adde.ucar.edu - no data

Hi Greg,

re:
> RTNEXRAD stopped again at 13:02 UTC today. Can you give it a swift kick?

Hmm... it looks like the TDS is sucking up more and more of the CPU on
the machine that is currently adde.ucar.edu (currently atm.ucar.edu).
I suggest you point at motherlode.unidata.ucar.edu since it is not having
TDS problems, and I just verified that the RTNEXRAD/N0Q dataset is up
to date there:

DATALOC ADD RTNEXRAD MOTHERLODE.UNIDATA.UCAR.EDU

Group Name                    Server IP Address
--------------------         ----------------------------------------
RTNEXRAD                     MOTHERLODE.UNIDATA.UCAR.EDU

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done
 
IMGLIST RTNEXRAD/N0Q.-10 ID=FTG
Image file directory listing for:RTNEXRAD/N0Q
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
 402  RADAR          5 AUG 16218  21:02:16     FTG    1
 401  RADAR          5 AUG 16218  21:00:38     FTG    1
 400  RADAR          5 AUG 16218  20:58:02     FTG    1
 399  RADAR          5 AUG 16218  20:56:24     FTG    1
 398  RADAR          5 AUG 16218  20:53:48     FTG    1
 397  RADAR          5 AUG 16218  20:52:10     FTG    1
 396  RADAR          5 AUG 16218  20:49:36     FTG    1
 395  RADAR          5 AUG 16218  20:47:58     FTG    1
 394  RADAR          5 AUG 16218  20:45:23     FTG    1
 393  RADAR          5 AUG 16218  20:43:45     FTG    1
 392  RADAR          5 AUG 16218  20:41:09     FTG    1
IMGLIST: done

I will alert the TDS guys to the situation...

> Thanks,
> Greg
> 
> address@hidden> wrote:
> 
> > Hi Greg,
> >
> > re:
> > > Sorry for the lack of details. I was using RTNEXRAD/N0Q ID=FTG which
> > > grew stale after about 12:13 Z yesterday morning.
> >
> > OK.  I checked the RTNEXRAD/N0Q dataset on adde.ucar.edu yesterday right
> > after seeing this note, and everything looked up to date then.
> >
> > re:
> > > I tried using RTNEXRAD on the following:
> > >
> > >
> > > Query: imglist RTNEXRAD/N0Q.-10 ID=FTG
> > > weather2.admin.niu.edu - data seemed about 20 min behind
> > > weather3.admin.niu.edu - no images found that meet criteria
> > > tornado.geos.ulm.edu - could not resolve TORNADO.GOES.ULM.EDU. Entry not
> > > filed.
> > > adde.cise-nsf.gov - no images found that meet criteria
> >
> > Because of your observations, I made the first of what will likely be
> > a series of changes to the Publically Accessible ADDE servers page
> > in the McIDAS portion of our website:
> >
> > http://www.unidata.ucar.edu/software/mcidas/adde_servers.html
> >
> > As you will see, my first step was to organize the ADDE servers listed
> > into three groups: Unidata, Institutional and Community.  The second
> > step was to remove any entries that were known to be out of date.
> > The next step, which will take time, will be to work with the folks
> > hosting ADDE servers to see if help is needed to make sure that things
> > are running correctly and datasets are up to date.
> >
> > Cheers,
> >
> > Tom
> > --
> >
> > ****************************************************************************
> > Unidata User Support                                    UCAR Unidata
> > Program
> > (303) 497-8642                                                 P.O. Box
> > 3000
> > address@hidden                                   Boulder, CO
> > 80307
> >
> > ----------------------------------------------------------------------------
> > Unidata HomePage                       http://www.unidata.ucar.edu
> >
> > ****************************************************************************
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: NZQ-510524
> > Department: Support McIDAS
> > Priority: Normal
> > Status: Closed
> > ===================
> > 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.
> >
> >
> >
> 
> 

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: NZQ-510524
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
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.