R Development Page
Contributed R Packages
Below is a list of all packages provided by project Divorce.
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
| divoRce | Diagnosing Separation Phenomena in Categorical Response Models | |||||||||||
| Utilities for checking and diagnosing separation phenomena (complete separation, quasi-complete separation, overlap) for binary, nominal and ordinal data models with link construction as baseline-category, adjacent-category, cumulative, sequential (continuation-ratio), ordered stereotype and arbitrary link error distribution (including logit, probit, cauchit, cloglog, loglog, log, ...). The package functionality includes a check for overlap with a linear program, a quick check for overlap, detailed separation diagnostics such as identification of columns in the design matrix that leads to separation, identification of observations that lead to separation, the dimension of the recession cone and the structure vectors that are linearities. | ||||||||||||
| Version: 0.1-2 | Last change: 2026-01-28 14:21:46+01 | Rev.: 13 | ||||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Failed to build | ||||||||||||
R install command:
install.packages("divoRce", 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.
