EvoPhylo
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
A side-by-side editorial comparison of oblicubes and qtl — release velocity, themes, recent moves, and the top alternatives to consider.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
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.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
The package is finished and its maintainer is treating it that way. 1.0.0 removed the R 4.1 native pipe from examples specifically so earlier R versions could use it — reaching backward, not forward — and added image alt text. The only change since is swapping a deprecated dplyr call in examples.
Expect nothing beyond occasional dependency deprecation fixes; the release pattern shows a small, deliberately complete package being kept installable.
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.
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.
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.
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 oblicubes or qtl.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
treespace ships once every year or two, and only when CRAN or a user forces it.
Rpath 1.1.0 learns to read Ecopath's own files, easing migration off the desktop tool.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
See all oblicubes alternatives → · See all qtl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. oblicubes and qtl 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. oblicubes and qtl 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.
Top oblicubes alternatives in Analytics are ranked by recent ship velocity. Browse the "oblicubes alternatives" section above for the current picks, or visit /alternatives/oblicubes-r for the full list with editorial commentary on each.
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.