qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of dietr and r5r — release velocity, themes, recent moves, and the top alternatives to consider.
A fish diet package whose release history is really a record of surviving rfishbase.
dietr computes diet and trophic indices for fish from FishBase-style data, including electivity measures and composite indices. Its recent releases exist because upstream rfishbase changes repeatedly broke it — the latest pair restore functionality after a break severe enough to get the package removed from CRAN, while adding GII, MFI and Windell significance to the composite indices. The 1.1.6-1 patch restates the same notes as 1.1.6.
r5r's jump to JDK 21 fixed Apple Silicon and broke everyone's toolchain at once.
r5r runs Conveyal's R5 routing engine from R for multimodal travel-time matrices, accessibility measures and isochrones. The current line requires JDK 21 and R5 v7.1, stores the engine jar under a managed user directory, and detects when a chosen date has no transit service instead of returning silent nonsense. Isochrones can now be returned as polygons rather than lines.
dietr computes diet and trophic indices for fish from FishBase-style data, including electivity measures and composite indices. Its recent releases exist because upstream rfishbase changes repeatedly broke it — the latest pair restore functionality after a break severe enough to get the package removed from CRAN, while adding GII, MFI and Windell significance to the composite indices. The 1.1.6-1 patch restates the same notes as 1.1.6.
Almost every release in this window names an upstream dependency as its cause: rfishbase updates in four of them, duckdb in another. The genuine methodological additions arrive bundled inside those repair releases rather than on their own. That is a fragile position for a package whose core value is convenient access to a remote database.
The next release most likely follows the next rfishbase change; new indices will probably continue to ride along with compatibility repairs.
r5r runs Conveyal's R5 routing engine from R for multimodal travel-time matrices, accessibility measures and isochrones. The current line requires JDK 21 and R5 v7.1, stores the engine jar under a managed user directory, and detects when a chosen date has no transit service instead of returning silent nonsense. Isochrones can now be returned as polygons rather than lines.
Development alternates between tracking upstream R5 and smoothing the rough edges its Java dependency creates. The v2.0 release was the pivotal one: raising the JDK floor was a breaking change, but it is what resolved the Mac ARM incompatibility and unblocked users on modern hardware. Since then the work has returned to routing outputs and error handling.
Expect further upstream R5 tracking plus incremental isochrone and accessibility options; the JDK floor has just been reset, so another runtime break is unlikely soon.
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 dietr or r5r.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. dietr and r5r 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. dietr and r5r 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 dietr alternatives in Analytics are ranked by recent ship velocity. Browse the "dietr alternatives" section above for the current picks, or visit /alternatives/dietr-r for the full list with editorial commentary on each.
Top r5r alternatives in Analytics are ranked by recent ship velocity. Browse the "r5r alternatives" section above for the current picks, or visit /alternatives/r5r-r for the full list with editorial commentary on each.