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

Add cancer_gene flag to get_gene_information #107

Merged
merged 3 commits into from
Nov 17, 2023

Conversation

mathieulemieux
Copy link
Member

graphkb/genes.py Outdated
@@ -444,6 +444,10 @@ def get_gene_information(
gene_flags["oncogene"] = convert_to_rid_set(get_oncokb_oncogenes(graphkb_conn))
logger.info("fetching tumour supressors list")
gene_flags["tumourSuppressor"] = convert_to_rid_set(get_oncokb_tumour_supressors(graphkb_conn))
logger.info("fetching cancer_gene list")
gene_flags["cancer_gene"] = convert_to_rid_set(get_cancer_genes(graphkb_conn))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mathieulemieux - did you check that IPR is already able to accept 'cancer_gene'?

Hi @Nithriel, @mathieulemieux
Is there a reason why 'cancer_gene' is not camel case like all the other gene flags? eg. (cancerRelated, tumourSuppressor)

Copy link
Member Author

@mathieulemieux mathieulemieux Nov 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you check that IPR is already able to accept 'cancer_gene'?

Work needed to be done on both side, gkb and ipr, and I don't thing it matters which one first, as long as we make sure it's done on both sides before release. @Nithriel should tell us when the work on her side is done.

Is there a reason why 'cancer_gene' is not camel case like all the other gene flags?

I thought we agreed on that before. I can change it to camel case if not too late from the ipr side. @Nithriel , what is the exact flag you're using on your side?

Copy link
Member Author

@mathieulemieux mathieulemieux Nov 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cancer_gene changed for cancerGene.

Copy link

codecov bot commented Nov 16, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e60a2e8) 90.33% compared to head (31b886b) 90.35%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #107      +/-   ##
===========================================
+ Coverage    90.33%   90.35%   +0.02%     
===========================================
  Files            8        8              
  Lines          838      840       +2     
===========================================
+ Hits           757      759       +2     
  Misses          81       81              
Flag Coverage Δ
unittests 90.35% <100.00%> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -23,7 +23,7 @@

CANONICAL_ONCOGENES = ["kras", "nras", "alk"]
CANONICAL_TS = ["cdkn2a", "tp53"]
CANONICAL_CG = ["ercc1", "fanci", "h2bc4", "h2bc17", "acvr1b"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, were these genes not good tests?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I first chose these gene randomly among the 500+ I had on hand, then I replaced them with gene 'alb' that I knew I had a related Statement in GKB. The list is here to be fill with more 'canonical' ones once we have some specific use cases we want to test for. I didn't wanted to make it looks as these genes were 'special', so I removed them.

@mathieulemieux mathieulemieux merged commit 1ba0713 into develop Nov 17, 2023
6 checks passed
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 this pull request may close these issues.

2 participants