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 tmap — 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.
Two years after a from-scratch rewrite, tmap is filling in the layers v4 promised.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
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.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
The extension mechanism introduced in 4.0 is where the interesting work is migrating: PMTiles support arrived through a separate experimental tmap.sources package, mode cycling became configurable via tmap_mode_pool() so packages like tmap.mapgl can register themselves, and shiny dispatch methods were added specifically to let other modes integrate. The core package is increasingly a rendering contract that satellite packages plug into.
Expect more rendering backends to land as sibling packages rather than in tmap itself, with the core continuing to absorb the dispatch and mode-management plumbing they need.
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 tmap.
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 tmap 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 tmap 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 tmap alternatives in Analytics are ranked by recent ship velocity. Browse the "tmap alternatives" section above for the current picks, or visit /alternatives/tmap-r for the full list with editorial commentary on each.