-
Notifications
You must be signed in to change notification settings - Fork 29
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
densify_sites update #279
densify_sites update #279
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we make it an option with default False incase using an older MT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will both now be keyed by locus and alleles? will this always work?
last_END_positions_ht[sites_ht.key].last_END_position
what if sites_ht has different alleles but you still want to keep the locus?
that's a good point. what if I change |
Yeah both would need to be re_keyed by locus, so I think that will work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sparse MTs were previously only keyed by locus by default. They are now keyed by locus and alleles by default