Package: inlaops 0.1.2

Novica Nakov

inlaops: Deployment, Versioning and Scoring Tools for 'inlabru' Models

Serves Bayesian spatial and latent Gaussian models fit with 'inlabru' as versioned Representational State Transfer (REST) application programming interfaces (APIs). Includes a 'vetiver' bridge (versioning, REST API serving with posterior uncertainty, 'Docker' packaging) for 'bru' objects, a 'parsnip' model constructor scoped to fixed-effects models, and predictive scoring helpers (continuous ranked probability, log, squared-error and Dawid-Sebastiani scores) computed from inlabru::generate() posterior samples via 'scoringRules'.

Authors:Novica Nakov [aut, cre, cph]

inlaops_0.1.2.tar.gz
inlaops_0.1.2.zip(r-4.7-any)inlaops_0.1.2.zip(r-4.6-any)
inlaops_0.1.2.tar.gz(r-4.7-any)inlaops_0.1.2.tar.gz(r-4.6-any)
inlaops_0.1.2.tgz(r-4.6-emscripten)
manual.pdf |manual.html✨
DESCRIPTION |NEWS
card.svg |card.png
inlaops/json (API)

# Install 'inlaops' in R:
install.packages('inlaops', repos = c('https://cran.r-universe.dev', 'https://cloud.r-project.org'))

Bug tracker:https://github.com/novica/inlaops/issues

Pkgdown/docs site:https://novica.github.io

On CRAN:

Conda:

quarto

3.65 score 6 exports 33 dependencies

Last updated from:5605757416. Checks:6 OK. Indexed: yes.

TargetResultTimeFilesSyslog
linux-develOK168
source / vignettesOK307
linux-releaseOK188
windows-develOK155
windows-releaseOK205
wasm-releaseOK166

Exports:bru_cv_predictbru_inlaops_fitbru_pred_formulabru_predict_conf_intbru_regbru_score

Dependencies:classclassIntcliDBIdplyre1071fmeshergenericsglueinlabruKernSmoothlatticelifecyclemagrittrMatrixMatrixModelspillarpkgconfigproxyR6Rcpprlangs2sfspsplancstibbletidyselectunitsutf8vctrswithrwk

How inlaops maps to the vetiver workflow
Step by step | In short

Last update: 2026-11-03
Started: 2026-11-03

inlabru as a Bayesian GLM with parsnip
Scope | Setup | Example: Poisson regression for count data | Fit with bru_reg() | Inspect with broom | Predict | Comparing against a frequentist baseline | Cross-validation with bru_cv_predict() | Connecting to vetiver

Last update: 2026-11-03
Started: 2026-11-03

Model versioning and MLOps workflows
Setup | 1. Baseline model — version 1 | 2. New data, new version | 3. Compare versions before promoting | 4. Promote the better version | 5. Roll back | 6. Longitudinal quality tracking | 7. Serving the production model | 8. Real production boards | Posit Connect | S3 (or any object store) | Auth in serving code | A note on board hygiene | Versioning checklist

Last update: 2026-11-03
Started: 2026-11-03

Packaging an inlabru model API in a container
Why not vetiver_prepare_docker()? | 1. Write plumber.R | 2. Write the Dockerfile | 3. Build and test locally | 4. Spatial models | 5. Image size

Last update: 2026-11-03
Started: 2026-11-03

Proper scoring rules for Bayesian model comparison
Setup | The four scores | Example: comparing two models | Visualising score distributions | Relationship to WAIC and DIC | Scoring spatial and non-Gaussian models | Notes on n_samples

Last update: 2026-11-03
Started: 2026-11-03

Serving an inlabru model on Posit Connect
1. Install inlaops from GitHub | 2. Fit and pin the model | 3. Write plumber.R | 4. Publish | 5. Call the API | INLA on the server

Last update: 2026-11-03
Started: 2026-11-03

Serving LGCP intensity surfaces
Setup | 1. Fit the LGCP | 2. Serve via the vetiver bridge | 3. Fallback — custom plumber API | What you keep, what you give up

Last update: 2026-11-03
Started: 2026-11-03

Spatial models: scope and limitations
What works | vetiver bridge — supported with spatial metadata | LGCP intensity surfaces | Out-of-scope for the bridge (rejected at pin time) | Areal lookup — planned | broom tidiers — supported for the fixed part | What does NOT work | bru_reg() parsnip constructor | bru_cv_predict() cross-validation helper | Recommended workflow for spatial models | Request body contract | Docker image for spatial fits | Multi-likelihood models

Last update: 2026-11-03
Started: 2026-11-03

Versioning and serving inlabru models with vetiver
Prerequisites | 1. Fit a model | 2. Wrap with vetiver | Aside — parsnip-fitted models | 3. Pin to a versioned board | 4. Serve the API and call it | 5. Track model quality across versions | Pins board options | Multi-likelihood models

Last update: 2026-11-03
Started: 2026-11-03