qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of dietr and geodist — 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.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
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.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
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 geodist.
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.
See all dietr alternatives → · See all geodist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. dietr and geodist 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 geodist 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 geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.