Dependency analysis on package nnfor

General information

CRAN link link
Package version0.9.6
Number of strong dependencies95
Number of all dependencies98
Number of parent packages7
Max heaviness from parent packages30
Total heaviness from parent packages40
Number of parent packages (including Suggests and Enhances)8
Max co-heaviness from parent packages ("tsutils" and "forecast")43

Dependency heatmap

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

Adjust heatmap size:
Base packages Other packages Depends Imports Suggests stats graphics grDevices utils methods grid splines parallel tools Rcpp MASS lattice Matrix colorspace fracdiff ggplot2 lmtest magrittr nnet timeDate tseries urca zoo RcppArmadillo digest glue gtable isoband mgcv rlang scales tibble withr quadprog quantmod nlme farver labeling lifecycle munsell R6 RColorBrewer viridisLite ellipsis fansi pillar pkgconfig vctrs xts TTR curl cli crayon utf8 RcppEigen forecast Deriv foreach shape survival codetools iterators MAPA plotrix smooth greybox generics pracma statmod nloptr texreg testthat httr brio callr desc evaluate jsonlite pkgload praise processx ps waldo mime openssl rprojroot rstudioapi diffobj rematch2 askpass sys hts SparseM 0 2 4 Imported methods 0 20 40 60 80 Required packages 0 10 20 30 Heaviness from parents forecast uroot plotrix MASS neuralnet glmnet tsutils thief In total 95 packages are required directly or indirectly (98) when installing 'nnfor' (0.9.6) Depends Imports Suggests Base packages that are required Recommended packages that are required Contributed packages that are required Packages that are required for installing 'nnfor' Imported functions Package is listed in 'Imports' but namespace is not imported


Dependency table

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

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

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on nnfor
forecast Depends 2 0 0 53 0
tsutils Imports 4 0 0 84 30
glmnet Imports Parent package is listed in Imports of nnfor but no object from parent package is imported. 16 7
neuralnet Imports Parent package is listed in Imports of nnfor but no object from parent package is imported. 8 2
uroot Imports Parent package is listed in Imports of nnfor but no object from parent package is imported. 1 1
plotrix Imports Parent package is listed in Imports of nnfor but no object from parent package is imported. 4 0
MASS Imports Parent package is listed in Imports of nnfor but no object from parent package is imported. 5 0
thief Suggests No object is imported into the namespace of nnfor. 57 3

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 nnfor Co-heaviness as Jaccard coeffcient
forecast tsutils 43 0.589

Analysis was done with pkgndep.