-
Notifications
You must be signed in to change notification settings - Fork 25
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
test_gene_overrepresentation: visualising results #47
Comments
Just to follow up here, don't think this issue is a high priority (for workshop anyway) as may not have time for any pathway analyses, but if needed we could maybe have this below as a suggestion for how to visualise results. It's not using
|
I'm lost with this issue? Is it still relevant? |
Well I think we should have a tidybulk pathway/gene set analysis section at some point for a workshop. For the moment I just put some info in the supplementary here But it doesn't use the tidybulk pathway analysis, it just uses tidybulk de results and then clusterprofiler viz:
Not sure whether better to use clusterprofiler for the viz or try to visualise tidybulk pathway results? |
tidybulk can be used for calculation and attr(..., "") can be used to extract raw results and plotting them. Now sure if it's too messy. OK let's try to keep thinking about this |
Is this still relevant? @mblue9 any interest in doing a blog post on pathway analyses with tidybulk? so there would be a real application for me to get this improved. |
For me at the moment it's not a very high priority but I'd be happy to write a blog post if you want to focus on improving this aspect. Or we can wait til we have more time to work on it. Just noting here I have a tiny bit on tidybulk pathway analysis here which we could build on using that dataset or airway or another |
Do you have any recommendations for visualising the output of test_gene_overrepresentation?
Can it/should it use a clusterprofiler viz method: https://yulab-smu.github.io/clusterProfiler-book/ or a ggplot2 one?
The text was updated successfully, but these errors were encountered: