Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prORAC expects the libraries to contain only functional executables #63

Open
adamcpovey opened this issue Nov 9, 2021 · 0 comments
Open
Assignees
Labels

Comments

@adamcpovey
Copy link
Collaborator

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

raise OracError('ncdump is non-functional.')
which ends execution. At some point, I should go do this better.

@adamcpovey adamcpovey added the bug label Nov 9, 2021
@adamcpovey adamcpovey self-assigned this Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant