-
Notifications
You must be signed in to change notification settings - Fork 3
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
How to process mutect2 caller after fade out #16
Comments
You may need to sort your bam again after running |
@deb0612 Please let us know if this has fixed your problem -- currently, It is not clear from your comment if you mean using sort AFTER the FADE commands also leads to the same indexing error? |
Dear jblachly, |
@deb0612 We would certainly like to help solve this issue. Could you provide a minimal reproducible example? For example, could you provide SAM line that causes the error when using samtools index? |
Dear @charlesgregory, |
Try this:
In order to index the bam you need to do a coordinate sort. |
Thanks! It works. |
Dear sir,
I tried to use docker to process fade on my bam file, and the filtered bam cannot indexed by samtools so that I can't call somatic variants by mutect2.
command I used:
sudo docker run -v
pwd
:/data blachlylab/fade out -b -c /data/input.hg38.fade.bam >out.hg38.fade.filtered.bamsamtools index out.hg38.fade.filtered.bam
[E::hts_idx_push] Unsorted positions on sequence #1: 203008683 followed by 203008623
[E::sam_index] Read 'A00355:191:HJ2TWDSXY:2:1101:1009:14982' with ref_name='chr1', ref_length=248956422, flags=163, pos=2030d
Even I use samtools sort. The same error keep coming.
The text was updated successfully, but these errors were encountered: