← Back to home
Comparison · Analytics

bbotk vs see

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

bbotk vs see: at a glance

Featurebbotksee
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesblack-box optimization, mlr3, async execution, api deprecationr, easystats, data-visualization, ggplot2
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is bbotk?

bbotk is generalizing from an optimizer toolkit into an evaluation framework.

bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.

Read the full bbotk trajectory →

What is see?

see grows wherever easystats adds a diagnostic, one plot method at a time.

see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.

Read the full see trajectory →

bbotk vs see: editorial side-by-side

B
bbotk
ANALYTICS
2.5

bbotk is generalizing from an optimizer toolkit into an evaluation framework.

◆ Current state

bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.

◆ Where it's heading

Two threads run through the visible history. The first is async optimization maturing: ArchiveAsync gained a full push/finish/fail vocabulary over rush tasks in 1.11.0, and 1.12.0 deleted the deprecated extra arguments it replaced. The second is dependency consolidation, with custom C hypervolume code handed to moocore and rush pinned to 1.0.0, trimming maintenance surface as the async path becomes the default.

◆ Prediction

The deprecation removals in 1.12.0 suggest the async archive API is now treated as settled; the next releases most likely build on EvalInstance rather than continuing to churn ArchiveAsync.

S
see
ANALYTICS
0.0

see grows wherever easystats adds a diagnostic, one plot method at a time.

◆ Current state

see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.

◆ Where it's heading

Growth here is downstream-driven rather than self-directed: see expands to cover new diagnostics as easystats produces them. Running alongside that is a sustained investment in presentation control — theme arguments on plot methods, elements that scale with base_size — which suits users embedding these plots in documents rather than glancing at them interactively.

◆ Prediction

Expect new plot methods to keep arriving in step with performance and parameters releases, with continued theming work rather than any change in the package's scope.

Alternatives to bbotk and see

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 bbotk or see.

See all bbotk alternatives → · See all see alternatives →

Recent activity from bbotk and see

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

  1. 24d agobbotkDeprecated extra argument removed from ArchiveAsync methods
  2. 1mo agoseesee 0.14.1 adds plots for prior checks and grouped means
  3. 1mo agobbotkArchiveAsync gains full push/finish/fail task API over rush
  4. 2mo agobbotkDominance and hypervolume computation moved to moocore
  5. 2mo agoseesee 0.14.0 renders factor loadings as node-edge graphs
  6. 4mo agobbotkmlr_test_functions adds standard optimization benchmarks
  7. 5mo agobbotkEvalInstance base class separates evaluation from optimization
  8. 6mo agoseesee 0.13.0 fixes reversed plot sorting, adds theme arguments
  9. 8mo agobbotkFix: conditions now work with OptimizerLocalSearch
  10. 11mo agoseesee 0.12.0 extends normality checks to psych factor models
  11. 1y agoseesee 0.11.0 scales theme elements with base_size
  12. 1y agoseesee 0.10.0 plots random-effect group levels for mixed models

Frequently asked questions

What is the difference between bbotk and see?

They serve adjacent needs but don't currently overlap on shipped themes. bbotk is currently shipping more aggressively (velocity 2.5 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 bbotk better than see?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bbotk is currently shipping more aggressively (velocity 2.5 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 bbotk?

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

What are the best alternatives to see?

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