rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
plssem vs surveycore
A side-by-side editorial comparison of plssem and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
plssem vs surveycore: at a glance
| Feature | plssem | surveycore |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | structural-equation-modeling, partial-least-squares, multilevel-models, standard-errors | survey-statistics, variance-estimation, replicate-weights, api-stability |
| Last editorial update | 1h ago | 1h ago |
| Website | Visit → | Visit → |
What is plssem?
plssem took PLS-SEM into multilevel data, then spent two releases making the estimates trustworthy.
plssem is a young R implementation of partial least squares structural equation modelling, three CRAN releases old and shipping monthly. Its distinguishing work is the MC-PLS family — consistent PLS estimators the maintainer extended to mixed-effects designs in June — and the releases since have been about getting standard errors, admissibility and fit measures onto the same footing as the point estimates.
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.
plssem vs surveycore: editorial side-by-side
plssem
0.0INFRA · APIS
plssem took PLS-SEM into multilevel data, then spent two releases making the estimates trustworthy.
◆ Current state
plssem is a young R implementation of partial least squares structural equation modelling, three CRAN releases old and shipping monthly. Its distinguishing work is the MC-PLS family — consistent PLS estimators the maintainer extended to mixed-effects designs in June — and the releases since have been about getting standard errors, admissibility and fit measures onto the same footing as the point estimates.
◆ Where it's heading
The pattern is capability first, inference second. Multilevel MC-PLSc and MC-OrdPLSc arrived in 0.1.2 together with Monte-Carlo delta-method standard errors and a Polyak-Juditsky extrapolation step; 0.1.3 then extended delta-method errors to redundant parameters and thresholds, optimized their computation, added a loglikelihood-based fit measure and generated dynamic bounds to keep MC-PLS solutions admissible. Admissibility recurs throughout — penalized inadmissible solutions in 0.1.1, variance lower bounds and negative residual variance handling in 0.1.3, and an option to drop inadmissible bootstraps rather than silently include them. The release notes are pull-request lists, so the reasoning behind each change stays in the repository.
◆ Prediction
The MIMIC mode and GLS estimator both landed in the most recent release without the standard-error and fit-measure work that followed earlier additions, so extending inference to cover them is the natural next step. Bootstrap defaults moving to 500 replications suggests runtime is a live constraint and further optimization is likely.
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 plssem 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 plssem or surveycore.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all plssem alternatives → · See all surveycore alternatives →
Recent activity from plssem and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoplssemMIMIC mode, a GLS structural estimator and delta-method thresholds
- 2mo agoplssemMC-PLSc and MC-OrdPLSc extend to multilevel and mixed-effects models ⚡
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agoplssemParallel bootstrapping, kNN and mean imputation, higher-order constructs
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
Frequently asked questions
What is the difference between plssem and surveycore?
Both compete on the same themes — r-packages — within Infra & APIs. plssem 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 plssem better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. plssem 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 plssem?
Top plssem alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "plssem alternatives" section above for the current picks, or visit /alternatives/plssem 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.