Prepare for upcoming Seurat v5 release about clustree

[lazappi]

Hi @Gesmira. Thanks for the notification. I have done a quick check and it looks like things might break with the new version 😿. Is there any documentation about what has been changed and what changes developers need to make for compatibility?

[Gesmira]

Hi,
First I would make sure you have all of the v5 versions installed of the packages listed here. Explanations of updates are included here and v5 vignettes are here.

The SeuratObject structure has changed significantly in Seurat V5. Within each assay, we now have layers. Layers can have different cells and/or features from each other to allow for more flexibility in single-cell analyses. We expect that the change in object structure might be the cause of potential issues if there are any. More details on how to access data in the new structure can be found here.

We've tried to maintain backwards compatibility so ideally there shouldn't be any large issues. If you could also include some details of the errors you're facing, that would be helpful for us and might help in debugging as well. Finally, I would recommend checking out our issues to see if what you're facing has been previously reported!

Best,
Gesi

[saketkc]

Hi @lazappi,
Seuratv5 will make its way to CRAN soon and reverse-dependency checks indicate following tests will fail:

Running the tests in ‘tests/testthat.R’ failed.
Last 13 lines of output:
    1. ├─testthat::expect_warning(...) at test-clustree.R:165:4
    2. │ └─testthat:::quasi_capture(...)
    3. │   ├─testthat (local) .capture(...)
    4. │   │ └─base::withCallingHandlers(...)
    5. │   └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
    6. ├─clustree::clustree(...)
    7. └─clustree:::clustree.Seurat(...)
    8.   ├─Seurat::FetchData(x, vars = node_aes_value, slot = exprs)
    9.   └─SeuratObject:::FetchData.Seurat(x, vars = node_aes_value, slot = exprs)
   10.     ├─SeuratObject::FetchData(...)
   11.     └─SeuratObject:::FetchData.Assay5(...)
   12. ```

One potential fix would be to do:

op <- options(Seurat.object.assay.brackets = "v3")
on.exit(options(op), add = TRUE)

so that your users will stick to V3 assays. But it is possible you might have to update your accessor methods to be compatible with Seurat5 going ahead.

[lazappi]

Hi @saketkc. Yes, I am aware the tests are currently failing. I just haven't had a chance to make the changes yet.

As a sidenote, it would have been great if you sent out these messages in March when you say the changes were announced rather than waiting a few weeks before you want to do the release.

[lazappi]

I have pushed a version to the develop branch that should be compatible. I am happy to release this on CRAN but wanted to check if there are any timelines etc. I should be available of first.