Dependency analysis on package Bergm

General information

CRAN link link
Package version5.0.3
Number of strong dependencies54
Number of all dependencies54
Number of parent packages8
Max heaviness from parent packages18
Total heaviness from parent packages27
Number of parent packages (including Suggests and Enhances)8
Max co-heaviness from parent packages ("network" and "ergm")14

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of Bergm and columns are the dependency packages that each parent package brings in. On the right side of the heatmap, there are three barplot annotations: 1. number of imported functions/S4 methods/S4 classes from parent packages; 2. number of dependency packages from each parent package; 3. heaviness of each parent package on Bergm.

Adjust heatmap size:
Base packages Other packages Depends Imports stats methods utils graphics grid grDevices parallel tools splines lattice coda Matrix MASS statnet.common rlang tibble magrittr ellipsis fansi lifecycle pillar pkgconfig vctrs glue cli crayon utf8 network robustbase trust lpSolveAPI rle purrr memoise knitr digest stringr DEoptimR cachem evaluate highr yaml xfun stringi fastmap mcmc quantreg SparseM MatrixModels survival 0 0.5 1 Imported methods 0 20 40 Required packages 0 5 10 15 Heaviness from parents ergm matrixcalc mvtnorm coda Matrix statnet.common MCMCpack network In total 54 packages are required directly or indirectly (54) when installing 'Bergm' (5.0.3) Depends Imports Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'Bergm' Imported functions The whole namespace is imported


Dependency table

"Import" information is from the NAMESPACE file of Bergm.

imports: number of imported functions/objects; importMethods: number of imported S4 methods; importClasses: number of imported S4 classes.

Required packages: number of strong dependency packages for each of the parent package (or in other words, number of dependency packages the parent package brings in).

Heaviness from parent on Bergm: number of required packages that can be reduced if moving parent package to Suggests of Bergm.

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on Bergm
ergm Depends The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 44 18
MCMCpack Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 16 7
matrixcalc Imports 1 0 0 0 1
mvtnorm Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 2 1
coda Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 6 0
Matrix Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 7 0
statnet.common Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 10 0
network Imports The whole set of functions/methods/classes from parent package is imported to the namespace of Bergm. 24 0

The following table lists pairs of parent packages with co-heaviness larger than 10. The co-heaviness measures the number of additional dependencies that two parent packages simultaneously import and are only imported by the two parents.

Note the co-heaviness from parents can be always easily observed in the dependency heatmap.

Parent 1 Parent 2 Co-heaviness on Bergm Co-heaviness as Jaccard coeffcient
ergm network 14 0.438

Analysis was done with pkgndep.