tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of OpenMC and Simple Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Privacy analytics tightening its API and moving IP blocking off the CDN
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
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.
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
The work is about removing borrowed constraints. IP blocking inherited the CDN's limits and blast radius; moving it in-house made it per-site and custom-domain compatible. API v6 does the same for time handling — hourly data separates day and hour, weeks and months carry explicit start dates — while keeping v5 stable so nobody is forced to migrate. Both are the moves of a product whose users integrate it and stay.
With v6 shipped alongside an unchanged v5, expect a deprecation timeline for v5 to be the next API announcement, though the entries do not name one.
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 Simple Analytics.
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.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
See all OpenMC alternatives → · See all Simple Analytics 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 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.
Top Simple Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Simple Analytics alternatives" section above for the current picks, or visit /alternatives/simple-analytics for the full list with editorial commentary on each.