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.
Hi Jeff, re: > All I can say is, "Wow. Thanks." No worries. I'm glad to help when I can... > I did do a couple of those things (run gen_pqact.csh as gempak and copy > over the new decoders, but I didn't do most of the other stuff! I thought that you had done the gen_pqact.csh and copying steps. I redid them just to make sure. > This is definitely a learning experience... It is always hard trying to setup packages without the benefit of attending a training worskhop. Your "mistakes" were not large at all. Things came down to "crossing the Ts and dotting the Is" :-) > On the 0byte corrupted file(s) - Is that common? No. This is the first time I have seen this kind of error with GEMPAK decoding. > I've seen the "can't write to file" messages quite a bit, salted throughout > the > various decoder logs. Seen or are seeing? This is the sort of thing we need to keep an eye out for. > I'll keep an eye on things and see if it looks like everything is working > appropriately. Sounds good. One thing: I am a bit concerned by the product receipt latencies I am seeing for the various feeds that whistler has requested: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+whistler.creighton.edu http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?HRS+whistler.creighton.edu http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NIMAGE+whistler.creighton.edu ... The high latency each time there is a CONDUIT peak in volume while the request is split in fifths seems to imply that the network bandwidth available to the LDM is not as large as it should be. If it turns out to be the case that there is a network bandwidth limitation, you will be forced to review all of the data you are requesting and possibly cutting back on what you want. The logical place to start this process would be in the CONDUIT feed as it completely dominates the volume you are receiving: http://www.unidata.ucar.edu/cgi-bin/rtstats/rtstats_summary_volume?whistler.creighton.edu Data Volume Summary for whistler.creighton.edu Maximum hourly volume 5248.194 M bytes/hour Average hourly volume 2036.212 M bytes/hour Average products per hour 107356 prods/hour Feed Average Maximum Products (M byte/hour) (M byte/hour) number/hour CONDUIT 1529.822 [ 75.131%] 4653.226 43547.652 HDS 199.725 [ 9.809%] 426.167 17732.565 NEXRAD3 171.810 [ 8.438%] 223.467 19959.413 NIMAGE 88.167 [ 4.330%] 163.776 25.087 IDS|DDPLUS 27.762 [ 1.363%] 37.607 26065.370 UNIWISC 18.919 [ 0.929%] 27.497 17.696 LIGHTNING 0.006 [ 0.000%] 0.038 8.717 > Thanks again. I truly appreciated the assistance. No worries. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: IZJ-689237 Department: Support IDD Priority: Normal Status: Closed