R Development Page
Contributed R Packages
Below is a list of all packages provided by project Open Perimeter Interface (OPI).
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
| OPI | Open Perimetry Interface | |||||||||
| This package contains the current version of the Open Perimetry Interface (OPI), for simulating and controlling visual field machines using R. The OPI is a standard for interfacing with visual field testing machines (perimeters). It specifies basic functions that allow many visual field tests to be constructed. As of September 2013 it is fully implemented on the Octopus 900 and partially on the Heidelberg Edge Perimeter. Note to use these two machines you will need either the Rhep or OPIOctopus900 packages which require permission from the respective companies to obtain: see the OPI www site. It also has a cousin: the R package visualFields, which has tools for analysing and manipulating visual field data. | ||||||||||
| Version: 1.6 | Last change: 2013-09-23 07:50:34+02 | Rev.: 57 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | Stable Release: Get OPI 2.9 from CRAN | ||||||||||
R install command:
install.packages("OPI", repos="http://R-Forge.R-project.org") | ||||||||||
|
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.
