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.

epicontacts: Handling, Visualisation and Analysis of Epidemiological Contacts

A collection of tools for representing epidemiological contact data, composed of case line lists and contacts between cases. Also contains procedures for data handling, interactive graphics, and statistics.

Version: 1.1.4
Imports: grDevices, dplyr, igraph, visNetwork, threejs, methods
Suggests: outbreaks, testthat, covr, shiny, readr, knitr, rmarkdown
Published: 2024-04-30
DOI: 10.32614/CRAN.package.epicontacts
Author: Finlay Campbell [aut, cre], Thibaut Jombart [aut], Nistara Randhawa [aut], Bertrand Sudre [aut], VP Nagraj [aut], Thomas Crellen [aut], Zhian N. Kamvar [aut]
Maintainer: Finlay Campbell <finlaycampbell93 at gmail.com>
BugReports: https://github.com/reconhub/epicontacts/issues
License: GPL-2 | GPL-3 [expanded from: GPL (≥ 2)]
URL: https://www.repidemicsconsortium.org/epicontacts/
NeedsCompilation: no
Citation: epicontacts citation info
Materials: NEWS
In views: Epidemiology
CRAN checks: epicontacts results

Documentation:

Reference manual: epicontacts.pdf
Vignettes: epicontacts overview
epicontacts class

Downloads:

Package source: epicontacts_1.1.4.tar.gz
Windows binaries: r-devel: epicontacts_1.1.4.zip, r-release: epicontacts_1.1.4.zip, r-oldrel: epicontacts_1.1.4.zip
macOS binaries: r-release (arm64): epicontacts_1.1.4.tgz, r-oldrel (arm64): epicontacts_1.1.4.tgz, r-release (x86_64): epicontacts_1.1.4.tgz, r-oldrel (x86_64): epicontacts_1.1.4.tgz
Old sources: epicontacts archive

Reverse dependencies:

Reverse imports: doublIn, epiflows
Reverse suggests: epichains, outbreaker2

Linking:

Please use the canonical form https://CRAN.R-project.org/package=epicontacts 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.