rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of campsismod and surveytidy — 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.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
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.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
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 surveytidy.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all campsismod alternatives → · See all surveytidy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. campsismod 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. campsismod 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 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 surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.