-
Notifications
You must be signed in to change notification settings - Fork 253
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
enricher not working properly #739
Comments
You may want to rephrase your question. By converting the results into a data.frame filtering is applied; first on (adjusted) p-values, and then on q-value. This is highlighted in #737. In the first part of your code ( By using the @ accessor, you directly pull out the raw c.q. all results. Finally, by reading the help page for p.adjust (type: |
Thanks for your reply, I think I made a mistake because I didn't see any description about pvalueCutoff
so if I got some results and I want to filter by pvalue , I need to set pAdjustMethod to "none", right ? and I have another question about qvalue > go_res = enricher(gene = target_id, + TERM2GENE = go_df[,c("go_id","gene")], + TERM2NAME = go_df[,c("go_id","go_description")], + pvalueCutoff = 0.05, + pAdjustMethod = "none", + qvalueCutoff = 1, + minGSSize = 10, + maxGSSize = 500)
> qvalue(go_res@result$pvalue)$qvalue %>% head()
[1] 0.0001686506 0.0096398217 0.0231162575 0.0231162575 0.0231162575 0.0343386871
> go_res@result$qvalue %>% head()
[1] 0.001281166 0.073229585 0.175604280 0.175604280 0.175604280 0.260856257
> packageVersion("qvalue")
[1] ‘2.36.0’ I want to know what causes this difference |
Yes, if Regarding gene set filtering: first values in in column Regarding the calculation of Values can be fully reproduced by manual calculation. See below.
|
Thank you for your patient answer |
I'm wondering how the enricher filters the results by these cutoffs, I also saw issue #737 but I think I'm encountering a bug rather than a feature
The text was updated successfully, but these errors were encountered: