You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
After diving into your wonderful tool, I find one more question. After running my bam file (reacalibrate.bam with GATK best practice) with the fade annotate and fade out (without -c) , most PF variants will not show in the bam( The first IGV panel bam, fade.bam).
And the second bam, mt2.bam, which comes from mutect2 --bamout option, let's ignore it.
However, there are still some FP variants which can not be filtered by fade software, I know it is not a bug of fade.
We know that fade can filter/trim reads that meet fade‘s inter threshold. But if a variant contains reads both meet fade‘s inter threshold (read A) and not (read B). Should we remove the read B also?
Best,
xiucz
The text was updated successfully, but these errors were encountered:
Currently the only reads fade can remove are those it identifies as "artifact". It determines this by realigning the read to the local sequence of the original alignment. If you queryname sort your bam/sam file before using fade out fade will remove any read pair in which either mate is identified as "artifact". In order to assess variants, as a way of determining artifact reads, fade would have to use some variant caller or perform some rudimentary variant calling as part of its analysis.
This would be quite out of fade's scope and would likely be a large undertaking.
Currently you could use fade's extract function to extract the artifact reads in bam format. Then you could create a bed file of regions to in which you wish to ignore variants using the bam file.
Hi,
After diving into your wonderful tool, I find one more question. After running my bam file (reacalibrate.bam with GATK best practice) with the
fade annotate
andfade out
(without -c) , most PF variants will not show in the bam( The first IGV panel bam, fade.bam).However, there are still some FP variants which can not be filtered by fade software, I know it is not a bug of fade.
We know that fade can filter/trim reads that meet fade‘s inter threshold. But if a variant contains reads both meet fade‘s inter threshold (read A) and not (read B). Should we remove the read B also?
Best,
xiucz
The text was updated successfully, but these errors were encountered: