ggfootball
A football-viz package just swapped scraping for an API and broke its own output to do it.
Comparison · Infra & APIs
campsis vs rollupTree
A side-by-side editorial comparison of campsis and rollupTree — release velocity, themes, recent moves, and the top alternatives to consider.
campsis vs rollupTree: at a glance
What is campsis?
Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.
Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.
What is rollupTree?
The recursive-computation engine under massProps grows the accessors its consumer needed
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
campsis vs rollupTree: editorial side-by-side
campsis
3.8INFRA · APIS
Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.
◆ Current state
Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.
◆ Where it's heading
The 1.8 and 1.9 releases together describe a package being made drivable from outside R. JSON interfaces arrived first for models in Campsismod 1.3.0 and for datasets in Campsis 1.8.0, then extended to scenarios, settings and study replication; the output side has now been generalised the same way, from fixed result processing to a collection of output functions applied to simulated results. Renaming every function and cutting RxODE loose is the cost of that consolidation, paid in one deliberate breaking release rather than spread across several.
◆ Prediction
With the rename and the RxODE removal behind it, the next releases should restore the rxode2 engine to the test suite, which 1.9.0 removed temporarily, and continue filling out the output-function catalogue beyond NCA. The JSON surface looks like the intended entry point for driving Campsis from outside R, though the entries do not say what is meant to consume it.
rollupTree
0.0INFRA · APIS
The recursive-computation engine under massProps grows the accessors its consumer needed
◆ Current state
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
◆ Where it's heading
The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.
◆ Prediction
On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.
Alternatives to campsis and rollupTree
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 campsis or rollupTree.
goat
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
See all campsis alternatives → · See all rollupTree alternatives →
Recent activity from campsis and rollupTree
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15d agocampsissnake_case across the API; RxODE compatibility removed ⚡
- 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
- 6mo agorollupTreeMissing column names in the new row setters
- 6mo agorollupTreeRow-level get and set accessors by key and by id
- 7mo agocampsisMaintenance release for future package warnings
- 7mo agocampsisJSON import for Campsis datasets
- 1y agorollupTreeMinor vignette improvements
- 1y agorollupTreeBadges and GitHub Actions added to the README
- 1y agocampsisDosing gains vectorized compartments and cycle repetition
- 1y agorollupTreedefault_validate_dag() extends validation past strict trees
- 1y agocampsisParameter uncertainty from SIR and bootstrap output
Frequently asked questions
What is the difference between campsis and rollupTree?
They serve adjacent needs but don't currently overlap on shipped themes. campsis is currently shipping more aggressively (velocity 3.8 vs 0.0), 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.
Is campsis better than rollupTree?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. campsis is currently shipping more aggressively (velocity 3.8 vs 0.0), 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.
What are the best alternatives to campsis?
Top campsis alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsis alternatives" section above for the current picks, or visit /alternatives/campsis for the full list with editorial commentary on each.
What are the best alternatives to rollupTree?
Top rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.