-
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
Add densify_all_reference_sites
to perform a densify at all sites in a reference HT
#661
Conversation
…nstitute/gnomad_methods into jg/generalize_densify_at_all_ref_sites
…nstitute/gnomad_methods into jg/generalize_densify_at_all_ref_sites
… into jg/generalize_densify_at_all_ref_sites # Conflicts: # gnomad/utils/sparse_mt.py
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.
Two tiny suggestions and one question but then this LGTM!
mt = mtds.variant_data | ||
else: | ||
mt = mtds | ||
entry_keep_fields.add("END") |
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.
I'm not sure I know the use keep for keeping END here? Is it if you passed the vds.reference_data to this function with adding "END" to the entry_keep_fields?
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.
This supports a sparse MT, the END is in the reference_data of the VDS which we handle differently below, but in the sparse MT it's all in one so we need to make sure we keep it when when we localize entries
Co-authored-by: Mike Wilson <[email protected]>
I have been using this notebook for testing: http://localhost:8123/notebooks/gnomad-julia/gnomad_v4/test_v4_densify_all_reference_sites.ipynb