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 Matthew, I've had an additional thought about testing things, and I'd appreciate your help. I setup ADDE serving of ABI image products on both of our GOES-16 ingest systems quite some time ago so I could monitor the quality of the images directly using McIDAS and the IDV. I just added ADDE dataset definitions for GLM products on both machines, and the test I have in mind is you trying to create GLM displays from the data on each of the machines. So, if you are willing to help in testing: - point RTGOESR at each of the following machines for a test ingest.unidata.ucar.edu - GRB datastream used is the combined one from SSEC ingest2.unidata.ucar.edu - GRB datastream used is from our local GOES-16 dish NB: - what I have in mind is for a short term test only We do NOT want external sites accessing our ingest machines on a routine basis!! Comments: - the test will ascertain if there is any difference in the GLM netCDF files produced by two different versions of CSPP GEO: ingest2.unidata.ucar.edu - CSPP GEO v1.0 ingest.unidata..ucar.edu - CSPP GEO v0.4.7 - the fact that we feed CSPP GEO generated products to our IDD relay clusters tells me that the GLM files created by v1.0 and v0.4.7 are identical If they were not, we would have twice the number of GLM files being distributed in the IDD. - there is a possibility that the latest version of CSPP GEO has a change for GLM data v1.0 is not the latest version, so it may be the case that we need to upgrade to take advantage of a change. This is just me musing about what, if anything, might be wrong, so take the comment with a bag of salt :-) 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: DVA-616382 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.