-
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
Functions to process, filter, annotate and aggregate variants by transcript expression (get the pext scores per variant) #651
Conversation
…/gnomad_methods into jg/tx_annotate_mt_suggestions # Conflicts: # gnomad/utils/transcript_annotation.py
…ions Suggestions to tx_annotate_mt PR
…adinstitute/gnomad_methods into jg/tx_annotate_mt_suggestions # Conflicts: # gnomad/utils/transcript_annotation.py
…adinstitute/gnomad_methods into jg/tx_annotate_mt_suggestions
…/gnomad_methods into jg/tx_annotate_mt_suggestions # Conflicts: # gnomad/utils/transcript_annotation.py
…ions Suggestions to tx_annotate_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.
A few more comments. Also, can you modify the name of the PR and add to the PR description to indicate all the functions that are modified and added? Good example here
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.
Just a little bit more
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.
A few smaller things related to naming and doc strings
return ht | ||
|
||
|
||
def process_annotate_aggregate_variants( |
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 think this needs another name. Maybe something like "perform_tx_based_expression_annotation" or "perform_tx_annotation_pipeline", or something else?
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.
How about this new name?
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.
So close! Just a few more suggestions and a couple fixes to the new additions
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.
One small thing, and can you change the PR description with the updated function names. Then I will approve.
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!
Modifications:
process_consequences
,filter_vep_transcript_csqs
andpreprocess_variants_for_tx
to process and filter variants;import_gencode
intoresources_utils.py
since it's versatile in any genome build.Additions:
filter_vep_to_gene_list
,import_gencode
, andfilter_to_gencode_cds
to filter variants;vep.py
;tx_filter_variants_by_csqs
,tx_annotate_variants
,tx_aggregate_variants
and an ensemble functionperform_tx_annotation_pipeline
to combine the first 3 functions;