Conduct a noncompartmental analysis with industrial strength. Some features are 1) CDISC SDTM terms 2) Automatic or manual slope selection 3) Supporting both 'linear-up linear-down' and 'linear-up log-down' method 4) Interval(partial) AUCs with 'linear' or 'log' interpolation method 5) Produce pdf, rtf, text report files. 6) Produce Installation and Operational Qualification (IQ/OQ) reports in pdf. After installation, qualify the package in your own environment: run pdfIQ() for Installation Qualification and pdfOQ() for Operational Qualification. Run writeMD5() once after installation so the IQ file-integrity check passes. To approve a report, sign it digitally in Adobe Acrobat Reader (generate with sigField=TRUE, or run addSigField(), to add click-to-sign fields), instead of printing and scanning; or use signPDF()/verifyPDF() for a scriptable signature. * Reference: Gabrielsson J, Weiner D. Pharmacokinetic and Pharmacodynamic Data Analysis - Concepts and Applications. 5th ed. 2016. (ISBN:9198299107).
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.