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

Error in pathfindR with finding gene set #153

Closed
richardcoca opened this issue Jan 27, 2023 · 4 comments
Closed

Error in pathfindR with finding gene set #153

richardcoca opened this issue Jan 27, 2023 · 4 comments

Comments

@richardcoca
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Prepare input as 'library(pathfindR)

#create input data frame
input_df<-#imported excel file with three columns
output_df <- run_pathfindR(input_df, 0.005)'

  1. See error

Error in pathfindR::fetch_gene_set(gene_sets = gene_sets, min_gset_size = min_gset_size, :
gene_sets should be one of “KEGG”, “Reactome”, “BioCarta”, “GO-All”, “GO-BP”, “GO-CC”, “GO-MF”, “cell_markers”, “mmu_KEGG”, “Custom”

Expected behavior
I didn't get a pathway generated.

Desktop (please complete the following information):

  • OS: macOS

** R Session Information:**
R version 4.0.3 (2020-10-10)
Platform: x86_64-apple-darwin17.0 (64-bit)
Running under: macOS Big Sur 10.16

Matrix products: default
LAPACK: /Library/Frameworks/R.framework/Versions/4.0/Resources/lib/libRlapack.dylib

Context
If I rewrite syntax to specify gene set, it gives me non-numerical p-value error

@egeulgen
Copy link
Owner

this occurred because the second argument of run_pathfindR() is gene_sets. Please try run_pathfindR(input_df, p_val_threshold = 0.005 and it should work

@richardcoca
Copy link
Author

richardcoca commented Jan 28, 2023 via email

@egeulgen
Copy link
Owner

The error refers to the p-values in the data frame. I think the order is wrong. It should be gene name, lfc, p value

@richardcoca
Copy link
Author

richardcoca commented Jan 30, 2023 via email

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

2 participants