paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of qtl and rosm — release velocity, themes, recent moves, and the top alternatives to consider.
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.
rosm 0.3.0 silently deprecates its entire API and rebuilds on wk and curl
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
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.
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
The package is being brought back from dormancy on modern foundations rather than extended. rgdal's retirement forced the issue, and the maintainer used it to replace the download path with concurrent curl requests and to hand geometry handling to wk. What follows is consolidation: dead built-in tile sources are being tested around rather than replaced, which leaves the source registry as the obvious unfinished edge.
The dead Bing and Stamen endpoints are currently skipped rather than fixed, so the next release most likely prunes or re-points the built-in tile source list and continues retiring the silently deprecated functions.
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 rosm.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. qtl and rosm 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. qtl and rosm 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 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.
Top rosm alternatives in Analytics are ranked by recent ship velocity. Browse the "rosm alternatives" section above for the current picks, or visit /alternatives/rosm for the full list with editorial commentary on each.