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

[McIDAS #KXY-614160]: What are the plans for the Japanese Satellite



Hi Fred,

re:
> I received the following from NESDIS:
> 
> "Hi Fred,
> 
> Due to significant resources required, our management decided
> not to host H-8 McIDAS data on SATEPSANON.  If you wish to acquire
> H-8 data and have a real-time need, please fill-in the attached
> Data Access Request Form and then submit to email address:
> address@hidden
> 
> When received, we will review your request with management and
> get back to you on a decision."

It is not surprising that they have decided to not host H8 data on
satepsanone given that the AIX machine is now pretty old, lacks the
disk resources to keep a reasonable number of hours of the data, and,
most especially, because SSEC no longer supports McIDAS-X on AIX.

re:
> I have sent in a request to access the H-8 data.  We will see
> how it is received.

It seems to me that they will be getting a number of requests like
this given their decision to not host the data on their publically-
accessible ADDE server.  Given this, they may be more open to granting
access to individuals that may not be approved for some of their
other servers (e.g., the one hosting realtime METEOSAT data).

re:
> Might UNIDATA consider hosting an ADDE server for foreign satellite
> data in addition to the two GOES servers?

I would love to do this as I view it as an important service for the
community.  Right now, we do not have the computing resources to
bite off the H8 data, so some other option needs to be investigated.
We are in "low level" talks with Amazon Web Services folks about
moving all GOES-R data up to AWS in as close to real-time once GOES-R
has been launched and is declared to be operational.  Given the
similarity of the H8 data to GOES-R, and given what I perceive to
be the keen community interest in H8 data (we are receiving H8-related
emails from a number of folks in the Unidata community), AWS may be
interested in hosting the H8 data.  That being said, AWS is not interested
in developing and/or providing the value-added access to data that
they host (reference the NEXRAD Level II archive that is being moved
to S3 buckets as part of the NOAA Big Data project).  Instead, they
are looking for folks that want to operate (and, of course, pay for) services
in AWS.  In order to explore this opportunity (I see AWS' interest as
a clear opportunity, and I have contacted SSEC to express my belief
that they should see this as an opportunity also), we (Jeff Weber and
Mohan Ramamurthy) will be meeting with AWS folks at the AGU Fall Meeting
in San Francisco next week.  We foresee that there will be a follow-on
meeting at the AMS Annual Meeting in New Orleans in January.  What may
come out of these meetings is still unclear; stay tuned...

> 
> ________________________________________
> From: Unidata McIDAS Support <address@hidden>
> Sent: Monday, December 7, 2015 12:19 PM
> To: Mosher, Frederick R.
> Cc: address@hidden
> Subject: [McIDAS #KXY-614160]: What are the plans for the Japanese Satellite
> 
> Hi Fred,
> 
> re:
> > December 4 has arrived and the Japanese have turned off the
> > MTSAT-2 data.
> 
> Yup.
> 
> re:
> > I do not see Himawari-8 data on PUB.
> 
> Evidently, SATEPS has not decided to host the Himawari-8 data on satepsanone 
> yet.
> This is not surprising given that the machine might not have enough resources
> (disk, RAM, etc.) to be able to serve the Himawari data, AND because the
> OS that the machine is running (AIX) is no longer supported as a viable
> McIDAS-X platform by SSEC.
> 
> re:
> > You mentioned that the Himawari-8 ADDE definitions have been created, but
> > were empty.
> 
> Yes, they were at one point, but I think I remember checking the
> ADDE server subsequently and seeing that the definitions had been
> removed.  This was probably a reaction to my pointing out that
> the dataset definitions had been created but the datasets were
> empty.
> 
> re:
> > What are the ADDE dataset definitions for the Himawari-8 data?
> 
> I can't remember what they were.  If you run:
> 
> DSINFO IMAGE PUB
> 
> you will see all of the datasets that are defined.
> 
> Given the apparent reluctance to host the Himawari-8 data on satepsanone,
> it may be best to get access to the machine where the data is being hosted.
> I think I sent you one of the SATEPS messages about this previously, but
> if I did not, or you can't find it, I will send it again.  I am not sure
> how hard getting access to the machine will be.  A long time ago, NOAA
> required some sort of "relationship" (active collaborations, etc.) before
> setting up access to their non-public ADDE servers.
> 
> 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: KXY-614160
> Department: Support McIDAS
> Priority: Normal
> Status: Closed
> 
> 

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: KXY-614160
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.