HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
bsvarSIGNs vs Luminescence
A side-by-side editorial comparison of bsvarSIGNs and Luminescence — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
bsvarSIGNs vs Luminescence: at a glance
What is bsvarSIGNs?
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
bsvarSIGNs estimates structural vector autoregressions identified by sign, zero and narrative restrictions, with the sampler in C++ and the objects, workflows and code structure deliberately matched to the bsvars package. Since the 1.0 launch in mid-2024 the releases have been consolidation: a fix pass, then a vignette, citation metadata and C++ changes to stay ahead of an upcoming compiler check.
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.
bsvarSIGNs vs Luminescence: editorial side-by-side
bsvarSIGNs
0.0INFRA · APIS
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
◆ Current state
bsvarSIGNs estimates structural vector autoregressions identified by sign, zero and narrative restrictions, with the sampler in C++ and the objects, workflows and code structure deliberately matched to the bsvars package. Since the 1.0 launch in mid-2024 the releases have been consolidation: a fix pass, then a vignette, citation metadata and C++ changes to stay ahead of an upcoming compiler check.
◆ Where it's heading
The package launched with a published roadmap and the stated intention of intensive development, then spent its next two releases on documentation and compliance rather than new identification schemes. The 2.0 version number is not matched by the changes described under it. What the feed shows is a methods package settling in after launch, not one expanding.
◆ Prediction
The roadmap referenced at launch is the only stated plan, and the entries since do not say which part of it is next.
Luminescence
2.5INFRA · APIS
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 bsvarSIGNs 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 bsvarSIGNs or Luminescence.
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.
finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all bsvarSIGNs alternatives → · See all Luminescence alternatives →
Recent activity from bsvarSIGNs and Luminescence
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
- 4mo agoLuminescenceFixes an uninitialised array and background overcounting
- 5mo agoLuminescenceImport functions now append detector type to record names
- 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
- 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
- 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers
- 1y agobsvarSIGNsFirst vignette, citation metadata, C++ check fixes
- 1y agobsvarSIGNsbsvarSIGNs 1.0.1
- 2y agobsvarSIGNsLaunch: sign, zero and narrative restrictions for bsvars ⚡
Frequently asked questions
What is the difference between bsvarSIGNs 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 bsvarSIGNs 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 bsvarSIGNs?
Top bsvarSIGNs alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bsvarSIGNs alternatives" section above for the current picks, or visit /alternatives/bsvarsigns 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.