← Back to home
Comparison · Analytics

effectplots vs incase

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

Shared themes:r-package

effectplots vs incase: at a glance

Featureeffectplotsincase
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, model-interpretability, ale, partial-dependencedata-wrangling, recoding, tidyverse, api-deprecation
Last editorial update49m ago1h ago
WebsiteVisit →Visit →

What is effectplots?

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.

Read the full effectplots trajectory →

What is incase?

A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.

incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.

Read the full incase trajectory →

effectplots vs incase: editorial side-by-side

E
effectplots
ANALYTICS
0.0

A young ALE and PDP plotting package that rebuilt its numeric core after a data-corrupting bug.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

I
incase
ANALYTICS
0.0

A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.

◆ Current state

incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.

◆ Where it's heading

The arc is consistently toward catching recoding mistakes at the call site rather than letting them pass silently. Early releases broadened how a match can be expressed — pattern matching, function application, factor and list returns. Recent work has shifted to guarantees about the result: correct factor level ordering relative to .default, and now an exhaustiveness check. Notably 0.4.0 reverses the 0.3.2 decision to accept arguments with or without dots, trading that flexibility for namespace safety against user-supplied case names.

◆ Prediction

The deprecation warnings introduced in 0.4.0 point to a follow-up release that removes the undotted arguments outright. Whether .exhaustive eventually becomes the default is unclear from these entries.

Alternatives to effectplots and incase

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 incase.

See all effectplots alternatives → · See all incase alternatives →

Recent activity from effectplots and incase

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

  1. 11mo agoincaseDotted arguments and an .exhaustive matching check
  2. 1y agoeffectplotsRare categories collapse into an 'other' level
  3. 1y agoeffectplotsMissing x values now plotted for numeric features
  4. 1y agoeffectplotsNumeric core rewritten after an in-place data corruption fix
  5. 1y agoeffectplotsInitial CRAN release
  6. 2y agoincaseDotted and undotted arguments both accepted
  7. 5y agoincaseFix NULL return when no condition matches
  8. 5y agoincaseFactor and list return families arrive
  9. 5y agoincaseDrop unused stats import to clear a check NOTE
  10. 5y agoincasePattern and function-based matching families added

Frequently asked questions

What is the difference between effectplots and incase?

Both compete on the same themes — r-package — within Analytics. effectplots and incase 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 effectplots better than incase?

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

What are the best alternatives to effectplots?

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.

What are the best alternatives to incase?

Top incase alternatives in Analytics are ranked by recent ship velocity. Browse the "incase alternatives" section above for the current picks, or visit /alternatives/incase for the full list with editorial commentary on each.