← Back to home
Comparison · Infra & APIs

Luminescence vs survivoR

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

Shared themes:r-package

Luminescence vs survivoR: at a glance

FeatureLuminescencesurvivoR
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesr-package, luminescence-dating, geochronology, dose-responsedata-package, r-package, television, reality-tv
Last editorial update2h ago33m 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 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.

Read the full survivoR trajectory →

Luminescence vs survivoR: 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.

S
survivoR
INFRA · APIS
0.0

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

See all Luminescence alternatives → · See all survivoR alternatives →

Recent activity from Luminescence and survivoR

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

  1. 26d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
  2. 2mo agosurvivoRUS50 and AU12 land, castaway scores split into three tiers
  3. 4mo agoLuminescenceFixes an uninitialised array and background overcounting
  4. 5mo agoLuminescenceImport functions now append detector type to record names
  5. 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
  6. 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
  7. 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers
  8. 7mo agosurvivoRUS49 data completed and season 50 cast added
  9. 11mo agosurvivoRSurvivor Australia vs. The World added
  10. 1y agosurvivoRboot_order table added and castaways deduplicated
  11. 2y agosurvivoRComplete AU09 data reaches CRAN
  12. 2y agosurvivoRChallenge tables rebuilt around a shared linking key

Frequently asked questions

What is the difference between Luminescence and survivoR?

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 survivoR?

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 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.