merging SCTransformed objects removes cell clusters #9695
Unanswered
daniquebax
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear Seurat team/users,
Thanks for the great package! I'm just running into an issue when I try to merge a couple of different datasets:
I am trying to merge 4 seuratobjects, of a timeline experiment. In which each timepoint should contain different cell types.

When I analyze (SCTransform, runPCA, find neighbors, find clusters, runUMAP) the objects by themselves (before merging) I get the clusters which I expect. Only one cluster at timepoint 0 and more cell types emerging as the timeline continues.
However, when I try to merge the 4 objects (according to https://satijalab.org/seurat/articles/integration_introduction.html#perform-integration-with-sctransform-normalized-datasets), I get a completely overlapping UMAP, with no biologically logical cell clusters:
Then my UMAP looks like this:

The 120h timepoint should be completely different than the ESC. And the ESC should not contain any different cell types. So, biologically, this doesn't make any sense
Things I've tried already:
-removing the JoinLayers, and split steps
-running SCTransform on individual objects before merging and using scale.data as variable features, as described in #2814
-running SCTransform on individual objects before merging and using SelectIntegrationFeatures as variable features, as described in #6185
-In RunUMAP adjusting the number of: dimensions, n.neighbors, min.dist or spread
Probably I am doing something wrong, but I cannot figure out what. Any help would be greatly appreciated!!
Best,
Danique
Beta Was this translation helpful? Give feedback.
All reactions