qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of ggdemetra and gwasvcf — release velocity, themes, recent moves, and the top alternatives to consider.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
gwasvcf has stopped adding features and now just keeps proxy matching from failing.
gwasvcf reads and queries GWAS summary statistics stored as VCF, with LD proxy lookup as its most-used entry point. Every release in the visible window is a fix, and all but one land in or around proxy_match(). The last functional addition was gwasvcf_to_summaryset() in 0.1.2, which hands data to gwasglue2 rather than doing new work here.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.
Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.
gwasvcf reads and queries GWAS summary statistics stored as VCF, with LD proxy lookup as its most-used entry point. Every release in the visible window is a fix, and all but one land in or around proxy_match(). The last functional addition was gwasvcf_to_summaryset() in 0.1.2, which hands data to gwasglue2 rather than doing new work here.
The package is in custodial maintenance inside the MRC IEU OpenGWAS stack, and its releases are reactive: each one answers a specific user-reported failure, credited to the reporter. The 0.1.6 pattern is telling — rather than replace the proxy VCF construction, it keeps the original path and adds a fallback only for inputs that fail, so existing results are left bit-for-bit unchanged.
Expect further narrow robustness fixes to proxy_match() driven by user-reported VCF shapes; nothing in the entries suggests new analysis capability is being built here rather than in gwasglue2.
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 ggdemetra or gwasvcf.
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 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 ggdemetra alternatives → · See all gwasvcf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggdemetra and gwasvcf 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. ggdemetra and gwasvcf 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 ggdemetra alternatives in Analytics are ranked by recent ship velocity. Browse the "ggdemetra alternatives" section above for the current picks, or visit /alternatives/ggdemetra for the full list with editorial commentary on each.
Top gwasvcf alternatives in Analytics are ranked by recent ship velocity. Browse the "gwasvcf alternatives" section above for the current picks, or visit /alternatives/gwasvcf for the full list with editorial commentary on each.