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 Jim, re: > Excuse my poor grammar on the previous email. That was typed from my phone > when I was out taking the pictures. The small keyboard and autocorrect kill > me daily! Count me in that group too! re: > I went back and looked on wxengine3 and it was a matter of place value... > it actually reads 3863884 making it basically 4GB of RAM. Ah Ha! So, I did read the amount of data incorrectly. My bad! re: > No worries. re: > Quick question, what time do you grab the gapcounts at so I would make > sure I FTP my data to my server for you prior to that? All sites are running their cron job that compiles 'yesterday's summary Gap stats "just" after 0 UTC. We, UWisc/SSEC and LSU/SRCC run the script at 00:05 UTC, and I think that NOAA/GSL is doing the same. NOAA/GSL sends the results as soon as they are compiled. Since I have SSH access to all of the other sites that are included in the nightly summary Gap stat emails, I run a script that goes out and grabs the numbers anytime after about 00:10 UTC. 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: JZP-576695 Department: Support NOAAPORT Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.