paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
Comparison · Analytics
dipsaus vs qtl
A side-by-side editorial comparison of dipsaus and qtl — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
dipsaus vs qtl: at a glance
What is dipsaus?
dipsaus sheds five dependencies and rebuilds its native layer on Rcpp
dipsaus is a utility toolbox for R and Shiny developers — parallel helpers, fast map and queue wrappers, RStudio integrations, and custom Shiny inputs — and the foundation layer under the RAVE neuroimaging stack. The 0.3.x line dropped magrittr, remotes, glue, base64url and startup, moved off RcppParallel and TBB, and switched to Rcpp specifically to stop calling R's internal ENCLOS and CLOSENV interfaces. On the user-facing side it added fancyDirectoryInput, a Shiny widget for uploading whole directories with streaming and a progress bar.
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.
dipsaus vs qtl: editorial side-by-side
dipsaus
0.0ANALYTICS
dipsaus sheds five dependencies and rebuilds its native layer on Rcpp
◆ Current state
dipsaus is a utility toolbox for R and Shiny developers — parallel helpers, fast map and queue wrappers, RStudio integrations, and custom Shiny inputs — and the foundation layer under the RAVE neuroimaging stack. The 0.3.x line dropped magrittr, remotes, glue, base64url and startup, moved off RcppParallel and TBB, and switched to Rcpp specifically to stop calling R's internal ENCLOS and CLOSENV interfaces. On the user-facing side it added fancyDirectoryInput, a Shiny widget for uploading whole directories with streaming and a progress bar.
◆ Where it's heading
Two long-running threads run through every release: cut dependencies, and make asynchronous work in R less fragile. The package has been removing packages it once required — synchronicity, qs, RcppRedis, htmltools, stringr, now five more — while successively replacing its own async machinery (make_async_evaluator, then async_workers, then lapply_callr and lapply_async with automatic global handling). The Rcpp move adds a third pressure: staying inside R's supported C interfaces as the non-API surface is closed off.
◆ Prediction
The dependency-shedding pattern points at the remaining soft-deprecated pieces — dipsaus_lock/unlock and PersistContainer have both been marked for removal for several releases and are the obvious next things to go.
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.
Alternatives to dipsaus and qtl
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 dipsaus or qtl.
geodist
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors
errors keeps making uncertainty print the way each scientific field expects.
CMAQ
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls
enpls has not changed its statistics since 2016 — only its website, twice.
grex
grex is a lookup table with a version number — it ships when the annotation moves.
Recent activity from dipsaus and qtl
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agodipsausDirectory upload widget lands; native layer moves to Rcpp ⚡
- 8mo agoqtlRemove R_ext/PrtUtil.h include flagged by CRAN
- 8mo agoqtlClearer cim() error when multiple phenotypes are passed
- 1y agoqtlC memory calls migrated to R_Calloc/R_Realloc/R_Free
- 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
- 4y agodipsausrs_edit_file, constrained %OF% operator, nested rs_exec
- 4y agodipsausget_credential added; synchronicity dependency dropped
- 4y agodipsauslapply_callr replaces async_workers; qs and RcppRedis removed
- 5y agodipsausBackground job scheduling and parallel covariance helpers
- 6y agodipsausRStudio-aware helpers with console fallbacks
Frequently asked questions
What is the difference between dipsaus and qtl?
Both compete on the same themes — r-package — within Analytics. dipsaus 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.
Is dipsaus better than qtl?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dipsaus 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.
What are the best alternatives to dipsaus?
Top dipsaus alternatives in Analytics are ranked by recent ship velocity. Browse the "dipsaus alternatives" section above for the current picks, or visit /alternatives/dipsaus-r for the full list with editorial commentary on each.
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.