Table of Contents

Hierarchical Consensus Partitioning

Author: Zuguang Gu ( z.gu@dkfz.de )

Date: 2021-05-19

Package version: 1.8.0


The problem

Choosing the best k (number of partitions) is not an easy problem for consensus partitioning. In consensus partitioning, various metrics based on the consensus matrix are normally calculated, e.g. PAC scores (or 1-PAC) or mean silhouette scores, and the best k is normally selected based on the “extremal method”, i.e. to select the k that corresponds to the highest or lowest values of the metrics. When the number of partitions is small, it is relatively easy to determine the best k with high confidence, while when the real number of clusters gets very large, it is difficult to identify the correct or approximate k for several reasons, some of which we list in the following: 1) Variation in the “big clusters” affect the eCDF of the consensus matrix stronger than variation in the “small clusters”, this can strongly affect PAC scores. 2) Groups showing weaker differences (we can call them secondary groups) are more difficult to separate especially when there are already other groups showing distinct differences (we can call them major groups). 3) The curve of various metrics against k gets flattened for large k and the value of k with the extremal values will be less distinct.

The following four figures illustrate the eCDF curves of a consensus matrix, 1-PAC, mean silhouette and concordance scores for different k where k ranges from 2 to 10 (from the analysis here). Basically, when k >= 5, the eCDF curves have a long plateau with less and less curvature, i.e. they lose their step-like shape, which results in 1-PAC getting almost stable for k >= 5. Also for the curves of mean silhouette and concordance scores against k, they are almost flattened for k >= 3. If using the “extremal method”, k = 6 is taken as the best k because 1-PAC selects k = 9 while mean silhouette and concordance select k = 6.

When inspecting the consensus heatmaps for different k (cf. heatmaps below), actually it is difficult to assess whether the partitioning for k = 6 is better than any other k in [5, 10].

The problems of the “big clusters / small clusters” or “major clusters / secondary clusters” in selecting the best k are mainly due to the consensus partitioning procedure that all samples are taken into account equally. From version 1.9.0, we proposed a new method which tries to solve this issue by applying consensus partitioning in a hierarchical way. Simply speaking, one could first classify the samples into nmajor groups (nmajor is a small number, major clusters), then for each subgroup of samples, one could repeatedly apply consensus clustering. By this means, theoretically, small clusters or secondary clusters could be detected in later steps of the hierarchical procedure.

The workflow

The figure below illustrates the workflow of the hierarchical consensus partitioning.

The steps are:

  1. The input matrix M is treated as the top node in the hierarchy, with a node label “0”.
  2. Apply multiple combinations of top-value methods and partitioning methods on the matrix with a small set of k (e.g., 2-4).
  3. Select the consensus partitioning result (i.e. with a specific top-value method and a partitioning method) which shows the highest 1-PAC scores with its best k. This consensus partitioning is treated as the partitioning on the node.
  4. If this partitioning is not stable (e.g., 1-PAC > 0.8), the hierarchical partitioning stops and the columns of the matrix are treated as a subgroup.
  5. If the number of signatures or the fraction of signatures to the total number of rows in the matrix is too small, it means the partitioning does not show biological meaningful results and the hierarchical partitioning stops. The columns are treated as a subgroup.
  6. If the partioning passes the filtering on step 4 and 5, the columns are split into two groups, where the one group with the label “1” from cola classification and the second group contains columns with other class labels, with the corresponding submatrices denoted as M1 and M0 respectively. In cola, the group with label “1” always has the minimal mean within-group distance. The two submatrices are treated as two children node of the current node and “1” or “0” is append to the node label as the labels for the two children nodes.
  7. For each submatrix, if the number of columns is too small, the hierarchical partitioning stops and the columns are treated as a subgroup.
  8. If the submatrix has enough columns, go to step 2 to perform consensus partioning recursively.

The process of the hierarchical consensus partitioning is saved as a dendrogram internally.

The usage

In this section, we demonstrate the functionalities of hierarchical consensus partitioning. The design of these new functionalities tries to be as consistent as the functions for normal consensus partitioning in cola, i.e., the function consensus_partition() or run_all_consensus_partition_methods(). Thus, you may find many functions having the same names as the functions for normal consensus partitioning.

The following code applies hierarchical consensus partitioning on the Golub dataset. Function hierarchical_partition() applies the analysis where the main arguments are very similar as in consensus_partition() or run_all_consensus_partition_methods(), which are the input matrix, the sample annotations and the number of cores. The function returns a HierarchicalPartition object.

library(golubEsets)  # from Bioconductor
data(Golub_Merge)
m = exprs(Golub_Merge)
colnames(m) = paste0("sample_", colnames(m))
anno = pData(Golub_Merge)

m[m <= 1] = NA
m = log10(m)

m = adjust_matrix(m)

# apply quantile normalization
library(preprocessCore)  # from Bioconductor
cn = colnames(m)
rn = rownames(m)
m = normalize.quantiles(m)
colnames(m) = cn
rownames(m) = rn

set.seed(123)
golub_cola_rh = hierarchical_partition(
    m, anno = anno[, c("ALL.AML"), drop = FALSE]
)

Some important arguments in hierarchical_partition() are listed as follows:

The object golub_cola_rh is already generated and shipped in cola package, so we directly load it.

data(golub_cola_rh)
golub_cola_rh
## A 'HierarchicalPartition' object with 'ATC:skmeans' method.
##   On a matrix with 4116 rows and 72 columns.
##   Performed in total 1050 partitions.
##   There are 5 groups.
## 
## Hierarchy of the partition:
##   0, 72 cols
##   |-- 01, 31 cols, 494 signatures
##   |   |-- 011, 11 cols (b)
##   |   |-- 012, 11 cols (b)
##   |   `-- 013, 9 cols (b)
##   |-- 02, 24 cols, 178 signatures (c)
##   `-- 03, 17 cols (a)
## Stop reason:
##   a) PAC score was too big.
##   b) Subgroup had too few columns.
##   c) There were too few signatures.
## 
## Following methods can be applied to this 'HierarchicalPartition' object:
##  [1] "all_leaves"            "all_nodes"             "cola_report"           "collect_classes"      
##  [5] "colnames"              "compare_signatures"    "dimension_reduction"   "functional_enrichment"
##  [9] "get_anno"              "get_anno_col"          "get_classes"           "get_matrix"           
## [13] "get_signatures"        "is_leaf_node"          "max_depth"             "ncol"                 
## [17] "node_info"             "nrow"                  "rownames"              "show"                 
## [21] "suggest_best_k"        "test_to_known_factors" "top_rows_heatmap"      "top_rows_overlap"     
## 
## You can get result for a single node by e.g. object["01"]

Directly entering golub_cola_rh prints the hierarchy. As you already see in the previous output, the node in the hierarchy is encoded in a special way. As explained in previous text, on each node, the columns are split into two groups and “1” or “0” is appended with the current node label to the two children node labels. Thus, the length (or nchar) of the label represents the depth of that node in the hierarchy and from the node label, it is also straightforward to infer its parent node. E.g., a node with label 0101 has its parent node 010.

Also you can find the functions that can be applied to the HierarchicalPartition object.

The first function you may try is to see how the columns are separated and the hierarchy of the subgroups. This can be done by collect_classes() function:

collect_classes(golub_cola_rh)

plot of chunk unnamed-chunk-4

There are several metrics saved for each node which can be retrieved by node_info().

node_info(golub_cola_rh)
##    id best_method depth best_k n_columns n_signatures p_signatures node_height is_leaf
## 1   0 ATC:skmeans     1      3        72         2046   0.49708455   1.0000000   FALSE
## 2  01 ATC:skmeans     2      4        31          494   0.12001944   0.5877504   FALSE
## 3 011 not applied     3     NA        11           NA           NA   0.0000000    TRUE
## 4 012 not applied     3     NA        11           NA           NA   0.0000000    TRUE
## 5 013 not applied     3     NA         9           NA           NA   0.0000000    TRUE
## 6  02 ATC:skmeans     2      3        24          178   0.04324587   0.0000000    TRUE
## 7  03  ATC:kmeans     2      3        17           NA           NA   0.0000000    TRUE

There are following columns from node_info():

These values are useful to merge the children nodes.

Most functions for dealing with the HierarchicalPartition object accept a merge_node argument, where you can set different paremeters to select the children node to merge. These parameters should be set by the function merge_node_param() function. And there are the four parameters can be adjusted:

node_height is the most direct way to adjust the hierarchy which controls which levels on the dendrogram to merge. In the following, we demonstrate to manuplate the dendrogram by setting different node_height values.

We set 0.6 and 0.8 to filter node_height:

collect_classes(golub_cola_rh, merge_node = merge_node_param(node_height = 0.52))
collect_classes(golub_cola_rh, merge_node = merge_node_param(node_height = 0.6))
collect_classes(golub_cola_rh, merge_node = merge_node_param(node_height = 0.8))

plot of chunk unnamed-chunk-7

We can also compare to the normal consensus partitioning classification:

data(golub_cola)
golub_cola_cp = golub_cola["ATC:skmeans"]
collect_classes(golub_cola_rh, 
    anno = cbind(get_anno(golub_cola_rh), 
        cola_cp = factor(get_classes(golub_cola_cp, k = suggest_best_k(golub_cola_cp))[, "class"])),
    anno_col = c(get_anno_col(golub_cola_rh))
)

plot of chunk unnamed-chunk-8

get_classes() returns the subgroups of columns:

get_classes(golub_cola_rh)
## sample_39 sample_40 sample_42 sample_47 sample_48 sample_49 sample_41 sample_43 sample_44 sample_45 
##      "03"      "03"     "012"     "013"     "011"      "03"     "011"     "013"     "013"     "013" 
## sample_46 sample_70 sample_71 sample_72 sample_68 sample_69 sample_67 sample_55 sample_56 sample_59 
##     "013"     "013"      "02"     "012"     "011"     "011"     "012"      "03"      "03"     "013" 
## sample_52 sample_53 sample_51 sample_50 sample_54 sample_57 sample_58 sample_60 sample_61 sample_65 
##      "02"      "02"      "02"      "02"     "013"      "02"      "02"      "02"      "02"      "02" 
## sample_66 sample_63 sample_64 sample_62  sample_1  sample_2  sample_3  sample_4  sample_5  sample_6 
##     "012"      "02"      "02"      "02"      "03"     "012"      "03"      "03"     "011"      "03" 
##  sample_7  sample_8  sample_9 sample_10 sample_11 sample_12 sample_13 sample_14 sample_15 sample_16 
##      "03"      "03"     "012"     "012"     "012"      "02"     "011"     "012"     "011"     "011" 
## sample_17 sample_18 sample_19 sample_20 sample_21 sample_22 sample_23 sample_24 sample_25 sample_26 
##     "012"      "03"     "013"     "011"     "011"      "03"      "03"     "011"      "03"      "03" 
## sample_27 sample_34 sample_35 sample_36 sample_37 sample_38 sample_28 sample_29 sample_30 sample_31 
##      "03"      "02"      "02"      "02"      "02"      "02"      "02"     "012"      "02"      "02" 
## sample_32 sample_33 
##      "02"      "02"

Also you can control merge_node argument to decide on which level …

get_classes(golub_cola_rh, merge_node = merge_node_param(node_height = 0.8))
## sample_39 sample_40 sample_42 sample_47 sample_48 sample_49 sample_41 sample_43 sample_44 sample_45 
##      "03"      "03"      "01"      "01"      "01"      "03"      "01"      "01"      "01"      "01" 
## sample_46 sample_70 sample_71 sample_72 sample_68 sample_69 sample_67 sample_55 sample_56 sample_59 
##      "01"      "01"      "02"      "01"      "01"      "01"      "01"      "03"      "03"      "01" 
## sample_52 sample_53 sample_51 sample_50 sample_54 sample_57 sample_58 sample_60 sample_61 sample_65 
##      "02"      "02"      "02"      "02"      "01"      "02"      "02"      "02"      "02"      "02" 
## sample_66 sample_63 sample_64 sample_62  sample_1  sample_2  sample_3  sample_4  sample_5  sample_6 
##      "01"      "02"      "02"      "02"      "03"      "01"      "03"      "03"      "01"      "03" 
##  sample_7  sample_8  sample_9 sample_10 sample_11 sample_12 sample_13 sample_14 sample_15 sample_16 
##      "03"      "03"      "01"      "01"      "01"      "02"      "01"      "01"      "01"      "01" 
## sample_17 sample_18 sample_19 sample_20 sample_21 sample_22 sample_23 sample_24 sample_25 sample_26 
##      "01"      "03"      "01"      "01"      "01"      "03"      "03"      "01"      "03"      "03" 
## sample_27 sample_34 sample_35 sample_36 sample_37 sample_38 sample_28 sample_29 sample_30 sample_31 
##      "03"      "02"      "02"      "02"      "02"      "02"      "02"      "01"      "02"      "02" 
## sample_32 sample_33 
##      "02"      "02"

suggest_best_k() extracts the the best k as well as related metrics for the best partitions on each node.

suggest_best_k(golub_cola_rh)
##  node best_method is_leaf best_k 1-PAC mean_silhouette concordance n_sample   
##     0 ATC:skmeans              3 0.980           0.971       0.987       72 **
##    01 ATC:skmeans              4 0.958           0.878       0.951       31 **
##   011 not applied    ✓(b)     NA    NA              NA          NA       11   
##   012 not applied    ✓(b)     NA    NA              NA          NA       11   
##   013 not applied    ✓(b)     NA    NA              NA          NA        9   
##    02 ATC:skmeans    ✓(c)      3 0.978           0.921       0.965       24 **
##    03  ATC:kmeans    ✓(a)      3 0.625           0.826       0.911       17   
## --------------------------------------------------------------------------- 
## Stop reason:
##   a) PAC score was too big.
##   b) Subgroup had too few columns.
##   c) There were too few signatures.

Another important function which gives a direct feeling of how the subgrouping look like is to check the signatures that are significantly different between subgroups. Similarly as normal consensus partitioning, we can use get_signatures() here. The function basically applies get_signatures,ConsesusPartition-method() on the partition on every node and collect all the signatures as the signatures of the hierarchical consensus partitioning.

get_signatures(golub_cola_rh, verbose = FALSE)

plot of chunk unnamed-chunk-12

Other useful functions are dimension_reduction(), compare_signatures() and test_to_known_factors(). The usages are as follows:

dimension_reduction(golub_cola_rh)
## use UMAP

plot of chunk unnamed-chunk-13

compare_signatures(golub_cola_rh)

plot of chunk unnamed-chunk-14

test_to_known_factors(golub_cola_rh)
##            ALL.AML
## class 9.519018e-11

Note all these functions mentioned above allow the merge_node argument to adjust the hierarchy.

Automated reporting

One of the key advantage of cola package is it automates the complete analysis. There is also a cola_report() function for HierarchicalPartition class and it automates the complete analysis as well. Simply run:

rh = hierarchical_partition(...)
cola_report(rh, output_dir = ...)

Work with huge datasets

In the vignette “Work with Big Datasets”, we introduced a DownSamplingConsensusPartition class and its corresponding method consensus_partition_by_down_sampling() which performs consensus partitioning on a randomly sampled subset of columns and predict the subgroup labels for the remaining columns from the … Here hierarchical_partition() also supports down sampling which makes it possible to work on extremly large datasets.

The only thing for dealing with huge datasets is to set the subset argument.

hierarchical_partition(..., subset = ...)

On each node, to consider the euqal sizes of groups, we first perform a fast k-means and random sample columns with different weight according to the size the groups.

Session info

sessionInfo()
## R version 4.1.0 (2021-05-18)
## Platform: x86_64-pc-linux-gnu (64-bit)
## Running under: Ubuntu 20.04.2 LTS
## 
## Matrix products: default
## BLAS:   /home/biocbuild/bbs-3.13-bioc/R/lib/libRblas.so
## LAPACK: /home/biocbuild/bbs-3.13-bioc/R/lib/libRlapack.so
## 
## locale:
##  [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=en_GB             
##  [4] LC_COLLATE=C               LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8   
##  [7] LC_PAPER=en_US.UTF-8       LC_NAME=C                  LC_ADDRESS=C              
## [10] LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       
## 
## attached base packages:
##  [1] grid      parallel  stats4    stats     graphics  grDevices utils     datasets  methods  
## [10] base     
## 
## other attached packages:
##  [1] GetoptLong_1.0.5     mvtnorm_1.1-1        matrixStats_0.58.0   circlize_0.4.12     
##  [5] ComplexHeatmap_2.8.0 hu6800.db_3.2.3      org.Hs.eg.db_3.13.0  AnnotationDbi_1.54.0
##  [9] IRanges_2.26.0       S4Vectors_0.30.0     Biobase_2.52.0       BiocGenerics_0.38.0 
## [13] cola_1.8.0           knitr_1.33           markdown_1.1        
## 
## loaded via a namespace (and not attached):
##  [1] colorspace_2.0-1       rjson_0.2.20           ellipsis_0.3.2         mclust_5.4.7          
##  [5] XVector_0.32.0         GlobalOptions_0.1.2    clue_0.3-59            bit64_4.0.5           
##  [9] RSpectra_0.16-0        fansi_0.4.2            xml2_1.3.2             codetools_0.2-18      
## [13] splines_4.1.0          doParallel_1.0.16      cachem_1.0.5           impute_1.66.0         
## [17] polyclip_1.10-0        jsonlite_1.7.2         Cairo_1.5-12.2         umap_0.2.7.0          
## [21] annotate_1.70.0        cluster_2.1.2          png_0.1-7              data.tree_1.0.0       
## [25] compiler_4.1.0         httr_1.4.2             assertthat_0.2.1       Matrix_1.3-3          
## [29] fastmap_1.1.0          htmltools_0.5.1.1      tools_4.1.0            gtable_0.3.0          
## [33] glue_1.4.2             GenomeInfoDbData_1.2.6 dplyr_1.0.6            Rcpp_1.0.6            
## [37] slam_0.1-48            eulerr_6.1.0           jquerylib_0.1.4        vctrs_0.3.8           
## [41] Biostrings_2.60.0      iterators_1.0.13       polylabelr_0.2.0       xfun_0.23             
## [45] stringr_1.4.0          mime_0.10              lifecycle_1.0.0        irlba_2.3.3           
## [49] XML_3.99-0.6           dendextend_1.15.1      zlibbioc_1.38.0        scales_1.1.1          
## [53] microbenchmark_1.4-7   RColorBrewer_1.1-2     yaml_2.2.1             gridExtra_2.3         
## [57] memoise_2.0.0          reticulate_1.20        ggplot2_3.3.3          sass_0.4.0            
## [61] stringi_1.6.2          RSQLite_2.2.7          highr_0.9              genefilter_1.74.0     
## [65] foreach_1.5.1          shape_1.4.6            GenomeInfoDb_1.28.0    rlang_0.4.11          
## [69] pkgconfig_2.0.3        bitops_1.0-7           evaluate_0.14          lattice_0.20-44       
## [73] purrr_0.3.4            bit_4.0.4              tidyselect_1.1.1       magrittr_2.0.1        
## [77] R6_2.5.0               magick_2.7.2           generics_0.1.0         DBI_1.1.1             
## [81] pillar_1.6.1           survival_3.2-11        KEGGREST_1.32.0        RCurl_1.98-1.3        
## [85] tibble_3.1.2           crayon_1.4.1           utf8_1.2.1             rmarkdown_2.8         
## [89] viridis_0.6.1          skmeans_0.2-13         blob_1.2.1             digest_0.6.27         
## [93] xtable_1.8-4           brew_1.0-6             openssl_1.4.4          munsell_0.5.0         
## [97] viridisLite_0.4.0      bslib_0.2.5.1          askpass_1.1