Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Gerry Tyler Allison wrote:
[for ldm-6.6.0 and ldm-6.6.2] If I use the following feed pattern [upstream = idd@wisc and bigbird@tamu]: request WMO "((WF|WO|WU|WR|WW|WG|AC|NW)US)|^S[AP]|^S[NS]|^WT(PZ|PN|PA|NT)|(^S[IMN]V[^GINS])|(^S[IMN]W[^KZ])|(^S(HV|HXX|S[^X]))|(^SX(VD|V.50|US(2[0-3]|08|40|82|86)))|(^Y[HO]XX84)|^A CUS11|/p(FTM|FWDDY)" upstream.server.edu the data seems to flow down to me in "chunks". What I mean by this is that is when I run 'ldmadmin watch' I see no data for between 4 and 10 minutes. Then all of a sudden the last 4-10 minutes worth of data comes down within a 3 second period. It then holds again...and 4-10 minutes later another payload of data comes down...etc...etc. If the *ONLY* thing I change is the feed pattern to: request WMO ".*" upstream.server.edu The data feed runs normal. I'm confused! I, and the upstream, have bandwidth to burn so I'm leaving the feed as ".*"...my pattern was attempting to conserve bandwidth for the upstream providers but it seems I did more harm than good. I havent totally verified this issue but it seems to be the culprit. Can anybody confirm? -Tyler
-- Gerry Creager -- gerry.creager@xxxxxxxx Texas Mesonet -- AATLT, Texas A&M University Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983 Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843
ldm-users archives: