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.

processcheckR: Rule-Based Conformance Checking of Business Process Event Data

Check compliance of event-data from (business) processes with respect to specified rules. Rules supported are of three types: frequency (activities that should (not) happen x number of times), order (succession between activities) and exclusiveness (and and exclusive choice between activities).

Version: 0.1.4
Depends: R (≥ 3.5.0)
Imports: dplyr, bupaR (≥ 0.5.1), rlang, edeaR (≥ 0.9.0), stringr, stringi, glue, lifecycle, tidyr
Suggests: knitr, rmarkdown, eventdataR, covr, compare, testthat (≥ 3.0.0)
Published: 2022-10-03
DOI: 10.32614/CRAN.package.processcheckR
Author: Gert Janssenswillen [aut, cre], Gerard van Hulzen [ctb]
Maintainer: Gert Janssenswillen <gert.janssenswillen at uhasselt.be>
BugReports: https://github.com/bupaverse/processcheckr/issues
License: MIT + file LICENSE
URL: https://bupar.net/, https://github.com/bupaverse/processcheckr, https://bupaverse.github.io/processcheckR/
NeedsCompilation: no
Materials: README NEWS
CRAN checks: processcheckR results

Documentation:

Reference manual: processcheckR.pdf
Vignettes: Rule-Based Conformance Checking

Downloads:

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

Reverse dependencies:

Reverse imports: bupaverse

Linking:

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