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.

offsetreg: An Extension of 'Tidymodels' Supporting Offset Terms

Extend the 'tidymodels' ecosystem <https://www.tidymodels.org/> to enable the creation of predictive models with offset terms. Models with offsets are most useful when working with count data or when fitting an adjustment model on top of an existing model with a prior expectation. The former situation is common in insurance where data is often weighted by exposures. The latter is common in life insurance where industry mortality tables are often used as a starting point for setting assumptions.

Version: 1.1.0
Depends: R (≥ 4.1)
Imports: generics, glue, parsnip (≥ 1.2.0), poissonreg, rlang, stats
Suggests: broom, glmnet, knitr, recipes, rmarkdown, rpart, testthat (≥ 3.0.0), tune, workflows, rsample, xgboost
Published: 2024-04-11
DOI: 10.32614/CRAN.package.offsetreg
Author: Matt Heaphy [aut, cre, cph]
Maintainer: Matt Heaphy <mattrmattrs at gmail.com>
BugReports: https://github.com/mattheaphy/offsetreg/issues
License: MIT + file LICENSE
URL: https://github.com/mattheaphy/offsetreg/, https://mattheaphy.github.io/offsetreg/
NeedsCompilation: no
Materials: README NEWS
CRAN checks: offsetreg results

Documentation:

Reference manual: offsetreg.pdf
Vignettes: When to use offsetreg

Downloads:

Package source: offsetreg_1.1.0.tar.gz
Windows binaries: r-devel: offsetreg_1.1.0.zip, r-release: offsetreg_1.1.0.zip, r-oldrel: offsetreg_1.1.0.zip
macOS binaries: r-release (arm64): offsetreg_1.1.0.tgz, r-oldrel (arm64): offsetreg_1.1.0.tgz, r-release (x86_64): offsetreg_1.1.0.tgz, r-oldrel (x86_64): offsetreg_1.1.0.tgz
Old sources: offsetreg archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=offsetreg 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.