← Back to home
Comparison · Analytics

Fulcrum vs mlr3fselect

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

Fulcrum vs mlr3fselect: at a glance

FeatureFulcrummlr3fselect
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesfield-data-collection, esri-arcgis, offline-maps, on-device-inferencefeature-selection, mlr3, machine-learning, r-stats
Last editorial update18h ago1h ago
WebsiteVisit →

What is Fulcrum?

Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.

Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.

Read the full Fulcrum trajectory →

What is mlr3fselect?

mlr3fselect turned feature selection into an asynchronous, distributable job

mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.

Read the full mlr3fselect trajectory →

Fulcrum vs mlr3fselect: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.

◆ Current state

Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.

◆ Where it's heading

This is a platform consolidation being paid down one point release at a time. Having committed to Esri, Fulcrum is absorbing the instability that came with it, and each release reads as fixes to symptoms of the same migration. Underneath, the offline and field-capture story continues to get real attention — downloaded offline map layers can now be updated in place, and Photo FastFill moved to background processing so it no longer blocks editing.

◆ Prediction

Expect the release notes to stay fix-dominated through the September Google Maps cutoff, with the migration-related map defects tapering after it passes. Photo FastFill leaving early access is the most likely next substantive item.

M
mlr3fselect
ANALYTICS
0.0

mlr3fselect turned feature selection into an asynchronous, distributable job

◆ Current state

mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.

◆ Where it's heading

Two threads run in parallel: scaling the search itself through async execution and the rush backend, and making ensemble selection results easier to analyse via Pareto fronts, knee points and now removal of empty result rows. The rush backward-compatibility shim was dropped in 1.6.0, so the async path is now the assumed one.

◆ Prediction

Expect the ensemble result API to keep gaining analysis helpers, with async execution treated as the default rather than an option.

Alternatives to Fulcrum and mlr3fselect

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 Fulcrum or mlr3fselect.

See all Fulcrum alternatives → · See all mlr3fselect alternatives →

Recent activity from Fulcrum and mlr3fselect

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

  1. 1d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
  2. 2d agoFulcrumiOS fix: slow location resolution blocked record saves
  3. 6d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
  4. 8d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
  5. 8d agoFulcrumiOS fixes: basemap loading and black map screen
  6. 9d agoFulcrumiOS: ArcGIS SDK 300.0.0 and ONNX replaced by a new INFERENCE format
  7. 2mo agomlr3fselectEmpty-selection rows removable from ensemble results
  8. 8mo agomlr3fselectFaster objective evaluation and always_included roles
  9. 1y agomlr3fselectAsynchronous feature selection arrives with FSelectorAsync
  10. 1y agomlr3fselectEmbedded ensemble selection and result combination
  11. 1y agomlr3fselectInternal tuning callback added
  12. 1y agomlr3fselectmlr3 0.21.0 compatibility and archive slimming

Frequently asked questions

What is the difference between Fulcrum and mlr3fselect?

They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Fulcrum better than mlr3fselect?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to Fulcrum?

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

What are the best alternatives to mlr3fselect?

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