Using seurat FindClusters on the tSNE embeddings
1
0
Entering edit mode
3.3 years ago

My objective is using Leiden algorithm on the 2D tSNE embeddings of the pbmc.

What I am unable to understand is that if FindClusters is working on the reduced dimensions or on the whole dataset, since the size of clust_obj is same as sce . Also, the number of clusters are way more than scanpy provides using the 2D tSNE projection on the same data.

Please help me understand if I am doing this correctly. If I have made any mistakes, kindly help me correct it.

RNA-Seq seurat tSNE R • 1.8k views
ADD COMMENT
0
Entering edit mode

A reduced dimension is the whole dataset in terms of all cells have values for the redDims. Typically these redDims though are based on a selection of genes (the highly variable ones) and the reducedDim, (usually PCA) is then used for graph-based clustering.

ADD REPLY
0
Entering edit mode

So, what I have done will find clusters on the reduced dims itself, and not use the whole assay?

ADD REPLY
0
Entering edit mode

Yes, and I strongly suggest you exactly follow the Seurat clustering and/or integration vignette.

ADD REPLY
0
Entering edit mode
3.3 years ago
igor 13k

the size of clust_obj is same as sce

The input and output of all those functions is a Seurat object. Most of the size will be due to the expression data which would not change.

the number of clusters are way more than scanpy provides

Is it using the same resolution?

seurat documentations shows clustering on the whole assay

FindNeighbors uses PCA by default (the PCA is based on variable genes by default). Then FindClusters will use that SNN graph.

You should check the documentation for all the functions you are using which provide all of this information.

ADD COMMENT
0
Entering edit mode

Yes, it's using the same resolution as scanpy.

ADD REPLY

Login before adding your answer.

Traffic: 2321 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6