mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
emuR vs surveycore
A side-by-side editorial comparison of emuR and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
emuR vs surveycore: at a glance
What is emuR?
The R half of the EMU speech database system, fixing what was quietly broken.
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
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.
emuR vs surveycore: editorial side-by-side
emuR
0.0INFRA · APIS
The R half of the EMU speech database system, fixing what was quietly broken.
◆ Current state
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
◆ Where it's heading
The releases read as a package being brought up to the standard its own API implied. delete_itemsInLevel() shipped in 2.1.1 as a first version, was described in 2.5.0 as heavily flawed and now usable, and the create/update/delete family is still called ongoing work. Alongside that, the query engine was rewritten onto CTEs and the signal-processing layer is being opened past the bundled wrassp, starting with Matlab. Speed work recurs — SQLite transactions, prepared statements, on-the-fly caching — consistent with corpora outgrowing the original design.
◆ Prediction
Two threads are explicitly unfinished: the CRUD documentation and behaviour, described as ongoing, and the add_signalVia family, described as a draft starting with Matlab. Expect the next release to advance one of them rather than open new ground.
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 emuR 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 emuR or surveycore.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
GencoDymo2
A GENCODE annotation toolkit spent its first year getting out of CRAN's way.
See all emuR alternatives → · See all surveycore alternatives →
Recent activity from emuR 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
- 8mo agoemuRemuR 2.6.0
- 1y agoemuRemuR 2.5.1
- 1y agoemuRemuR 2.5.0
- 3y agoemuRemuR 2.4.0
- 5y agoemuRemuR 2.3.0
- 5y agoemuRemuR 2.2.0
Frequently asked questions
What is the difference between emuR and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. emuR 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 emuR better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. emuR 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 emuR?
Top emuR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "emuR alternatives" section above for the current picks, or visit /alternatives/emur 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.