Run other estimation and simulation software via the 'nlmixr2' (Fidler et al (2019) <doi:10.1002/psp4.12445>) interface including 'PKNCA', 'NONMEM' and 'Monolix'. It also converts 'nlmixr2'/'rxode2' models to 'PopED' optimal design databases (Fidler et al (2024) <doi:10.70534/XUMG6226>). While not required, you can get/install the 'lixoftConnectors' package in the 'Monolix' installation, as described at the following url <https://monolixsuite.slp-software.com/r-functions/2024R1/installation-and-initialization>. When 'lixoftConnectors' is available, 'Monolix' can be run directly instead of setting up command line usage.
Contents
No documentation found
Dependencies Show recursive | ||
|---|---|---|
| ||
| ||
|
| Suggests |
|---|
Graph Navigation
- Pan: Click and drag the canvas
- Zoom: Hold ctrl + scroll wheel
- Reset view: Click "Fit View" button
Legend
Dependency Anatomy Guide
Understanding Dependency Borders
Dependencies are visually distinguished by their border styles to help you understand their relationship to the current package:
Direct Dependencies
Thick solid border: These are dependencies directly specified in the package's DESCRIPTION file (Depends, Imports, Enhances, or LinkingTo).
Recursive Dependencies
Thin solid border: These are dependencies of dependencies (recursive/indirect dependencies). They are initially hidden but can be toggled with the switch button.
Version Constraint Conflicts
Thick border + Info icon: When both direct and recursive dependencies exist for the same package with different version constraints. This indicates the "true" version constraint for the package, as the recursive dependency requires the more strict version constraint.
Understanding the Info Icon
The yellow info circle appears when there are version constraint conflicts between direct and recursive dependencies for the same package. This helps give a more accurate picture of the version constraints for the dependencies of a given package.
Compare Versions
Select an older version above to compare dependencies.