The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

apmx: Automated Population Pharmacokinetic Dataset Assembly

Automated methods to assemble population PK (pharmacokinetic) and PKPD (pharmacodynamic) datasets for analysis in 'NONMEM' (non-linear mixed effects modeling) by Bauer (2019) <doi:10.1002/psp4.12404>. The package includes functions to build datasets from SDTM (study data tabulation module) <https://www.cdisc.org/standards/foundational/sdtm>, ADaM (analysis dataset module) <https://www.cdisc.org/standards/foundational/adam>, or other dataset formats. The package will combine population datasets, add covariates, and create documentation to support regulatory submission and internal communication.

Version: 1.1.1
Depends: R (≥ 4.00)
Imports: dplyr, tidyr, purrr, this.path, flextable, officer, tidyselect, utils, arsenal
Suggests: rmarkdown, knitr, testthat, tibble
Published: 2024-01-09
DOI: 10.32614/CRAN.package.apmx
Author: Stephen Amori [aut, cre, cph], Ethan DellaMaestra [aut], Michael Dick [aut], Daniel Litow [ctb], Jonah Lyon [ctb]
Maintainer: Stephen Amori <stephen.amori at amadorbio.com>
BugReports: https://github.com/stephen-amori/apmx/issues
License: GPL (≥ 3)
URL: https://github.com/stephen-amori/apmx
NeedsCompilation: no
Materials: README NEWS
CRAN checks: apmx results

Documentation:

Reference manual: apmx.pdf
Vignettes: PKPD_analysis

Downloads:

Package source: apmx_1.1.1.tar.gz
Windows binaries: r-devel: apmx_1.1.1.zip, r-release: apmx_1.1.1.zip, r-oldrel: apmx_1.1.1.zip
macOS binaries: r-release (arm64): apmx_1.1.1.tgz, r-oldrel (arm64): apmx_1.1.1.tgz, r-release (x86_64): apmx_1.1.1.tgz, r-oldrel (x86_64): apmx_1.1.1.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=apmx to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.