tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of dowhy and OpenMC — release velocity, themes, recent moves, and the top alternatives to consider.
DoWhy adds one estimation method a year and keeps its identification edge.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
OpenMC's random ray solver has gone from new arrival to the centre of every release
OpenMC is a Monte Carlo particle transport code for neutronics and radiation analysis. Since the random ray transport solver landed in 0.15.0 it has received substantial work in every subsequent release, most recently local adjoint sources, temperature and distributed-density feedback, fission-heating tallies and a weight-window bootstrapping workflow. The other consistent thread is shutdown-dose and depletion tooling, where 0.15.3 introduced an R2SManager to automate the rigorous two-step workflow and 0.16.0 extended it with reactivity control, CRAM substeps and multiple meshes.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
Two threads run through the window. The identification side — DoWhy's differentiator against libraries that only estimate — keeps gaining criteria, from frontdoor with multiple variables through the Generalized Adjustment Criterion. The GCM side grows separately with missing-data handling, classifier selection logic and calibration work. The two halves are converging on a single API rather than staying separate entry points.
Given the pace of one estimator or criterion per release and the experimental flags still on missing-data support in GCM, the next release most likely promotes existing experimental features rather than opening a new estimation family.
OpenMC is a Monte Carlo particle transport code for neutronics and radiation analysis. Since the random ray transport solver landed in 0.15.0 it has received substantial work in every subsequent release, most recently local adjoint sources, temperature and distributed-density feedback, fission-heating tallies and a weight-window bootstrapping workflow. The other consistent thread is shutdown-dose and depletion tooling, where 0.15.3 introduced an R2SManager to automate the rigorous two-step workflow and 0.16.0 extended it with reactivity control, CRAM substeps and multiple meshes.
The project is layering a deterministic-adjacent solver alongside its Monte Carlo core rather than replacing it, and the ratio of random-ray work to core-solver work in each release keeps rising. In parallel it is packaging expert workflows into objects — R2SManager is the clearest case, turning a multi-stage shutdown dose calculation into a class rather than a recipe. The Python API is where most of that packaging surfaces, and it is also where the compatibility breaks land, with the minimum version moving to 3.12 in 0.16.0.
Given that every release since 0.15.0 has expanded the random ray solver's feedback and tally coverage, the next is likely to continue closing the gap between it and the main solver's feature set. The notes do not indicate whether it is intended to become a default path.
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 dowhy or OpenMC.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
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 dowhy alternatives → · See all OpenMC alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenMC 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. OpenMC 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 dowhy alternatives in Analytics are ranked by recent ship velocity. Browse the "dowhy alternatives" section above for the current picks, or visit /alternatives/dowhy for the full list with editorial commentary on each.
Top OpenMC alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenMC alternatives" section above for the current picks, or visit /alternatives/openmc for the full list with editorial commentary on each.