R Development Page
Contributed R Packages
Below is a list of all packages provided by project pa4bayesmeta: Prior accuracy in NNHM.
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
| pa4bayesmeta | Prior Accuracy for Bayesian Meta-Analysis | |||||||||
| Functionality for sensitivity-based identification and classification of inaccurate heterogeneity priors in the Bayesian normal-normal hierarchical model (NNHM) used for Bayesian meta-analysis, as described in Ott, Hunanyan, Held and Roos (2021, "Sensitivity-based identification of inaccurate heterogeneity priors in Bayesian meta-analysis", submitted to Statistical Methods in Medical Research). Classifies inaccurate heterogeneity priors - i.e. heterogeneity priors which do not assign equal probability mass to both sides of the true between-study standard deviation - as either anticonservative (puts more than half of its probability mass on too small heterogeneity values) or conservative (puts more than half of its probability mass on too large heterogeneity values). Includes a function to compute the relative latent model complexity associated with a heterogeneity prior and a data set. The functions operate on data sets which are compatible with the bayesmeta package on CRAN. | ||||||||||
| Version: 0.1-4 | Last change: 2021-08-01 09:57:08+02 | Rev.: 3 | ||||||||||
Download:
 (.tar.gz) |
 (.zip) |
Build status: Current | ||||||||||
R install command:
install.packages("pa4bayesmeta", 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.
