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

bug in alignmentSieve --ATACshift #1268

Open
njwehi opened this issue Oct 9, 2023 · 0 comments
Open

bug in alignmentSieve --ATACshift #1268

njwehi opened this issue Oct 9, 2023 · 0 comments

Comments

@njwehi
Copy link

njwehi commented Oct 9, 2023

Hi,

I performed the alignmentSieve --ATACshift, before that the bam file was:

R1 1107 chr1 3050133 40 35M 3050133 -35
R2 1187 chr1 3050133 40 35M 3050133 35

after the alignmentSieve, output is

R1 1107 chr1 3050133 40 30M 3050137 -26
R2 1187 chr1 3050137 40 31M 3050133 26

It seems that the alignmentSieve failed to consider the situation that Read1 and Read2 are completely or virtually complementary, making the fragment size (26bp) shorter than the read lengths (30bp, 31bp).

Thanks

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

No branches or pull requests

1 participant