Cut & run - bowtie2 dovetail option
0
4
Entering edit mode
4.1 years ago
blur ▴ 280

Hi,

I am working on a CUT & RUN library for the first time. The methods state: "Dovetail alignment policy. Bowtie210 aligns each mate of a pair separately and then discards any pairs that have been aligned inconsistently. Dovetail refers to the situation when mates extend past each other. In the default setting, these alignments are discarded. Dovetail is unusual but encountered in CUT&RUN experiments. The --dove-tail setting10 was enabled to flag this situation as normal or “concordant” instead of elimination of such reads."

But, when I checked my version of bowtie2 it seems that the default includes inconsistent pairs and that the only dove-tail option is " --no-dovetail not concordant when mates extend past each other" So... do I run bowtie2 as is?

Thanks in advance,

cut and run dovetail bowtie2 • 4.0k views
ADD COMMENT
1
Entering edit mode

I will answer my own question :) I ran this with --dovetail as per the bowtie2 manual and to make sure it makes sense I used the protocol's original "--local --very-sensitive- local --no-unal --no-mixed --no-discordant --phred33 -I 10 -X 700" The results were almost identical (alignment rates were almost identical) - slightly better with --dovetail so --dovetail it is !

ADD REPLY
0
Entering edit mode

Hi, I am just wondering where you found those statements "Dovetail alignment policy. Bowtie210 aligns each mate of a pair separately and then discards any pairs that have been aligned inconsistently. Dovetail refers to the situation when mates extend past each other. In the default setting, these alignments are discarded. Dovetail is unusual but encountered in CUT&RUN experiments. The --dove-tail setting10 was enabled to flag this situation as normal or “concordant” instead of elimination of such reads."

ADD REPLY

Login before adding your answer.

Traffic: 2627 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6