Dependency analysis on package rootSolve

General information

CRAN link link
Package version1.8.2.3
Number of strong dependencies3
Number of all dependencies3
Number of parent packages3
Max heaviness from parent packages1
Total heaviness from parent packages3
Number of parent packages (including Suggests and Enhances)3

Dependency heatmap

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

Adjust heatmap size:
All required packages for 'rootSolve' are base packages.


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on rootSolve
stats Imports The whole set of functions/methods/classes from parent package is imported to the namespace of rootSolve. 0 1
graphics Imports The whole set of functions/methods/classes from parent package is imported to the namespace of rootSolve. 0 1
grDevices Imports The whole set of functions/methods/classes from parent package is imported to the namespace of rootSolve. 0 1

Analysis was done with pkgndep.