Skip to content
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

Relevant changes in Bismark v0.14.4 #99

Open
PeteHaitch opened this issue Aug 19, 2015 · 1 comment
Open

Relevant changes in Bismark v0.14.4 #99

PeteHaitch opened this issue Aug 19, 2015 · 1 comment
Assignees

Comments

@PeteHaitch
Copy link
Owner

PeteHaitch commented Aug 19, 2015

From http://www.bioinformatics.babraham.ac.uk/projects/bismark/RELEASE_NOTES.txt:

Changed the FLAG values of paired-end alignments to the CTOT or CTOB strands so that reads can
be properly displayed in SeqMonk when imported as BAM files. This change affects only paired-end
alignments in --pbat or --non_directional mode. In detail we simply swapped the Read 1 and Read 2
FLAG values round so reads now resemble exactly concordant read pairs to the OT and OB strands.
Note that results produced by the methylation extractor or further downstream of that are not
affected by this change. FLAG values now look like this:

                                  Read 1       Read 2

                          OT:         99          147

                          OB:         83          163

                          CTOT:      147           99

                          CTOB:      163           83
@PeteHaitch PeteHaitch self-assigned this Aug 19, 2015
@PeteHaitch
Copy link
Owner Author

PeteHaitch commented May 6, 2016

I don't have any --pbat or --non_directional libraries with which to test. However, I think this will cause problems with methtuple. Specifically, read-1 when mapped to CTOT or CTOB has the "second in pair" flag set when it is really the first in the pair. SImilarly, read-2 when mapped to CTOT or CTOB has the "first in pair" flag set when it is really the second in the pair. So this change seems like a workaround in order to get Seqmonk to display things in a desired way, but it also breaks the meaning of the flags according to the SAM specifications. Have raised with Felix FelixKrueger/Bismark#41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant