vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
inlabru vs OpenRepGrid
A side-by-side editorial comparison of inlabru and OpenRepGrid — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
inlabru vs OpenRepGrid: at a glance
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.
What is OpenRepGrid?
Repertory grids learn which pole is the preferred one — a data-model change, not another plot option.
OpenRepGrid is the R toolkit for repertory grid analysis, the personal-construct-psychology technique of rating elements against bipolar constructs. Releases arrive every few months and the package passed JOSS review in late 2024. The current release, 0.1.18, is the largest in the window: a rebuilt import/export layer and the introduction of construct pole preference into the grid object itself.
inlabru vs OpenRepGrid: editorial side-by-side
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.
OpenRepGrid
0.0INFRA · APIS
Repertory grids learn which pole is the preferred one — a data-model change, not another plot option.
◆ Current state
OpenRepGrid is the R toolkit for repertory grid analysis, the personal-construct-psychology technique of rating elements against bipolar constructs. Releases arrive every few months and the package passed JOSS review in late 2024. The current release, 0.1.18, is the largest in the window: a rebuilt import/export layer and the introduction of construct pole preference into the grid object itself.
◆ Where it's heading
The arc moves from presentation outward to the data model. 0.1.15 and 0.1.17 were about plots, colours, clustering options, and base-R ergonomics — subsetting by element name, cbind, names(). 0.1.18 changes what a grid can hold rather than how it is drawn, and threads that new attribute through import, construction, and analysis in one release. Getting data in and out is clearly the other priority: three dataframe layouts, long and wide Excel, multi-sheet import, workbook export.
◆ Prediction
With preferred poles now representable, the next likely step is analysis built on top of them — ideal-element distance and alignment measures — plus continued expansion of the import formats the package accepts.
Alternatives to inlabru and OpenRepGrid
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 inlabru or OpenRepGrid.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
ordinalsimr
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
transltr
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
hereR
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all inlabru alternatives → · See all OpenRepGrid alternatives →
Recent activity from inlabru and OpenRepGrid
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 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 agoOpenRepGridPreferred construct poles enter the grid data model ⚡
- 1y agoOpenRepGridGrids gain name-based subsetting, cbind, and per-pole plot colours
- 1y agoOpenRepGridDocumentation revised for JOSS review
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 2y agoOpenRepGridDependency-grid dispersion indexes added; rgl becomes optional
Frequently asked questions
What is the difference between inlabru and OpenRepGrid?
Both compete on the same themes — r-package — within Infra & APIs. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 inlabru better than OpenRepGrid?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 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.
What are the best alternatives to OpenRepGrid?
Top OpenRepGrid alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenRepGrid alternatives" section above for the current picks, or visit /alternatives/openrepgrid for the full list with editorial commentary on each.