← Back to home
Comparison · Infra & APIs

BayLum vs IsoriX

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

Shared themes:r-package

BayLum vs IsoriX: at a glance

FeatureBayLumIsoriX
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagsstable-isotopes, geolocation, r-package, spatial-modelling
Last editorial update31m ago1h ago
WebsiteVisit →Visit →

What is BayLum?

Bayesian luminescence dating that finally replaced its folder-structure input format.

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

Read the full BayLum trajectory →

What is IsoriX?

An isotope geolocation package still recovering from the r-spatial retirement

IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.

Read the full IsoriX trajectory →

BayLum vs IsoriX: editorial side-by-side

B
BayLum
INFRA · APIS
0.0

Bayesian luminescence dating that finally replaced its folder-structure input format.

◆ Current state

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

◆ Where it's heading

Two long-running threads have converged: making JAGS runs survivable (parallel methods, halved MCMC memory, injectable custom models) and making the inputs survivable (YAML config, consistency checks, auto-detected sample names). With the deprecated generators on their way out, the next phase is removal rather than addition. Release cadence is roughly annual and slowing.

◆ Prediction

The deprecated Generate_DataFile(), Generate_DataFile_MG() and LT_RegenDose() are the obvious next casualties; a release that drops them would be the first breaking change since the YAML rework.

I
IsoriX
INFRA · APIS
0.0

An isotope geolocation package still recovering from the r-spatial retirement

◆ Current state

IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.

◆ Where it's heading

Two years of the visible history have gone on infrastructure the science did not ask for. The 0.9.1 notes are unusually candid, warning users that the surrounding package landscape was still in flux and that incompatibility bugs were likely to keep surfacing, which 0.9.2 then confirmed. Only in 0.9.3 does domain work reappear: the bat fur isotope values in the calibration and assignment datasets were corrected to align with current keratin reference material normalisation, so results computed against the old datasets are not comparable with new ones.

◆ Prediction

With the spatial migration settled and the documentation rehomed, the next release is more likely to return to isoscape functionality than to infrastructure, though the entries do not name a specific feature.

Alternatives to BayLum and IsoriX

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 BayLum or IsoriX.

See all BayLum alternatives → · See all IsoriX alternatives →

Recent activity from BayLum and IsoriX

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

  1. 7mo agoIsoriXDocumentation rehomed after bookdown.org shutdown
  2. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  3. 1y agoIsoriXCalibration datasets corrected to current keratin reference standards
  4. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  5. 2y agoIsoriXSaving objects and masked plotting restored after the spatial migration
  6. 2y agoIsoriXv0.9.1.9999
  7. 2y agoIsoriXPackage recoded to drop the retiring spatial dependencies
  8. 3y agoBayLumMCMC memory halved; density plots for age distributions
  9. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  10. 4y agoBayLumCustom model injection and RNG control for parallel runs
  11. 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data
  12. 5y agoIsoriXCRAN release version 0.5

Frequently asked questions

What is the difference between BayLum and IsoriX?

Both compete on the same themes — r-package — within Infra & APIs. BayLum and IsoriX are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is BayLum better than IsoriX?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BayLum and IsoriX are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to BayLum?

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

What are the best alternatives to IsoriX?

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