[conduit] No GFS data on CONDUIT since FV3 update

• To: "ldm-users@xxxxxxxxxxxxxxxx" <ldm-users@xxxxxxxxxxxxxxxx>, "support-conduit@xxxxxxxxxxxxxxxx" <support-conduit@xxxxxxxxxxxxxxxx>, "conduit@xxxxxxxxxxxxxxxx" <conduit@xxxxxxxxxxxxxxxx>
• Subject: [conduit] No GFS data on CONDUIT since FV3 update
• From: Pete Pokrandt <poker@xxxxxxxxxxxx>
• Date: Wed, 12 Jun 2019 18:08:19 +0000
• Authentication-results: spf=none (sender IP is ) smtp.mailfrom=poker@xxxxxxxxxxxx;

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



<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  - poker@xxxxxxxxxxxx

• Follow-Ups:
  • Re: [conduit] No GFS data on CONDUIT since FV3 update
    • From: James Murakami
  • Re: [conduit] No GFS data on CONDUIT since FV3 update
    • From: Pete Pokrandt