-
Notifications
You must be signed in to change notification settings - Fork 117
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
Does nf-core/atacseq apply an offset to each ATAC-seq fragment? #164
Comments
I am also interested in this question. |
Now that v2.0 has come out, I'm curious if this was implemented yet? It seems pretty standard for ATACseq reads to be shifted in this way, such that |
Tagging @drpatelh - could we get an update on the above? |
ktrns
added a commit
to ktrns/atacseq
that referenced
this issue
Jun 27, 2023
…eq data. Fixed nf-core#168 - Always write out genome fa and fai so IGV session file can be opened.
ktrns
added a commit
to ktrns/atacseq
that referenced
this issue
Jul 3, 2023
…ixed nf-core#168 (write genome fa and fai for IGV), fixed nf-core#169 (peak calling).
8 tasks
bjlang
added a commit
that referenced
this issue
Sep 6, 2023
bjlang
added a commit
that referenced
this issue
Sep 6, 2023
10 tasks
lpantano
added a commit
that referenced
this issue
Jul 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does the pipeline apply the standard +4/-5 offsets to aligned reads to account for the precise Tn5 binding site? I have not been able to find this in the documentation or in the code base.
The text was updated successfully, but these errors were encountered: