← Back to home
Comparison · Analytics

fastml vs incase

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

fastml vs incase: at a glance

Featurefastmlincase
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesautoml, tidymodels, survival analysis, cross-validationdata-wrangling, recoding, tidyverse, api-deprecation
Last editorial update2h ago52m ago
WebsiteVisit →Visit →

What is fastml?

fastml added survival modelling and leakage-proof resampling, moving past classification and regression.

A tidymodels-based AutoML wrapper that trains, tunes and compares many engines from one call. The 0.6.x line added engine-specific tuning parameters, class-imbalance handling, early stopping and DALEX-based explainability. The 0.7.5 release is far larger: a full survival analysis task with its own engines, MICE imputation and integrated Brier scoring, plus unbiased nested cross-validation, grouped, blocked and rolling resampling helpers, fold-wise imputation, recipe leakage checks, and a sandbox for user-supplied preprocessing.

Read the full fastml 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 →

fastml vs incase: editorial side-by-side

F
fastml
ANALYTICS
0.0

fastml added survival modelling and leakage-proof resampling, moving past classification and regression.

◆ Current state

A tidymodels-based AutoML wrapper that trains, tunes and compares many engines from one call. The 0.6.x line added engine-specific tuning parameters, class-imbalance handling, early stopping and DALEX-based explainability. The 0.7.5 release is far larger: a full survival analysis task with its own engines, MICE imputation and integrated Brier scoring, plus unbiased nested cross-validation, grouped, blocked and rolling resampling helpers, fold-wise imputation, recipe leakage checks, and a sandbox for user-supplied preprocessing.

◆ Where it's heading

The package is moving from convenience wrapper to something that has to be defensible statistically. Nested cross-validation, fold-wise rather than up-front imputation, and explicit leakage checks are all corrections to the shortcuts that make AutoML easy and its scores optimistic. Survival adds a third task type alongside classification and regression, and it arrived with its own metrics rather than being bolted onto the existing ones. Note the entry body is cut off at 8,000 characters, so the release is larger than what is shown.

◆ Prediction

Expect the remaining survival engines to fill in and the sandboxing of custom preprocessing to tighten, since both were still being iterated on within this same release's commit list.

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

See all fastml alternatives → · See all incase alternatives →

Recent activity from fastml and incase

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

  1. 8mo agofastmlVersion 0.7.5
  2. 11mo agoincaseDotted arguments and an .exhaustive matching check
  3. 1y agofastmlEngine-specific tuning, imbalance handling and explainability
  4. 1y agofastmlSingle-workflow evaluation fix
  5. 1y agofastmlVersion 0.5.0
  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 fastml and incase?

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

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

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