constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
A side-by-side editorial comparison of qqman and r5r — release velocity, themes, recent moves, and the top alternatives to consider.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
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.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
The real development window was 2014 to 2015. The 0.1.2 release did the substantive work, replacing the assumption that SNPs are evenly distributed across chromosomes and handing users control of axis limits, labels and log transformation; 0.1.3 then added annotation by p-value threshold and top-SNP-per-chromosome. After that the package stops. Notably, the archival 0.0.0 entry records that the original script had confidence intervals on QQ plots and richer highlighting than the released package ever regained.
With one packaging fix in the last decade, these entries support no prediction of further releases. The package reads as complete for its narrow purpose rather than abandoned mid-arc.
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 qqman or r5r.
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.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. qqman 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. qqman 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 qqman alternatives in Analytics are ranked by recent ship velocity. Browse the "qqman alternatives" section above for the current picks, or visit /alternatives/qqman-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.