simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of effectplots and roclang — release velocity, themes, recent moves, and the top alternatives to consider.
A young ALE and PDP plotting package that rebuilt its numeric core after a data-corrupting bug.
effectplots computes and plots partial dependence, ALE, and observed-versus-predicted effect curves for fitted models. It reached CRAN in November 2024 and shipped three releases in the four months after. The 0.2.0 release is the pivot: an outlier-clipping routine that silently modified the caller's data frame was fixed, the numeric path was rewritten for speed and memory, and the plotting and category-collapsing defaults were reset.
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.
effectplots computes and plots partial dependence, ALE, and observed-versus-predicted effect curves for fitted models. It reached CRAN in November 2024 and shipped three releases in the four months after. The 0.2.0 release is the pivot: an outlier-clipping routine that silently modified the caller's data frame was fixed, the numeric path was rewritten for speed and memory, and the plotting and category-collapsing defaults were reset.
After 0.2.0 the work turns to the awkward cases - missing values on the x axis, explicit and empty factor levels, discrete grid detection. The package is also widening past a single modelling ecosystem: h2o support and tidymodels examples arrived with 0.2.0, and fcut() was exported as a fast replacement for cut(). Release notes are issue-numbered throughout, so the roadmap is effectively the issue tracker.
Expect continued default tuning around collapse_m and discrete_m plus more model-backend coverage; the cadence points to another batch of issue fixes rather than a new plot type.
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 effectplots 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.
See all effectplots alternatives → · See all roclang alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. effectplots 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. effectplots 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 effectplots alternatives in Analytics are ranked by recent ship velocity. Browse the "effectplots alternatives" section above for the current picks, or visit /alternatives/effectplots 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.