EvoPhylo
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
Comparison · Analytics
qtl vs redist
A side-by-side editorial comparison of qtl and redist — release velocity, themes, recent moves, and the top alternatives to consider.
qtl vs redist: at a glance
What is qtl?
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
R/qtl is the long-established R package for QTL mapping in experimental crosses, covering interval mapping, composite interval mapping, multiple-QTL model fitting and the associated cross data formats. Nothing in the recent release history adds capability. Version 1.74 removes an include that started warning on CRAN, 1.72 improves an error message in cim(), and 1.70 migrates the C code from Calloc/Realloc/Free to their R_-prefixed equivalents for R-devel.
What is redist?
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.
qtl vs redist: editorial side-by-side
qtl
0.0ANALYTICS
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
◆ Current state
R/qtl is the long-established R package for QTL mapping in experimental crosses, covering interval mapping, composite interval mapping, multiple-QTL model fitting and the associated cross data formats. Nothing in the recent release history adds capability. Version 1.74 removes an include that started warning on CRAN, 1.72 improves an error message in cim(), and 1.70 migrates the C code from Calloc/Realloc/Free to their R_-prefixed equivalents for R-devel.
◆ Where it's heading
The package is being maintained, not developed. The work divides cleanly into keeping the compiled code building against successive R and toolchain versions, and fixing narrow bugs reported through the issue tracker. The C-level migrations in particular are compliance with R's tightening of its C interface rather than anything chosen. Users should read the stability as maturity: the analysis surface has been fixed for years and the maintainer is keeping it installable.
◆ Prediction
R has continued to restrict its non-API C entry points, and this package has already made two such migrations, so further compile-time compliance work is the most likely content of the next release.
redist
0.0ANALYTICS
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
◆ Current state
redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.
◆ Where it's heading
The direction is toward exactness and throughput at once — the new kernel is described as both eliminating approximation error and costing far less computation, and successive releases keep adding parallelism, most recently to the flip algorithm. Feature growth has moved into the optimization side, where short-burst gained multiple independent scorers and a Pareto frontier. The release notes are not a reliable ledger: 4.3.1 ships the identical text as 4.3.0.
◆ Prediction
Expect the remaining single-threaded algorithms to gain the chains-style parallelism that flip just received, following the pattern SMC established several releases ago.
Alternatives to qtl and redist
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 qtl or redist.
treespace
treespace ships once every year or two, and only when CRAN or a user forces it.
Rpath
Rpath 1.1.0 learns to read Ecopath's own files, easing migration off the desktop tool.
TAF
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist
parallelDist is in pure preservation mode — one build fix every few years.
cairo
Cairo finally catches R's graphics engine, all the way to GE API 16.
Recent activity from qtl and redist
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoredistParallel chains for redist_flip()
- 6mo agoredistPatch release reusing the 4.3.0 notes
- 8mo agoqtlRemove R_ext/PrtUtil.h include flagged by CRAN
- 8mo agoqtlClearer cim() error when multiple phenotypes are passed
- 10mo agoredistSMC backward kernel removes label-counting approximation error
- 1y agoqtlC memory calls migrated to R_Calloc/R_Realloc/R_Free
- 2y agoredistMulti-objective short-burst search with Pareto frontier
- 2y agoqtlFix Rprintf call and remaining compiler warnings
- 2y agoqtlFix summary.scanone() thresholds and csvs phenotype reading
- 3y agoqtlFix addint()/addcovarint() with X chromosome QTL and missing phenotypes
- 3y agoredistredist_ci interface and faster loop-erased random walk
- 4y agoredistredist_constr() unifies constraints and admits user-defined ones ⚡
Frequently asked questions
What is the difference between qtl and redist?
They serve adjacent needs but don't currently overlap on shipped themes. qtl and redist 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 qtl better than redist?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qtl and redist 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 qtl?
Top qtl alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl alternatives" section above for the current picks, or visit /alternatives/qtl-r for the full list with editorial commentary on each.
What are the best alternatives to redist?
Top redist alternatives in Analytics are ranked by recent ship velocity. Browse the "redist alternatives" section above for the current picks, or visit /alternatives/redist-r for the full list with editorial commentary on each.