← Back to home
Comparison · Analytics

dowhy vs OpenMC

A side-by-side editorial comparison of dowhy and OpenMC — release velocity, themes, recent moves, and the top alternatives to consider.

dowhy vs OpenMC: at a glance

FeaturedowhyOpenMC
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themescausal-inference, effect-estimation, identification, gcmmonte-carlo-transport, random-ray, depletion, neutronics
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is dowhy?

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.

Read the full dowhy trajectory →

What is OpenMC?

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.

Read the full OpenMC trajectory →

dowhy vs OpenMC: editorial side-by-side

D
dowhy
ANALYTICS
0.0

DoWhy adds one estimation method a year and keeps its identification edge.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

O
OpenMC
ANALYTICS
2.5

OpenMC's random ray solver has gone from new arrival to the centre of every release

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to dowhy and OpenMC

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.

See all dowhy alternatives → · See all OpenMC alternatives →

Recent activity from dowhy and OpenMC

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 6d agoOpenMCSurface-flux tallies and PDG particle identifiers in OpenMC 0.16.0
  2. 8mo agoOpenMCR2SManager automates shutdown dose rate calculations in OpenMC 0.15.3
  3. 9mo agodowhyv0.14: Python 3.13 support and a new doubly robust estimator
  4. 1y agodowhyv0.13: Generalized Adjustment Criterion for effect estimation and missing data support in GCM
  5. 1y agoOpenMCOpenMC 0.15.2 hotfixes an MPI regression
  6. 1y agoOpenMCRay-traced material volumes and Phong-shaded plots in OpenMC 0.15.1
  7. 1y agodowhyv0.12: Python 3.12 compatibility, [experimental] support for time-series data, and extensions to new scenarios
  8. 2y agoOpenMCOpenMC 0.15.0 introduces a random ray transport solver
  9. 2y agodowhyv0.11.1: Bug fixes and improvements
  10. 2y agodowhyv0.11: New GCM features and improved compatibility of GCM with CausalModel API
  11. 2y agoOpenMCWeight window generation and continuous nuclide feed in OpenMC 0.14.0
  12. 2y agodowhyv0.10.1: Minor fixes to main 0.10 release

Frequently asked questions

What is the difference between dowhy and OpenMC?

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.

Is dowhy better than OpenMC?

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.

What are the best alternatives to dowhy?

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.

What are the best alternatives to OpenMC?

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.