-
Notifications
You must be signed in to change notification settings - Fork 77
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
IOError: [Errno 2] could not open alignment file #116
Comments
I've had the same problem, and had Optitype work for 9 samples but it gave this error on the 10th. |
I think I'm having the same problem, at least the error message is the same. I'm using the docker image and running on a linux server. My command line is:
From the time stamps it looks like the alignment starts and then quickly stops without providing any feedback. |
I am having this same issue, it was working for me but now am receiving this same error. Has anyone managed to resolve this? Thanks |
I fixed most of my problems with Optitype by switching ILP solver from cplex to cbc. Sometimes cplex does not converge to a solution, which gives problems down the line. Did not have of those problems with cbc (version 2.9.5) |
I fixed this problem, it is beacause when we run the images, its default user is “bioxxx”(I forget the name), but the "root" is required to execute the command of OptiTypePipeline.py. So we must use the command with |
Another thing important, if you are using Windows, you should also pay attention to using the shell with administrator privileges. |
Hi there,
I know this particular error has come up a few times now on different issues (e.g. #66), but I believe I have taken all the steps mentioned in the solution and am still receiving an error message (I am using the same folder I mounted as my output folder).
I am trying to run OptiType via docker using Docker Desktop for windows, and using fished fastq files that were successfully generated by razerS3. The command I am trying is:
D:\Test is an empty folder. I have similarly tried using an empty folder on my C: drive, and get the same message. Since this runs off of a linux subsystem, I have also tried replacing the windows filepaths with the corresponding linux subsystem filepaths, which returns an entirely new error:
I have ensured that these folders have full permissions for user and group. Attempting to write to ~ (/home/username/) gives the same result. Any advice would be greatly appreciated!
The text was updated successfully, but these errors were encountered: