A common problem for ORAC is that it attempts to run something it found in the PATH that it shouldn't be running. pyORAC tries to work around this by both being very particular about what goes into the PATH and actually testing things work before calling ORAC.
A common problem for ORAC is that it attempts to run something it found in the PATH that it shouldn't be running. pyORAC tries to work around this by both being very particular about what goes into the PATH and actually testing things work before calling ORAC.
That's all well and good until someone leaves broken
ncdump
executables in their library folder. That will trip https://github.com/ORAC-CC/orac/blob/938109a1adb922a8b52bbe2684575f065ef09b75/tools/pyorac/drivers.py#L157 which ends execution. At some point, I should go do this better.