silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of epiparameter and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
epiparameter split its parameter library out of the package — and relicensed what remained.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
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.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
Each release has clarified the boundary between the data and the tools that operate on it. 0.2.0 added coercion from {epireview} tables, 0.3.0 rewrote the classes and renamed much of the API, and 0.4.0 completed the separation while adding caching so loading the library stays cheap. Breaking changes have been frequent and deliberate rather than incidental.
With code and data separated, the two can version independently — expect parameter additions to appear in {epiparameterDB} releases while this package's changes stay focused on classes and methods.
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.
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.
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.
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 epiparameter or TimescaleDB.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all epiparameter alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top epiparameter alternatives in Analytics are ranked by recent ship velocity. Browse the "epiparameter alternatives" section above for the current picks, or visit /alternatives/epiparameter for the full list with editorial commentary on each.
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.