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 x$consistency : $ operator is invalid for atomic vectors #133

Open
yfei-w opened this issue Jun 14, 2024 · 0 comments
Open

Error in x$consistency : $ operator is invalid for atomic vectors #133

yfei-w opened this issue Jun 14, 2024 · 0 comments

Comments

@yfei-w
Copy link

yfei-w commented Jun 14, 2024

Hi there!
I am running VISION using Seurat object and it was working fine before but I am now encountering error:

sig <- c("gene_sets/GO_ALPHA_BETA_T_CELL_ACTIVATION.gmt")
vis <- Vision(Seurat_obj, dimRed ="umap", signatures = sig, projection_methods = NULL)
vis <- analyze(vis)
  |=======================================================================================| 100%, Elapsed 00:00
  |=======================================================================================| 100%, Elapsed 00:00
  sigSize sigBalance
1      43          1
  |=======================================================================================| 100%, Elapsed 00:00
  |=======================================================================================| 100%, Elapsed 00:16
  |=======================================================================================| 100%, Elapsed 01:56
  |========================                                                                   |  26%, ETA 00:01
Warning: all scheduled cores encountered errors in user codeError in x$consistency : $ operator is invalid for atomic vectors

I believe this might because of the input Seurat object but I compared the ones that worked and the ones don't work and I could not find out what is causing the error. Would it be possible that you could point me to the right direction in how to fix the input or anything that would fix this issue?
Thanks!!

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

1 participant