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

feat: Allow read filtering based on mapping quality to junctions extract #189

Open
yfarjoun opened this issue Jul 3, 2024 · 0 comments · May be fixed by #194
Open

feat: Allow read filtering based on mapping quality to junctions extract #189

yfarjoun opened this issue Jul 3, 2024 · 0 comments · May be fixed by #194

Comments

@yfarjoun
Copy link

yfarjoun commented Jul 3, 2024

Currently all reads, regardless of mapping quality are considered as valid support for junctions. However, if reads have low mapping quality, that could indicate that they are mappable elsewhere with similar alignment score. It would be an improvement to allow the user to set a mapping quality threshold, below which reads are filtered and not considered as valid support for junctions.

TimD1 added a commit to fulcrumgenomics/regtools that referenced this issue Sep 19, 2024
 - closes griffithlab#183, flag based filtering
 - closes griffithlab#189, mapping quality based filtering
 - option '-F' filters reads containing any of these flags
 - option '-f' filters reads not containing all these flags
 - option '-q' filters reads below this mapping quality
TimD1 added a commit to fulcrumgenomics/regtools that referenced this issue Sep 19, 2024
 - closes griffithlab#183, flag based filtering
 - closes griffithlab#189, mapping quality based filtering
 - option '-F' filters reads containing any of these flags
 - option '-f' filters reads not containing all these flags
 - option '-q' filters reads below this mapping quality
@TimD1 TimD1 linked a pull request Sep 19, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant