← Back to home
Comparison · Analytics

bbk vs qtl2

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

Shared themes:r-package

bbk vs qtl2: at a glance

Featurebbkqtl2
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themescentral-bank-data, macro-statistics, r-package, api-wrapperqtl-mapping, statistical-genetics, bioinformatics, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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.

Read the full bbk trajectory →

What is qtl2?

The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.

qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.

Read the full qtl2 trajectory →

bbk vs qtl2: editorial side-by-side

B
bbk
ANALYTICS
0.0

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.

Q
qtl2
ANALYTICS
2.5

The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.

◆ Current state

qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.

◆ Where it's heading

The eQTL and pQTL direction is the clearest thread — cis-trans plots, hotspot counting over a sliding window, multi-trait scan heat maps, and genome-wide genotype plots all arrived together, which is the toolkit an experiment with thousands of traits needs rather than one with a handful. Running underneath it is a steady generalisation of the core: a scan function that accepts an arbitrary likelihood, permutations that work with alternative scan functions, full variance-covariance output from single-position fits. Performance and parallelism get attention each cycle, including a more considerate default that leaves one core free. The rest is the ordinary maintenance of a long-lived package — renames to avoid tidyverse collisions, compiler warnings, and correctness fixes on specific cross types.

◆ Prediction

With scan1gen and permutation support for alternative scan functions in place, the natural next step is more model types built on that hook rather than more special-cased scan functions; the entries do not indicate which models are planned.

Alternatives to bbk and qtl2

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 qtl2.

See all bbk alternatives → · See all qtl2 alternatives →

Recent activity from bbk and qtl2

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

  1. 27d agoqtl2chr_lengths() extended to cross2 objects
  2. 1mo agobbkBrazil and Mexico join, bringing survey expectations data
  3. 1mo agoqtl2A genome scan that takes your own likelihood function
  4. 2mo agobbkCzech National Bank support lands with a broad parser repair
  5. 2mo agoqtl2Hotspot counting and cis-trans plots for eQTL studies
  6. 3mo agobbkIncremental retrieval generalised beyond the ECB endpoint
  7. 3mo agoqtl2Confidence interval plotting, plus a documentation correction
  8. 4mo agobbkOpt-in response caching plus dimension introspection everywhere
  9. 10mo agobbkBank of Canada data and exchange rates added
  10. 11mo agobbkFour European central banks added; validation moves to checkmate
  11. 1y agoqtl2Finer-grained parallelism for kinship-based scans
  12. 1y agoqtl2CSV readers renamed to avoid the readr collision

Frequently asked questions

What is the difference between bbk and qtl2?

Both compete on the same themes — r-package — within Analytics. qtl2 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 bbk better than qtl2?

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

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