artoo
artoo makes any-to-any clinical dataset conversion lossless by construction.
Comparison · Infra & APIs
glcdp vs inlabru
A side-by-side editorial comparison of glcdp and inlabru — release velocity, themes, recent moves, and the top alternatives to consider.
glcdp vs inlabru: at a glance
What is glcdp?
glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.
glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.
What is inlabru?
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
glcdp vs inlabru: editorial side-by-side
glcdp
6.3INFRA · APIS
glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.
◆ Current state
glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.
◆ Where it's heading
The package is serving two audiences from one model. Programmatic users get glc_collect(), extract_metadata() and add_metadata(), with imports that reject file groups whose factor labels or level order disagree. Interactive users get an Explorer that filters by device, wearing position, modality, role and data state, pages large inventories at 100 rows, and caches remote metadata for immutable revisions. Schemas 1.0.0 and 2.0.0 stay reachable as barebones legacy paths.
◆ Prediction
With 3.0.2 named the primary stable contract and the older schemas explicitly labelled legacy, retiring the barebones paths is the most likely next structural move. The notes give no indication of work beyond the current schema line.
inlabru
2.5INFRA · APIS
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
◆ Current state
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
◆ Where it's heading
The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.
◆ Prediction
The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.
Alternatives to glcdp and inlabru
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either glcdp or inlabru.
tabular
tabular went from clinical tables to complete TFL output in under two months.
usmapdata
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
prova
prova adds expected-utility calculation on top of its Bayesian inference core.
checkhelper
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
rstudio.prefs
Four years dormant, rstudio.prefs returns under a new maintainer.
See all glcdp alternatives → · See all inlabru alternatives →
Recent activity from glcdp and inlabru
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agoglcdpSchema 3.0.2 becomes the default import contract
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 29d agoglcdpglc_explore() adds a Shiny browser and metadata joins ⚡
- 1mo agoglcdpLogo and favicon refresh
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
Frequently asked questions
What is the difference between glcdp and inlabru?
They serve adjacent needs but don't currently overlap on shipped themes. glcdp is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is glcdp better than inlabru?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glcdp is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to glcdp?
Top glcdp alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "glcdp alternatives" section above for the current picks, or visit /alternatives/glcdp for the full list with editorial commentary on each.
What are the best alternatives to inlabru?
Top inlabru alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inlabru alternatives" section above for the current picks, or visit /alternatives/inlabru for the full list with editorial commentary on each.