vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
DMRnet vs inlabru
A side-by-side editorial comparison of DMRnet and inlabru — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
DMRnet vs inlabru: at a glance
What is DMRnet?
A categorical-variable selection package that publishes its full test logs as release candidates.
DMRnet implements delete-or-merge-regressors model selection for high-dimensional categorical data, alongside SOSnet and GLAMER variants from the same research group. Development is slow and academic — 0.4.0 in 2023, then two years to 0.4.1 in August 2025, which corrects an invalid lambda.1se computation and the cross-validation plots that displayed it. Every real release is preceded days earlier by a release-candidate entry containing the raw output of the correctness and consistency test suite.
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.
DMRnet vs inlabru: editorial side-by-side
DMRnet
0.0INFRA · APIS
A categorical-variable selection package that publishes its full test logs as release candidates.
◆ Current state
DMRnet implements delete-or-merge-regressors model selection for high-dimensional categorical data, alongside SOSnet and GLAMER variants from the same research group. Development is slow and academic — 0.4.0 in 2023, then two years to 0.4.1 in August 2025, which corrects an invalid lambda.1se computation and the cross-validation plots that displayed it. Every real release is preceded days earlier by a release-candidate entry containing the raw output of the correctness and consistency test suite.
◆ Where it's heading
The package is converging on correctness rather than expanding. 0.3.3 was a wall of fixes to inference, log-likelihood, and degenerate cross-validation cases; 0.4.0 added the var_sel algorithm and brought GLAMER into the package's own net idiom over its tau parameter; 0.4.1 is again a statistical correctness fix. The published test-log releases are the tell — this maintainer treats reproducible evidence that hard cases still pass as part of the release artifact, which is unusual outside academic statistical software.
◆ Prediction
Given the two-year gap before 0.4.1 and its narrow scope, the next release is most likely another correctness fix arriving on a multi-year cadence, again preceded by a full test-log release candidate.
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 DMRnet 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 DMRnet or inlabru.
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 DMRnet alternatives → · See all inlabru alternatives →
Recent activity from DMRnet and inlabru
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 agoDMRnetInvalid lambda.1se computation corrected in cross-validation
- 1y agoDMRnetTest-suite log published ahead of the 0.4.1 release
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 3y agoDMRnetvar_sel added; GLAMER reworked as a net over tau
- 3y agoDMRnetTest-suite log published ahead of the 0.4.0 release
- 3y agoDMRnetInference, log-likelihood, and degenerate-CV fixes across all model families
- 3y agoDMRnetTest-suite log published ahead of the 0.3.3 release
Frequently asked questions
What is the difference between DMRnet and inlabru?
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 DMRnet better than inlabru?
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 DMRnet?
Top DMRnet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DMRnet alternatives" section above for the current picks, or visit /alternatives/dmrnet 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.