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 Mike, re: > I'm starting to crunch on the MFA and TOE GLM products. Excellent! re: > Unlike FED where I just used an existing EU table, I'm thinking I'll need > to make new ones. You might find that you will also need to make a stretch table (.ST). re: > I want to base them off of what's in AWIPS, found the > ones below, and will write some Python code to port those over... > > https://raw.githubusercontent.com/Unidata/awips2-goesr/unidata_18.2.1/edexOsgi/com.raytheon.uf.edex.plugin.goesr/utility/common_static/base/colormaps/GOES-R/GOESR-L2/glm_energy.cmap > https://raw.githubusercontent.com/Unidata/awips2-goesr/unidata_18.2.1/edexOsgi/com.raytheon.uf.edex.plugin.goesr/utility/common_static/base/colormaps/GOES-R/GOESR-L2/glm_flashsize.cmap > > First question: do you see any outright flaw in that plan, or do you think > there might be a better/easier way? No, I don't see a flaw in this approach at all. re: > And secondly, am I correct in thinking McIDAS still doesn't have a LOG > scale I could use in abincalb.inc? You are correct. I have been wanting to add that to the Unidata release, but a large number of other tasks have always pushed that intention to the background, sigh! re: > I did a quick first pass at this today and I did not like the results. So > I figured I'd run this by you before I tread much further in case I'm > missing something. What was wrong with the first result? Aside: It may well be that the scalings (to map values to brigtnesses) used for these products need to be adjusted. This can be done in part using stretch tables, but the process is, in my mind, fiddly to say the least. 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: USW-595984 Department: Support McIDAS Priority: Normal Status: Open =================== 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.