AbSeq core analyses

AbSeq includes, but is not limited to, merging paired-end reads, annotating V-(D)-J germlines, calculating unique clonotypes, analyzing primer specificity, facilitating the selection of best restriction enzymes, predicting frameshifts, identifying functional clones, and calculating diversity indices and estimations. These analyses are seamlessly extrapolated to analyze multiple library repertoires simultaneously when multiple samples are present. Figure @ref(fig:abseq-wf) depicts the complete AbSeq workflow. Sequencing files are taken as input to be annotated and analyzed by abseqPy before they are further analyzed and visualized by abseqR.

AbSeq workflow. Comprehensive analyses and visualizations are generated from input sequencing files using abseqPy and abseqR.

Bioconductor

To install abseqR via the BiocManager, type in R console:

if (!require("BiocManager"))
    install.packages("BiocManager")
BiocManager::install("abseqR")

GitHub

To install the development version of abseqR from GitHub, type in R console:

if (!require("BiocManager"))
    install.packages("BiocManager")
BiocManager::install("malhamdoosh/abseqR")

System prerequisites

abseqR requires pandoc version 1.19.2.1 or higher to render the HTML reports. If pandoc cannot be detected while executing abseqR, the HTML report will not be generated. abseqR is a cross-platform library and will work on any major operating system ².

R package dependencies

abseqR depends on several packages from the CRAN and Bioconductor repositories:

• RColorBrewer provides colour schemes for maps and graphics. To install it, type in R console install.packages("RColorBrewer")

• VennDiagram provides a set of functions to generate Venn diagrams. To install it, type in R console install.packages("VennDiagram")

• circlize is a visualization tool used to summarize the distributions of associations between V-J gene segments. To install it, type in R console install.packages("circlize")

• flexdashboard is a package that provides a template for RMarkdown that resembles a grid oriented dashboard and is used to generate the HTML reports. To install it, type in R console install.packages("flexdashboard")

• ggplot2 is an implementation of the “Grammar of Graphics” in R. It is used extensively to generate plots. To install it, type in R console install.packages("ggplot2")

• ggcorrplot is used to visualize a correlation matrix using ggplot2. To install it, type in R console install.packages("ggcorrplot")

• ggdendro provides a set of tools for drawing dendrograms and tree plots using ggplot2. To install it, type install.packages("ggdendro")

• grid is used to arrange plots. It has been integrated into the base R package.

• gridExtra provides functions to work with “grid” graphics and used to arrange grid-based plots in the HTML reports. To install it, type in R console install.packages("gridExtra")

• knitr provides the capability to dynamically generate reports in R. To install it, type in R console install.packages("knitr")

• plotly is used to translate ggplot2 graphs to interactive web-based plots. To install it, type in R console install.packages("plotly")

• plyr offers a set of tools used in this package to apply operations on subsets of data in manageable pieces. To install it, type in R console install.packages("plyr")

• png is used to read and display PNG images. To install it, type in R console install.packages("png")

• reshape2 allows this package to restructure and aggregate dataframes. To install it, type in R console install.packages("reshape2")

• rmarkdown converts R Markdown documents into a variety of formats. To install it, type in R console install.packages("rmarkdown")

• vegan provides a suite of functions to calculate diversity and distance statistics between repertoires. To install it, type in R console install.packages("vegan")

• BiocParallel is a package from Bioconductor used to enable parallel computing. To install it, type in R console

if (!require("BiocManager"))
    install.packages("BiocManager")
BiocManager::install("BiocParallel")

Datasets

The example dataset is packaged with abseqR. For the sake of brevity, the dataset generation is described under the Appendices section.

Briefly, the dataset includes three samples, namely PCR1, PCR2, and PCR3, that was generated using in silico simulations. abseqPy was then used to analyze the datasets and the output directory argument --outdir specified in abseqPy was initiated with the value "./ex/".

# substitute with any directory that you have read/write access to
sandboxDirectory <- tempdir()

# path to provided data (comes installed with abseqR)
exdata <- system.file("extdata", "ex", package = "abseqR")

