R Development Page

Contributed R Packages

Below is a list of all packages provided by project Event related potentials.

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).

Packages

erpR	Event-Related Potentials (ERP) Analysis, Graphics and Utility Functions
	Functions and utilities for the analysis of event-related potentials (ERPs). Event-related potentials are the measured brain responses associated with a specific sensory, cognitive, or motor event and are obtained from electroencephalographic (EEG) signal. The erpR package contains a series of functions for importing ERP data, computing traditional ERP measures, exploratory ERP analyses and plotting.
	Version: 0.4.1 | Last change: 2020-04-26 13:00:57+02 | Rev.: 118
	Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get erpR 0.2.0 from CRAN
	R install command: install.packages("erpR", repos="http://R-Forge.R-project.org")
	Logs:   Package build: Source package (Linux x86_64) Windows binary (x86_64/i386) Package check: Linux x86_64 (patched) | Linux x86_64 (devel) Windows (patched) | Windows (devel)

 

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.