igrabski

Can you try updating to `Seurat 5.1.0` (the current CRAN release)? If that doesn't help, if you are able to share your Seurat object with me at igrabski [at] nygenome...

Hi Sara, in correspondence outside this issue, the original poster was able to resolve their issue by ensuring the `Seurat` and `SeuratObject` packages were up to date, closing their R...

This is fixed as of [this commit](https://github.com/satijalab/seurat/commit/21f82c81dc4096f68e253faf528356b5fbe28a40), and will be reflected in the next release.

Hi all, these issues should be resolved using the most up-to-date versions of `Seurat`, `SeuratObject`, and `Matrix`, and by installing `Matrix` and `irlba` from source as suggested as above. If...

Hi, are there any duplicates in the set of features `rev(goi)`?

Great, I'm glad this worked for you, @raunakkar! @ejscience, are you able to share your object? If you can email it to igrabski [at] nygenome [dot] org, I am happy...

Thanks for sharing your object -- the error turns out to be that one specified factor level had a typo, which resulted in `NA`s in `nucSamples$LowResOrdered` and consequently in `Idents(nucSamples)`....

Hi, this issue seems unlikely to be due to `JoinLayers`, but the runtime is definitely unusually long here. Based on the output of your object, the layer names look very...

Hi Ryan, it's possible the issue is related to the very long and similar layer names produced by this pairwise merging process. We will investigate whether naming causes an issue...

Yes, that amount of time is definitely abnormal! Would you be able to share your objects with me at this email address: igrabski [at] nygenome [dot] org? It's possible it...