← Back to home
Comparison · Analytics

haze vs qtl2fst

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

Shared themes:r-package

haze vs qtl2fst: at a glance

Featurehazeqtl2fst
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesneuroimaging, mesh-processing, interpolation, r-packager-package, genetics, memory-efficiency, on-disk-storage
Last editorial update2h ago40m ago
WebsiteVisit →Visit →

What is haze?

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

Read the full haze trajectory →

What is qtl2fst?

The out-of-memory backend for R/qtl2, feature-complete since 2020 and now purely on upkeep

qtl2fst backs R/qtl2 genotype probabilities with on-disk fst files so large crosses don't have to fit in RAM. Its defining release was 0.22 in 2020, which added calc_genoprob_fst() and genoprob_to_alleleprob_fst() to fuse calculation and storage in one step. The five releases since are documentation links, directory-creation robustness, a Windows example fix, and — in 0.32 — a change to how cores=0 is interpreted.

Read the full qtl2fst trajectory →

haze vs qtl2fst: editorial side-by-side

H
haze
ANALYTICS
2.5

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

◆ Current state

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

◆ Where it's heading

The July 2026 release arrived 56 minutes after its sibling regfusionr 0.3.0 from the same maintainer, which is the tell: this is a maintainer sweeping a set of related neuroimaging packages back into working order, not independent development on haze itself. haze is the dependency, regfusionr the consumer, and the substantive work sits on the regfusionr side. The off-by-one correction is the only change here that alters results.

◆ Prediction

Expect haze to move only when a downstream dfsp-spirit package needs it to — its cadence is driven by the sibling packages, not by its own roadmap.

Q
qtl2fst
ANALYTICS
0.0

The out-of-memory backend for R/qtl2, feature-complete since 2020 and now purely on upkeep

◆ Current state

qtl2fst backs R/qtl2 genotype probabilities with on-disk fst files so large crosses don't have to fit in RAM. Its defining release was 0.22 in 2020, which added calc_genoprob_fst() and genoprob_to_alleleprob_fst() to fuse calculation and storage in one step. The five releases since are documentation links, directory-creation robustness, a Windows example fix, and — in 0.32 — a change to how cores=0 is interpreted.

◆ Where it's heading

The package has settled into the role of a stable satellite of R/qtl2: it tracks the parent package's conventions rather than setting its own. The cores=0 change in 0.32 arrived alongside the identical change in qtl2convert, so the parallel-computing default is being standardized across the maintainer's packages at once. Release intervals have stretched from months to years.

◆ Prediction

Further releases will most likely mirror changes originating in R/qtl2 or CRAN checks, in the same follow-the-parent pattern as 0.24 and 0.32.

Alternatives to haze and qtl2fst

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 haze or qtl2fst.

See all haze alternatives → · See all qtl2fst alternatives →

Recent activity from haze and qtl2fst

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

  1. 18d agohazeVersion 0.3.0 -- Fixes and modernization
  2. 1mo agoqtl2fstcores=0 now leaves one core free instead of taking all
  3. 1y agoqtl2fstWindows fix for the replace_path() example
  4. 2y agoqtl2fstDocumentation link fix
  5. 4y agohazev0.2.0 -- kdtrees
  6. 4y agohazev0.1.0: Initial release
  7. 4y agoqtl2fstCreates missing directories instead of erroring out
  8. 5y agoqtl2fstTest coverage for qtl2 functions against fst-backed probabilities
  9. 6y agoqtl2fstDocumentation and metadata cleanup for CRAN

Frequently asked questions

What is the difference between haze and qtl2fst?

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

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

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

What are the best alternatives to qtl2fst?

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