simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of aqp and roclang — release velocity, themes, recent moves, and the top alternatives to consider.
The 1.x line, tagged retroactively after a decade of SoilProfileCollection redesign.
aqp provides the SoilProfileCollection class and the algorithms built on it for soil profile data, colour, and taxonomy. The most recent tag in this feed is explicitly retroactive: 1.42 was cut in 2025 to mark the last CRAN state before the 2.0 release. Between 2018 and 2021 the class internals were reworked twice, the Munsell colour tooling grew substantially, and data.table replaced reshape underneath the wide-to-long transformations.
A roxygen2 documentation-reuse helper whose release notes are mostly upstream damage control.
roclang lets package authors pull documentation text out of an existing function's roxygen block and splice it into their own — extract_roc_text() with type = "param", "dot_params" or a section selector. The feature surface has been stable since 0.2.1; the parameter-matching rules and the checks for invalid or ambiguous extractions are the substance of what shipped.
aqp provides the SoilProfileCollection class and the algorithms built on it for soil profile data, colour, and taxonomy. The most recent tag in this feed is explicitly retroactive: 1.42 was cut in 2025 to mark the last CRAN state before the 2.0 release. Between 2018 and 2021 the class internals were reworked twice, the Munsell colour tooling grew substantially, and data.table replaced reshape underneath the wide-to-long transformations.
Two threads run through the window. The core object was progressively rebuilt - a new horizon-ID slot in 1.17, then a wave of renames and argument removals in 1.25 that broke code deliberately ahead of 2.0. Alongside it, colour work compounded: mixMunsell, spectral mixing, colour quantiles, a chip-frequency chart, and PMS conversion. Tag order here is not release order, since 1.42 was applied to an older commit.
This feed reads as a closed chapter - further entries on it would be backfill, with active work having moved to the 2.x series.
roclang lets package authors pull documentation text out of an existing function's roxygen block and splice it into their own — extract_roc_text() with type = "param", "dot_params" or a section selector. The feature surface has been stable since 0.2.1; the parameter-matching rules and the checks for invalid or ambiguous extractions are the substance of what shipped.
Nearly every release since 0.2.0 has been reactive. The package parses documentation text produced by other packages, so a wording change in stats::lm()'s documentation breaks its test suite, and a roxygen2 selection-semantics change forces its parameter matching to follow. The 0.2.3 release is exactly this pattern again. Release cadence has slowed to roughly one entry every two years, and the last two carried no functional change at all.
Further releases are most likely triggered by upstream roxygen2 or base R documentation edits breaking tests rather than by new extraction capability. The entries show no queued feature work.
Other Analytics 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 aqp or roclang.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. aqp and roclang 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. aqp and roclang 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 Analytics products to evaluate alongside.
Top aqp alternatives in Analytics are ranked by recent ship velocity. Browse the "aqp alternatives" section above for the current picks, or visit /alternatives/aqp for the full list with editorial commentary on each.
Top roclang alternatives in Analytics are ranked by recent ship velocity. Browse the "roclang alternatives" section above for the current picks, or visit /alternatives/roclang for the full list with editorial commentary on each.