JointFPM
Recurrent-event modelling settles, with mean_no() promoted to stable.
A side-by-side editorial comparison of nzilbb.vowels and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
A vowel-analysis package trimming dependencies after an email address got it archived.
nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.
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.
nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.
The package is reducing what it relies on, and paying for it in small interface breaks — plot_correlation_counts() lost its half_violin argument and gained a points argument in the same move. The 0.4.2 notes also record that version 0.4.1 was archived by CRAN because the maintainer's email had become unreliable, prompting a switch to an institutional address. That is administrative rather than technical, but it explains why three closely spaced patches exist at all.
With the two external plotting and ordination dependencies gone and the maintainer address stabilised, the visible pressure that produced these releases is resolved. Nothing in the entries indicates what comes next, and the history is too short to read a feature direction from.
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.
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.
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.
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 nzilbb.vowels or surveycore.
Recurrent-event modelling settles, with mean_no() promoted to stable.
Nonparametric change point detection swaps p-values for importance scores.
A Prism-styled ggplot2 theme in maintenance, now surviving ggplot2 4.0.
Wavelet trend estimation tightens the defaults it shipped with.
Back from CRAN removal under a new maintainer, with the compiled layer rebuilt.
mice can finally predict, not just estimate, from multiply imputed data.
See all nzilbb.vowels alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nzilbb.vowels 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nzilbb.vowels 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.
Top nzilbb.vowels alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nzilbb.vowels alternatives" section above for the current picks, or visit /alternatives/nzilbb-vowels for the full list with editorial commentary on each.
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.