Dependency analysis on package emulator
General information
| CRAN link | link |
|---|---|
| Package version | 1.2-21 |
| Number of strong dependencies | 3 |
| Number of all dependencies | 29 |
| Number of parent packages | 1 |
| Max heaviness from parent packages | 3 |
| Total heaviness from parent packages | 3 |
Number of parent packages (including Suggests and Enhances) | 3 |
Dependency heatmap
In the following dependency heatmap, rows are the parent packages of emulator 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 emulator.
Dependency table
"Import" information is from the NAMESPACE file of emulator.
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 emulator: number of required packages that can be reduced if moving parent package to Suggests of emulator.
| Parent package | Field | imports | importMethods | importClasses | Required packages | Heaviness from parent on emulator |
|---|---|---|---|---|---|---|
| mvtnorm | Depends | The whole set of functions/methods/classes from parent package is imported to the namespace of emulator. | 2 | 3 | ||
| rmarkdown | Suggests | No object is imported into the namespace of emulator. | 27 | 26 | ||
| knitr | Suggests | No object is imported into the namespace of emulator. | 12 | 11 | ||
Analysis was done with pkgndep.