HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
BayLum vs jstable
A side-by-side editorial comparison of BayLum and jstable — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
BayLum vs jstable: 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 jstable?
A clinical table generator paying down years of edge cases in survey-weighted models
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
BayLum vs jstable: 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.
jstable
0.0INFRA · APIS
A clinical table generator paying down years of edge cases in survey-weighted models
◆ Current state
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
◆ Where it's heading
Each CRAN release bundles several GitHub patch versions, so the notes read as rolled-up fix lists rather than feature announcements. The substantive thread is pcut.univariate, introduced across seven display functions in 1.3.11 to allow multivariable analysis restricted to significant variables, and repaired repeatedly since as it collided with interaction terms, single-variable selections, clustered models and data.table inputs. The survey-weighted path is the other recurring source: counts, labels and family handling that worked for unweighted data kept failing once weights were involved.
◆ Prediction
Expect further patches in the survey-weighted subgroup functions, since 1.3.25 fixed four separate issues there and each recent release has surfaced more in the same area.
Alternatives to BayLum and jstable
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 jstable.
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 jstable alternatives →
Recent activity from BayLum and jstable
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agojstableSurvey-weighted logistic regression and sample counts corrected
- 6mo agojstableCompeting-risk counts drawn from original rather than transformed data
- 9mo agojstableMulti-state Cox models detected without a manual flag
- 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
- 10mo agojstableWide fix pass across the display functions
- 0y agojstableCrude p-values computed from raw data via data_for_univariate
- 1y agojstableSignificance-filtered multivariable analysis added across seven functions
- 2y agoBayLumOne data-file function and a YAML config replace the folder layout ⚡
- 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 jstable?
Both compete on the same themes — r-package — within Infra & APIs. BayLum and jstable 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 jstable?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BayLum and jstable 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 jstable?
Top jstable alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "jstable alternatives" section above for the current picks, or visit /alternatives/jstable for the full list with editorial commentary on each.