-
Notifications
You must be signed in to change notification settings - Fork 57
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
gseaAfterBoot enriched genes #154
Comments
The function name is probably a misnomer, because it performs a competitive test like To step through gseaAfterBoot you might clone this repo from github, then |
Hi Andrew, |
As a proof-of-concept, you might use the signed hurdle p-values, eg, from the Working with the bootstraps, which would only be necessary if you are worried about gene-gene correlations, would be much more complicated--definitely beyond the scope of random thoughts on a github issues page. You would need to modify code to work |
Hi Andrew, |
Unfortunately, this would not be easy -- the competitive gene set test is really a much different beast than the GSEA of Subramanian. More like a project for a PhD student than a couple hours' work. |
Dear all,
thanks for the terrific tool. I've been analysing my dataset following the excellent MAIT tutorial (https://www.bioconductor.org/packages/release/bioc/vignettes/MAST/inst/doc/MAITAnalysis.html). Considering the gene set enrichment analysis, methods from the GSEA family (GSEA, fGSEA, etc) provide, in addition to the enrichment score and significance, also a list of genes contributing to the enrichment (leadingEdge). I was wondering if this kind of information can actually be derived using gseaAfterBoot.
I've been trying to run the source of gseaAfterBoot line by line but I encountered a number of dependency errors of internal functions of the library (eg functions from GSEA-by-boot.R cannot be found). Is there a better way to tinker with the MAST functions/items?
I hope I was clear, I'm looking forward to your reply.
Emanuele
The text was updated successfully, but these errors were encountered: