PF variants in fade region are not totally filtered about fade HOT 2 OPEN

Thank you for your kind words about fade!

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.

Hopefully that helps answer your question.

from fade.

@charlesgregory

Thank you, it is a good idea to use fade's extract. So I begin to find the breakpoint where the reverse-complemented happened.

The picture is taken from the article.

1. The first length refers to 47bp(softclip) + 8bp(inverted repeat), which should be trimmed with -c option.
2. BreakpointA refers to reverse-complemented point.
3. The second length refers to 8bp(inverted repeat) + 47bp(maybe the natural sequence base). But it seems fade software use this strategy to trim bases.

I want to know which strategy should be used, the first length strategy or the second length ?

Best,
xiucz

from fade.