R Development Page
Contributed R Packages
Below is a list of all packages provided by project audited.
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).
Automatic Tracing and Display of Changes to Row Count
|Classifies a data.frame such that row deletions and additions are tracked. A mechanism exists to give formal names to the row subsets that are coming or going. These names are used to populate a directed graph giving an account of all the transactions contributing to the state of the data.frame. The generic as.audited() has a method for keyed data.frames that creates an audited data.frame. Methods exist that track row count changes for the generics: Ops, !, ^, |, [, subset, head, tail, unique, cast, melt, aggregate, and merge. audit() extracts the transaction table from the audited object, while write.audit() and read.audit() control exchange with the file system. An audit method for as.igraph() creates a graph object that can be displayed with the corresponding plot method. Use options(audit= ) to provide an extra level of classification. Use options(artifact=TRUE) and as.xlsx() to save dropped records to file.|
|Version: 1.10 | Last change: 2015-01-07 15:31:58+01 | Rev.: 2|
|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.