Re: [conduit] [ldm-users] Missing GFS files on conduit this morning

  • To: "Tyle, Kevin R" <ktyle@xxxxxxxxxx>
  • Subject: Re: [conduit] [ldm-users] Missing GFS files on conduit this morning
  • From: Justin Cooke - NOAA Federal <justin.cooke@xxxxxxxx>
  • Date: Fri, 23 Feb 2018 09:35:57 -0500
All,

It looks like we are seeing some residual problems with our CONDUIT
systems, our administrators are investigating, sorry for the continued
impacts.

Justin

On Fri, Feb 23, 2018 at 6:49 AM, Tyle, Kevin R <ktyle@xxxxxxxxxx> wrote:

> Same here ... (no surprise since we feed from Madison)
>
>
> _____________________________________________
> Kevin Tyle, Manager of Departmental Computing
> Dept. of Atmospheric & Environmental Sciences
> University at Albany
> Earth Science 235, 1400 Washington Avenue
> Albany, NY 12222
> Email: ktyle@xxxxxxxxxx
> Phone: 518-442-4578 <(518)%20442-4578>
> _____________________________________________
> ------------------------------
> *From:* conduit-bounces@xxxxxxxxxxxxxxxx <conduit-bounces@xxxxxxxxxxxxxxxx>
> on behalf of Pete Pokrandt <poker@xxxxxxxxxxxx>
> *Sent:* Friday, February 23, 2018 1:13:17 AM
>
> *To:* Rebecca Cosgrove - NOAA Federal; Phil Birnie
> *Cc:* ldm-users@xxxxxxxxxxxxxxxx; Ryan Hickman;
> support-conduit@xxxxxxxxxxxxxxxx
> *Subject:* Re: [conduit] [ldm-users] Missing GFS files on conduit this
> morning
>
>
> The attached image shows the lag to idd.aos.wisc.edu as of about 06 UTC
> 23. Here's a link to the current lag:
>
>
> http://rtstatstest.unidata.ucar.edu/cgi-bin/rtstats/
> iddstats_nc?CONDUIT+idd.aos.wisc.edu
>
>
>
> <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>
> --
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086 <(608)%20262-3086>  - poker@xxxxxxxxxxxx
>
>
> ------------------------------
> *From:* conduit-bounces@xxxxxxxxxxxxxxxx <conduit-bounces@xxxxxxxxxxxxxxxx>
> on behalf of Pete Pokrandt <poker@xxxxxxxxxxxx>
> *Sent:* Friday, February 23, 2018 12:05 AM
> *To:* Rebecca Cosgrove - NOAA Federal; Phil Birnie
> *Cc:* ldm-users@xxxxxxxxxxxxxxxx; Ryan Hickman;
> support-conduit@xxxxxxxxxxxxxxxx
> *Subject:* Re: [conduit] [ldm-users] Missing GFS files on conduit this
> morning
>
>
> Just saw the all clear come through on the mailing list, but the 00 UTC
> NAM didn't come in, and the 00 UTC GFS files are all really short.
> Latencies are way up, close to an hour, starting around 23 UTC Feb 22.
>
>
> I'm seeing the high latencies on idd.aos.wisc.edu and also on
> motherlode.unidata.ucar.edu.
>
>
> Pete
>
>
>
> <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>
> --
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086 <(608)%20262-3086>  - poker@xxxxxxxxxxxx
>
>
> ------------------------------
> *From:* conduit-bounces@xxxxxxxxxxxxxxxx <conduit-bounces@xxxxxxxxxxxxxxxx>
> on behalf of Rebecca Cosgrove - NOAA Federal <rebecca.cosgrove@xxxxxxxx>
> *Sent:* Thursday, February 22, 2018 12:56 PM
> *To:* Phil Birnie
> *Cc:* ldm-users@xxxxxxxxxxxxxxxx; Ryan Hickman;
> support-conduit@xxxxxxxxxxxxxxxx
> *Subject:* Re: [conduit] [ldm-users] Missing GFS files on conduit this
> morning
>
> Hi Phil.
> We're far enough along in our recovery that we believe CONDUIT is up and
> running again.  Please let me know if this is not the case.
>
> Becky
>
> On Wed, Feb 21, 2018 at 8:04 PM, Phil Birnie <me@xxxxxxxxxxxxxx> wrote:
>
> Hey All,
>
> Iâm assuming the CONDUIT feed is still unstable  â havenât received any
> model data since about 15Z this morningâ If Iâm incorrect, let me know.
>
> - phil
>
>
> From: Ryan Hickman <ryan@xxxxxxxxxxxxxxxx> <ryan@xxxxxxxxxxxxxxxx>
> Reply: Ryan Hickman <ryan@xxxxxxxxxxxxxxxx> <ryan@xxxxxxxxxxxxxxxx>
> Date: February 20, 2018 at 2:36:40 PM
> To: Patrick L. Francis <wxprofessor@xxxxxxxxx> <wxprofessor@xxxxxxxxx>
> Cc: ldm-users@xxxxxxxxxxxxxxxx <ldm-users@xxxxxxxxxxxxxxxx>
> <ldm-users@xxxxxxxxxxxxxxxx>, support-conduit@xxxxxxxxxxxxxxxx
> <conduit@xxxxxxxxxxxxxxxx> <conduit@xxxxxxxxxxxxxxxx>
> Subject:  Re: [ldm-users] [conduit] Missing GFS files on conduit this
> morning
>
> I, too, have the GFS 12 UTC GRIB2 files in a publicly available location
> should anyone wish to access them.
>
> https://storage.googleapis.com/ah-maps-raw/GFS_2018022012000
> 0_20180220120000.grib2 (F001)
> https://storage.googleapis.com/ah-maps-raw/GFS_2018022012000
> 0_20180220130000.grib2 (F002)
> etc. etc. through 120 hours.
> https://storage.googleapis.com/ah-maps-raw/GFS_2018022012000
> 0_20180225120000.grib2 (F120)
>
> On Tue, Feb 20, 2018 at 11:45 AM, Patrick L. Francis <
> wxprofessor@xxxxxxxxx> wrote:
>
>
> somebody just asked where the files are when they looked in this directory
> http://modelweather.com/noaaport/dish/ncep/model/gfs/
>
> my fault.. I didn't explain very well.. sorry!
>
> since GEMPAK is being phased out, I am writing a custom ingest package for
> our internal uses, and filing the products as each source sends them over
> NOAAPort
>
> for example, GFS which was brought up today comes over the dish as:
>
>  71550 20180220035934.747355  NGRID 19629065  YRPK40 KWBC 200000
> !grib2/ncep/GFS/#003/201802200000F072/RELH/400 hPa PRES
>
> where:
> 'ncep' is the source
> 'GFS' is the model
> '#003' is the grid
>
> so I chose to file things as
> ../root/www/dir/noaaport/dish/'source'/'model'/'grid'/
>
> and then instead of a crazy filename.. simply pipe everything into
> YYYYMMDD.HHHH.{F}HHH.grib
>
> so all variables for each product are filed into the corresponding date,
> hour, and forecast hour by model type.
>
> then with NIDS data for example, I file all products by:
> ../root/www/dir/noaaport/dish/nids/'source'/'radome'/'prod'/
> YYYYMMDD.HHMM.nid
>
> so to answer the unspoken person's question, while this is a work in
> progress for me internally, of course I don't mind sharing with the unidata
> community if you should need to grab something... unidata is good people
>  Eventually I hope to file every single product that comes over noaaport,
> because what I'm doing is instead of copying from pqact.gempak, writing
> everything manually by parsing the notifyme output of every feed.. it just
> takes awhile.. but this way, products will be able to be used natively with
> MetPy and other new apps being developed
>
>
> cheers,
>
> --patrick
>
> -----------------------
> Patrick L. Francis
> AerisWeather.com
> modelweather.com
>
> --
>
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> conduit mailing list
> conduit@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> conduit mailing list
> conduit@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>