The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Provides fast and scalable Gibbs sampling algorithms for Bayesian Lasso regression model in high-dimensional settings. The package implements efficient partially collapsed and nested Gibbs samplers for Bayesian Lasso, with a focus on computational efficiency when the number of predictors is large relative to the sample size. Methods are described at Davoudabadi and Ormerod (2026) <https://github.com/MJDavoudabadi/LassoHiDFastGibbs>.
| Version: | 0.1.4 |
| Imports: | Rcpp |
| LinkingTo: | Rcpp, RcppArmadillo, RcppEigen, RcppNumerical, RcppClock |
| Suggests: | posterior |
| Published: | 2026-01-29 |
| DOI: | 10.32614/CRAN.package.LassoHiDFastGibbs |
| Author: | John Ormerod |
| Maintainer: | Mohammad Javad Davoudabadi <mohammad.davoudabadi at qut.edu.au> |
| BugReports: | https://github.com/MJDavoudabadi/LassoHiDFastGibbs/issues |
| License: | GPL-3 |
| Copyright: | see file COPYRIGHTS |
| URL: | https://github.com/MJDavoudabadi/LassoHiDFastGibbs |
| NeedsCompilation: | yes |
| SystemRequirements: | C++17 |
| Citation: | LassoHiDFastGibbs citation info |
| Materials: | README, NEWS |
| CRAN checks: | LassoHiDFastGibbs results |
| Reference manual: | LassoHiDFastGibbs.html , LassoHiDFastGibbs.pdf |
| Package source: | LassoHiDFastGibbs_0.1.4.tar.gz |
| Windows binaries: | r-devel: LassoHiDFastGibbs_0.1.4.zip, r-release: LassoHiDFastGibbs_0.1.4.zip, r-oldrel: LassoHiDFastGibbs_0.1.4.zip |
| macOS binaries: | r-release (arm64): LassoHiDFastGibbs_0.1.4.tgz, r-oldrel (arm64): LassoHiDFastGibbs_0.1.4.tgz, r-release (x86_64): LassoHiDFastGibbs_0.1.4.tgz, r-oldrel (x86_64): LassoHiDFastGibbs_0.1.4.tgz |
Please use the canonical form https://CRAN.R-project.org/package=LassoHiDFastGibbs to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.