tidyr
tidyr replaced separate() with a family that says what it does.
Comparison · Analytics
OpenMC vs silx
A side-by-side editorial comparison of OpenMC and silx — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMC vs silx: at a glance
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.
What is silx?
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
silx releases a couple of times a year and reached 3.0.0 in April 2026, which raised the Python floor to 3.10 and switched the default Qt binding to PySide6. The same release reworked the viewer's data views: 3D scatter support, dedicated RGB(A) image views, the composite ImageView split into Plot2dView and ComplexImageView, and NXdata stacks displayed as images. 3.1.0 has since added asinh axis scaling, the twilight colormaps, and dark-theme icons.
OpenMC vs silx: editorial side-by-side
OpenMC
2.5ANALYTICS
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.
silx
2.5ANALYTICS
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
◆ Current state
silx releases a couple of times a year and reached 3.0.0 in April 2026, which raised the Python floor to 3.10 and switched the default Qt binding to PySide6. The same release reworked the viewer's data views: 3D scatter support, dedicated RGB(A) image views, the composite ImageView split into Plot2dView and ComplexImageView, and NXdata stacks displayed as images. 3.1.0 has since added asinh axis scaling, the twilight colormaps, and dark-theme icons.
◆ Where it's heading
The project is doing a generational refresh of its GUI layer: modern Qt binding, modules broken out of the composite widgets that had accumulated responsibilities, and the theming work that a desktop application needs to look current. Underneath, the recurring fixes are about HDF5 behavior in real facility environments — file locking, NFS refresh, Windows display paths — which is where a synchrotron toolkit actually gets stressed. Feature growth is concentrated in silx view rather than the library API.
◆ Prediction
Expect the 3.1.x line to keep filling in plotting options and theming, with the PySide6 default flushing out binding-specific bugs from downstream applications over the next few releases.
Alternatives to OpenMC and silx
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 OpenMC or silx.
modeltime
modeltime built conformal intervals in, then went quiet on features.
performance
performance keeps adding ways to check a model you have already fitted.
cmdstanpy
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
dowhy
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse
OpenHouse is hardening the seams where table policies and jobs quietly fail.
Recent activity from OpenMC and silx
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agosilx3.1.0: asinh axis scaling, twilight colormaps, dark-theme icons
- 6d agoOpenMCSurface-flux tallies and PDG particle identifiers in OpenMC 0.16.0
- 3mo agosilx3.0.1: 2026/05/07
- 3mo agosilx3.0.0: PySide6 becomes the default Qt binding, Python 3.10 required ⚡
- 3mo agosilx3.0.0rc1: release candidate for the PySide6 migration
- 8mo agoOpenMCR2SManager automates shutdown dose rate calculations in OpenMC 0.15.3
- 1y agosilx2.2.2: 2025/04/07
- 1y agoOpenMCOpenMC 0.15.2 hotfixes an MPI regression
- 1y agoOpenMCRay-traced material volumes and Phong-shaded plots in OpenMC 0.15.1
- 1y agosilx2.2.0b0: HSDS URL support and a multi-curve comparison window
- 2y agoOpenMCOpenMC 0.15.0 introduces a random ray transport solver ⚡
- 2y agoOpenMCWeight window generation and continuous nuclide feed in OpenMC 0.14.0
Frequently asked questions
What is the difference between OpenMC and silx?
They serve adjacent needs but don't currently overlap on shipped themes. OpenMC and silx are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is OpenMC better than silx?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenMC and silx are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
What are the best alternatives to silx?
Top silx alternatives in Analytics are ranked by recent ship velocity. Browse the "silx alternatives" section above for the current picks, or visit /alternatives/silx for the full list with editorial commentary on each.