# copy the provided data to sandboxDirectory
file.copy(exdata, sandboxDirectory, recursive = TRUE)

# dataPath now holds the path to a local copy of the data
dataPath <- file.path(sandboxDirectory, "ex")
# the sample names can be found inside the auxiliary directory
list.files(path = file.path(dataPath, "auxiliary"))

## [1] "PCR1" "PCR2" "PCR3"

Basic analysis

After obtaining the datasets, the abseqReport function from abseqR is invoked to visualize the different analysis results as follows:

# This section will visualize all the datasets individually
# and compare PCR1 with PCR2 with PCR3

# Interim solution
if (Sys.info()["sysname"] == "Darwin") {
    BPPARAM <- BiocParallel::SerialParam()
} else {
    BPPARAM <- BiocParallel::bpparam()
}

# you should use report = 3 to generate a HTML report
samples <- abseqReport(dataPath,
                       compare = c("PCR1, PCR2, PCR3"),
                       report = 1,
                       BPPARAM = BPPARAM)

# ignore the message:
# "Sample output directory <path> is different from provided path
#   <path> assuming directory was moved"
# This warning message tells us that the directory has
# been moved (we copied the provided examples to "dataPath")

This creates plots for all samples included in dataPath. In addition, The compare = c("PCR1, PCR2, PCR3") argument specifies that samples PCR1, PCR2, and PCR3 are explicitly compared against each other. Other possible values for compare, report , and BPPARAM will be discussed in detail in later sections (here, here, and here).

HTML reports’ directory structure

Figure @ref(fig:abseq-final-folder-structure) shows the folder structure of ./ex/ after abseqR completes.

Folder structure after abseqR completes. The landing page index.html provides a convenient way to navigate around the standalone HTML reports in html\_files/.

Invoking abseqReport generates plots in the same folder as the corresponding data files within the auxiliary directory. They are then collated together in an HTML document found in the report directory.

The report directory is structured as follows:

• index.html file is the entry point to browse AbSeq’s HTML reports. It summarizes the AbSeq analysis and provides a convenient way for navigating individual and comparative analysis results. For example, within this file, there are links to the reports generated for PCR1, PCR2, PCR3 and PCR1 vs PCR2 vs PCR3.

• html_files directory contains HTML files that are used build the individual and comparative reports. They can be accessed directly or via the main page index.html.

In conclusion, the individual sample reports in html_files can be shared as-is, but index.html must be accompanied by the html_files directory and thus it is recommended to share the entire report folder.

Comparative analysis

# Example of 1 comparison
# Analyze all samples, but only compare PCR1 with PCR2
pcr1.pcr2 <- abseqReport(dataPath,
                         compare = c("PCR1, PCR2"),
                         report = 0)

# Example of 2 comparisons
# Analyze all samples. In addition, compare:
#  * PCR1 with PCR2
#  * PCR2 with PCR3
multiComparison <- abseqReport(dataPath,
                               compare = c("PCR1, PCR2", "PCR2, PCR3"),
                               report = 0)

# compare = c("PCR1,PCR2")
names(pcr1.pcr2)

# compare = c("PCR1, PCR2", "PCR2 ,PCR3")
names(multiComparison)

## [1] "PCR1" "PCR2" "PCR3"
## [1] "PCR1" "PCR2" "PCR3"

# recall that samples is a named list where each element's name
# is the sample's own name (see names(samples))

# use report = 3 if the results should be collated in a HTML document
pcr1.pcr3 <- samples[["PCR1"]] + samples[["PCR3"]]
refinedComparison <- report(pcr1.pcr3,
                            outputDir = file.path(sandboxDirectory,
                                                  "refined_comparison"),
                            report = 1)

names(refinedComparison)

## [1] "PCR1" "PCR3"

# first abseqPy run on SRR dataset from control group
abseq --file1 fasta/SRR_ACGT_CTRL.fasta --outdir SRR_CTRL

# second abseqPy run on SRR dataset from experiment group
abseq --file1 fasta/SRR_ACGT_EXP.fasta --outdir SRR_EXP

SRRControl <- abseqReport("SRR_CTRL")
SRRExp <- abseqReport("SRR_EXP")

# short for SRRControl[[1]] + SRRControl[[2]] + ... + SRRExp[[1]] + ...
all.samples <- Reduce("+", c(SRRControl, SRRExp))
report(all.samples, outputDir = "SRRControl_vs_SRRExp")

Lazy loading

In the previous section, the SRRControl dataset was loaded using SRRControl <- abseqReport("SRR_CTRL"), which will generate all plots and reports by default. However, this dataset might have already been analyzed and users are interested in only loading the S4 objects of the samples. This can be efficiently carried out by using the report=0 argument as follows:

# in essence, this is identical to SRRControl <- abseqReport("SRR_CTRL"),
# but will not regenerate plots and reports!
SRRControl.lazy <- abseqReport("SRR_CTRL", report = 0)

# exactly the same return value
stopifnot(names(SRRControl.lazy) == names(SRRControl))

Alternative reporting options

In the previous section, the report parameter of abseqReport was used to load the samples in SRRControl without actually plotting any data.

The report argument can accept one of four possible values as follows:

1. abseqReport("SRR_CTRL", report = 0) does not generate plots and HTLM reports and only returns a named list of S4 objects.

2. abseqReport("SRR_CTRL", report = 1) generates static plots in PNG format but does not generate HTML reports.

3. abseqReport("SRR_CTRL", report = 2) generates static plots in PNG format in addition to HTML reports.

4. abseqReport("SRR_CTRL", report = 3) generates static plots in PNG format and interactive plots in the HTML reports using plotly. This is the default behaviour when the report argument is not specified.

Parallelization

One of abseqReport’s parameters is BPPARAM, which is used to pass arguments into the BiocParallel::bplapply function for customizing parallelization. More information regarding the accepted values to BPPARAM can be found at BiocParallel’s page.

Below is a simplified example of using 4 cores and serializing the loop.

# use 4 CPU cores
nproc <- 4
samples <- abseqReport(dataPath,
                       BPPARAM = BiocParallel::MulticoreParam(nproc))


# run sequentially - no multiprocessing
samples <- abseqReport(dataPath,
                       BPPARAM = BiocParallel::SerialParam())

Sequence quality analysis

The plots described in this section can be found in the Summary and Quality tabs of the HTML report.

Sequence length

The sequence length distribution is a simple way of validating the quality of a sequencing run. The histogram is expected to show a large proportion of sequences falling within the expected lengths.

Sequence length distribution of PCR1. Histogram of (merged) sequence lengths.

Figure @ref(fig:seq-len) plots sequence length (x-axis) against proportion (y-axis). A similar plot with outliers removed can be found in the Summary tab.

Alignment quality

abseqPy filters low quality sequences based on the quality of the sequence alignment against germline sequence databases and thus the following parameters can be used:

1. Alignment bitscore
2. Subject start index
3. Query start index
4. Alignment length

However, setting the optimal cut-off thresholds for these parameters is challenging. Stringent values could filter too many sequences while lenient values could retain low quality sequences.

The alignment quality heatmaps generated in the Quality tab of the HTML report shows the relationship between alignment lengths and these alignment parameters to help determine the percentage of sequences falling within a given range and thus inform the selection of cut-off thresholds.

For example, Figure @ref(fig:align-qual) shows one of the 5 heatmaps: bitscore against V germline alignment length. abseqPy has some recommendations on the values of these parameters to retain good quality sequences.

Bitscore vs V germline alignment length in PCR1. Heatmap of bitscore vs alignment length shows percentage of sequences in a given value range.

Insertions, deletions, and mismatches

Indels (Insertions or deletions) and mismatches can be used as an indicator of sequence quality.

Figure @ref(fig:indel) shows the proportions of indels in PCR1. This graph plots the rate of indels (y-axis) in the V germlines of PCR1 against the number of indels (x-axis). A similar plot for rate of mismatches in V germlines can be found in the same directory. A high rate of indels in the germline sequences might indicate a quality problem with the library because this would affect the functionality of the sequenced clones. However, this could be due to the sequencing quality depending on which sequencing technology is used. For example, long read sequencing technologies tend to produce more indel errors than short read sequencing technologies.

Rate of insertions and deletions in PCR1. The percentage of indels found within the V germlines of PCR1.

Abundance and association analysis

The plots generated in this section can be found in the Abundance tab of the HTML report.

V-(D)-J germline abundance

The proportions of V-(D)-J germlines is essential in some experiment designs. For example, it can be used to validate that the germline abundance of an in-house antibody library is in-line with the donor antibody repertoire. Experiments that artificially amplify certain germline families can also be validated similarly using this analysis.

V family germline distribution in PCR1. The percentage of IGHV families after germline annotation using IgBLAST.

Figure @ref(fig:vgermline) shows the distribution of IGHV families in PCR1. Similar plots can be generated for individual V germlines genes and for the D and J germlines.

V-J germline associations

This plot visualizes the recombination process of V and J germlines. Figure @ref(fig:vjassoc) summarizes the associations between V and J family germlines in a plot generated using circlize.

V-J family germline association in PCR1. Segment size represents germline proportion while the thickness of the arcs shows the proportion of associations between V and J germline families. This plot was heavily inspired by VDJTools)

This plot can be used to check whether the Ab library is biased towards a particular combination of germline genes due to cloning errors.

Productivity analysis

The plots described in this section can be found in the Productivity tab in PCR1’s HTML report. The main factors affecting the productiveness of a clone by AbSeq’s interpretation are:

1. Concordance of the coding frames of V and J germline genes
2. Presence of stop codons
3. Presence of indels within a framework or complementarity-determining region

Any sequence that satisfies at least one of the above condition will be classified as unproductive and thus it is unlikely that it will express a functional antibody.

Figure @ref(fig:prod-summ) summarizes the productivity analysis results of PCR1. Factors that cause sequences to be non-functional are colour coded as follows:

1. Green – sequences without stop codons but have a frameshift
2. Cyan – sequences that are in-frame but contain at least one stop codon
3. Purple – sequences that contain at least one stop codon and have a frameshift

Productivity rate of sequences in PCR1. This plot shows the percentage of productive and unproductive sequences, the reason for unproductive sequences are colour coded.

A good antibody library should have as low unproductive clones as possible. Cloning strategies that are used to clone sequences from the donor libraries or used to construct the Ab library play a key role in this aspect of the library quality.

V-J frameshifts

Figure @ref(fig:frameshift) shows the percentage of clones that are out-of-frame due to either misaligned V-J coding frames or to the presence of non-multiple of three-indels in one of the framework or complementarity-determining regions.

Rate of in-frame and out-of-frame sequences in PCR1. Misaligned V-J frame or non-multiple of 3 indels in either one of the framework or complementarity-determining regions causes a frameshift and therefore renders the sequence unproductive.

Stop codons

Figure @ref(fig:stopcod) shows the hot spots for stop codons segregated by framework and complementarity-determining regions.

Proportion of stop codons in any given CDR or FR of out-of-frame sequences in PCR1. The percentages show the frequency of stop codons in a given region relative to the total number of stop codons present.

The figure above shows the percentage of stop codons in the FR and CDR regions of out-of-frame sequences. As discussed earlier, these stop codons may be introduced due to cloning or sequencing errors, hence a similar plot for in-frame sequences can also be found within the same tab.

Indels and mismatches

Some sequences are productive despite having indels and mismatches. This occurs when indels are multiple of three and mismatches do not introduce stop codons. The following figures show the proportion of indels and mismatches for each germline, framework region, and complementarity-determining region on productive sequences (unless specified otherwise).

Figure @ref(fig:mismatches), Figure @ref(fig:gaps), and Figure @ref(fig:gaps-out) plots the proportion of mismatches in productive sequences, indels in productive sequences, and indels in out-of-frame (unproductive) sequences for framework region 3 (FR3). The motivation behind these plots is to quickly identify the quality of productive sequences.

Proportion of mismatches in productive sequences of PCR1.

Proportion of indels in productive sequences of PCR1.

Proportion of indels in out-of-frame sequences of PCR1.

Ideally, the number of mismatches in framework regions and IGJ are expected to be low because they are relatively conserved regions. Similarly, the number of indels in productive sequences are expected to be low or some multiple of 3.

Similar plots are generated for other FR and CDR regions, IGV, IGD, and IGJ.

Diversity analysis

The plots described in this section can be found in the Diversity tab of the HTML report. AbSeq only conducts diversity analysis on clones that are productive.

Clonotype-based analysis

To estimate repertoire diversity, abseqR employs three commonly used techniques:

Duplication-level analysis in which the number of times a clone appears in the sequenced sample is calculated. Figure @ref(fig:duplication) plots the proportion of sequences (y-axis) that appear once (singletons), twice (doubletons), and at higher-orders (x-axis). The higher the percentage of singletones and doubletones, the more diverse the library would likely be.

Rarefaction analysis in which bootstrapping is used to estimate the richness of a library by calculating the proportion of unique sequences at different sample sizes. Figure @ref(fig:rarefaction) plots the number of deduplicated clonotypes (y-axis) againse sample sizes (x-axis). For each sample size, five samples are drawn and the mean with confidence intervals are calculated. In a highly diverse library, the percentage of unique clones should significantly increase as the sample size increases.

Capture-recapture analysis in Figure @ref(fig:recapture) plots the percentage of clonotypes recaptured (y-axis) in a capture-recapture experiment at different sample sizes (x-axis). For each sample size, the percentage of recaptured clonotypes is calculated for five repeated capture-recapture experiments and the mean and confidence intervals are reported.

In below figures, the complementarity-determining regions (CDRs) are used to define a “clonotype”. Similar plots can be generated for the framework regions (FRs) and the entire variable domain sequences.

Proportion of duplicated clonotypes in PCR1. Higher-order duplication levels starting from 10 are binned.

Rarefaction curve of clonotypes in PCR1. The number of deduplicated sequences are taken over the mean of 5 resampling rounds, where the shaded areas indicate 95% confidence interval.

Capture-recapture of clonotypes in PCR1. The number of recaptured sequences are taken over the mean of 5 resampling rounds, where the shaded areas indicate 95% confidence interval.

Spectratype analysis

Spectratypes are histograms of the clonotype lengths calculated based on the amino acid sequences. Figure @ref(fig:spectra) shows a CDR3 spectratype. Spectratypes for other FRs and CDRs are available in the same tab. In a good quality library, the framework regions would have quite conserved lengths while CDRs show high length diversity. CDR3 spectratype tends to follow a normal distribution in libraries cloned from naive repertoires.

CDR3 amino acid spectratype for PCR1 with outliers removed.

Position-specific analysis

This analysis examines the diversity of Ab library at each amino acid position of the variable domain by estimating the utilization of each of the 20 amino acids at each position. Position-specific frequency matrices (PSFMs) are calculated by aligning all the sequences of a region of interest to anchor at the first position and then the frequency of each amino acid is calculated accordingly. Two PSFMs are calculated: (1) the unscaled PSFM, in which the frequencies are calculated based on the total number of observed sequences per sample at each position and (2) the sacled PSFM, in which the frequencies are calculated based on the total number of observed sequences per sample.

Figure @ref(fig:comp) shows the PSFM of CDR3 in PCR1. Amino acids are coloured based on their physiochemical properties. The left plot shows the unscaled composition logo and the right plot shows the scaled composition logo. Similar plots for other FRs and CDRs are available in the same tab.

Amino acid composition logo for PCR1’s CDR3. The unscaled (left) and the scaled (right) composition logos are colour coded and grouped by their physicochemical properties.

Comparative analysis

The plots described in this section can be found in the Clonotypes tab of PCR1 vs PCR2 vs PCR3’s HTML report.

Since comparative analysis deals with overlapping clonotypes, this analysis only applies when compare was supplied with at least one sample comparison. Earlier, the call to abseqReport had compare = c("PCR1, PCR2, PCR3"), therefore PCR1, PCR2, and PCR3 are compared against each other.

Throughout this analysis, a clonotype is synonymous to its CDR3 amino acid sequence.

Over-representation analysis

Figure @ref(fig:topclones) offers a simple overview of the top 10 over-represented clones found in each sample. Since the clonotypes are colour coded, overlapping clonotypes can easily be identified within the top 10 of each samples. Note that the proportions are scaled relative to the top 10 clones in the respective samples.

This plot complements the scatter plot mentioned above. It displays the most abundant clonotypes in each sample with the amino acid sequence in the legend.

Top 10 clonotypes from PCR1, PCR2, and PCR3. The clonotype proportions displayed are scaled relative to the top 10 clones in each sample.

Overlapping analysis

Multi-sample analysis

While Figure @ref(fig:topclones) is capable of showing overlapping clones, it is restricted to the top 10 over-represented clones from each sample. Figure @ref(fig:overlap) aims to overcome the restriction by using a venn diagram to visualize the number of overlapping (and non-overlapping) clones from each sample. Each number within the venn diagram shows the number of unique clonotypes that are overlapping (in an intersection) or are non-overlapping (not in any intersection). That is, by taking the sum of all the numbers in a sample segment, it becomes the number of unique clonotypes found in that sample.

Number of unique overlapping clones found in PCR1, PCR2, and PCR3. The numbers in an intersection denotes the number of unique clones that are shared between the samples involved in the said intersection.

Note that this venn diagram will not be plotted if there are more than 5 samples.

Two-sample analysis

In order to visualize the correlation between any pair of samples, abseqR plots a scatter plot of every possible combination. Figure @ref(fig:scatter) shows one of them, plotting the clonotype frequencies in PCR2 against PCR1.

The scatter plot:

• has log₁₀-scaled clonotype frequencies
• has a point for each clonotype
  • the coordinate of each point denotes the log₁₀(frequency) in the sample on the x and y axis respectively
  • point sizes are mapped to the mean frequency of a clonotype
• has marginal density plots colour coded as such:
  • blue: density of overlapping clonotypes
  • purple: density of non-overlapping clonotypes
  • grey: density of all clonotypes

Log-scaled scatter plot of clonotype frequencies in PCR1 and PCR2. Point size denotes mean frequency of the 2 samples and marginal density plots are colour coded by overlapping (blue), non-overlapping (purple), and all (grey) clonotypes.

This plot is heavily inspired by VDJTools.

Correlation analysis

In addition to Figure @ref(fig:scatter), the linear correlation of clonotype frequencies between samples can be directly quantified using Pearson’s correlation coefficient. Figure @ref(fig:corr) shows the plot generated by ggcorrplot used to visualize pearson coefficients. A similar plot using Spearman’s correlation coefficient (rank-based) is also available in the same directory.

Pearson correlation between PCR1, PCR2, and PCR3. Values denote the pearson correlation coefficient of the clonotypes frequencies between the samples. These values will appear with a cross ‘x’ to signify an insignificant coefficient if the p-value of the coefficient is larger than 0.05.

Clustering analysis

The vegan package was used to calculate distances between samples. The distances between samples are calculated using its clonotype frequencies by applying methods from Morisita-Horn’s overlap index, Jaccard index, and Dice’s coefficient.

Figure @ref(fig:cluster) shows a dendrogram plotted using Morisita-Horn’s overlap index. The length of each line denotes the distance between the 2 samples or clusters it is connected to. Other dendrograms using Jaccard and Dice’s formula are available in the same directory.

Morisita-Horn distances of PCR1, PCR2, and PCR3. The distances are calculated using clonotype frequencies and are visualized as the length of the lines connecting samples or clusters.

Datasets

The datasets used in the above examples was obtained from a combination of synthetic sample datasets generated using MiXCR’s program here. Firstly, three distinct samples were generated, each simulated with the following parameters in MiXCR:

Following that, an arbitrary number of sequences were randomly drawn from each of the three samples and randomly amplified. This process was repeated 3 times, resulting in a final repertoire of three samples, named PCR1, PCR2, and PCR3.

