R Development Page
Contributed R Packages
Below is a list of all packages provided by project RMI based REngine implementation.
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
| RemoteREngine | RMI based REngine implementation | |||||||||
| RMI based REngine implementation | ||||||||||
| Version: 0.0-8 | Last change: 2009-10-28 12:19:27+01 | Rev.: 213 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("RemoteREngine", repos="http://R-Forge.R-project.org") | ||||||||||
|
| RemoteREngine.examples | Examples of client code using the Remote R engine | |||||||||
| Examples of client code using the RemoteREngine package | ||||||||||
| Version: 0.0-0 | Last change: 2009-09-22 13:47:58+02 | Rev.: 178 | ||||||||||
|
Download:
(.tar.gz) |
(.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("RemoteREngine.examples", repos="http://R-Forge.R-project.org") | ||||||||||
|
| RemoteREngine.test | Unit test suite for the Remote R engine | |||||||||
| Test suite for the Remote R engine package | ||||||||||
| Version: 0.0-0 | Last change: 2009-09-28 19:33:01+02 | Rev.: 190 | ||||||||||
|
Download:
(.tar.gz) |
(.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("RemoteREngine.test", 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.
