-
Notifications
You must be signed in to change notification settings - Fork 26
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 report: junction extract tool should not count overlapping reads as double support for a junction #187
Comments
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 1, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 2, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 2, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 2, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 3, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map - updated regtools to v1.1.0
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Sep 19, 2024
- closes griffithlab#187, implemented by adding set of `reads` to `Junction`, and only incrementing `read_count` if read has not been seen yet - this commit should also increase RegTools speed by removing the barcode updating bottleneck caused by repeatedly copying the barcode map - updated regtools to v1.1.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the current implementation, read-mates can provide 2 "counts" to the same junction if they both span it. This results in inflated counts and therefore inflated significance when downstream tools consider the counts.
I would like to advocate for each queryname to be able to provide a maximum of 1 count towards any single junction. This must be implemented carefully so memory use doesn't spike too much.
The text was updated successfully, but these errors were encountered: