Contents

1 Introduction

Chromatin modifications orchestrate the dynamic regulation of gene expression during development and in disease. Bulk approaches have characterized the wide repertoire of histone modifications across cell types, detailing their role in shaping cell identity. However, these population-based methods do not capture cell-to-cell heterogeneity of chromatin landscapes, limiting our appreciation of the role of chromatin in dynamic biological processes. Recent technological developments enable the mapping of histone marks at single-cell resolution, opening up perspectives to characterize the heterogeneity of chromatin marks in complex biological systems over time. Yet, existing tools used to analyze bulk histone modifications profiles are not fit for the low coverage and sparsity of single-cell epigenomic datasets.



ChromSCape Overview: The application takes as input various single-cell format and let the user filter & cluster cells, run differential analysis & gene set enrichment analysis between epigenomic subpopulations, in an unsupervised manner.

ChromSCape is a user-friendly interactive Shiny/R application that processes single-cell epigenomic data to assist the biological interpretation of chromatin landscapes within cell populations. ChromSCape analyses the distribution of repressive and active histone modifications as well as chromatin accessibility landscapes from single-cell datasets (scATAC-seq, scChIP-seq, scCUT&TAG…).

The goal of ChromSCape is to provide user a interactive interface to explore and run a complete analyse (QC, preprocessing, analysis, interpretation) on various single-cell epigenomic data. The application has multiple advantages:

2 Quick Start

To launch the application simply run:

if (!requireNamespace("BiocManager", quietly = TRUE)){
  install.packages("BiocManager")
}
BiocManager::install("ChromSCape")

Load ChromSCape

print("Loading ChromSCape")
## [1] "Loading ChromSCape"
library(ChromSCape)

Launch the shiny application

launchApp()

A browser should open with the application. If the browser doesn’t open automatically, navigate to the displayed url, e.g. “Listening on http://127.0.0.1:5139”. The first time you’ll open the application, you will be guided through a small tour of the application, that you can come back to any time you like by clicking the Help button on the upper right corner.

3 ChromSCape step by step

The user interface is organized by ‘Tab’ corresponding to specific ‘step’ of the analysis. In order to be able to access to each Tab you need to complete the previous steps. For example, before accessing the ‘Filter & Normalize’ Tab, you need to first complete the ‘Select & Import’ Tab.
Each one of your project is named an ‘Analysis’ and is comprised of one raw dataset and additional objects that you have produced by going further into the analysis. A folder named ‘ChromSCape_analyses’ which will contain all your Analysis is produced in the output directory when you create an Analysis for the first time. In this folder, each of your Analysis is a folder with the following organisation:

ChromSCape_analyses/
├── Analysis_1
│   ├── annotation.txt
│   ├── Filtering_Normalize_Reduce
│   │   └── Analysis_1_(…).RData
│   ├── correlation_clustering
│   │   └── Analysis_1_(…).RData
│   ├── Diff_Analysis_Gene_Sets
│   │   └── Analysis_1_(…).RData
│   └── scChIP_raw.RData

The raw data is stored at the root of the folder, and at each main step (‘Filtering & Normalization’, ‘Correlation Clustering’ and ‘Differential Analysis’) the objects are saved. This enable you to close the application and later re-load your analysis without the need of re-doing all those steps. This also enable you to share your analysis with colleagues simply by copying your Analysis folder.
Note: The (…) in the saved objects contained the values of the parameters for an Analysis. If you try multiple parameter, each results will be saved this way and all trials will accessible in the future.

3.1 Input files (before launching ChromSCape)

Various existing technologies allow to produce single-cell genome-wide epigenomic datasets :

  • scChIP-seq (Grosselin et al., 2019) scCUT&Tag (Kaya-Okur et al., 2019), scChIL-seq (Harada et al., 2019), scChIC-seq (Ku et al.,) reveal the distribution of histone marks (H3K27me3, H3K4me3) or transcription factors (RNA Polymerase 2,…) with single-cell resolution.
  • scATAC-seq (Buenorostro et al., 2015) or sciATAC-seq (Cusanovitch et al.,
  1. assess regions of open chromatin in single-cells
  • scDNA methylation profiling, scRRBS, scWGBS …


After sequencing a single-cell epigenomic experiment, the raw sequencing files (.fastq) are demultiplexed, aligned against a reference genome to output different kind of data depending on the technology. ChromSCape allows user to input a variety of different format. Depending on the output of the data-engineering/pre-processing pipeline used, the signal can be already summarized into features (Count matrix, Peak-Index-Barcode files) or stored directly in raw format (single-cell BAM or single-cell BED files).

Anyhow the format, ChromSCape needs signal to be summarized into features. If inputting raw signal (scBAM or scBED), the application lets user summarize signal of each cells into various features:

  • Genomic features (extended region around TSS of genes, enhancers)
  • Peaks called on bulk or single-cell signal (BED file must be provided by the user)
  • Genomic bins (windows of constant length, e.g. 100kbp, 50kbp, 5kbp…)

Note that summarizing will take longer if using BAM files than BED files, and if the number of features is important (e.g. 5kbp bins, enhancers…).

3.1.1 Count matrices files

Each sample should be contained into single-cell count matrix (features x cells) in tab-separated format (extension .txt or .tsv) or comma-separated format (.csv). The first column is genomic location in standard format (chr:start-end) and the next columns are reads counted in each cells in the corresponding genomic feature. Note that the first entry (row 1, column 1) must be empty. All files should be placed in the same folder.
If inputing only a single matrix regrouping different samples, the user can check the ‘multiple sample’ check box and specify a number of samples. ChromSCape will automatically find the different samples based on the names of the cells, so please make sure samples names are all quite different (e.g. K562_.., GM12878_..).

An example of such dataset is availablefor H3K27me3 mouse scChIP-seq of paired PDX samples at: PDX mouse cells H3K27me3 scChIP-seq matrices.

BC969404 BC893525 BC239068 BC073314 chr10:0-50000 0 0 0 0 chr10:50000-100000 0 0 0 0 chr10:100000-150000 0 0 0 0 …


3.1.2 Peak-Index-Barcode files

This format regroups three files containing signal of all samples of one or multiple experiment:

  • The barcode file contains one cell barcode per line and finish by ’_barcode.txt’ :

HBCx95_BC969404 HBCx95_BC893525 HBCx22_BC239068 HBCx22_BC073314 …

  • The peak file contains feature location (usually peaks) must be in BED format and finish by ’_peaks.bed’:

chr3 197959001 197961500 chr3 198080001 198081500 chr4 53001 55500 …

  • The index file contains indexes of non-zero signal and finish by ’_indexes.txt’, the first column is the index of peaks, the second column contains barcode index, the last column contains the signal:

459 1 1 461 1 1 556 1 2


3.1.3 Single-cell BAM or BED files

Each BAM or BED (.bed or .bed.gz) file must be grouping signal of a single-cell, and all files must be placed in the same folder. The signal will be summarized into either bins, peaks, or around gene TSS depending on user choice.

An example of such dataset is publicly available for H3K27me3 single-cell CUT&TAG (Kaya-Okur et al., 2019) K562 and H1 cells at: K562 H3K27me3 cells and K562 + H1 H3K27me3 cells. All files need to be placed in the same folders, the BED files do not need to be unzipped.

3.1.4 Alignment BAM files for Peak Calling (optional)

For the optional step of Peak Calling on cluster of cells found de novo, users have to input one BAM file per sample, placed in the same folder. The barcode information of each read should be contained in a specific tag (XB, CB..) and correspond to the column names of the corresponding count matrix.


samtools view example_matrix.bam | head NS500388:436:HNG5VAFXX:2:21311:26430:3816 89 chr10 3102405 255 51M * 0 0 CTTGGTGTCTAGTGGATCTGCTGCAGTCTTCTGTTGTCAGTGCTAAATCAC EEEEE/E6EEEAEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEAAAAA NH:i:1 HI:i:1 AS:i:50 nM:i:0 XS:i:2147483647 XD:Z:GATGACAAAG XB:Z:BC969404 …

3.2 Create & import a dataset

Once you have launched the application, you arrive on the “Select & Import”. Here you can selet an output directory, where your analyses will be saved. ChromSCape will automatically save the folder’s location so that you don’t have to select it each time you connect.

You must then name your analysis. The name shouldn’t contain special characters (except ’_‘). Choose either the Human (hg38) or Mouse (mm10) genome. This is used to annotate your features with the closest genes TSS for the Gene Set Analysis. Browse your computer for one or multiple matrices that will be analyzed together. To select multiple matrices, they must be placed in the same folder and then the user can select multiples matrices with (Shift + Click) or (Ctrl + Click). Finally, clicking on ’Create Analysis’ will create an analysis & import the count matrices in this analysis. This will create a folder named ‘ChromSCape_analyses’ in the output directory you specified, inside which another folder ‘Your_analysis_name’ is nested. If you create another analysis, it will also be created under ‘ChromSCape_analyses’. If you already created an analysis in a previous section, selecting the same output directory as you chose in the previous session will enable you to load your analysis.




Select & Import Tab: Select an output directory, Create an analysis or load previous analyses, import count matrix into your new analysis.



Select an type of format input, and eventually a type of feature to summarize signal.

3.2.1 Summarizing features

Depending on what kind of data you are analyzing, you might want to summarized your data on different features. For open/active chromatin measures, such as ATAC or ChIP against H3K4me3, we recommand to summarize signal into small bins of 5kbp to 10kbp or to count aroung gene TSS. When counting around gene TSS, the default is to take overlapping regions of 2,500bp around the gene TSS, but you might want to increase this value for scATAC-seq if looking to retrieve enhancers open regions. For repressive marks such as H3K27me3, we recommand summarizing into large bins of 50kbp to 100kbp, as those mark are known to accumulate into large domains.

3.2.2 Recognition of samples

ChromSCape will recognize automatically to which sample/condition each cell belongs. In order to do so, the names of the cells (e.g. names of the files for scBED/scBAM or barcodes names for combined Index-Peaks-Barcode/count matrix) should explicitely contains name of the samples/conditions.

Example: if inputing two cell types, e.g. Jurkat and Ramos, names of the files/cells should be something like : Jurkat_cell1.BED, Jurkat_cell2.BED, …, Ramos_cell1.BED, Ramos_cell2.BED.

The more different the names of the samples/conditions are, the more easily ChromSCape will classify correctly each cell. If having two samples with a similar name, users should manually change the names of the label. For example if having ‘CMP’ (common myeloid progenitors) and ‘GMP’ (granulocytes myeloid progenitors) samples, change the name manually to ‘commonMP’ and ‘granulocytesMP’ respectively.

3.2.3 Inputing BAM files

Inputting BAM files is the most demanding task in terms of ressource in the application, despite the fact that the summarizing of features will take place in parallel. To give an example, for 1,287 single-cell BAM files, summarizing into 50kbp bins takes 9 minutes to finish. Counting from BED files is way faster, therefore if analyzing lots of cells in BAM format, users might consider running ‘bamToBed’ command from BEDTools on each file beforehand.

3.3 2. Filter, Normalize & Reduce Dimensionality

In order to efficiently remove outlier cells from the analysis, e.g. cells with excessively high or low coverage, the user sets a threshold on a minimum read count per cell and the upper percentile of cells to remove. The latter could correspond to doublets, e.g. two cells in one droplet, while lowly covered cells are not informative enough or may correspond to barcodes ligated to contaminant DNA or library artifacts. Regions not supported by a minimum user-defined percentage of cells that have a coverage greater than 1,000 reads are filtered out.

Defaults parameters were chosen based on the analysis of multiple scChIP-seq datasets:

  • A minimum coverage of 1,600 unique reads per cell
  • Filtering out the cells with the top 5% coverage
  • Keeping regions detected in at least 1 % of cells.

Post quality control filtering, the matrices are normalized by total read count and region size (CPM normalization. At this step, the user can provide a list of genomic regions, in BED format, to exclude from the subsequent analysis, in cases of known copy number variation regions between cells for example.

To reduce the dimensions of the normalized matrix for further analysis, PCA is applied to the matrix, with centering, and the 50 first PCs are kept for further analysis.

If you want to run t-SNE for vizualisation in addition to PC and UMAP, tick the ‘Run T-SNE’ checkbox. This might take some time to run, depending on the size of the dataset.

For some large datasets (e.g. more than 15,000 cells) or unbalance datasets (i.e. number of cells per sample is very different), it might be a good option to first run with the subsampling option. To do so, tick the ‘Perform subsampling’ and select the maximum number of cells to subsample from each sample. The sampling is done without replacement.

Users might want to remove specific loci from the analysis, e.g. repeat regions, known Copy Number Altered regions that might bias the analysis. To do so, tick the ‘Exclude specific genomic regions’ and browse for a BED file containing the regions to exclude.

A batch correction option using mutual nearest neighbors ‘FastMNN’ function from batchelor is implemented to remove any known batch effect in the reduced feature space. To do so, tick the ‘Perform batch correction’, select the number of batches and add each sample to a batch.




Filter, Normalize & Reduce Tab: Adjust paramters to filter out low covered cells & features, as well as too highly covered cells that might be potential doublets. Normalize & Reduce dimensionality using PCA.

3.4 Visualize cells in reduced dimensions

The user can visualize the data after quality control in the PCA , t-SNE or UMAP reduced dimensional space. The PCA and t-SNE plots are a convenient way to check if cells form clusters in a way that was expected before any clustering method is applied. For instance, the user should verify whether the QC filtering steps and normalization procedure were efficient by checking the distribution of cells in PC1 and PC2 space. Cells should group independently of normalized coverage.

Depending on wether you have ticked the ‘Run T-SNE’ checkbox in the previous Tab, you will see the T-SNE two dimensional plot.

Note: You can change the colors of each samples, batch or cluster and the saved colors will be saved in the Analysis.




Visualize Cells: Visualize cells in reduced dimensions: PCA, UMAP & TSNE. Color cells by sample, batch, or total count to make sure cells are not separating due to library size only.


A brief understanding into what features drives the main PCs is shown in the ‘Contribution to PCA’ box.

  • In the barplot, you will get the top loci / closest genes associated to the top loci contributing to the Component of your choice. The top contributing features are taken by sorting the values of the features in the componenent of intereset (e.g. PC1, PC2…). If you observe a huge gap between the top 2-3 features and the rest, this means that very few features are driving most of the dimensionality reduction, and that other less contributing features might be hidden. This also gives you interesting features to look at in the Peak Calling & Coverage or Differential Analysis tabs.

  • In the pie chart, the chromosome repartition of the top 100 most contributing features to the componenent of interest (e.g. PC1, PC2…) are displayed. This is used to see if there is any strong imbalance in the “chromosome contribution”, e.g. if a chromosome is contributing more than it should be. Usually, if a single chromosome has > 30% representation, this might indicate that CNVs or genetic events are happening on this chromosome, and you might want to look into more details at these events, or exclude them from the analysis (see Filter & Normalize tab)




Most contributing features

3.5 Cluster cells

Using the first 50 first PCs of computed PCA as input, hierarchical clustering is performed, taking 1-Pearson’s correlation score as distance metric. The cell to cell correlation heatmap and dendogram describing the hierarchical clustering is represented in the left panel.

To improve the stability of the clustering approaches and to remove from the analysis isolated cells that do not belong to any subgroup, cells displaying a Pearson’s pairwise correlation score below a threshold t with at least p % of cells can be filtered out. The correlation threshold t is calculated as a user-defined percentile of Pearson’s pairwise correlation scores for a randomized dataset (percentile is recommended to be set as the 99th percentile). To do so, open the “Filter lowly correlated cells” panel and click on “Filter & Save”. This will filter any cells that are too rare to correlate with enough other cells and form stable clusters.

To select a number of clusters, looking at the correlation heatmap and dendogram, choose a number in the ‘Select Cluster Number’ panel and click on ‘Choose Cluster’.

If you are unsure of how many cluster to choose, you can run consensus clustering using Bioconductor’s package ConsensusClusterPlus package to determine what is the appropriate k-partition of the dataset into k clusters. To do so, it evaluates the stability of the clusters and computes item consensus score for each cell for each possible partition from k=2 to n. For each k, consensus partitions of the dataset are done on the basis of 1,000 resampling iterations (80% of cells sampled at each iteration) of hierarchical clustering, with Pearson’s dissimilarity as the distance metric and Ward’s method for linkage analysis. The optimal number of clusters is then chosen by the user; one option is to maximize intra-cluster correlation scores based on the graphics displayed on the ‘Consensus Clustering’ Tab after processing.

If you ran consensus clustering, re-pick the cluster numbers in the ‘Select Cluster Number’ panel making sure you check the ‘Use consensus’ checkbox and re-click on ‘Choose Cluster’.

Cell clusters can then be visualized in two dimensions with the t-SNE or UMAP plot.

Note: The correlation filtering and consensus clustering steps are optional as they need long runtime. You might want to proceed to Differential Analysis and Gene Set Analysis directly if you are confident in your choice of clusters.




Cluster Cells: Choose a number of cluster if you have clear clusters of cells, or run consensus clustering to test multiple clustering and find the optimal cluster number. Optionally filter out lowly correlated cells that might impact the clustering performance.


Cluster Cells - results: Cluster visualization with UMAP. ## Inter & Intra correlation violin plots

In this box, the heterogeneity of cells in various groups (e.g. sample or cluster) are displayed with two plots:

  • In the intra-correlation plot, the distribution of cell-to-cell Pearson correlation scores within each cluster or sample is displayed. Heterogeneous groups will have lower correlation than homogeneous groups.

  • In the inter-correlation plot, the distribution of cell-to-cell Pearson correlation scores between each cluster or sample is displayed. This allows to understand which groups are closer to each other than other groups.

For both plots, you can add a layer of information by adding the single-cell as jitter points on the plots. This is interesting when combining samples and clusters to see the repartition of conditions into the clusters.



Inter/Intra correlation

3.6 Peak Calling to refine bins to gene annotation

This step of the analysis is optional, but recommended for Gene Set Analysis if working on genomic bins in order to refine the peak annotation prior to enrichment analysis. To be able to run this module, some additional command line tools are required such as SAMtools, BEDTools and MACS2. Therefore, this step is only available for Linux and MacOS systems.

You need to input BAM files for the samples (one separate BAM file per sample), with each read being labeled with the barcode ID in the ‘XB’ tag. ChromSCape merges all files and splits them again according to the previously determined clusters of cells (one separate BAM file per cluster). To do so, place all your BAM files in a folder and click on the ‘Choose a folder containing the BAM files’ button to browse for your folder. If some of the BAM files in the folder are not part of your analyis, remove them by pressing the write box and deleting them.

You can select significance threshold for peak detection (passed to MACS2) and merging distance for peaks (defaults to p-value=0.05 and peak merge distance to 5,000). This allows to identify peaks in close proximity (<1,000bp) to a gene transcription start site (TSS); these genes will be later used as input for the enrichment analysis.




Peak Calling to refine bins to gene annotation: Call peaks on ‘pseudo-bulk’ cell clusters, and refine bins to genes annotation.

3.7 Differential Analysis

To identify differentially enriched regions across single-cells for a given cluster, ChromSCape can perform 1. A non-parametric two-sided Wilcoxon rank sum test comparing normalized counts from individual cells from one cluster versus all other cells, or cluster of choice, 2. Or a parametric test comparing raw counts from individual cells, using the Bioconductor package edgeR, based on the assumption that the data follows a negative-binomial distribution. We test for the null hypothesis that the distribution of normalized counts from the two compared groups have the same median, with a confidence interval 0.95. The calculated p-values are then corrected by the Benjamini-Hocheberg procedure. You can modify the log2 fold-change threshold and corrected p-value threshold for regions to be considered as significantly differentially enriched (default settings are a p-value and log2 fold-change thresholds respectively of 0.01 and 1).

If you have specified batches to correct for batch effect, the differential analysis is done using the ‘pairwiseWilcox’ function from the Bioconductor package scran , setting the batch of origin as a ‘blocking level’ for each cell.



Differential Analysis: Identify most differential features between the various cell clusters

3.8 Gene Sets Analysis

In this tab, using the refined annotation of peaks if available, the final step is to look for enriched gene sets of the MSigDB v5 database within differentially enriched regions (either enriched or depleted regions in the studied histone mark). Click on ‘Start Enrichment Analysis’ in order to apply hypergeometric tests to identify gene sets from the MSigDB v5 database over-represented within differentially enriched regions, correcting for multiple testing with the Benjamini-Hochberg procedure. Users can then visualize most significantly enriched or depleted gene sets corresponding to the epigenetic signatures of each cluster and download gene sets enrichment tables.

The top 100 most significant differential regions, single-cell Epigenomic enrichment levels can be visualized overlaying read counts for each cell at selected genes onto a t-SNE plot (right panel).



Gene Set Analysis: Look for pathways activated or depleted in most differential regions between clusters

4 Datasets

Try out ChromSCape with various kind of dataset : Dropbox repository

5 Session information

sessionInfo()
## R version 4.4.0 beta (2024-04-15 r86425)
## Platform: x86_64-pc-linux-gnu
## Running under: Ubuntu 22.04.4 LTS
## 
## Matrix products: default
## BLAS:   /home/biocbuild/bbs-3.19-bioc/R/lib/libRblas.so 
## LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0
## 
## locale:
##  [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C              
##  [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8    
##  [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8   
##  [7] LC_PAPER=en_US.UTF-8       LC_NAME=C                 
##  [9] LC_ADDRESS=C               LC_TELEPHONE=C            
## [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       
## 
## time zone: America/New_York
## tzcode source: system (glibc)
## 
## attached base packages:
## [1] stats     graphics  grDevices utils     datasets  methods   base     
## 
## other attached packages:
## [1] ChromSCape_1.14.0 BiocStyle_2.32.0 
## 
## loaded via a namespace (and not attached):
##   [1] later_1.3.2                 batchelor_1.20.0           
##   [3] BiocIO_1.14.0               bitops_1.0-7               
##   [5] matrixTests_0.2.3           tibble_3.2.1               
##   [7] XML_3.99-0.16.1             gggenes_0.5.1              
##   [9] lifecycle_1.0.4             edgeR_4.2.0                
##  [11] lattice_0.22-6              magrittr_2.0.3             
##  [13] limma_3.60.0                plotly_4.10.4              
##  [15] sass_0.4.9                  rmarkdown_2.26             
##  [17] jquerylib_0.1.4             yaml_2.3.8                 
##  [19] rlist_0.4.6.2               metapod_1.12.0             
##  [21] httpuv_1.6.15               askpass_1.2.0              
##  [23] reticulate_1.36.1           ConsensusClusterPlus_1.68.0
##  [25] ResidualMatrix_1.14.0       abind_1.4-5                
##  [27] zlibbioc_1.50.0             Rtsne_0.17                 
##  [29] GenomicRanges_1.56.0        purrr_1.0.2                
##  [31] BiocGenerics_0.50.0         msigdbr_7.5.1              
##  [33] RCurl_1.98-1.14             GenomeInfoDbData_1.2.12    
##  [35] IRanges_2.38.0              S4Vectors_0.42.0           
##  [37] ggrepel_0.9.5               irlba_2.3.5.1              
##  [39] umap_0.2.10.0               RSpectra_0.16-1            
##  [41] dqrng_0.3.2                 svglite_2.1.3              
##  [43] DelayedMatrixStats_1.26.0   codetools_0.2-20           
##  [45] DelayedArray_0.30.0         DT_0.33                    
##  [47] scuttle_1.14.0              xml2_1.3.6                 
##  [49] RApiSerialize_0.1.2         tidyselect_1.2.1           
##  [51] UCSC.utils_1.0.0            ScaledMatrix_1.12.0        
##  [53] viridis_0.6.5               shinyWidgets_0.8.6         
##  [55] matrixStats_1.3.0           stats4_4.4.0               
##  [57] GenomicAlignments_1.40.0    jsonlite_1.8.8             
##  [59] BiocNeighbors_1.22.0        scater_1.32.0              
##  [61] systemfonts_1.0.6           tools_4.4.0                
##  [63] stringdist_0.9.12           Rcpp_1.0.12                
##  [65] glue_1.7.0                  gridExtra_2.3              
##  [67] SparseArray_1.4.0           xfun_0.43                  
##  [69] qualV_0.3-5                 MatrixGenerics_1.16.0      
##  [71] GenomeInfoDb_1.40.0         dplyr_1.1.4                
##  [73] shinydashboard_0.7.2        BiocManager_1.30.22        
##  [75] fastmap_1.1.1               bluster_1.14.0             
##  [77] fansi_1.0.6                 shinyjs_2.1.0              
##  [79] openssl_2.1.2               digest_0.6.35              
##  [81] rsvd_1.0.5                  R6_2.5.1                   
##  [83] mime_0.12                   colorspace_2.1-0           
##  [85] utf8_1.2.4                  tidyr_1.3.1                
##  [87] generics_0.1.3              data.table_1.15.4          
##  [89] rtracklayer_1.64.0          httr_1.4.7                 
##  [91] htmlwidgets_1.6.4           S4Arrays_1.4.0             
##  [93] pkgconfig_2.0.3             gtable_0.3.5               
##  [95] SingleCellExperiment_1.26.0 XVector_0.44.0             
##  [97] htmltools_0.5.8.1           shinyhelper_0.3.2          
##  [99] bookdown_0.39               scales_1.3.0               
## [101] kableExtra_1.4.0            Biobase_2.64.0             
## [103] png_0.1-8                   scran_1.32.0               
## [105] colorRamps_2.3.4            knitr_1.46                 
## [107] rstudioapi_0.16.0           rjson_0.2.21               
## [109] curl_5.2.1                  shinydashboardPlus_2.0.4   
## [111] cachem_1.0.8                stringr_1.5.1              
## [113] KernSmooth_2.23-22          parallel_4.4.0             
## [115] miniUI_0.1.1.1              vipor_0.4.7                
## [117] shinycssloaders_1.0.0       restfulr_0.0.15            
## [119] pillar_1.9.0                grid_4.4.0                 
## [121] vctrs_0.6.5                 promises_1.3.0             
## [123] ggfittext_0.10.2            stringfish_0.16.0          
## [125] BiocSingular_1.20.0         shinyFiles_0.9.3           
## [127] beachmat_2.20.0             xtable_1.8-4               
## [129] cluster_2.1.6               beeswarm_0.4.0             
## [131] evaluate_0.23               cli_3.6.2                  
## [133] locfit_1.5-9.9              compiler_4.4.0             
## [135] Rsamtools_2.20.0            rlang_1.1.3                
## [137] crayon_1.5.2                forcats_1.0.0              
## [139] fs_1.6.4                    ggbeeswarm_0.7.2           
## [141] stringi_1.8.3               viridisLite_0.4.2          
## [143] BiocParallel_1.38.0         babelgene_22.9             
## [145] munsell_0.5.1               Biostrings_2.72.0          
## [147] lazyeval_0.2.2              coop_0.6-3                 
## [149] colourpicker_1.3.0          Matrix_1.7-0               
## [151] sparseMatrixStats_1.16.0    ggplot2_3.5.1              
## [153] statmod_1.5.0               shiny_1.8.1.1              
## [155] SummarizedExperiment_1.34.0 qs_0.26.1                  
## [157] igraph_2.0.3                RcppParallel_5.1.7         
## [159] bslib_0.7.0