← Back to home
Comparison · Infra & APIs

Luminescence vs rgm

A side-by-side editorial comparison of Luminescence and rgm — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

Luminescence vs rgm: at a glance

FeatureLuminescencergm
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesr-package, luminescence-dating, geochronology, dose-responsemicrobiome, graphical-models, bayesian-inference, cran-maintenance
Last editorial update1d ago1h ago
WebsiteVisit →Visit →

What is Luminescence?

Luminescence is revisiting the statistical assumptions baked into its dose-response fits.

The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.

Read the full Luminescence trajectory →

What is rgm?

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

Read the full rgm trajectory →

Luminescence vs rgm: editorial side-by-side

L
Luminescence
INFRA · APIS
2.5

Luminescence is revisiting the statistical assumptions baked into its dose-response fits.

◆ Current state

The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.

◆ Where it's heading

Two kinds of change dominate. The first is deliberate breaking changes made for correctness or consistency: the weighting rework, and import functions now uniformly appending the detector to record types so all formats behave as one always did. The second is a steady stream of new analysis functions contributed by the wider research community, covering crosstalk correction, spatial autocorrelation on grain discs, and incomplete bleaching models. Deprecated functions are being removed on a clear schedule rather than left indefinitely.

◆ Prediction

Expect further consolidation of defaults that were inherited rather than chosen, since the weighting change is framed as correcting earlier reasoning rather than adding an option.

R
rgm
INFRA · APIS
0.0

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

◆ Current state

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

◆ Where it's heading

Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.

◆ Prediction

The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.

Alternatives to Luminescence and rgm

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 Luminescence or rgm.

See all Luminescence alternatives → · See all rgm alternatives →

Recent activity from Luminescence and rgm

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 27d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
  2. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  3. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  4. 3mo agorgmUnreleased twin of the CRAN recovery release
  5. 4mo agoLuminescenceFixes an uninitialised array and background overcounting
  6. 5mo agoLuminescenceImport functions now append detector type to record names
  7. 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
  8. 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
  9. 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers
  10. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between Luminescence and rgm?

Both compete on the same themes — r-package — within Infra & APIs. Luminescence 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 Luminescence better than rgm?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Luminescence 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 Luminescence?

Top Luminescence alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Luminescence alternatives" section above for the current picks, or visit /alternatives/luminescence for the full list with editorial commentary on each.

What are the best alternatives to rgm?

Top rgm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rgm alternatives" section above for the current picks, or visit /alternatives/rgm for the full list with editorial commentary on each.