← Back to home
Comparison · Infra & APIs

contagionchannels vs Luminescence

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

Shared themes:r-package

contagionchannels vs Luminescence: at a glance

FeaturecontagionchannelsLuminescence
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themeseconometrics, contagion-analysis, cran-submission, r-packager-package, luminescence-dating, geochronology, dose-response
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is contagionchannels?

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

Read the full contagionchannels trajectory →

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 →

contagionchannels vs Luminescence: editorial side-by-side

C
contagionchannels
INFRA · APIS
0.0

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

◆ Current state

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

◆ Where it's heading

There is no product trajectory to read here yet, only a submission one, and it is unusually well documented — each entry names the reviewer or check that prompted it and quotes the feedback verbatim. That transparency is the one signal available: the maintainer treats review rounds as releases worth publishing rather than squashing. Any judgement about direction will have to wait for a release that changes the package rather than its metadata.

◆ Prediction

With CRAN acceptance secured, the next release should be the first to carry actual methodological content; until one appears, there is not enough in these entries to say where the package is heading.

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.

Alternatives to contagionchannels and Luminescence

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

See all contagionchannels alternatives → · See all Luminescence alternatives →

Recent activity from contagionchannels and Luminescence

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

  1. 27d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
  2. 3mo agocontagionchannelsv0.1.3 — first CRAN release
  3. 3mo agocontagionchannelsv0.1.2: switch arXiv reference in DESCRIPTION to canonical DOI form
  4. 3mo agocontagionchannelsv0.1.1: address CRAN reviewer feedback (License) + add arXiv reference
  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

Frequently asked questions

What is the difference between contagionchannels and Luminescence?

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 contagionchannels better than Luminescence?

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

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

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.