-
Notifications
You must be signed in to change notification settings - Fork 71
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
VIRUSBREAKEND > failure identifying viral sequences #644
Comments
Hi, |
Of note, this does not happen on all my cram files (75 worked for ~15 that ended with that error). It seems to be coming from this line https://github.com/PapenfussLab/gridss/blob/09900c48d6d0e899a155cbc185f3d8e7c511bf05/scripts/virusbreakend#L498C19-L498C31 , which pipes 3 processes (executing the bash file created in the folder that extracts unmapped reads, running kraken2, and running gridss.kraken.SubsetToTaxonomy) and then moves $file_readname.tmp $file_readname . The weird part is that I do see in the log a message " gridss.kraken.SubsetToTaxonomy done" and I see a file *readname.tmp created with readnames in it, but not moved to *readname, so I guess there is a an error at some point for one read somewhere in the pipe. The timing file created mentions a non-zero status 141:
I will keep investigating, but if anyone has an idea, please share! |
Hello, I am attempting to utilize virusbreakend and have been running into an issue I have been unable to solve. Whenever I attempt to run the shell script I am returned with the following error: Thu Oct 12 11:52:52 EDT 2023: Failure running identifying viral sequences
Thu Oct 12 11:52:52 EDT 2023: Exit status 0 for print_failure "identifying viral sequences"
I have been unable to find a solution based on the error message given in the log files.
also here are some screenshots of my full terminal page as well as the log
Any help is greatly appreciated!
The text was updated successfully, but these errors were encountered: