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

[McIDAS #KXA-733353]: GOES 16/17 datasets on adde.ssec.wisc.edu

Hi,

re:
> Thanks for all of the information!

No worries.

re:
> We had the GOES16 datasets on
> lead.unidata.ucar.edu included in the McV server list at one point, but
> removed it.  At one point I thought I remembered you saying that you
> wanted users to first use adde.ucar.edu, then atm.ucar.edu, and then
> lead.unidata.ucar.edu as a last resort.

I don't recall saying use lead as a last resort, but the ordering of
use of the servers is correct.

Aside comment:

I have been working on combining ADDE serving of GRB-delivered ABI imagery
(the core ABIN servers) with serving of the reconstituted ABI L2 imagery
we will be distributing in the IDD NIMAGE feed _soon_.  Right now,
lead.unidata.ucar.edu is running a new ADDE server for the NOAAPort
ABI L2 imagery that was created using the ABIN servers as a template.
The improvement in data serving speed that was able to be realized when
the NOAAPort ABI L2 imagery follows the GOES-R mission standard naming
has been dramatic.  You can see the improvement by loading images
and loops of images from lead.unidata.ucar.edu (new server) and
adde.ucar.edu (old SCMI server).   The particulars are:

ADDE Dataset group names:  NPGOESR, NPGOESS

lead.unidata.ucar.edu: new ADDE server
adde.ucar.edu:         old server

I am very close to having a combined server set (ADIR and AGET) working,
and when I do have it, I will be switching to its use on lead.unidata.ucar.edu
first.

re:
> Since adde.ucar.edu and
> atm.ucar.edu seemed to always work, we removed lead.unidata.ucar.edu to
> avoid any unnecessary traffic on that server.

We want people to use adde.ucar.edu because our plans are that it will
be the canonical server name that will at some point be the front end
to a cluster of servers.

Second, adde.ucar.edu simply points at atm.ucar.edu, so they are the
same thing ** right now **.

re:
> With your suggestion to
> add the GOES 16/17 datasets to lead.unidata.ucar.edu, I'll go ahead and
> do so.

I think that it is useful for end-users to have a list of ADDE servers
that they can use.  If there were a way to force a prioritization of
the servers, then the list would be:

adde.ucar.edu (which right now is atm.ucar.edu)
lead.unidata.ucar.edu

As soon as we can get unidata2-new upgraded and install a dedicated
IDD relay machine in the Data Center, then adde.ssec.wisc.edu will
be added to this list.

re:
> Thanks again, Tom!

No worries.

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: KXA-733353
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.