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 Bob, re: > I was wondering if there are plans to make McIDAS-X version 2017.2 (or its > equivalent) > available to Unidata subscribers. Yes. re: > Apparently this "fastrack" release can handle GOES ABI and GLM data. Yes, but so could SSEC v2017.1. There have been quite a few updates to in routines that support ABI and GLM data, however. re: > If so, is there an approximate release data? I downloaded the SSEC v2017.2 fastrack release yesterday afternoon, and I am busily incorporating all of their changes/additions to the Unidata McIDAS-X/-XCD v2017 release. I should be done with incorporating the SSEC v2017.2 code this afternoon, and then I need to return to finishing my ADDE servers for the ABI imagery delivered in NOAAPort. Exactly when this all of this will be done is not clear to me right now, but it should be "soon" (meaning as fast as possible). re: > Thanks! 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: DXS-904976 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.