rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
mdatools vs surveytidy
A side-by-side editorial comparison of mdatools and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
mdatools vs surveytidy: at a glance
What is mdatools?
mdatools spun out its cross-validation method, then came back for three-way data.
mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.
What is surveytidy?
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
mdatools vs surveytidy: editorial side-by-side
mdatools
0.0INFRA · APIS
mdatools spun out its cross-validation method, then came back for three-way data.
◆ Current state
mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.
◆ Where it's heading
The shape of the package has been managed deliberately rather than allowed to sprawl. Procrustes cross-validation grew large enough to warrant its own package and was moved out to pcv in 0.14.0; preprocessing was consolidated in 0.12.0 into a composable prep() framework rather than a set of loose functions. Around that, the recurring work is numerical: a more stable SIMPLS implementation, cross-validation rewritten to accept user-supplied segment indices, prep.savgol() and prep.alsbasecorr() rewritten for speed, and now the baseline iteration default raised to match the web applications the maintainer also runs.
◆ Prediction
Three-way DD-SIMCA arrives with two decompositions and no companion regression or resolution methods for multiway data, so extending the multiway path to the rest of the toolkit is the obvious follow-up. The alignment of defaults with the maintainer's web applications suggests those two codebases will keep being reconciled.
surveytidy
0.0INFRA · APIS
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
◆ Current state
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
◆ Where it's heading
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
◆ Prediction
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Alternatives to mdatools and surveytidy
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 mdatools or surveytidy.
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 mdatools alternatives → · See all surveytidy alternatives →
Recent activity from mdatools and surveytidy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomdatoolsDD-SIMCA classification arrives for three-way data ⚡
- 2mo agosurveytidymutate() syncs metadata for across() recodes
- 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
- 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
- 5mo agomdatoolsv. 0.15.0
- 2y agomdatoolsData frames converted to matrices automatically for model training
- 3y agomdatoolscv.scope lets centering and scaling follow the global or local set
- 3y agomdatoolsProcrustes cross-validation moves out to its own pcv package ⚡
- 3y agomdatoolsgetRegcoeffs() fixed for unscaled models; ipls() gains a full mode
Frequently asked questions
What is the difference between mdatools and surveytidy?
Both compete on the same themes — r-packages — within Infra & APIs. mdatools and surveytidy 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 mdatools better than surveytidy?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mdatools and surveytidy 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 mdatools?
Top mdatools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mdatools alternatives" section above for the current picks, or visit /alternatives/mdatools for the full list with editorial commentary on each.
What are the best alternatives to surveytidy?
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.