JointFPM
Recurrent-event modelling settles, with mean_no() promoted to stable.
Comparison · Infra & APIs
netdiffuseR vs surveycore
A side-by-side editorial comparison of netdiffuseR and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
netdiffuseR vs surveycore: at a glance
What is netdiffuseR?
Network diffusion analysis returns from a seven-year gap able to track several behaviours at once
netdiffuseR analyses how behaviours spread through networks — exposure, adoption timing, thresholds, and simulation of diffusion processes. Its feed has a hole: four releases from 2024 to 2026 sit directly on top of three from 2016 and 2017, with the intervening versions absent. The current line is being maintained by a widening group of contributors and, at 1.24.0, was explicitly brought back to CRAN.
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.
netdiffuseR vs surveycore: editorial side-by-side
netdiffuseR
0.0INFRA · APIS
Network diffusion analysis returns from a seven-year gap able to track several behaviours at once
◆ Current state
netdiffuseR analyses how behaviours spread through networks — exposure, adoption timing, thresholds, and simulation of diffusion processes. Its feed has a hole: four releases from 2024 to 2026 sit directly on top of three from 2016 and 2017, with the intervening versions absent. The current line is being maintained by a widening group of contributors and, at 1.24.0, was explicitly brought back to CRAN.
◆ Where it's heading
The recent releases read as institutional rather than exploratory: CI fixes, CRAN-readiness passes, contributed PRs from new names, bundled teaching datasets. The one structural move is 1.23.0, named for multi-adoption, which alongside a refactor of the exposure and rdiffnet internals adds a function for splitting behaviours apart — the package handling several diffusing behaviours where its object model previously carried one.
◆ Prediction
With CRAN presence restored and a dataset for a teaching game added in the newest release, the near-term direction looks like classroom and workshop use rather than new method surface. Whether multi-adoption gets its own analysis functions, rather than a splitter, is the open question these notes do not answer.
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 netdiffuseR 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 netdiffuseR or surveycore.
CptNonPar
Nonparametric change point detection swaps p-values for importance scores.
ggprism
A Prism-styled ggplot2 theme in maintenance, now surviving ggplot2 4.0.
TrendLSW
Wavelet trend estimation tightens the defaults it shipped with.
mmpca
Back from CRAN removal under a new maintainer, with the compiled layer rebuilt.
mice
mice can finally predict, not just estimate, from multiply imputed data.
See all netdiffuseR alternatives → · See all surveycore alternatives →
Recent activity from netdiffuseR 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
- 4mo agonetdiffuseREpidemic game dataset added ahead of a CRAN submission
- 8mo agonetdiffuseRBack on CRAN with an adoption-timing diagnostic
- 1y agonetdiffuseRMulti-adoption: splitting several behaviours out of one network ⚡
- 1y agonetdiffuseRCRAN v1.22.6
- 8y agonetdiffuseRigraph-standard plotting and repeated diffusion simulations
- 9y agonetdiffuseRBootstrapping, mentor matching, and Bass model fitting
Frequently asked questions
What is the difference between netdiffuseR and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. netdiffuseR 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 netdiffuseR better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. netdiffuseR 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 netdiffuseR?
Top netdiffuseR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "netdiffuseR alternatives" section above for the current picks, or visit /alternatives/netdiffuser 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.