R Development Page
Contributed R Packages
Below is a list of all packages provided by project Benchmark Experiment Framework.
Important note for package binaries: R-Forge provides these binaries only for the most recent version of R, but not for older versions. In order to successfully install the packages provided on R-Forge, you have to switch to the most recent version of R or, alternatively, install from the package sources (.tar.gz).
Benchmark Experiments Toolbox
|The benchmark package provides a toolbox for setup, execution and analysis of benchmark experiments. Main focus is the analysis of data accumulating during the execution -- one primary objective is the statistical correct computation of the candidate algorithms order.|
|Version: 0.3-6 | Last change: 2014-05-02 21:33:25+02 | Rev.: 88|
|Download: (.tar.gz) | (.zip) | Build status: Failed to build | Stable Release: Get benchmark 0.3-6 from CRAN|
R install command:
Supplementary package "(Psycho-)Analysis of Benchmark Experiments"
|Supplementary package for the article "(Psycho-)Analysis of Benchmark Experiments: A Formal Framework for Investigating the Relationship between Data Sets and Learning Algorithms" by Eugster, Leisch, and Strobl (see citation("psychobench").|
|Version: 0.1 | Last change: 2012-03-15 15:33:35+01 | Rev.: 79|
|Download: (.tar.gz) | (.zip) | Build status: Current|
R install command:
Build status codes
0 - Current: the package is available for download. The corresponding package passed checks on the Linux and Windows platform without ERRORs.
1 - Scheduled for build: the package has been recognized by the build system and provided in the staging area.
2 - Building: the package has been sent to the build machines. It will be built and checked using the latest patched version of R. Note that it is included in a batch of several packages. Thus, this process will take some time to finish.
3 - Failed to build: the package failed to build or did not pass the checks on the Linux and/or Windows platform. It is not made available since it does not meet the policies.
4 - Conflicts: two or more packages of the same name exist. None of them will be built. Maintainers are asked to negotiate further actions.
5 - Offline: the package is not available. The build system may be offline or the package maintainer did not trigger a rebuild (done e.g., via committing to the package repository).
If your package is not shown on this page or not building, then check the build system status report.