mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
PINstimation vs surveycore
A side-by-side editorial comparison of PINstimation and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
PINstimation vs surveycore: at a glance
What is PINstimation?
A market-microstructure toolkit that keeps adding estimators as the papers land.
PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.
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.
PINstimation vs surveycore: editorial side-by-side
PINstimation
0.0INFRA · APIS
A market-microstructure toolkit that keeps adding estimators as the papers land.
◆ Current state
PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.
◆ Where it's heading
Each release tracks the literature: a Bayesian PIN estimator from Griffin et al., an improved VPIN from Ke and Lin, initial-parameter generation realigned to Ersan and Ghachem. The other steady thread is data handling — matrix inputs so the estimators compose with rolling windows, user-specified aggregation frequencies, and now quote leads as well as lags. The three-year gap between 0.1.2 and 0.2.0 makes this a slow, publication-paced package rather than an actively developed one.
◆ Prediction
On this pattern the next release adds whatever estimator the authors publish next, since two of the three feature releases here implement a specific paper. Nothing in the entries points to a change in the package's structure.
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 PINstimation 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 PINstimation or surveycore.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
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 PINstimation alternatives → · See all surveycore alternatives →
Recent activity from PINstimation 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 agoPINstimationPINstimation 0.2.0
- 3y agoPINstimationPINstimation v0.1.2
- 3y agoPINstimationPINstimation v0.1.1
- 3y agoPINstimationPINstimation v0.0.1-beta
- 3y agoPINstimationPINstimation v0.1.0
Frequently asked questions
What is the difference between PINstimation and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. PINstimation 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 PINstimation better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PINstimation 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 PINstimation?
Top PINstimation alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PINstimation alternatives" section above for the current picks, or visit /alternatives/pinstimation 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.