STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
b3gbi vs ggtrace
A side-by-side editorial comparison of b3gbi and ggtrace — release velocity, themes, recent moves, and the top alternatives to consider.
b3gbi vs ggtrace: at a glance
What is b3gbi?
b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
What is ggtrace?
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.
b3gbi vs ggtrace: editorial side-by-side
b3gbi
2.5ANALYTICS
b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.
◆ Current state
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
◆ Where it's heading
Two forces are shaping releases. Internally, the uncertainty split produced an indicator-specific rule book — species-level indicators bootstrap the whole cube, raw counts resample within year, evenness gets a logit transform — and that rule book is where the statistical thinking now lives. Externally, GBIF's taxonomic backbone migration to the Catalogue of Life forced string taxon keys through process_cube() and the plotting paths, while recurring EEA and MGRS grid-code fixes mark coordinate parsing as the least settled area.
◆ Prediction
The 0.9.4 notes are entirely JOSS review items — contributors, examples, tracked datasets — so the next release is most likely a JOSS-accepted 1.0 rather than new indicator work.
ggtrace
0.0ANALYTICS
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
◆ Current state
ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.
◆ Where it's heading
The package matured from raw tracing primitives into named workflows: 0.6.0 added the sublayer snapshot functions and error-context helpers, 0.7.x has been sanding down how reliably those workflows find and evaluate a method. Three consecutive releases in May 2025, two of them minutes apart, all address the same class of failure — one-liner ggproto methods without braces, and inheritance resolution on instances rather than subclasses. That pattern says the remaining bugs are in method introspection, not in the tracing machinery itself.
◆ Prediction
Expect continued fixes to method resolution as ggplot2's ggproto definitions vary, and realignment work when ggplot2 4.x changes internals this package deliberately reaches into. The entries do not signal new workflow functions.
Alternatives to b3gbi and ggtrace
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 b3gbi or ggtrace.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
eiaapi
A thin EIA energy-data client whose whole story is making bulk queries survive the API's limits.
See all b3gbi alternatives → · See all ggtrace alternatives →
Recent activity from b3gbi and ggtrace
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agob3gbiJOSS review fixes: contributors, examples, tracked data
- 1mo agob3gbiEEA grid coordinates no longer scaled by resolution
- 1mo agob3gbiadd_ci() no longer crashes on completeness indicators
- 1mo agob3gbiString taxon keys for GBIF's Catalogue of Life backbone
- 1mo agob3gbiUncertainty split out of the indicator workflow into add_ci() ⚡
- 1mo agob3gbiFAIR column mapping doc and Zenodo DOI badge
- 1y agoggtraceBrace-less one-liner methods traced gracefully
- 1y agoggtraceget_method_inheritance() fixed for class instances
- 1y agoggtraceWorkflow functions recognise one-liner ggproto methods
- 1y agoggtraceEager layer_is(), clearer method-mismatch errors, consistent tracedump names
- 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
- 1y agoggtracelayer_is() targets by_layer() downstream directly
Frequently asked questions
What is the difference between b3gbi and ggtrace?
They serve adjacent needs but don't currently overlap on shipped themes. b3gbi 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 b3gbi better than ggtrace?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. b3gbi 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 b3gbi?
Top b3gbi alternatives in Analytics are ranked by recent ship velocity. Browse the "b3gbi alternatives" section above for the current picks, or visit /alternatives/b3gbi for the full list with editorial commentary on each.
What are the best alternatives to ggtrace?
Top ggtrace alternatives in Analytics are ranked by recent ship velocity. Browse the "ggtrace alternatives" section above for the current picks, or visit /alternatives/ggtrace for the full list with editorial commentary on each.