R Development Page
Contributed R Packages
Below is a list of all packages provided by project track: store obects on disk.
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
track | Store Objects on Disk Automatically | |||||||||
Automatically stores objects in files on disk so that files are rewritten when objects are changed, and so that objects are accessible but do not occupy memory until they are accessed. Keeps track of times when objects are created and modified, and caches some basic characteristics of objects to allow for fast summaries of objects. Also provides a command history mechanism that saves the last command to a history file after each command completes. | ||||||||||
Version: 1.1.11 | Last change: 2017-03-16 04:43:05+01 | Rev.: 268 | ||||||||||
Download:
![]() ![]() | ||||||||||
R install command:
install.packages("track", repos="http://R-Forge.R-project.org") | ||||||||||
|
track.ff | Use ff objects with track | |||||||||
Cleanly use ff objects with the track package. Geared towards working with permanent ff objects. | ||||||||||
Version: 1.0-2 | Last change: 2012-04-29 17:50:54+02 | Rev.: 205 | ||||||||||
Download:
![]() ![]() | ||||||||||
R install command:
install.packages("track.ff", 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.