← Back to home
Comparison · Infra & APIs

midr vs surveytidy

A side-by-side editorial comparison of midr and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.

midr vs surveytidy: at a glance

Featuremidrsurveytidy
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesexplainable-ai, surrogate-models, shapley, survival-analysissurvey-statistics, tidyverse, dplyr-verbs, metadata-tracking
Last editorial update39m ago1h ago
WebsiteVisit →Visit →

What is midr?

A black-box interpreter reaches CRAN, then learns multi-class and survival responses

midr explains black-box models by fitting an interpretable surrogate through Maximum Interpretation Decomposition — main effects plus second-order interactions, with exact Shapley values for the surrogate. Two months after its first CRAN release it can take a matrix response, which covers multi-class classification and survival models, and hold collections of fitted interpretations in midlist and midrib objects for comparison.

Read the full midr trajectory →

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.

Read the full surveytidy trajectory →

midr vs surveytidy: editorial side-by-side

M
midr
INFRA · APIS
0.0

A black-box interpreter reaches CRAN, then learns multi-class and survival responses

◆ Current state

midr explains black-box models by fitting an interpretable surrogate through Maximum Interpretation Decomposition — main effects plus second-order interactions, with exact Shapley values for the surrogate. Two months after its first CRAN release it can take a matrix response, which covers multi-class classification and survival models, and hold collections of fitted interpretations in midlist and midrib objects for comparison.

◆ Where it's heading

The releases move outward along two axes at once: what can be interpreted, and how much of it fits in memory. Version 0.5.3 rebuilt the fitting path to avoid materialising large design matrices and added a save.memory option; 0.6.0 widened the response from a vector to a matrix and added parametric link functions. Class and argument names were shortened in the same release, so the package is still willing to break itself this early.

◆ Prediction

With multiple models now held in one object and visualisation methods for them, comparison across models is the surface most likely to fill out next — the collection classes exist but the notes describe manipulation and plotting rather than any comparison metric.

S
surveytidy
INFRA · APIS
0.0

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 midr 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 midr or surveytidy.

See all midr alternatives → · See all surveytidy alternatives →

Recent activity from midr and surveytidy

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agosurveytidymutate() syncs metadata for across() recodes
  2. 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
  3. 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
  4. 5mo agomidrMatrix responses bring multi-class and survival models in scope
  5. 7mo agomidrFirst CRAN release: MID surrogate models for black-box explanation
  6. 7mo agomidrMemory-efficient fitting for large design matrices

Frequently asked questions

What is the difference between midr and surveytidy?

They serve adjacent needs but don't currently overlap on shipped themes. midr 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 midr better than surveytidy?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. midr 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 midr?

Top midr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "midr alternatives" section above for the current picks, or visit /alternatives/midr 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.