Go to file
dr. M.S. (Matthijs) Berends 6652f7d82b fix warnings 2019-01-04 09:49:42 +01:00
R fix warnings 2019-01-04 09:49:42 +01:00
data fix for as.mo and freq 2018-11-30 12:05:59 +01:00
docs fix warnings 2019-01-04 09:49:42 +01:00
inst/rstudio big website update, licence txt update 2019-01-02 23:24:07 +01:00
man fix warnings 2019-01-04 09:49:42 +01:00
pkgdown big website update, licence txt update 2019-01-02 23:24:07 +01:00
tests guess_ab 2019-01-03 23:56:19 +01:00
vignettes big website update, licence txt update 2019-01-02 23:24:07 +01:00
.Rbuildignore fix warnings 2019-01-04 09:49:42 +01:00
.gitignore fix warnings 2019-01-04 09:49:42 +01:00
.gitlab-ci.yml fix warnings 2019-01-04 09:49:42 +01:00
DESCRIPTION big website update, licence txt update 2019-01-02 23:24:07 +01:00
LICENSE Update freq function 2018-05-22 16:34:22 +02:00
NAMESPACE guess_ab 2019-01-03 23:56:19 +01:00
NEWS.md guess_ab 2019-01-03 23:56:19 +01:00
README.md big website update, licence txt update 2019-01-02 23:24:07 +01:00
_pkgdown.yml big website update, licence txt update 2019-01-02 23:24:07 +01:00
appveyor.yml big website update, licence txt update 2019-01-02 23:24:07 +01:00
index.md big website update, licence txt update 2019-01-02 23:24:07 +01:00

README.md

AMR (for R)

NOTE: the original source code is on GitLab (https://gitlab.com/msberends/AMR), so you can report a bug at https://gitlab.com/msberends/AMR/issues. There is a mirror repository on GitHub (https://github.com/msberends/AMR). As the mirror process is automated by GitLab, both repositories always contain the latest changes.


Development source

This is the development source of AMR, a free and open-source R package to simplify the analysis and prediction of Antimicrobial Resistance (AMR) and to work with antibiotic properties by using evidence-based methods.

Not a developer? Then our website https://msberends.gitlab.io/AMR is probably a better place to read about this package. It contains documentation about all of the included functions and also a comprehensive tutorial about how to conduct AMR analysis.

Authors

Matthijs S. Berends 1,2,a, Christian F. Luz 1,a, Erwin E.A. Hassing2, Corinna Glasner 1,b, Alex W. Friedrich 1,b, Bhanu N.M. Sinha 1,b

1 Department of Medical Microbiology, University of Groningen, University Medical Center Groningen, Groningen, the Netherlands - rug.nl umcg.nl
2 Certe Medical Diagnostics & Advice, Groningen, the Netherlands - certe.nl
a R package author and thesis dissertant
b Thesis advisor

How to get this package

All stable versions of this package are published on CRAN, the official R network with a peer-reviewed submission process.

Install from CRAN

CRAN_Badge CRAN_Downloads

(Note: Downloads measured only by cran.rstudio.com, this excludes e.g. the official cran.r-project.org)

  • RStudio favicon Install using RStudio (recommended):

    • Click on Tools and then Install Packages...
    • Type in AMR and press Install
  • R favicon Install in R directly:

    • install.packages("AMR")

Install from Zenodo

DOI

This package was also published on Zenodo (stable releases only): https://doi.org/10.5281/zenodo.1305355

Install from GitLab

This is the latest development version. Although it may contain bugfixes and even new functions compared to the latest released version on CRAN, it is also subject to change and may be unstable or behave unexpectedly. Always consider this a beta version. All below 'badges' should be green:

Development Test Result Reference
All functions checked on Linux pipeline status GitLab CI [ref 1]
All functions checked on Windows AppVeyor_Build Appveyor Systems Inc. [ref 2]
Percentage of syntax lines checked Code_Coverage Codecov LLC [ref 3]

If so, try it with:

install.packages("devtools") 
devtools::install_gitlab("msberends/AMR")

This R package is licensed under the GNU General Public License (GPL) v2.0. In a nutshell, this means that this package:

  • May be used for commercial purposes

  • May be used for private purposes

  • May not be used for patent purposes

  • May be modified, although:

    • Modifications must be released under the same license when distributing the package
    • Changes made to the code must be documented
  • May be distributed, although:

    • Source code must be made available when the package is distributed
    • A copy of the license and copyright notice must be included with the package.
  • Comes with a LIMITATION of liability

  • Comes with NO warranty