HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
BayLum vs survivoR
A side-by-side editorial comparison of BayLum and survivoR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
BayLum vs survivoR: at a glance
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.
What is survivoR?
A Survivor data package that keeps turning a TV show into a relational database
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
BayLum vs survivoR: editorial side-by-side
BayLum
0.0INFRA · APIS
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.
survivoR
0.0INFRA · APIS
A Survivor data package that keeps turning a TV show into a relational database
◆ Current state
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
◆ Where it's heading
The work is less about adding seasons than about making the tables join cleanly. 2.3.1 rebuilt challenge_description and challenge_results around a shared challenge_id, added challenge characteristic flags and result notes, and put logical finalist, winner and jury flags on castaways. Since then the pattern repeats at smaller scale: boot_order as its own table, season_name deprecated everywhere except season_summary, castaways cleaned so people booted twice appear once. Derived analytical columns are being separated from raw records rather than mixed into them.
◆ Prediction
Expect the next release to add the current season's data on the same broadcast-following cadence, with any structural work continuing to split derived scores out of the raw tables.
Alternatives to BayLum and survivoR
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 survivoR.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
See all BayLum alternatives → · See all survivoR alternatives →
Recent activity from BayLum and survivoR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurvivoRUS50 and AU12 land, castaway scores split into three tiers
- 7mo agosurvivoRUS49 data completed and season 50 cast added
- 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
- 11mo agosurvivoRSurvivor Australia vs. The World added
- 1y agosurvivoRboot_order table added and castaways deduplicated
- 2y agoBayLumOne data-file function and a YAML config replace the folder layout ⚡
- 2y agosurvivoRComplete AU09 data reaches CRAN
- 2y agosurvivoRChallenge tables rebuilt around a shared linking key
- 3y agoBayLumMCMC memory halved; density plots for age distributions
- 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
- 4y agoBayLumCustom model injection and RNG control for parallel runs
- 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data
Frequently asked questions
What is the difference between BayLum and survivoR?
Both compete on the same themes — r-package — within Infra & APIs. BayLum and survivoR 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 survivoR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BayLum and survivoR 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 survivoR?
Top survivoR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "survivoR alternatives" section above for the current picks, or visit /alternatives/survivor for the full list with editorial commentary on each.