Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of SimInf and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
SimInf simulates stochastic disease spread over networks of nodes, with a model parser that compiles user-specified transitions to C. Version 10.0.0 was a deliberate major break: the SimInf_pfilter S4 class and the bootstrap filtering interface were redesigned, a replicates slot was added to SimInf_model, a multi-particle variant of the split-step solver arrived, and the package gained Particle Markov Chain Monte Carlo fitting against observed time series. The follow-up 10.1.0 is a single zero-length memcpy fix found by CRAN's M1 checks.
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.
SimInf simulates stochastic disease spread over networks of nodes, with a model parser that compiles user-specified transitions to C. Version 10.0.0 was a deliberate major break: the SimInf_pfilter S4 class and the bootstrap filtering interface were redesigned, a replicates slot was added to SimInf_model, a multi-particle variant of the split-step solver arrived, and the package gained Particle Markov Chain Monte Carlo fitting against observed time series. The follow-up 10.1.0 is a single zero-length memcpy fix found by CRAN's M1 checks.
The package has been moving from simulation toward inference for several releases. The 9.x line built the input side — utilities for cleaning raw individual event data, variables and enumeration constants in the model parser — and 10.0.0 closed the loop by making the simulator fittable to data through PMCMC. The version number was incremented precisely because that required breaking the particle filter interface.
Fitting machinery this new usually needs a second pass on usability, so the next releases most likely focus on diagnostics and documentation around PMCMC rather than on the simulation core, which has been stable across the whole 9.x and 10.x history.
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 SimInf or TimescaleDB.
Omni ships weekly, and almost every week the headline item is an AI feature.
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.
See all SimInf 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 SimInf alternatives in Analytics are ranked by recent ship velocity. Browse the "SimInf alternatives" section above for the current picks, or visit /alternatives/siminf-r 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.