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 spatstat — 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.
The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
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.
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
The split is effectively complete and the umbrella's role has settled into coordination — tracking version dependencies across sub-packages and pointing users to them. The family has kept subdividing over this period, with spatstat.univar joining in 3.1-0. The one substantive user-facing addition here is documentation infrastructure: 3.3-0 added the ability to list the history of changes to a specific function, which is a navigational answer to a codebase now spread across many packages.
Expect this package's notes to continue summarising sub-package activity rather than carrying features of its own, since every release in this window does exactly that. Read spatstat.geom, spatstat.random and spatstat.model for the substance.
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 spatstat.
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.
See all qqman alternatives → · See all spatstat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. qqman and spatstat 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 spatstat 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 spatstat alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat alternatives" section above for the current picks, or visit /alternatives/spatstat-r for the full list with editorial commentary on each.