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.
Gerry, I'm glad you got it working. Well, the README is displayed by default as the main content on the GitHub repo, so I look at them regularly like that: https://github.com/Unidata/ldm-alchemy I'm genuinely open to other suggestions on where to put this information (short of checking the version in the script itself--yuck) to help avoid this challenge for others. Ryan address@hidden> wrote: > New Client Reply: Error on GOES-16 parsing > > Python3 is installed and working. Thanks. > > And Readme? I mean, which programmer do you know who looks at that? > > Ticket Details =================== Ticket ID: QSM-175811 Department: Support Python 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.