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.
Tony, re: is your upstream feeder getting the data >Here's the result after about 50 minutes. (AREA files usually come in at 36 >minutes past the hour): Actually, by specifying the -o 3600 you don't have to wait to see if the site is getting anything. The assumption is that they should have received products from the stream within the last hour (3600 seconds of the -o flag). >Jul 19 20:07:06 notifyme[14411]: Starting Up: ihlseng.ugems.psu.edu: 199907191 > 90 >706.913 TS_ENDT {{MCIDAS, ".*"}} > NOTIFYME(ihlseng.ugems.psu.edu) returns OK >Jul 19 20:07:07 notifyme[14411]: NOTIFYME(ihlseng.ugems.psu.edu): OK >Jul 19 20:12:08 notifyme[14411]: Timed out after 300 seconds inactivity >Jul 19 20:12:08 notifyme[14411]: Disconnect >What does this say to you? It looks to me like PSU has gotten nothing over >this time. This listing shows that ihlseng is _NOT_ getting the MCIDAS products. They are getting data from thelma, so I checked thelma's log file to see if they are requesting MCIDAS products; they are not: Jul 19 10:39:09 5Q:thelma ihlseng(feed)[57686]: topo: ihlseng.ugems.psu.edu FSL 2|WMO This is telling us that they are asking for FSL2 and WMO, but not MCIDAS. I will send a note to the contact at PSU ( "Jeff Wolfe" <address@hidden>) and ask him to change his request to FSL2|UNIDATA. Until that happens, you may want to feed from a backup site. Tom