Dependency analysis on package MCL

General information

CRAN link link
Package version1.0
Number of strong dependencies9
Number of all dependencies9
Number of parent packages1
Max heaviness from parent packages9
Total heaviness from parent packages9
Number of parent packages (including Suggests and Enhances)1

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of MCL 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 MCL.

Adjust heatmap size:
Base packages Other packages Imports methods graphics grid stats utils grDevices Matrix lattice 0 0.5 1 Imported methods 0 2 4 6 8 Required packages 0 2 4 6 8 Heaviness from parents expm In total 9 packages are required directly or indirectly (9) when installing 'MCL' (1.0) Imports Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'MCL' Imported functions


Dependency table

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

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 MCL: number of required packages that can be reduced if moving parent package to Suggests of MCL.

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on MCL
expm Imports 1 0 0 8 9

Analysis was done with pkgndep.