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
Executable paths not found #18
Comments
Hmm, i'm also getting an error after this point where the MR log file can't be found, again using |
Thanks for reporting the issue. Could you try in SIMBAD to add the full path for |
Can confirm that giving the full path to the pdbcur executable does work, and that using |
Okay, that's good to know. Could you try the following: $ ccp4-python
>>> import subprocess
>>> subprocess.call(['pdbcur.exe'])
###############################################################
###############################################################
###############################################################
### CCP4 7.0.061: PDBCUR version 7.0.061 : ##
###############################################################
User: felix Run date: 2/ 9/2018 Run time: 21:30:46
Please reference: Collaborative Computational Project, Number 4. 2011.
"Overview of the CCP4 suite and current developments". Acta Cryst. D67, 235-242.
as well as any specific reference in the program write-up.
***** ERROR #43 READ:
Logical file name not found.
1 This should print something like above to Note, do not use the absolute path. |
Can confirm that it prints out Logical file name not found |
Tested 494d508 on windows and the full executable path is now being found. |
System information
Problem description
When running cexec I get a
PyJobExecutableNotFoundError
.This seems to come from the line in
cexec
:Commenting the line out bypasses the problem. At first glance the error appears to arise because we're giving just the executable name rather than the full path to the executable. Therefore it searches the directory you're running the job in for the executable.
Example
Traceback
The text was updated successfully, but these errors were encountered: