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

Assign multimappers randomly to one of the candidate mapping positions #359

Closed
marcelm opened this issue Nov 13, 2023 · 0 comments · Fixed by #367
Closed

Assign multimappers randomly to one of the candidate mapping positions #359

marcelm opened this issue Nov 13, 2023 · 0 comments · Fixed by #367

Comments

@marcelm
Copy link
Collaborator

marcelm commented Nov 13, 2023

(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.

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
marcelm added a commit that referenced this issue Nov 16, 2023
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
marcelm added a commit that referenced this issue Nov 20, 2023
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