rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of Nematode and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
A nematode ecology toolbox whose last two releases corrected the arithmetic in its own indices.
Nematode packages the standard soil-nematode community indices — maturity, enrichment, structure and channel indices, trophic diversity, plant parasite index — alongside ordination helpers and a bundled taxonomy and traits dataset drawn from Nemaplex. The visible history is short: a large function drop in 0.2.0, then a run of releases correcting formulas and refreshing the reference data.
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.
Nematode packages the standard soil-nematode community indices — maturity, enrichment, structure and channel indices, trophic diversity, plant parasite index — alongside ordination helpers and a bundled taxonomy and traits dataset drawn from Nemaplex. The visible history is short: a large function drop in 0.2.0, then a run of releases correcting formulas and refreshing the reference data.
Two of the four documented releases fix a formula in an index the package already shipped — the Species Richness Index in 0.2.1 and a missing division by two in the Functional Metabolic Footprints calculation in 0.3.1 — and the 0.2.1 note tells users their earlier values were wrong. That, more than the feature additions, is what the feed records. The other thread is keeping the bundled taxonomy current against Nemaplex, which grew the genus table from 2,484 to 2,524 entries and the body-mass table from 987 to 1,094 in March.
Given the pattern of index formulas being corrected after release, further verification of the remaining indices against their source publications is the likeliest next work. The Nemaplex datasets carry a revision date and are refreshed on the upstream schedule, so another data update is the other predictable item.
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.
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.
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.
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 Nematode or surveytidy.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all Nematode alternatives → · See all surveytidy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. Nematode 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nematode 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.
Top Nematode alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nematode alternatives" section above for the current picks, or visit /alternatives/nematode for the full list with editorial commentary on each.
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.