Paul Hoffman

Whoops, my bad. I wasn't properly checking for certain HDF5 attributes. Try reinstalling and running `combine` again.

Thanks for pointing this out, we will work on a fix.

Hi @MGjorgoska, This is likely because your object has cells present in one part of the object, but not another. This behavior isn't allowed in SeuratObject v5. If you can...

Hi Frederik, we are aware that this is a highly-requested feature. We are investigating ways to make this happen (it's a bit more complicated that just renaming the matrices in...

Hi Abel and Robert, `UpdateSeuratObject()` is not intended to transform internal assays from the v3 spec to the v5 spec. Given that conversion between the two assays is one-way only...

Hi Lionel, Thanks for reporting. We did it this way to control how `%||%` shows up in documentation (roxygen2 is rather aggressive about how it documents reexports). We'll adjust this...

Hi all, sorry for the delay The reason `Seurat` objects in v4 cannot be read in v3 is that in v4 the class definition was moved into {SeuratObject}. S4 classes...

Hi Stefano, we are working on expanding the types of matrices that can be used for expression matrices with `Seurat` objects, including `DelayedArray`-derived matrices, as part of Seurat/SeuratObject v5; we...

v5 assays were designed to be behaviorly similar to and forwards-compatible with v3 assays, but are fundamentally different and violate many of the conditions of a v3 Assay. These conditions...

@samuel-marsh @dcollins15 One thing to note is that `DefaultDimReduc()` is assay-aware, meaning it doesn't just search for dimensional reductions based on names, but also takes into account the assay used...