-
Notifications
You must be signed in to change notification settings - Fork 183
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
samtools-1.3 sort bug #23
Comments
Hi Nikos, |
Hi Nicolas, Yes that would work, but make sure you don't just specify the output suffix but use the full output file name. It will work with all samtools >1.0 versions which is already a prerequisite for HiC-Pro. Bests, |
Hi Nikos, |
Hi Nicolas, Sorry for the delay. You are right. In samtools-1.2 (also 1.0 and 1.1) the option -T or -O has to be supplied if -o is used. I would suggest to keep both -o and -T to cover all cases. Bests, |
Fixed in current master (v2.7.3b). Thank you again Nikos ! |
Hi,
I had an error while running the pipeline during the bamfile pairing step. More specifically got the "Forward and reverse reads not paired. Check that BAM files are sorted." error from mergeSam.py file.
Tracking it down I realised that the 'samtools sort' output was never stored. In bowtie_combine.sh samtools sort is called by:
cmd="${SAMTOOLS_PATH}/samtools sort -@ ${N_CPU} -n ${BOWTIE2_FINAL_OUTPUT_DIR}/${prefix}.bwt2merged.bam ${BOWTIE2_FINAL_OUTPUT_DIR}/${prefix}.bwt2merged.sorted"
In samtools 1.3, "The obsolete samtools sort in.bam out.prefix usage has been removed. If you are still using ‑f, ‑o, or out.prefix, convert to use -T PREFIX and/or -o FILE instead."
Consider switching the sort call by specifying the output name with the -o flag.
Thank you for a great pipeline. :-)
Regards,
Nikos
The text was updated successfully, but these errors were encountered: