In this tutorial we will continue the analysis of the integrated dataset. We will use the integrated PCA to perform the clustering. First we will construct a \(k\)-nearest neighbour graph in order to perform a clustering on the graph. We will also show how to perform hierarchical clustering and k-means clustering on PCA space.
Let’s first load all necessary libraries and also the integrated dataset from the previous step.
suppressPackageStartupMessages({
library(Seurat)
library(cowplot)
library(ggplot2)
library(pheatmap)
library(rafalib)
library(clustree)
})
alldata <- readRDS("data/results/covid_qc_dr_int.rds")The procedure of clustering on a Graph can be generalized as 3 main steps:
Build a kNN graph from the data
Prune spurious connections from kNN graph (optional step). This is a SNN graph.
Find groups of cells that maximizes the connections within the group compared other groups.
The first step into graph clustering is to construct a k-nn graph, in case you don’t have one. For this, we will use the PCA space. Thus, as done for dimensionality reduction, we will use ony the top N PCA dimensions for this purpose (the same used for computing UMAP / tSNE).
As we can see above, the Seurat function
FindNeighbors already computes both the KNN and SNN graphs,
in which we can control the minimal percentage of shared neighbours to
be kept. See ?FindNeighbors for additional options.
# check that CCA is still the active assay
alldata@active.assay
alldata <- FindNeighbors(alldata, dims = 1:30, k.param = 60, prune.SNN = 1/15)## Computing nearest neighbor graph
## Computing SNN
# check the names for graphs in the object.
names(alldata@graphs)## [1] "CCA"
## [1] "CCA_nn" "CCA_snn"
We can take a look at the kNN graph. It is a matrix where every connection between cells is represented as \(1\)s. This is called a unweighted graph (default in Seurat). Some cell connections can however have more importance than others, in that case the scale of the graph from \(0\) to a maximum distance. Usually, the smaller the distance, the closer two points are, and stronger is their connection. This is called a weighted graph. Both weighted and unweighted graphs are suitable for clustering, but clustering on unweighted graphs is faster for large datasets (> 100k cells).
pheatmap(alldata@graphs$CCA_nn[1:200, 1:200], col = c("white", "black"), border_color = "grey90",
main = "KNN graph", legend = F, cluster_rows = F, cluster_cols = F, fontsize = 2)pheatmap(alldata@graphs$CCA_snn[1:200, 1:200], col = colorRampPalette(c("white",
"yellow", "red"))(100), border_color = "grey90", main = "SNN graph", legend = F,
cluster_rows = F, cluster_cols = F, fontsize = 2)Once the graph is built, we can now perform graph clustering. The clustering is done respective to a resolution which can be interpreted as how coarse you want your cluster to be. Higher resolution means higher number of clusters.
In Seurat, the function FindClusters
will do a graph-based clustering using “Louvain” algorithim by default
(algorithm = 1). TO use the leiden algorithm, you need to
set it to algorithm = 4. See ?FindClusters for
additional options.
# Clustering with louvain (algorithm 1)
for (res in c(0.1, 0.25, 0.5, 1, 1.5, 2)) {
alldata <- FindClusters(alldata, graph.name = "CCA_snn", resolution = res, algorithm = 1)
}
# each time you run clustering, the data is stored in meta data columns:
# seurat_clusters - lastest results only CCA_snn_res.XX - for each different
# resolution you test.
plot_grid(ncol = 3, DimPlot(alldata, reduction = "umap", group.by = "CCA_snn_res.0.5") +
ggtitle("louvain_0.5"), DimPlot(alldata, reduction = "umap", group.by = "CCA_snn_res.1") +
ggtitle("louvain_1"), DimPlot(alldata, reduction = "umap", group.by = "CCA_snn_res.2") +
ggtitle("louvain_2"))We can now use the clustree package to visualize how
cells are distributed between clusters depending on resolution.
suppressPackageStartupMessages(library(clustree))
clustree(alldata@meta.data, prefix = "CCA_snn_res.")K-means is a generic clustering algorithm that has been used in many application areas. In R, it can be applied via the kmeans function. Typically, it is applied to a reduced dimension representation of the expression data (most often PCA, because of the interpretability of the low-dimensional distances). We need to define the number of clusters in advance. Since the results depend on the initialization of the cluster centers, it is typically recommended to run K-means with multiple starting configurations (via the nstart argument).
for (k in c(5, 7, 10, 12, 15, 17, 20)) {
alldata@meta.data[, paste0("kmeans_", k)] <- kmeans(x = alldata@reductions[["pca"]]@cell.embeddings,
centers = k, nstart = 100)$cluster
}
plot_grid(ncol = 3, DimPlot(alldata, reduction = "umap", group.by = "kmeans_5") +
ggtitle("kmeans_5"), DimPlot(alldata, reduction = "umap", group.by = "kmeans_10") +
ggtitle("kmeans_10"), DimPlot(alldata, reduction = "umap", group.by = "kmeans_15") +
ggtitle("kmeans_15"))clustree(alldata@meta.data, prefix = "kmeans_")The base R stats package already contains a function
dist that calculates distances between all pairs of
samples. Since we want to compute distances between samples, rather than
among genes, we need to transpose the data before applying it to the
dist function. This can be done by simply adding the
transpose function t() to the data. The distance methods
available in dist are: “euclidean”, “maximum”, “manhattan”,
“canberra”, “binary” or “minkowski”.
d <- dist(alldata@reductions[["pca"]]@cell.embeddings, method = "euclidean")As you might have realized, correlation is not a method implemented
in the dist function. However, we can create our own
distances and transform them to a distance object. We can first compute
sample correlations using the cor function. As you already
know, correlation range from -1 to 1, where 1 indicates that two samples
are closest, -1 indicates that two samples are the furthest and 0 is
somewhat in between. This, however, creates a problem in defining
distances because a distance of 0 indicates that two samples are
closest, 1 indicates that two samples are the furthest and distance of
-1 is not meaningful. We thus need to transform the correlations to a
positive scale (a.k.a. adjacency):
\[adj = \frac{1- cor}{2}\]
Once we transformed the correlations to a 0-1 scale, we can simply
convert it to a distance object using as.dist function. The
transformation does not need to have a maximum of 1, but it is more
intuitive to have it at 1, rather than at any other number.
# Compute sample correlations
sample_cor <- cor(Matrix::t(alldata@reductions[["pca"]]@cell.embeddings))
# Transform the scale from correlations
sample_cor <- (1 - sample_cor)/2
# Convert it to a distance object
d2 <- as.dist(sample_cor)After having calculated the distances between samples calculated, we
can now proceed with the hierarchical clustering per-se. We will use the
function hclust for this purpose, in which we can simply
run it with the distance objects created above. The methods available
are: “ward.D”, “ward.D2”, “single”, “complete”, “average”, “mcquitty”,
“median” or “centroid”. It is possible to plot the dendrogram for all
cells, but this is very time consuming and we will omit for this
tutorial.
# euclidean
h_euclidean <- hclust(d, method = "ward.D2")
# correlation
h_correlation <- hclust(d2, method = "ward.D2")Once your dendrogram is created, the next step is to define which
samples belong to a particular cluster. After identifying the
dendrogram, we can now literally cut the tree at a fixed threshold (with
cutree) at different levels to define the clusters. We can
either define the number of clusters or decide on a height. We can
simply try different clustering levels.
#euclidean distance
alldata$hc_euclidean_5 <- cutree(h_euclidean,k = 5)
alldata$hc_euclidean_10 <- cutree(h_euclidean,k = 10)
alldata$hc_euclidean_15 <- cutree(h_euclidean,k = 15)
#correlation distance
alldata$hc_corelation_5 <- cutree(h_correlation,k = 5)
alldata$hc_corelation_10 <- cutree(h_correlation,k = 10)
alldata$hc_corelation_15 <- cutree(h_correlation,k = 15)
plot_grid(ncol = 3,
DimPlot(alldata, reduction = "umap", group.by = "hc_euclidean_5")+ggtitle("hc_euc_5"),
DimPlot(alldata, reduction = "umap", group.by = "hc_euclidean_10")+ggtitle("hc_euc_10"),
DimPlot(alldata, reduction = "umap", group.by = "hc_euclidean_15")+ggtitle("hc_euc_15"),
DimPlot(alldata, reduction = "umap", group.by = "hc_corelation_5")+ggtitle("hc_cor_5"),
DimPlot(alldata, reduction = "umap", group.by = "hc_corelation_10")+ggtitle("hc_cor_10"),
DimPlot(alldata, reduction = "umap", group.by = "hc_corelation_15")+ggtitle("hc_cor_15")
)Finally, lets save the integrated data for further analysis.
saveRDS(alldata, "data/results/covid_qc_dr_int_cl.rds")Your turn
By now you should know how to plot different features onto your data. Take the QC metrics that were calculated in the first exercise, that should be stored in your data object, and plot it as violin plots per cluster using the clustering method of your choice. For example, plot number of UMIS, detected genes, percent mitochondrial reads.
Then, check carefully if there is any bias in how your data is separated due to quality metrics. Could it be explained biologically, or could you have technical bias there?
sessionInfo()## R version 4.1.3 (2022-03-10)
## Platform: x86_64-apple-darwin13.4.0 (64-bit)
## Running under: macOS Big Sur/Monterey 10.16
##
## Matrix products: default
## BLAS/LAPACK: /Users/asabjor/miniconda3/envs/scRNAseq2023/lib/libopenblasp-r0.3.21.dylib
##
## locale:
## [1] C/UTF-8/C/C/C/C
##
## attached base packages:
## [1] stats graphics grDevices utils datasets methods base
##
## other attached packages:
## [1] clustree_0.5.0 ggraph_2.1.0 rafalib_1.0.0 pheatmap_1.0.12
## [5] ggplot2_3.4.0 cowplot_1.1.1 SeuratObject_4.1.3 Seurat_4.3.0
## [9] RJSONIO_1.3-1.7 optparse_1.7.3
##
## loaded via a namespace (and not attached):
## [1] Rtsne_0.16 colorspace_2.1-0 deldir_1.0-6
## [4] ellipsis_0.3.2 ggridges_0.5.4 spatstat.data_3.0-0
## [7] farver_2.1.1 leiden_0.4.3 listenv_0.9.0
## [10] graphlayouts_0.8.4 getopt_1.20.3 ggrepel_0.9.2
## [13] fansi_1.0.4 codetools_0.2-18 splines_4.1.3
## [16] cachem_1.0.6 knitr_1.41 polyclip_1.10-4
## [19] jsonlite_1.8.4 ica_1.0-3 cluster_2.1.4
## [22] png_0.1-8 uwot_0.1.14 ggforce_0.4.1
## [25] shiny_1.7.4 sctransform_0.3.5 spatstat.sparse_3.0-0
## [28] compiler_4.1.3 httr_1.4.4 backports_1.4.1
## [31] assertthat_0.2.1 Matrix_1.5-3 fastmap_1.1.0
## [34] lazyeval_0.2.2 cli_3.6.0 tweenr_2.0.2
## [37] later_1.3.0 formatR_1.14 htmltools_0.5.4
## [40] tools_4.1.3 igraph_1.3.5 gtable_0.3.1
## [43] glue_1.6.2 RANN_2.6.1 reshape2_1.4.4
## [46] dplyr_1.0.10 Rcpp_1.0.10 scattermore_0.8
## [49] jquerylib_0.1.4 vctrs_0.5.2 nlme_3.1-161
## [52] spatstat.explore_3.0-5 progressr_0.13.0 lmtest_0.9-40
## [55] spatstat.random_3.0-1 xfun_0.36 stringr_1.5.0
## [58] globals_0.16.2 mime_0.12 miniUI_0.1.1.1
## [61] lifecycle_1.0.3 irlba_2.3.5.1 goftest_1.2-3
## [64] future_1.30.0 MASS_7.3-58.2 zoo_1.8-11
## [67] scales_1.2.1 tidygraph_1.2.2 promises_1.2.0.1
## [70] spatstat.utils_3.0-1 parallel_4.1.3 RColorBrewer_1.1-3
## [73] yaml_2.3.7 reticulate_1.27 pbapply_1.7-0
## [76] gridExtra_2.3 sass_0.4.5 stringi_1.7.12
## [79] highr_0.10 checkmate_2.1.0 rlang_1.0.6
## [82] pkgconfig_2.0.3 matrixStats_0.63.0 evaluate_0.20
## [85] lattice_0.20-45 tensor_1.5 ROCR_1.0-11
## [88] purrr_1.0.1 labeling_0.4.2 patchwork_1.1.2
## [91] htmlwidgets_1.6.1 tidyselect_1.2.0 parallelly_1.34.0
## [94] RcppAnnoy_0.0.20 plyr_1.8.8 magrittr_2.0.3
## [97] R6_2.5.1 generics_0.1.3 DBI_1.1.3
## [100] withr_2.5.0 pillar_1.8.1 fitdistrplus_1.1-8
## [103] survival_3.5-0 abind_1.4-5 sp_1.6-0
## [106] tibble_3.1.8 future.apply_1.10.0 KernSmooth_2.23-20
## [109] utf8_1.2.2 spatstat.geom_3.0-5 plotly_4.10.1
## [112] rmarkdown_2.20 viridis_0.6.2 grid_4.1.3
## [115] data.table_1.14.6 digest_0.6.31 xtable_1.8-4
## [118] tidyr_1.2.1 httpuv_1.6.8 munsell_0.5.0
## [121] viridisLite_0.4.1 bslib_0.4.2