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

TP53 mutation prediction from metadata #66

Closed
joshlevy89 opened this issue Oct 26, 2016 · 3 comments
Closed

TP53 mutation prediction from metadata #66

joshlevy89 opened this issue Oct 26, 2016 · 3 comments

Comments

@joshlevy89
Copy link
Member

I'm new to the group so let me know if there is a better place to write this kind of thing...

I am working on assessing whether the gene expression data provides considerably more predictive information than the metadata (samples.tsv). I created a notebook to predict TP53 mutation from the metadata alone and achieved .82 AUROC. This is substantially lower than the AUROC achieved using gene expression (.92). I have a few other ideas for what to do next, but am interested in any input. The new notebook can be found on my forked repo (4.TCGA-Metadata-MLexample). Have not submitted a pull request.

@dhimmel
Copy link
Member

dhimmel commented Oct 26, 2016

I'm new to the group so let me know if there is a better place to write this kind of thing...

Nope Issues are the right place. I'm going to tag a few related issues for convenience: #8, #21, #47.

See this notebook from #47 which looks at performance for several mutations only using the covariates (metadata). So I think the next step based on what currently exists will be find a way to fit two models:

  1. using covariates only
  2. using covariates and gene expression

Then seeing how much better 2 performs will give us the marginal contribution of gene expression over sample metadata. @joshlevy89, do you want to tackle this analysis. You can make a new directory in explore and open a pull request (even if it's still a work in progress -- just put WIP in the pull request title).

Cheers!

@joshlevy89
Copy link
Member Author

@dhimmel Thanks for the reply. That sounds good. I can tackle it in the next couple of days.

@rdvelazquez
Copy link
Member

I think this was closed by #67.

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

No branches or pull requests

3 participants