nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
bbk vs e2tree
A side-by-side editorial comparison of bbk and e2tree — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
bbk vs e2tree: at a glance
What is bbk?
One R interface is absorbing the world's central bank data portals, one API at a time.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
What is e2tree?
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
e2tree builds a single interpretable tree that approximates a fitted ensemble, working from the proximity structure the ensemble induces between observations. The 1.0.0 release added the piece that had been missing: a Goodness of Interpretability index quantifying how well the approximating tree reconstructs the ensemble's own proximity matrix, with a permutation test for significance. Interactive visualisation and a C++ backend with OpenMP parallelism arrived alongside, and support now spans ranger and CatBoost as well as the original targets.
bbk vs e2tree: editorial side-by-side
bbk
0.0ANALYTICS
One R interface is absorbing the world's central bank data portals, one API at a time.
◆ Current state
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
◆ Where it's heading
The expansion is steady and the integration work is what makes it more than a list of wrappers: arguments introduced for one provider get pushed to the others, dimension introspection is being generalised across dataflows, and the bug fixes in recent releases are almost all about the same class of problem — series with missing observations, unsupported frequency codes, or date/value misalignment breaking a parser written for a tidier feed. The maintainer ships the same infrastructure across their packages in lockstep; bbk 0.9.0 and the sibling treasury package's 0.5.0 landed identical opt-in caching within minutes of each other. Geography is the visible frontier, but consistency across an increasingly ragged set of upstream APIs is the actual work.
◆ Prediction
Expect more national central banks to be added on the same template, and the newer providers to be retrofitted with the dimension and updated_after functions the older ones already have.
e2tree
0.0ANALYTICS
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
◆ Current state
e2tree builds a single interpretable tree that approximates a fitted ensemble, working from the proximity structure the ensemble induces between observations. The 1.0.0 release added the piece that had been missing: a Goodness of Interpretability index quantifying how well the approximating tree reconstructs the ensemble's own proximity matrix, with a permutation test for significance. Interactive visualisation and a C++ backend with OpenMP parallelism arrived alongside, and support now spans ranger and CatBoost as well as the original targets.
◆ Where it's heading
Development has moved from producing an explanation to defending it. The GoI index and its permutation test change the package's claim from here is a tree that resembles your ensemble to here is how closely it resembles it and whether that could have happened by chance — the question a reviewer asks of any surrogate model. Around that, the work is engineering: the proximity matrix construction moved from R-level parallel loops into C++ with thread-level parallelism, and recent releases have been absorbing the awkwardness of supporting multiple ensemble backends, where a multi-class CatBoost objective returns a score matrix where a vector was expected. Interactive visNetwork output and standalone HTML export point at explanations meant to be shared rather than only inspected.
◆ Prediction
Given how much recent effort has gone into per-backend adapters, expect further work on ensemble compatibility; the entries do not indicate whether the interpretability index is heading toward comparing surrogate trees against each other.
Alternatives to bbk and e2tree
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 bbk or e2tree.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
Recent activity from bbk and e2tree
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agobbkBrazil and Mexico join, bringing survey expectations data ⚡
- 2mo agobbkCzech National Bank support lands with a broad parser repair
- 3mo agobbkIncremental retrieval generalised beyond the ECB endpoint
- 3mo agoe2treeCatBoost multi-class and loss-function handling repaired
- 4mo agobbkOpt-in response caching plus dimension introspection everywhere
- 4mo agoe2treeA significance-tested measure of explanation fidelity ⚡
- 10mo agobbkBank of Canada data and exchange rates added
- 11mo agobbkFour European central banks added; validation moves to checkmate
- 1y agoe2treeranger models supported
Frequently asked questions
What is the difference between bbk and e2tree?
Both compete on the same themes — r-package — within Analytics. bbk and e2tree 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 bbk better than e2tree?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bbk and e2tree 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 bbk?
Top bbk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbk alternatives" section above for the current picks, or visit /alternatives/bbk for the full list with editorial commentary on each.
What are the best alternatives to e2tree?
Top e2tree alternatives in Analytics are ranked by recent ship velocity. Browse the "e2tree alternatives" section above for the current picks, or visit /alternatives/e2tree for the full list with editorial commentary on each.