mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of campsismod and Nextflow — release velocity, themes, recent moves, and the top alternatives to consider.
The model layer under Campsis, renamed in step with it and increasingly JSON-addressable.
Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.
Nextflow just made AI agents a task type, alongside processes and containers.
Nextflow ships on two tracks — dated edge releases carrying new work and 25.10.x/26.04.x stable lines taking backports — and the split is visible in every window: the edge builds run to dozens of commits while the stable patches are often plugin bumps alone. The current edge, 26.08.0-edge, introduces an agent primitive that makes AI agents first-class tasks, on top of steady work hardening the v2 config parser and type system. Cloud-executor plumbing, particularly for Seqera's own scheduler, is the other constant.
Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.
This package moves when Campsis needs it to move. The JSON constructor landed here in 1.3.0 and reached Campsis datasets a day later; parameter uncertainty generation was handed down from Campsis in that package's 1.6.0; and the snake_case migration started here before propagating up. That ordering makes Campsismod the place where suite-wide interface decisions are taken first, even though the visible payoff shows up in Campsis.
Expect Campsismod to keep absorbing model-level responsibilities that Campsis currently handles, and to extend the JSON mapping to whatever parts of the model object it does not yet cover. The entries give no signal on a 2.0, and with the rename already spent there is little reason to expect one soon.
Nextflow ships on two tracks — dated edge releases carrying new work and 25.10.x/26.04.x stable lines taking backports — and the split is visible in every window: the edge builds run to dozens of commits while the stable patches are often plugin bumps alone. The current edge, 26.08.0-edge, introduces an agent primitive that makes AI agents first-class tasks, on top of steady work hardening the v2 config parser and type system. Cloud-executor plumbing, particularly for Seqera's own scheduler, is the other constant.
Two arcs run in parallel. One is language maturity: the v2 parser, record types, typed outputs and the formatter have absorbed fix after fix across every release here, which is what a language does before it declares a syntax stable. The other is consolidation around Seqera — nf-tower folded into nf-seqera at 1.0.0, scheduler run identifiers propagate to Platform, and per-user CPU caps and secret references now cross that boundary. The agent primitive is the newest and least settled direction, arriving in edge rather than a stable line.
The agent primitive lands in an edge build, so the near-term question is whether it survives into a stable line unchanged or is reshaped first; the 26.04.x and 25.10.x branches show no sign of it yet. Expect the next edge releases to iterate on its interface while the stable branches continue taking parser and executor backports.
Other Infra & APIs 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 campsismod or Nextflow.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all campsismod alternatives → · See all Nextflow alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Nextflow is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Nextflow is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top campsismod alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsismod alternatives" section above for the current picks, or visit /alternatives/campsismod for the full list with editorial commentary on each.
Top Nextflow alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nextflow alternatives" section above for the current picks, or visit /alternatives/nextflow for the full list with editorial commentary on each.