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

[Support #XQH-733254]: LDM latency issue between NWS MAX and ERC client

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: [Support #XQH-733254]: LDM latency issue between NWS MAX and ERC client
  • Date: Wed, 24 Feb 2010 09:06:31 -0700
Gini,

> No, I understand the only source of data for the transitioned sites is
> the Aggregator at HQ

I believe that the Max Gigapop requests NEXRAD2 data from the Eastern Region 
HQ, in which case its feed to the ERC will be a proper superset of the Eastern 
Region HQ's feed of NEXRAD2 data to the ERC.  In such a situation, the 
feedtype/pattern pair in the ERC's requests should differ from one another; 
otherwise, there's a risk that the downstream LDM at the ERC that's receiving 
data from the Eastern Region HQ will decide to go into the less efficient 
ALTERNATE transfer mode when, in fact, it shouldn't.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: XQH-733254
Department: Support LDM
Priority: Normal
Status: Closed