R Development Page
Contributed R Packages
Below is a list of all packages provided by project strucchange: Structural Change Methods.
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).
Testing, Monitoring, and Dating Structural Changes
|Testing, monitoring and dating structural changes in (linear) regression models. strucchange features tests/methods from the generalized fluctuation test framework as well as from the F test (Chow test) framework. This includes methods to fit, plot and test fluctuation processes (e.g., CUSUM, MOSUM, recursive/moving estimates) and F statistics, respectively. It is possible to monitor incoming data online using fluctuation processes. Finally, the breakpoints in regression models with structural changes can be estimated together with confidence intervals. Emphasis is always given to methods for visualizing the data.|
|Version: 1.5-2 | Last change: 2018-01-30 23:50:49+01 | Rev.: 331|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get strucchange 1.5-1 from CRAN|
R install command:
C++ Speedup Functions for srucchange Using the Armadillo Library
|C++ speedup functions for srucchange using the Armadillo library.|
|Version: 1.5-1 | Last change: 2017-04-13 10:31:55+02 | Rev.: 329|
|Download: (.tar.gz) | (.zip) | Build status: Failed to build|
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.