rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
campsismod vs surveycore
A side-by-side editorial comparison of campsismod and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
campsismod vs surveycore: at a glance
What is campsismod?
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.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
campsismod vs surveycore: editorial side-by-side
campsismod
2.5INFRA · APIS
The model layer under Campsis, renamed in step with it and increasingly JSON-addressable.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to campsismod and surveycore
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 surveycore.
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
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all campsismod alternatives → · See all surveycore alternatives →
Recent activity from campsismod and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agocampsismodsnake_case migration lands here first
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agocampsismodBundled model suite refreshed
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 5mo agocampsismodJSON argument added to the CampsisModel constructor
- 7mo agocampsismodJSON import for Campsis models
- 1y agocampsismodreplaceAll fixed for unrecognised statements
- 1y agocampsismodPerformance tests skipped on CRAN
Frequently asked questions
What is the difference between campsismod and surveycore?
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.
Is campsismod better than surveycore?
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.
What are the best alternatives to campsismod?
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.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.