R Development Page
Contributed R Packages
Below is a list of all packages provided by project si4bayesmeta:Sensitivity-Identification.
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
| si4bayesmeta | Sensitivity and Identification for the Bayesian Meta-Analysis | |||||||||
| Sensitivity and identification estimates for all the parameters in the Bayesian normal-normal hierarchical model (NNHM) induced by a Half-Normal (HN) and a Half-Cauchy (HC) heterogeneity priors are produced by two d2BC_S_I_HN_raw and d2BC_S_I_HC_raw functions. Six scenarios are considered: target relative latent model complexity (RLMC) values fixed at 0.25, 0.5 and 0.75 with RLMC-adjusted HN and HC heterogeneity priors. Corresponding posterior estimates can be obtained by the functions raw_estimates_HN and raw_estimates_HC. The methodology implemented in this package has been developed in Roos et al. (2020). | ||||||||||
| Version: 0.1-1 | Last change: 2020-11-27 10:22:54+01 | Rev.: 22 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("si4bayesmeta", 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.
