Re: [conduit] No GFS data on CONDUIT since FV3 update

Hi Pete,


Things definitely slowed down with the arrival of the 12Z GFS run, but we're 
receiving the half degree output (incomplete grids after hour 168 so far). 
Maybe it's because we only request the half degree output that we're receiving 
it, but latency is high (more than a hour off).


CONDUIT    prod/gfs.*pgrb2.0p25.(anl|f...)
    PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITgfs25.log
        -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
             /gem2/data/model/gfs0.25deg/YYYYMMDDHH\1_gfs.gem


James

----------------------------------------------
James Murakami
Staff Meteorologist/Student Affairs
Department of Atmospheric and Oceanic Sciences
University of California, Los Angeles
405 Hilgard Ave.
Los Angeles, CA  90095-1565


   e-mail: tenki@xxxxxxxxxxxxxx<mailto:tenki@xxxxxxxxxxxxxx>
telephone: 310-825-2418
      Fax: 310-206-5219
----------------------------------------------


On 6/12/19 11:08 AM, Pete Pokrandt wrote:
All,

I don't know if it wasn't transmitted on CONDUIT or if it was and the pqact 
info for it just changed, but we didn't save any GFS data from today's 12 UTC 
run - since it was updated to the FV3 version. Based on the volume of CONDUIT 
traffic this morning, the peak of the 12 UTC run increased from ~20 Gb/h to 
almost 35 Gb/h so something definitely changed.

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?CONDUIT+idd.aos.wisc.edu


Looks like the Unidata thredds server is also missing the 12 UTC data.

I'm capturing the output from ldmadmin watch -f conduit running on our primary 
ingest server, so hopefully I'll be able to see what the data looks like coming 
through.

I'll let you know what I find - or if anyone else has any good info, please 
pass it along.

Thanks,
Pete



--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>



_______________________________________________
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<mailto:conduit@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit: 
http://www.unidata.ucar.edu/mailing_lists/
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the conduit archives: