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 again Carol, Another question with a thought: - were you trying to overlay an "old" (e.g., yesterday) image with corresponding GLM data? If yes, the reason your GLMDISP (glmdisp.k) invocations may have failed is that there were no GLM products for the same DAY and TIME for the image you were trying to overlay. Explanation: - the ADDE server setup that I made on the Unidata ADDE servers that have GOES-R/S GLM data is for a 12 hour set of GLM data in a 'current' set I did this _assuming_ that the core ADDE servers for GLM data AND routines like GLMLIST and GLMDISP would correctly access datasets of "archived" (non-current) data. I just ran some tests to see if lead.unidata.ucar.edu's ADDE server was functioning correctly, and I ran into unexpected failures. If, in fact, you were trying to overlay non-real-time GOES-16 full disk imagery with time matched GLM data, this may not be possible either because there is something I have not understood about setting up an "archived" dataset, or because there is a bug in either/both of the core ADDE servers for GLM data or in assumptions made in the GLMLIST and GLMDISP routines. I will have to do some investigations to see where the problem lies and work with SSEC to get the problem corrected. Until then, I recommend that you alter your processing procedures to product overlays of GLM data on real-time/near real-time imagery. Again, my ADDE server setups (which included the EOL ADDE server) only keep 12 hours of GLM data in a 'current' set. I hope that the above makes sense. Please (!) let me know if it does not!! For the meantime, I will increase the 'current' set size to be about 24 hours instead of the current 12 hours. 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: CLA-376903 Department: Support McIDAS 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.