R Development Page
Contributed R Packages
Below is a list of all packages provided by project zoo: Time Series Infrastructure.
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).
S3 Infrastructure for Regular and Irregular Time Series (Zs Ordered Observations)
|An S3 class with methods for totally ordered indexed observations. It is particularly aimed at irregular time series of numeric vectors/matrices and factors. zoos key design goals are independence of a particular index/date/time class and consistency with ts and base R by providing methods to extend standard generics.|
|Version: 1.7-13 | Last change: 2015-08-04 14:59:45+02 | Rev.: 1033|
|Download: (.tar.gz) | (.zip) | Build status: Failed to build | Stable Release: Get zoo 1.7-12 from CRAN|
R install command:
Supplementary Functionality for zoo Time Series
|Supplementary functionality that can be used with the zoo package for regular and irregular time series data. The package also serves as a development platform for ideas that might (or might not) eventually end up in the zoo package.|
|Version: 0.1-1 | Last change: 2010-05-05 14:27:19+02 | Rev.: 714|
|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.