← Back to home
Comparison · Infra & APIs

Luminescence vs sps

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

Shared themes:r-package

Luminescence vs sps: at a glance

FeatureLuminescencesps
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themesr-package, luminescence-dating, geochronology, dose-responser-package, survey-sampling, sequential-poisson, performance
Last editorial update1h 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 sps?

sps keeps sanding down sequential Poisson sampling rather than adding to it.

The package implements sequential Poisson sampling for survey design, covering inclusion probabilities, proportional allocation, replicate weights, and take-all strata. Recent releases are small and tightly scoped: a divisor method helper, an iterator that draws a sample one unit at a time, automatic selection of the replicate-weight parameter, and repeated performance work on inclusion probability calculation.

Read the full sps trajectory →

Luminescence vs sps: 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
sps
INFRA · APIS
2.5

sps keeps sanding down sequential Poisson sampling rather than adding to it.

◆ Current state

The package implements sequential Poisson sampling for survey design, covering inclusion probabilities, proportional allocation, replicate weights, and take-all strata. Recent releases are small and tightly scoped: a divisor method helper, an iterator that draws a sample one unit at a time, automatic selection of the replicate-weight parameter, and repeated performance work on inclusion probability calculation.

◆ Where it's heading

Development is consolidation rather than expansion. Most releases either speed up an existing routine or remove a decision the user previously had to make by hand, such as picking the smallest parameter that keeps replicate weights non-negative. Documentation and tooling get comparable attention to the algorithms, with a dedicated vignette on inclusion probabilities and a recent switch of test and documentation infrastructure. The API surface has been essentially stable across the window.

◆ Prediction

Expect continued small ergonomic and performance releases against the existing function set rather than new sampling designs, which is the pattern every release in this window follows.

Alternatives to Luminescence and sps

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

See all Luminescence alternatives → · See all sps alternatives →

Recent activity from Luminescence and sps

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

  1. 26d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
  2. 1mo agospsDocumentation polish; switches to tinytest and litedown
  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. 9mo agospsFixes extra argument handling in sps_iterator()
  9. 11mo agospsAdds divisor_method() and a one-unit-at-a-time sampling iterator
  10. 1y agospsAdds an inclusion-probability vignette and faster partial sorting
  11. 1y agospsAutomatic tau selection for replicate weights
  12. 2y agospsAdds becomes_ta() for take-all stratum sample sizes

Frequently asked questions

What is the difference between Luminescence and sps?

Both compete on the same themes — r-package — within Infra & APIs. Luminescence and sps are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 Luminescence better than sps?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Luminescence and sps are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 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 sps?

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