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.
Jamie, Then the exit status of 1 is likely the result of the Python script's execution. Does the script log error messages? Recall that LDM decoders don't have a standard output stream; consequently, they must log errors explicitly -- either to a file or to the system logging daemon. If the script doesn't log errors, then you might try FILE-ing a relevant data-product to the script and then running the script on that file manually to see if it writes an error message. > Steve, > The script is set as: -rwxrwxr-x Regards, Steve Emmerson Ticket Details =================== Ticket ID: IHY-300282 Department: Support LDM 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.