-
Notifications
You must be signed in to change notification settings - Fork 140
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 when using addClusters() on multiome data #2011
Comments
Hi @klgoss! Thanks for using ArchR! Please make sure that your post belongs in the Issues section. Only bugs and error reports belong in the Issues section. Usage questions and feature requests should be posted in the Discussions section, not in Issues. |
Sorry - hit enter too soon. The above post is from a related post. You can see that this error is coming from Seurat because your object is not properly formatted. If you need additional help, this seems like a Seurat issue to me. |
Hi klgoss, Have you figured this out? B |
Hi, I have the same issue here. Any suggestions will be appreciated! |
I am having the same issue. Seurat recently made an update, I guess that might be relevant? 2023-12-08 14:22:58.983551 : ERROR Found in FindNeighbors for <simpleError in validObject(.Object): invalid class “DimReduc” object: dimensions for ‘cell.embeddings’ must be in order> 2023-12-08 14:22:58.988674 : ERROR Found in runClusters for <simpleError in .logError(e, fn = "FindNeighbors", info = "", errorList = errorList, logFile = logFile): Exiting See Error Above> |
@rcorces @Sky970415 @Qi-Qiao @klgoss <simpleError in validObject(.Object): invalid class “DimReduc” object: dimensions for ‘cell.embeddings’ must be in order> |
Reverting to Seurat 4.3.0 fixes the problem with addClusters() |
Thank you! It worked:)) |
I reverted to Seurat 4.3.0 and still getting the same error. Any ideas? |
@ShashTrip1 |
I have the same problem after converting the seurat to 4.3.0. Any one figure it out? Many thank. |
I'm having the same issue as well. I'm using Seurat v5 for other analyses, so an update in ArchR to accommodate these changes would be very much appreciated. Thanks. |
Hi, I removed Seurat v5 and installed the packages below. Then it worked. I hope it will help. Install the remotes packageinstall.packages('remotes') Replace '4.3.0' with your desired versionremotes::install_version(package = 'Seurat', version = package_version('4.3.0')) |
I have done both just Seurat downgraded to 4.3.0 and the combined Seurat and Matrix downgrade and I am still having issues. Anyone else found a fix ? |
One option is to use |
Credit to @catpetersen for looking into this. Line 439 in 65968a4
Seurat won’t accept the embeddings matrix mat because the column names are not numbered perfectly in order. This only comes up in the multi-omic context where you run iterative LSI twice, so your column names are LSI1-30 and then LSI1-30 again. The fix should be simple but I dont have bandwidth to address it nor am I actively working with multiome data to test a fix. In theory, all you need to do is add a line directly before the one that errors out that renumbers the column names from LSI1-60 instead or similar so that they are in order. |
Following code solved the problem for me
|
Hello,
Thank you so much for creating such a great tool. I really appreciate how thorough you are in the manual and do a great job of explaining what you're doing/why you're doing it. I'm trying to use ArchR on 10X Multiome data. I'm following the tutorial here: https://greenleaflab.github.io/ArchR_2020/Ex-Analyze-Multiome.html and am getting an error on the addCluster() step.
Attach your log file
ArchR-addClusters-f90d110034e1-Date-2023-08-24_Time-15-28-08.442722.log
Describe the bug
I'm following the tutorial but get an error when I try to run addClusters(): <simpleError in validObject(.Object): invalid class “DimReduc” object: dimensions for ‘cell.embeddings’ must be in order>
Additional context
I did remove some cells that I previously determined to be low quality, so I'm not sure if this is causing the issue or not.
The text was updated successfully, but these errors were encountered: