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

[IDD #TMZ-743033]: Help? Our LDM Miami radar latency is too long

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.

  • Subject: [IDD #TMZ-743033]: Help? Our LDM Miami radar latency is too long
  • Date: Thu, 01 Mar 2018 10:48:52 -0700
Hi Brian!

I'm afraid that the LDM doesn't have any prioritization capability.

It wasn't clear from your email, however, how you're getting the radar 
data-products. Are you running an LDM that's requesting the products or are you 
pulling them from a THREDDS server?. If the latter, then is the THREDDS server 
local or remote? If local, then how does it get the products?

According to 
<http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD2+oliver.unidata.ucar.edu>,
 our latency in receiving NEXRAD2 products averages slightly more than 15 
seconds. Or course, the products have to be accumulated and stitched-together 
to make a volume-scan, which takes time.

> Can someone at Unidata suggest how we might reduce latency in our Miami
> KAMX radar feed?
> 
> Does the LDM have any prioritization possibilities?
> 
> Thanks for any advice (or direct interventions in the system at
> weather.rsmas.miami.edu!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TMZ-743033
Department: Support IDD
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.