-
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
Feature request: add per-read anchor requirement to junction extract
tool
#186
Comments
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 1, 2024
- closes griffithlab#186, reads now only 'support' a junction if they have at least a given minimum anchor length, supplied with the '-A' flag
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 2, 2024
- closes griffithlab#186, reads now only 'support' a junction if they have at least a given minimum anchor length, supplied with the '-A' flag (default 0)
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Jul 2, 2024
- closes griffithlab#186, reads now only 'support' a junction if they have at least a given minimum anchor length, supplied with the '-A' flag (default 0)
TimD1
added a commit
to fulcrumgenomics/regtools
that referenced
this issue
Sep 19, 2024
- closes griffithlab#186, reads now only 'support' a junction if they have at least a given minimum anchor length, supplied with the '-A' flag (default 0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been seeing cases where due to some library construction artifact a read has random-ish bases attached to its start/end. These can get aligned (1/2 bases, with the rest soft-clipped) to the next junction and cause that junction to have much more support than it should.
To remove this evidence from the junction, I was looking to implement an additional check that doesn't allow reads to support a junction if they anchor too lightly on the flanks of the junction. I'm aware of the
-a
argument, but that only controls whether the junction is valid. Once. a junction is valid, reads will be added to it regardless of their individual flanking status.If this will be implemented as optional (non-default) behavior, would you consider accepting it into the codebase?
Thanks!
The text was updated successfully, but these errors were encountered: