Maintaince or issue reports
Should you encounter any bugs or have any suggestions, please feel free to contact Wenpin Hou wh2526@cumc.columbia.edu, or open an issue on the Github page https://github.com/Winnie09/Lamian/issues.
Pseudotime analysis based on single-cell RNA-seq (scRNA-seq) data has been widely used to study dynamic gene regulatory programs along continuous biological processes such as cell differentiation, immune responses, and disease development. Existing pseudotime analysis methods primarily address the issue of reconstructing cellular pseudotemporal trajectories and inferring gene expression changes along the reconstructed trajectory in one biological sample. As scRNA-seq studies are increasingly performed on multiple patient samples, comparing gene expression dynamics across samples has been emerging as a new demand for which a systematic analytical solution is lacking.
We develop a systematic computational and statistical framework, Lamian, for multi-sample pseudotime analysis. Given scRNA-seq data from multiple biological samples with covariates (e.g., age, sex, sample type, disease status, etc.), this framework allows one to (1) construct cellular pseudotemporal trajectory, evaluate the uncertainty of the trajectory branching structure, (2) evaluate changes in branching structure associated with sample covariates, (3) identify changes in cell abundance and gene expression along the pseudotime, and (4) characterize how sample covariates modifies the pseudotemporal dynamics of cell abundance and gene expression. Importantly, when identifying cell abundance or gene expression changes associated with pseudotime and sample covariates, Lamian accounts for variability across biological samples which other existing pseudotime methods do not consider. As a result, Lamian is able to more appropriately control the false discovery rate (FDR) when analyzing multi-sample data, a property not offered by any other methods.
For more details, see our paper describing the Lamian package:
Please follow the details here https://github.com/Winnie09/Lamian to download Lamian package and then load it using the following commands.
# load in Lamian
options(warn=-1)
suppressMessages(library(Lamian))
The module 1 of Lamian is designed for detecting the stability of branches in a pseudotime tree structure. We automatically enumerate all branches from the pseudotime tree structure, and then test for their detection rate through 10,000 bootstraps. After each cell-bootstrapping, we reconstruct the tree structure and re-identify all branches. We apply both Jaccard statistics and overlap coefficient as the statistics for evaluating whether any branch in a bootstrap setting matches with one of the original branches. A branch’s detection rate is defined as the percentage of bootstrap settings that a branch finds it match. Module 1 also reports and tests for samples’ proportion in each branch.
We will need a gene by cell expression matrix, the low-dimension representation of the cells, and the cell annotation (which sample each cell belongs to). Here, we use example data hca_bm_saver, hca_bm_pca, hca_bm_cellanno to demonstrate their data structures. Users can read in their own data of interest in this step.
data(man_tree_data)
man_tree_data is a list containing gene by cell expression matrix, low-dimension representation (PCA) of the cells, and the cell annotation where the first column are the cell names, the second column are the sample names, and the row names are the cell names.
str(man_tree_data)
## List of 3
## $ pca : num [1:2000, 1:50] -19.6 -10.5 -13.2 -12.5 27.3 ...
## ..- attr(*, "dimnames")=List of 2
## .. ..$ : chr [1:2000] "BM2:50:male_205626" "BM4:29:male_164021" "BM3:39:male_104439" "BM3:39:male_93578" ...
## .. ..$ : chr [1:50] "PC_1" "PC_2" "PC_3" "PC_4" ...
## $ expression: num [1:11, 1:2000] 0.0172 0.2461 1.0014 0.1017 0.0072 ...
## ..- attr(*, "dimnames")=List of 2
## .. ..$ : chr [1:11] "CDK1" "CD14" "CDCA4" "CD7" ...
## .. ..$ : chr [1:2000] "BM2:50:male_205626" "BM4:29:male_164021" "BM3:39:male_104439" "BM3:39:male_93578" ...
## $ cellanno :'data.frame': 2000 obs. of 2 variables:
## ..$ cell : chr [1:2000] "BM2:50:male_205626" "BM4:29:male_164021" "BM3:39:male_104439" "BM3:39:male_93578" ...
## ..$ sample: chr [1:2000] "BM2" "BM4" "BM3" "BM3" ...
If your data is a Seurat object, the most straightforward way is to extract the slots of PCA, gene expression matrix (before integration), etc..
Please see below Module 3 and 4 for more details if you have an ultra large data and it is in the HDF5 format.
set.seed(12345)
res = infer_tree_structure(pca = man_tree_data[['pca']],
expression = man_tree_data[['expression']],
cellanno = man_tree_data[['cellanno']],
origin.marker = c('CD34'),
number.cluster = 5,
xlab='Principal component 1',
ylab = 'Principal component 2')
As we can see from the above inputs, there are five clusters, and the tree structure inferred based on these clusters consists of three branches: 2 –> 3 –> 1, 2 –> 4, and 2 –> 5. The result object res is a list containing information about the tree structure, branches, cell clusters, pseudotime ordering the cells, etc..
names(res)
## [1] "pcareduceres" "MSTtree" "clusterid" "clucenter" "pseudotime"
## [6] "branch" "js.cut" "oc.cut" "pca" "order"
## [11] "allsample"
Lamian::plotmclust(res, cell_point_size = 0.5,
x.lab = 'Principal component 1',
y.lab = 'Principal component 2')
We can call the function evaluate_uncertainty() to evaluate the tree topology uncertainty. We suggested that users set n.permute = 100 or more to ensure enough randomness to construct the null distribution, but here we set n.permute = 5 in order to provide a simplified example.
result <- evaluate_uncertainty(res, n.permute=5)
names(result)
## [1] "detection.rate" "sample.cellcomp.mean" "sample.cellcomp.sd"
Since for the simplicity of the example we set n.permute = 5 only, the branch proportions might not really make sense. When users set n.permute = 100 or more in their real applications, results will make much more sense. The result is a list of three elements. The first selement is the detection rate of each branch.
result[[1]]
The second element is the sample proportion mean information.
result[[2]]
## BM2 BM4 BM3 BM8 BM1 BM6
## 1:2 0.2268874 0.1625525 0.2043402 0.3333333 0.2367380 0.3333333
## c(1, 3) 0.5046939 0.2329026 0.5247018 0.3333333 0.2583391 0.3333333
## c(1, 5, 4) 0.2684187 0.6045449 0.2709579 0.3333333 0.5049229 0.3333333
## BM5 BM7
## 1:2 0.1880292 0.3333333
## c(1, 3) 0.1880292 0.3333333
## c(1, 5, 4) 0.6239415 0.3333333
The thrid element is the sample proportion sd (standard deviation) information.
result[[3]]
## BM2 BM4 BM3 BM8 BM1 BM6 BM5
## 1:2 0.006148083 0.004220924 0.01119082 0 0.011753888 0 0.003269304
## c(1, 3) 0.008780549 0.006676212 0.02276736 0 0.002057573 0 0.003269304
## c(1, 5, 4) 0.002632466 0.010897136 0.01157654 0 0.009696315 0 0.006538609
## BM7
## 1:2 0
## c(1, 3) 0
## c(1, 5, 4) 0
Module 2 of Lamian first identifies variation in tree topology across samples and then assesses if there are differential topological changes associated with sample covariates. For each sample, Lamian calculates the proportion of cells in each tree branch, referred to as branch cell proportion. Because a zero or low proportion can reflect absence or depletion of a branch, changes in tree topology can be described using branch cell proportion changes. With multiple samples, Lamian characterizes the cross-sample variation of each branch by estimating the variance of the branch cell proportion across samples. Furthermore, regression models can be fit to test whether the branch cell proportion is associated with sample covariates. This allows one to identify tree topology changes between different conditions, for example in a case-control cohort.
data = result[[2]]
rownames(data) <-
c('HSC->lymphocyte', 'HSC->myeloid', 'HSC->erythroid')
design = data.frame(sample = paste0('BM', 1, 8), sex = c(0, rep(1, 4), rep(0, 3)))
branchPropTest(data = data, design = design)
## HSC->lymphocyte HSC->myeloid HSC->erythroid
## 0.5129678 0.9790714 0.7383605
In the following, we will use an example dataset expdata of 100 genes and 1000 cells to demonstration the workflow. In practice, we can input any dataset of interest.
data(expdata)
The inputs should contain: (a) expr: a gene by cell expression matrix. The entires are library-size-normalized log-transformed gene expression values. They can be either imputed or non-imputed. Zero-expression genes should have been filtered out.
str(expdata$expr)
## num [1:120, 1:1000] 1.973 1.163 0.526 1.637 0.34 ...
## - attr(*, "dimnames")=List of 2
## ..$ : chr [1:120] "TPM4" "HLA-DMB" "KHSRP" "ACER3" ...
## ..$ : chr [1:1000] "BM4:26:female_219004" "BM1:26:female_219241" "BM4:29:male_179571" "BM3:26:female_52851" ...
head(expdata$cellanno)
str(expdata$pseudotime)
## Named int [1:1000] 1 2 3 4 5 6 7 8 9 10 ...
## - attr(*, "names")= chr [1:1000] "BM4:26:female_219004" "BM1:26:female_219241" "BM4:29:male_179571" "BM3:26:female_52851" ...
print(expdata$design)
## intercept group
## BM1 1 1
## BM2 1 1
## BM3 1 0
## BM4 1 0
## BM5 1 1
## BM6 1 1
## BM7 1 0
## BM8 1 0
The function lamian.test()
is designed to perform multiple tests. To perform the Sample Covariate Test, we need to set test.type = ‘variable’.
For ultra-large datasets, for example when there are hundreds of samples each of which consists of hundreds to thousands of cells, we recommend using the hdf5 format to store the gene expression information instead of a matrix. This step significantly reduces the memory usage of each round, and therefore in a parallel mode the program can run more rounds and be completed at a faster speed.
To save the gene expression in hdf5 file format, we apply the following codes which creates a new file data/multi.h5 (file multi.h5 in the folder data/ )
saveh5(expr = expdata$expr,
pseudotime = expdata$pseudotime,
cellanno = expdata$cellanno,
path = 'data/multi.h5')
We can perform XDE test using four inputs expr, cellanno, pseudotime, and design.
By default, test.method = ‘permutation’. The default permutation is 100, i.e. permuiter = 100, but in this small example we set it as permuiter = 5 only to save the running time. We recommend setting permuiter = 100 or higher in real applications. We also provide test.method = ‘chisq’.
Here, we set testvar = 2 to test the second column of the design matrix as the sample covariate while adjusting for other columns (except the intercept).
If the gene expression is in a regular matrix format,
Res <- lamian_test(
expr = expdata$expr,
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design,
test.type = 'variable',
testvar = 2,
permuiter = 5,
## This is for permutation test only.
## We suggest that users use default permuiter = 100.
## Alternatively, we can use test.method = 'chisq' to swich to the chi-square test.
ncores = 1
)
If the gene expression is in an hdf5 file format,
Res <- lamian_test_h5(
expr = 'data/multi.h5',
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design,
test.type = 'variable',
testvar = 2,
permuiter = 5,
## This is for permutation test only.
## We suggest that users use default permuiter = 100.
## Alternatively, we can use test.method = 'chisq' to swich to the chi-square test.
ncores = 1
)
We will know which are XDE from the statistics data frame in the result object Res.
## get differential dynamic genes statistics
stat <- Res$statistics
stat <- stat[order(stat[, 1],-stat[, 3]),]
## identify XDE genes with FDR.overall < 0.05 cutoff
diffgene <-
rownames(stat[stat[, grep('^fdr.*overall$', colnames(stat))] < 0.05, ])
We will get the population-level estimates for all the XDE genes by applying function getPopulationFit()
.
## population fit
Res$populationFit <-
getPopulationFit(Res, gene = diffgene, type = 'variable')
We can apply getCovariateGroupDiff()
to calculate the group difference regarding this sample covariate, and then cluster the XDE genes based on the group difference. By setting k = 4, we will get two clusters for meanSig XDE genes, and the other two clusters for XDE genes of other types.
## clustering
Res$covariateGroupDiff <-
getCovariateGroupDiff(testobj = Res, gene = diffgene)
Res$cluster <-
clusterGene(Res, gene = diffgene, type = 'variable', k = 5)
We can also plot original expression values, model fitted expression values, and model-fitted group difference in three seperate heatmaps.
plotXDEHm(
Res,
cellWidthTotal = 180,
cellHeightTotal = 350,
subsampleCell = FALSE,
sep = ':.*'
)
We can plot the cluster mean and difference.
## plotClusterMeanAndDiff
plotClusterMeanAndDiff(Res)
We can also plot the cluster difference seperately by calling plotClusterDiff(testobj=Res, gene = diffgene)
.
We can further check out whether the XDE genes in each cluster have any enriched genome functions by applying Gene Ontology (GO) analysis library(topGO); goRes <- GOEnrich(testobj = Res, type = 'variable')
. Please note that there are no enriched GO terms in any of the clusters in this simplified example since we only subset 1,000 genes. In practice, if there are significant GO terms in the clusters, we can generate a heatmap of the top GO terms using the command plotGOEnrich(goRes = goRes)
.
The inputs for Constant Time Test are the same as those for Sample Covariate Test (see above section), except that the design matrix can have only one intercept column. If there are more than one columns in design, only the first column will be considered.
Similar to the XDE test, we can perform the TDE test using four inputs expr, cellanno, pseudotime, and design. The only difference is that design can be a one-column matrix or dataframe whose values are 1s. If there are multiple columns, only the first column will be actually used. The default permutation is 100, i.e. permuiter = 100, but in this small example we set it as permuiter = 5 again to save the running time. We recommend setting permuiter = 100 or higher in real applications.
If the gene expression is in a matrix format,
Res <- lamian_test(
expr = expdata$expr,
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design,
test.type = 'time',
permuiter = 5
)
If the gene expression is in an hdf5 file format,
Res <- lamian_test_h5(
expr = 'data/multi.h5',
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design,
test.type = 'time',
permuiter = 5
## This is for permutation test only.
## We suggest that users use default permuiter = 100.
## Alternatively, we can use test.method = 'chisq' to swich to the chi-square test.
)
The result object is a list containing multiple elements. The first element is a dataframe of statistics.
head(Res$statistics)
We can further determine the TDE genes as the genes with fdr.overall \(< 0.05\).
diffgene <- rownames(Res$statistics)[Res$statistics[, 1] < 0.05]
We can estimate the population-level model-fitted patterns for all TDE genes.
Res$populationFit <-
getPopulationFit(Res, gene = diffgene, type = 'time')
Then we can further cluster these genes.
Res$cluster <-
clusterGene(Res, gene = diffgene, type = 'time', k = 3)
We can visualize the temporal patterns and compare original and fitted expression
plotTDEHm(
Res,
subsampleCell = FALSE,
showCluster = TRUE,
type = 'time',
cellWidthTotal = 200,
cellHeightTotal = 200
)
## TableGrob (1 x 9) "arrange": 3 grobs
## z cells name grob
## 1 1 (1-1,1-4) arrange gtable[layout]
## 2 2 (1-1,5-5) arrange gtable[layout]
## 3 3 (1-1,6-9) arrange gtable[layout]
To plot cluster mean patterns.
plotClusterMean(testobj = Res,
cluster = Res$cluster,
type = 'time')
## `geom_smooth()` using method = 'gam' and formula = 'y ~ s(x, bs = "cs")'
Similar to XDE test, we can further proceed to identify the enriched GO terms for each gene cluster using commands library(topGO); goRes <- GOEnrich(testobj = Res, type = 'time', sep = ':.*')
. Please note that there are no enriched GO terms in any of the clusters in this simplified example since we only subset 1,000 genes. In practice, if there are enriched GO terms, we can plot them using commands plotGOEnrich(goRes = goRes)
.
The inputs are the same as those for TDE test (see above), except that we don not need gene expression matrix.
Res <-
cellPropTest(
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design[, 1, drop = F],
ncores = 4,
test.type = 'Time'
)
The dataframe statistics in the Res object contains the test result: a p-value pval.overall and a effect size z-score z.overall.
head(Res$statistics)
The inputs are the same for XDE test (see above), except that we do not need gene expression matrix.
Res <-
cellPropTest(
cellanno = expdata$cellanno,
pseudotime = expdata$pseudotime,
design = expdata$design,
ncores = 4,
test.type = 'Variable',
testvar = 2
)
The dataframe statistics in the Res object contains the test result: a p-value pval.overall and a effect size z-score z.overall.
The uncertainty quantification of trajectory topology for other pseudotime methods is currently not supported in Lamian Modules 1 and 2 due to scalability issue (e.g. slingshot, which is another popular tree method similar to TSCAN but requires a more time-consuming principal curves fitting step), and/or technical complications in implementation (e.g. Monocle2, Monocle3, PhenoPath). However, Lamian allows one the cellular pseudotime generated by other methods as input for downstream analyses in Modules 3 and 4. In the following, we take the pseudotime method slingshot
as an example to demonstrate how to incoporate the pseudotime from another pseudotime method other than TSCAN
to run Lamian’s Module 3.
Use slingshot to infer cellular pseudotime
Load the data we prepared for this demo. It is subsetted from HCA-BM data.
data(slingshot_data)
Load the package slingshot
and its dependencies. Prepare the data objects, the low-dimentional representation (here we use principal components), and clusters.
suppressMessages(library(slingshot))
suppressMessages(library(SingleCellExperiment))
suppressMessages(library(mclust))
cnt <- slingshot_data$counts
pca <- slingshot_data$pca
sce <- SingleCellExperiment(assays = List(counts = cnt))
reducedDims(sce) <- SimpleList(PCA = pca)
cl1 <- Mclust(pca)$classification
colData(sce)$GMM <- cl1
Run slingshot()
to obtain cellcular pseudotime. At the same time, we check the running time using system.time()
.
system.time({
sce <- slingshot(sce, clusterLabels = 'GMM', reducedDim = 'PCA')
})
## Using full covariance matrix
## user system elapsed
## 12.206 0.085 12.310
(Optional) Plot slingshot’s MST
library(RColorBrewer)
plot(reducedDims(sce)$PCA,
col = brewer.pal(9,'Set1')[sce$GMM],
pch=16,
asp = 1,
xlab = 'Principal component 1',
ylab = 'Principal component 2')
lines(SlingshotDataSet(sce), lwd=2, type = 'lineages', col = 'black')
For example, we can visualize the first lineage pseudotime_1
constructed by slingshot
.
library(grDevices)
colors <- colorRampPalette(brewer.pal(11,'Spectral')[-6])(nrow(pca))
plotcol <- colors[cut(sce$slingPseudotime_1, breaks=nrow(pca))]
plot(reducedDims(sce)$PCA,
col = plotcol,
pch=16,
asp = 1,
xlab = 'Principal component 1',
ylab = 'Principal component 2')
lines(SlingshotDataSet(sce)@curves[[1]], lwd=2, col='black')
In practice, users may select any interesting lineage. In the following, we suppose users are interested in the first lineage. We can then subset the cellular pseudotime in the first lineage.
pt <- sce$slingPseudotime_1
names(pt) <- colnames(cnt) ## A vector with names is easier to handle in subsetting.
The following steps are important when using any pseudotime inference methods, not only for slingshot’s data.
First, check the cellcular pseudotime distribution. We can see that it contains NA
, meaning that some cells do not have pseudotime, so we can’t use these cells in the differential temporal analysis. We need to select the cells that have pseudotime.
summary(pt)
## Min. 1st Qu. Median Mean 3rd Qu. Max. NA's
## 0.000 8.899 49.879 37.966 54.192 62.475 748
pt <- pt[!is.na(pt)] ## important
selectedCell <- names(pt)
Second, check the numbers of cells in samples. We can see that only the first five samples (BM1, BM2, BM3, BM4, BM5) have enough cells for downstream analyses. The remaining samples have less than 50 cells. Samples with too few cells will lead to low signal-to-noise ratio or even bugs in the program. We need to select the cells in the first five samples.
table(slingshot_data$cellanno[selectedCell, 2]) ## important
##
## BM1 BM2 BM3 BM4 BM5 BM6 BM7 BM8
## 258 243 262 337 281 8 6 11
sample <- slingshot_data$cellanno[selectedCell, 2]
selectedSample <- c(paste0('BM', seq(1,5)))
selectedCell2 <- selectedCell[sample %in% selectedSample]
Now we can run Module 3 with slingshot’s pseudotime.
Res <- lamian_test(
expr = slingshot_data$expr[, selectedCell2],
cellanno = slingshot_data$cellanno[selectedCell2, ],
pseudotime = pt[selectedCell2],
design = slingshot_data$design[selectedSample,],
test.type = 'variable',
testvar = 2,
permuiter = 3,
## This argument is for permutation test only.
## Alternatively, we can use test.method = 'chisq' to swich to the chi-square test where we dont' need this argument.
## In permutation test, we suggest that users use default permuiter = 100.
ncores = 1
)
Analogously, we can use the above inputs to run Module 4. Since it is very straighforward, we won’t go into details here.
sessionInfo()
## R version 4.0.2 (2020-06-22)
## Platform: x86_64-apple-darwin17.0 (64-bit)
## Running under: macOS 10.16
##
## Matrix products: default
## BLAS: /Library/Frameworks/R.framework/Versions/4.0/Resources/lib/libRblas.dylib
## LAPACK: /Library/Frameworks/R.framework/Versions/4.0/Resources/lib/libRlapack.dylib
##
## locale:
## [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
##
## attached base packages:
## [1] stats4 parallel stats graphics grDevices utils datasets
## [8] methods base
##
## other attached packages:
## [1] RColorBrewer_1.1-3 mclust_6.0.0
## [3] SingleCellExperiment_1.12.0 SummarizedExperiment_1.20.0
## [5] Biobase_2.50.0 GenomicRanges_1.42.0
## [7] GenomeInfoDb_1.26.7 IRanges_2.24.1
## [9] S4Vectors_0.28.1 BiocGenerics_0.36.1
## [11] MatrixGenerics_1.2.1 matrixStats_0.63.0
## [13] slingshot_1.8.0 princurve_2.1.6
## [15] Lamian_0.99.1 knitr_1.42
##
## loaded via a namespace (and not attached):
## [1] colorspace_2.1-0 rjson_0.2.21 ellipsis_0.3.2
## [4] circlize_0.4.15 XVector_0.30.0 GlobalOptions_0.1.2
## [7] fs_1.6.2 clue_0.3-64 rstudioapi_0.14
## [10] farver_2.1.1 remotes_2.4.2 topGO_2.42.0
## [13] bit64_4.0.5 AnnotationDbi_1.52.0 fansi_1.0.4
## [16] splines_4.0.2 cachem_1.0.8 pkgload_1.3.2
## [19] jsonlite_1.8.4 Cairo_1.5-12.2 cluster_2.1.4
## [22] GO.db_3.12.1 png_0.1-8 pheatmap_1.0.12
## [25] graph_1.68.0 shiny_1.7.4 compiler_4.0.2
## [28] Matrix_1.5-4.1 fastmap_1.1.1 cli_3.6.1
## [31] later_1.3.1 htmltools_0.5.5 prettyunits_1.1.1
## [34] tools_4.0.2 igraph_1.4.2 GenomeInfoDbData_1.2.4
## [37] gtable_0.3.3 glue_1.6.2 reshape2_1.4.4
## [40] dplyr_1.1.2 Rcpp_1.0.10 scattermore_1.1
## [43] jquerylib_0.1.4 TSCAN_2.0.0 vctrs_0.6.2
## [46] rhdf5filters_1.2.1 ape_5.7-1 nlme_3.1-162
## [49] xfun_0.39 stringr_1.5.0 ps_1.7.5
## [52] mime_0.12 miniUI_0.1.1.1 lifecycle_1.0.3
## [55] gtools_3.9.4 devtools_2.4.5 org.Hs.eg.db_3.12.0
## [58] zlibbioc_1.36.0 scales_1.2.1 promises_1.2.0.1
## [61] rhdf5_2.34.0 SparseM_1.81 ComplexHeatmap_2.6.2
## [64] yaml_2.3.7 memoise_2.0.1 gridExtra_2.3
## [67] ggplot2_3.4.2 sass_0.4.6 fastICA_1.2-3
## [70] stringi_1.7.12 RSQLite_2.3.1 highr_0.10
## [73] caTools_1.18.2 pkgbuild_1.4.0 shape_1.4.6
## [76] rlang_1.1.1 pkgconfig_2.0.3 bitops_1.0-7
## [79] evaluate_0.21 lattice_0.21-8 purrr_1.0.1
## [82] Rhdf5lib_1.12.1 labeling_0.4.2 htmlwidgets_1.6.2
## [85] bit_4.0.5 processx_3.8.1 tidyselect_1.2.0
## [88] plyr_1.8.8 magrittr_2.0.3 R6_2.5.1
## [91] gplots_3.1.3 generics_0.1.3 profvis_0.3.8
## [94] combinat_0.0-8 DelayedArray_0.16.3 DBI_1.1.3
## [97] withr_2.5.0 pillar_1.9.0 mgcv_1.8-42
## [100] RCurl_1.98-1.12 tibble_3.2.1 crayon_1.5.2
## [103] KernSmooth_2.23-21 utf8_1.2.3 rmarkdown_2.21
## [106] urlchecker_1.0.1 viridis_0.6.3 GetoptLong_1.0.5
## [109] usethis_2.1.6 grid_4.0.2 blob_1.2.4
## [112] callr_3.7.3 matrixcalc_1.0-6 digest_0.6.31
## [115] xtable_1.8-4 httpuv_1.6.11 munsell_0.5.0
## [118] viridisLite_0.4.2 bslib_0.4.2 sessioninfo_1.2.2
If the Lamian package is useful in your work, please cite the following paper:
Should you encounter any bugs or have any suggestions, please feel free to contact Wenpin Hou wh2526@cumc.columbia.edu, or open an issue on the Github page https://github.com/Winnie09/Lamian/issues.