This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Brendon Hoch <address@hidden> >Organization: Plymouth State University >Keywords: 200508121359.j7CDxFjo001287 IDD FNEXRAD latency pqact kill -USR2 Hi Brendon, >Perhaps I should have been a bit more specific. We ingest FNEXRAD on >pscwx, which then feeds typhoon. It is on typhoon where we are seeing >the latency: > >http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?FNEXRAD+typhoon.plymout > h.edu Interesting. I see that the latency started to be an issue at about 20 UTC on the 10th. Did anything happen at our about that time on pscwx? >I pointed typhoon's FNEXRAD feed to atm.nsf.geo.gov and restarted ldm, >that seems to have caught things up. Very interesting. It is unusual to see the latency between machines in a department being orders of magnitude higher than to external machines. Cheers, Tom -- 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.