silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
OneSampleMR vs TimescaleDB
A side-by-side editorial comparison of OneSampleMR and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
OneSampleMR vs TimescaleDB: at a glance
What is OneSampleMR?
OneSampleMR found that argument order in a formula was silently changing its estimates
OneSampleMR implements one-sample Mendelian randomization estimators — two-stage predictor substitution, two-stage residual inclusion, and Sanderson-Windmeijer conditional F statistics for instrument strength. The package spent its first years on packaging and dependency upkeep. The 2026 releases turn to substance: broader support for models fitted elsewhere, then a correctness fix for a defect that depended on nothing more than where covariates appeared in a formula.
What is TimescaleDB?
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
OneSampleMR vs TimescaleDB: editorial side-by-side
OneSampleMR
0.0ANALYTICS
OneSampleMR found that argument order in a formula was silently changing its estimates
◆ Current state
OneSampleMR implements one-sample Mendelian randomization estimators — two-stage predictor substitution, two-stage residual inclusion, and Sanderson-Windmeijer conditional F statistics for instrument strength. The package spent its first years on packaging and dependency upkeep. The 2026 releases turn to substance: broader support for models fitted elsewhere, then a correctness fix for a defect that depended on nothing more than where covariates appeared in a formula.
◆ Where it's heading
Two threads. The first is reach — fsw() now reads models fitted by AER::ivreg(), estimatr::iv_robust() and fixest::feols() in addition to ivreg::ivreg(), which makes conditional F statistics available without refitting in the package's own idiom. The second is hardening: clear errors when more than one exposure is given or when a variable collides with the reserved name y, and print methods that no longer fail on user-specified t0 with log or logit links. Both come largely from user reports rather than a plan.
◆ Prediction
The estimator-support work has been adding one IV-fitting package at a time on outside contributions, so further backends are the likeliest next content — the package's own estimators have been stable since first release.
TimescaleDB
5.0ANALYTICS
TimescaleDB is paying down correctness debt in its columnstore query paths.
◆ Current state
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
◆ Where it's heading
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
◆ Prediction
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
Alternatives to OneSampleMR and TimescaleDB
Other Analytics 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 OneSampleMR or TimescaleDB.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
See all OneSampleMR alternatives → · See all TimescaleDB alternatives →
Recent activity from OneSampleMR and TimescaleDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoOneSampleMROneSampleMR fixes estimates broken by covariate order in the formula
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 5mo agoOneSampleMROneSampleMR computes conditional F for three more IV packages
- 1y agoOneSampleMROneSampleMR 0.1.6
- 2y agoOneSampleMROneSampleMR 0.1.5
- 2y agoOneSampleMROneSampleMR 0.1.4
- 3y agoOneSampleMROneSampleMR 0.1.3
Frequently asked questions
What is the difference between OneSampleMR and TimescaleDB?
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 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 OneSampleMR better than TimescaleDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 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 Analytics products to evaluate alongside.
What are the best alternatives to OneSampleMR?
Top OneSampleMR alternatives in Analytics are ranked by recent ship velocity. Browse the "OneSampleMR alternatives" section above for the current picks, or visit /alternatives/onesamplemr for the full list with editorial commentary on each.
What are the best alternatives to TimescaleDB?
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.