← Back to home
Comparison · Analytics

qtl2 vs treasury

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

Shared themes:r-package

qtl2 vs treasury: at a glance

Featureqtl2treasury
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesqtl-mapping, statistical-genetics, bioinformatics, r-packagetreasury-rates, fixed-income, r-package, api-wrapper
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is treasury?

A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.

treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.

Read the full treasury trajectory →

qtl2 vs treasury: editorial side-by-side

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.

T
treasury
ANALYTICS
0.0

A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.

◆ Current state

treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.

◆ Where it's heading

Endpoint coverage looks essentially complete, so the work has moved to the metadata a downstream analyst needs to join and audit results — cusip and maturity_date on bill quotes, the feed's updated_at stamp, and the extrapolation factor behind 2002-2006 long-term rate estimates. Error handling is tightening in the same direction: an out-of-range month now fails with a message instead of quietly returning nothing. That is the profile of a wrapper moving from coverage to correctness, where the remaining bugs are the subtle ones that only surface in other people's locales.

◆ Prediction

Expect further column-level enrichment and input validation on the endpoints already covered rather than new data sources, since the structural pieces — data.table returns and caching — are already in place.

Alternatives to qtl2 and treasury

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

See all qtl2 alternatives → · See all treasury alternatives →

Recent activity from qtl2 and treasury

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

  1. 27d agoqtl2chr_lengths() extended to cross2 objects
  2. 1mo agotreasuryBill rates gain CUSIP and maturity date; locale bug fixed
  3. 1mo agoqtl2A genome scan that takes your own likelihood function
  4. 2mo agoqtl2Hotspot counting and cis-trans plots for eQTL studies
  5. 3mo agoqtl2Confidence interval plotting, plus a documentation correction
  6. 4mo agotreasuryOptional response caching, one day by default
  7. 11mo agotreasuryRate functions renamed to singular for consistency
  8. 1y agotreasuryEvery function now returns a data.table
  9. 1y agoqtl2Finer-grained parallelism for kinship-based scans
  10. 1y agoqtl2CSV readers renamed to avoid the readr collision
  11. 2y agotreasuryHQM, coupon-issue and breakeven inflation curves added

Frequently asked questions

What is the difference between qtl2 and treasury?

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 qtl2 better than treasury?

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

What are the best alternatives to treasury?

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