rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
stochvol vs surveycore
A side-by-side editorial comparison of stochvol and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
stochvol vs surveycore: at a glance
What is stochvol?
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.
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.
stochvol vs surveycore: editorial side-by-side
stochvol
0.0INFRA · APIS
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
◆ Current state
stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.
◆ Where it's heading
This is what a finished computational package looks like. The formula interface arrived at 3.1.0 and nothing has been added since; what changes is the ground underneath — RcppArmadillo major versions, UBSan checks, error-handling conventions moving from Rf_error to Rcpp::stop for correct memory management. The recurring pattern worth watching is that several releases fix real errors in the sampler's proposal distributions, found by users and by CRAN's own instrumented checks rather than by the maintainer.
◆ Prediction
Nothing in these notes suggests new methodology. Expect the next release when RcppArmadillo or a CRAN check flavour forces one, and treat any bug report against the samplers as the more consequential event.
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 stochvol 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 stochvol 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
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all stochvol alternatives → · See all surveycore alternatives →
Recent activity from stochvol and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 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 agostochvolSampler crash with constant parameters fixed, plus RcppArmadillo 15
- 1y agostochvolTwo CRAN check notes cleared
- 1y agostochvolProposal variance corrected in the centered parameterisation
- 2y agostochvolCRAN stochvol 3.2.4
- 2y agostochvolRolling-window indexing and inverse gamma prior validation fixed
- 3y agostochvolCore C++ sampler routines exported for reuse
Frequently asked questions
What is the difference between stochvol and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. stochvol and surveycore are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is stochvol better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. stochvol and surveycore are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to stochvol?
Top stochvol alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "stochvol alternatives" section above for the current picks, or visit /alternatives/stochvol 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.