Finally, these three samples were analyzed by abseqPy. The command used to analyze these samples are as follows:

abseq -y params.yml

where the contents of params.yml is:

# params.yml
defaults:
    bitscore: 300
    sstart: 1-3
    alignlen: 250
    outdir: ex
    task: all
    threads: 1
---
file1: PCR1.fasta
name: PCR1
---
file1: PCR2.fasta
name: PCR2
---
file1: PCR3.fasta
name: PCR3

abseqPy’s analysis output on these three samples are contained within the dataset described in this vignette.

Session Info

This vignette was rendered in the following environment:

## R version 4.4.2 (2024-10-31)
## Platform: x86_64-pc-linux-gnu
## Running under: Ubuntu 24.04.1 LTS
## 
## Matrix products: default
## BLAS:   /usr/lib/x86_64-linux-gnu/openblas-pthread/libblas.so.3 
## LAPACK: /usr/lib/x86_64-linux-gnu/openblas-pthread/libopenblasp-r0.3.26.so;  LAPACK version 3.12.0
## 
## locale:
##  [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C              
##  [3] LC_TIME=en_US.UTF-8        LC_COLLATE=C              
##  [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: Etc/UTC
## tzcode source: system (glibc)
## 
## attached base packages:
## [1] grid      stats     graphics  grDevices utils     datasets  methods  
## [8] base     
## 
## other attached packages:
## [1] gridExtra_2.3    plotly_4.10.4    ggplot2_3.5.1    png_0.1-8       
## [5] abseqR_1.25.0    BiocStyle_2.35.0
## 
## loaded via a namespace (and not attached):
##  [1] gtable_0.3.6         circlize_0.4.16      shape_1.4.6.1       
##  [4] xfun_0.49            bslib_0.8.0          htmlwidgets_1.6.4   
##  [7] GlobalOptions_0.1.2  lattice_0.22-6       vctrs_0.6.5         
## [10] tools_4.4.2          generics_0.1.3       parallel_4.4.2      
## [13] tibble_3.2.1         fansi_1.0.6          cluster_2.1.6       
## [16] pkgconfig_2.0.3      Matrix_1.7-1         data.table_1.16.2   
## [19] RColorBrewer_1.1-3   VennDiagram_1.7.3    lifecycle_1.0.4     
## [22] farver_2.1.2         compiler_4.4.2       stringr_1.5.1       
## [25] munsell_0.5.1        codetools_0.2-20     permute_0.9-7       
## [28] htmltools_0.5.8.1    sys_3.4.3            buildtools_1.0.0    
## [31] sass_0.4.9           lazyeval_0.2.2       yaml_2.3.10         
## [34] tidyr_1.3.1          pillar_1.9.0         jquerylib_0.1.4     
## [37] MASS_7.3-61          BiocParallel_1.41.0  cachem_1.1.0        
## [40] vegan_2.6-8          flexdashboard_0.6.2  ggcorrplot_0.1.4.1  
## [43] nlme_3.1-166         tidyselect_1.2.1     digest_0.6.37       
## [46] stringi_1.8.4        purrr_1.0.2          dplyr_1.1.4         
## [49] reshape2_1.4.4       labeling_0.4.3       splines_4.4.2       
## [52] maketools_1.3.1      fastmap_1.2.0        colorspace_2.1-1    
## [55] cli_3.6.3            magrittr_2.0.3       utf8_1.2.4          
## [58] withr_3.0.2          scales_1.3.0         httr_1.4.7          
## [61] rmarkdown_2.29       lambda.r_1.2.4       futile.logger_1.4.3 
## [64] evaluate_1.0.1       knitr_1.49           viridisLite_0.4.2   
## [67] mgcv_1.9-1           rlang_1.1.4          ggdendro_0.2.0      
## [70] futile.options_1.0.1 Rcpp_1.0.13-1        glue_1.8.0          
## [73] BiocManager_1.30.25  formatR_1.14         jsonlite_1.8.9      
## [76] R6_2.5.1             plyr_1.8.9