Dependency analysis on package FME

General information

CRAN link link
Package version1.3.6.2
Number of strong dependencies14
Number of all dependencies16
Number of parent packages10
Max heaviness from parent packages3
Total heaviness from parent packages9
Number of parent packages (including Suggests and Enhances)11

Dependency heatmap

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

Adjust heatmap size:
Base packages Other packages Depends Imports Suggests graphics grDevices stats methods utils grid lattice Rcpp shape 0 5 10 Imported methods 0 2 4 6 Required packages 0 1 2 3 Heaviness from parents rootSolve deSolve coda minpack.lm graphics grDevices stats utils minqa MASS diagram In total 14 packages are required directly or indirectly (16) when installing 'FME' (1.3.6.2) Depends Imports Suggests Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'FME' Imported functions The whole namespace is imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on FME
coda Depends The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 6 3
rootSolve Depends The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 3 1
deSolve Depends The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 4 1
minqa Imports 1 0 0 3 2
minpack.lm Imports 2 0 0 0 1
MASS Imports 1 0 0 5 1
graphics Imports 13 0 0 0 0
grDevices Imports The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 0 0
stats Imports The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 0 0
utils Imports The whole set of functions/methods/classes from parent package is imported to the namespace of FME. 0 0
diagram Suggests No object is imported into the namespace of FME. 4 2

Analysis was done with pkgndep.