Closed elsherbini closed 4 years ago
Never seen this, but the segmentation fault in the blast step doesn't look good :-/ Is this happening with a smaller input (e.g. a subset of the 300 genomes) ? I wonder if there is something weird maybe with one of the sequences that would explain this.
The other things that may be worth trying would be checking in the "err" log, and also running the diamond line (i.e. "/nfs/polzlab001/josephe/projects/find_prophage/.snakemake/conda/4a1c5e7a/bin/diamond blastp --query temp/virsorter_out/10N28654E4/fasta/10N28654E4_prots.fasta --db temp/virsorter_out/10N28654E4/r_0/db/Pool_new_unclustered --out temp/virsorter_out/10N28654E4/r_0/Contigs_prots_vs_New_unclustered.tab --threads 10 --outfmt 6 -b 1 --more-sensitive -k 500 --evalue 0.001") separately to check the output (sometimes the full list of errors / stdout are not well captured by VirSorter)
Thank you for your reply! The issue seems to be that I was using an oooold version of the virsorter data that didn't include the diamond file.
Good to know, I'll add this to the Readme. Thanks !
I'm having issues getting virsorter to run on some ~300 genomes, using conda and the wrapper script. I'm unable to use the docker image unfortunately on our cluster. The first error in the error log for all the genomes is that it can't find the output from diamond. I'm using diamond instead of blastp because no matter which version I installed from conda I kept getting segmentation faults on the blastp step.
I installed these dependencies in a fresh environment:
I'm running using the wrapper script (run by snakemake so these wildcards get filled in for each genome): (I'm trying
diamond
because I kept getting segmentation faults withblastp
no matter which version i installed)The first error in the error log says that it can't find the diamond output:
I've commented out the code that cleans up the db folder, here is what's in there after a failed run:
Here is the
out
log: