tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of modeltime and PySCF — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime built conformal intervals in, then went quiet on features.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
Quantum chemistry package adding whole method families every release.
PySCF is a Python-based quantum chemistry toolkit, and its release cadence is unusually feature-dense: each version lands multiple new electronic-structure methods rather than polishing existing ones. Recent releases have built out the GW/BSE excited-state stack, k-point RPA for periodic systems, higher-order coupled cluster, and multi-state PDFT with analytical gradients. Platform work runs alongside — Windows DLL compatibility, GPU4PySCF interfacing, and configurable einsum backends.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
The arc runs from uncertainty quantification to execution. Conformal intervals arrived first and were then threaded through nested fitting, refitting and the printed forecast tables so users can see which confidence method produced an interval. The later work moves down a layer to how forecasts are computed — a portable future backend replacing foreach tuning — rather than what they express.
With only an xgboost compatibility fix since the 1.3.2 feature release, the entries do not support a confident prediction about what comes next beyond continued dependency maintenance.
PySCF is a Python-based quantum chemistry toolkit, and its release cadence is unusually feature-dense: each version lands multiple new electronic-structure methods rather than polishing existing ones. Recent releases have built out the GW/BSE excited-state stack, k-point RPA for periodic systems, higher-order coupled cluster, and multi-state PDFT with analytical gradients. Platform work runs alongside — Windows DLL compatibility, GPU4PySCF interfacing, and configurable einsum backends.
Two arcs are visible. The methods arc is pushing toward periodic (PBC) parity with molecular calculations — PBC GW, PBC RPA, SOC-ECP for PBC DFT, QM/MM for periodic systems all landed in this window. The infrastructure arc is about getting PySCF to run where it previously did not: Windows, GPUs, alternative tensor-contraction backends.
The PBC catch-up should continue, since each release closes another gap between molecular and periodic implementations of the same method; the entries do not indicate which gap is next.
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 modeltime or PySCF.
tidyr replaced separate() with a family that says what it does.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all modeltime alternatives → · See all PySCF alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. PySCF 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PySCF 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 Analytics products to evaluate alongside.
Top modeltime alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime alternatives" section above for the current picks, or visit /alternatives/modeltime for the full list with editorial commentary on each.
Top PySCF alternatives in Analytics are ranked by recent ship velocity. Browse the "PySCF alternatives" section above for the current picks, or visit /alternatives/pyscf for the full list with editorial commentary on each.