R Development Page

Contributed R Packages

Below is a list of all packages provided by project spinyReg: a sparse generative model.

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

spinyReg	Sparse Generative Model and Its EM Algorithm
	Implements a generative model for Bayesian variable selection in high-dimensional linear regression. It uses a spike-and-slab like prior distribution obtained by multiplying a deterministic binary vector with with a random Gaussian parameter vector. Such a model allows the use of an EM algorithm, optimizing a type-II log-likelihood, for inference.
	Version: 0.1-0 | Last change: 2015-09-08 14:58:32+02 | Rev.: 12
	Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get spinyReg 0.1-0 from CRAN
	R install command: install.packages("spinyReg", repos="http://R-Forge.R-project.org")
	Logs:   Package build: Source package (Linux x86_64) Windows binary (x86_64/i386) Package check: Linux x86_64 (patched) | Linux x86_64 (devel) Windows (patched) | Windows (devel)

 

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.