R Development Page
Contributed R Packages
Below is a list of all packages provided by project MvBinary.
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
| MvBinary | Modelling Multivariate Binary Data with Blocks of Specific One-Factor Distribution | |||||||||
| Modelling Multivariate Binary Data with Blocks of Specific One-Factor Distribution. Variables are grouped into independent blocks. Each variable is described by two continuous parameters (its marginal probability and its dependency strength with the other block variables), and one binary parameter (positive or negative dependency). Model selection consists in the estimation of the repartition of the variables into blocks. It is carried out by the maximization of the BIC criterion by a deterministic (faster) algorithm or by a stochastic (more time consuming but optimal) algorithm. Tool functions facilitate the model interpretation. | ||||||||||
| Version: 1.1 | Last change: 2016-12-14 15:16:05+01 | Rev.: 31 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | Stable Release: Get MvBinary 1.1 from CRAN | ||||||||||
R install command:
install.packages("MvBinary", repos="http://R-Forge.R-project.org") | ||||||||||
|
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.
