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.
Anne, The support-ldm address needs to be in the cc line of the message in order for procmail to automatically file in that mailbox. Chiz ------- Forwarded Message >To: Mark Tucker <address@hidden>, >To: address@hidden, >To: address@hidden >From: Anne Wilson <address@hidden> >Subject: Re: 20000211: Lyndon State losing IDD data >Organization: UCAR >Keywords: 200002171745.KAA21009 Mark Tucker wrote: > > Right now we are not seeing much lag in our feed. I will send you the > same info when I see that we are experiencing problems. > > cirrus:~/etc> ldmping -i 5 -h sunset.meteor.wisc.edu > Feb 15 17:39:03 State Elapsed Port Remote_Host > rpc_stat > Feb 15 17:39:04 RESPONDING 0.570931 388 sunset.meteor.wisc.edu > Feb 15 17:39:13 RESPONDING 3.484826 388 sunset.meteor.wisc.edu > Feb 15 17:39:18 RESPONDING 0.147400 388 sunset.meteor.wisc.edu > Feb 15 17:39:23 RESPONDING 0.146485 388 sunset.meteor.wisc.edu > Feb 15 17:39:28 RESPONDING 0.190661 388 sunset.meteor.wisc.edu > Feb 15 17:39:33 RESPONDING 0.149973 388 sunset.meteor.wisc.edu > > cirrus:~/etc> /usr/sbin/traceroute sunset.meteor.wisc.edu > traceroute to sunset.meteor.wisc.edu (144.92.130.6), 30 hops max, 40 byte > packets > 1 155.42.21.25 (155.42.21.25) 5.345 ms 11.7 ms 4.305 ms > 2 155.42.5.1 (155.42.5.1) 8.415 ms 9.177 ms 41.558 ms > 3 168.103.1.13 (168.103.1.13) 35.939 ms 37.468 ms 37.477 ms > 4 wash-gw2.f0-0-0.wash.interprise.net (168.103.0.251) 46.94 ms 66.581 > ms 54.682 ms > 5 168.103.254.97 (168.103.254.97) 134.681 ms 125.718 ms 131.362 ms > 6 s4-1-0.chicago2-cr4.bbnplanet.net (4.0.196.249) 158.382 ms 132.035 > ms 192.306 ms > 7 f0-1-0.chicago1-br1.bbnplanet.net (4.0.48.65) 131.438 ms 162.52 ms > 131.102 ms > 8 p2-3.chicago1-nbr1.bbnplanet.net (4.0.1.205) 129.962 ms 129.542 ms > 131.022 ms > 9 p12-0-0.nchicago1-core0.bbnplanet.net (4.0.5.234) 151.014 ms * > 130.431 ms > 10 chi1-oc3.wiscnet.net (207.227.0.202) 136.292 ms 141.176 ms 141.856 > ms > 11 r-peer-WNMadison-gw.net.wisc.edu (216.56.1.18) 134.976 ms 142.668 ms > 155.261 ms > 12 r-whopper.net.wisc.edu (144.92.128.130) 165.253 ms 142.321 ms > 151.933 ms > 13 sunset.meteor.wisc.edu (144.92.130.6) 146.251 ms 147.075 ms 157.438 > ms > Hi Mark, Thanks for the info. Do send the results when you are experiencing trouble. > > The T1 route between us in Lyndon and the VSC in Waterbury, VT is very > responsive. The T3 between Waterbury and Burlington, VT is also not a > problem. I am interested in finding out what is involved in installing a > NOAAPORT receiver if anyone there could provide us with some information. > > Thanks. > > Mark Tucker > Information Technology > Lyndon State College > address@hidden There is info available regarding the NOAAPORT receivers. You can always start with the NWS web search site http://www.nws.noaa.gov/search.html . Here's one page of info: http://www.nws.noaa.gov/noaaport/html/manu_lst.shtml. In particular, I understand that SSEC has built one relatively inexpensively. You might try contacting Denise Laitsch there. Also, at AMS I took a short course on NWS Data Sources, Formats, and Use. They spent time on specs for a NOAAPORT receiver. I have hard copies of those notes and would be willing to make them available to you. (I searched on the web for them but was unable to find them after only a brief effort.) Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 (303) 497-8677 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ **************************************************** ------- End of Forwarded Message