-
Notifications
You must be signed in to change notification settings - Fork 17
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
Assign multimappers randomly to one of the candidate mapping positions #359
Comments
marcelm
added a commit
that referenced
this issue
Nov 13, 2023
to one of the candidate mapping locations See #359
marcelm
added a commit
that referenced
this issue
Nov 16, 2023
by shuffling the top-scoring NAMs See #359
marcelm
added a commit
that referenced
this issue
Nov 16, 2023
by shuffling the top-scoring NAMs See #359
marcelm
added a commit
that referenced
this issue
Nov 16, 2023
by shuffling the NAMs that all have the same best number of hits See #359
marcelm
added a commit
that referenced
this issue
Nov 16, 2023
... by shuffling the NAMs that have the same score as the best one See #359
marcelm
added a commit
that referenced
this issue
Nov 16, 2023
... by shuffling the NAMs that have the same score as the best one See #359
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(As discussed by e-mail.)
For reads with multiple equally good mapping locations, we currently always pick the first location.
To reduce biases, we should instead pick one of the locations randomly.
The text was updated successfully, but these errors were encountered: