R Development Page
Contributed R Packages
Below is a list of all packages provided by project Thresher.
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).
Finding the Number of Significant Principal Components
Implements methods to automate the Auer-Gervini graphical
Bayesian approach for determining the number of significant
principal components. Automation uses clustering, change points, or
simple statistical models to distinguish "long" from "short" steps
in a graph showing the posterior number of components as a function
of a prior parameter. See |
|Version: 1.1.9 | Last change: 2018-05-18 03:26:58+02 | Rev.: 72|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get PCDimension 1.1.9 from CRAN|
R install command:
Threshing and Reaping for Principal Components
Defines the classes used to identify
outliers (threshing) and compute the number of significant principal
components and number of clusters (reaping) in a joint application
of PCA and hierarchical clustering. See Wang et al., 2018,
|Version: 1.0.2 | Last change: 2018-10-17 15:49:10+02 | Rev.: 76|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get Thresher 1.0.2 from CRAN|
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.