q2
Quarto's Rust rewrite ships daily, and the parity grind has resumed after its one leap ahead.
A side-by-side editorial comparison of stochvol and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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 stochvol or surveytidy.
Quarto's Rust rewrite ships daily, and the parity grind has resumed after its one leap ahead.
Nextflow just made AI agents a task type, alongside processes and containers.
The D-score reference implementation rebuilt its measurement foundation on seven countries.
A football-viz package just swapped scraping for an API and broke its own output to do it.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
The recursive-computation engine under massProps grows the accessors its consumer needed
See all stochvol 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. stochvol and surveytidy 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. stochvol and surveytidy 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.
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.
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.