rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
epiflows vs gwasvcf
A side-by-side editorial comparison of epiflows and gwasvcf — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:rmaintenance
epiflows vs gwasvcf: at a glance
What is epiflows?
epiflows has shipped four releases in eight years, none of which changed the code.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
What is gwasvcf?
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.
epiflows vs gwasvcf: editorial side-by-side
epiflows
0.0ANALYTICS
epiflows has shipped four releases in eight years, none of which changed the code.
◆ Current state
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
◆ Where it's heading
The package is being kept installable rather than developed. The one recent release is dependency maintenance contributed from outside, which is the pattern for RECON-era epidemiology packages that have outlived their original project funding. Two separate entries are both labelled version 0.2.1, so even the version history is not a reliable guide to what changed.
◆ Prediction
Any further releases will most likely be more deprecation cleanup to keep the package on CRAN; there is nothing in the record suggesting active development has resumed.
gwasvcf
0.0ANALYTICS
gwasvcf has stopped adding features and now just keeps proxy matching from failing.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to epiflows and gwasvcf
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 epiflows or gwasvcf.
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
broman
A statistician's personal toolbox, growing one plotting utility at a time
qtl
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all epiflows alternatives → · See all gwasvcf alternatives →
Recent activity from epiflows and gwasvcf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agogwasvcfproxy_match() gains a fallback VCF construction path
- 5mo agoepiflowsDeprecated ggplot2 and tibble calls replaced
- 8mo agogwasvcfproxy_match() handles multi-sample VCFs
- 1y agogwasvcfsqlite3 declared in SystemRequirements
- 1y agogwasvcfMessage fix in get_ld_proxies()
- 2y agogwasvcfgwasvcf_to_summaryset() bridges to gwasglue2
- 3y agoepiflowsRoxygen patch for CRAN checks
- 7y agoepiflowsFirst Zenodo archival tag
- 8y agoepiflowsFirst CRAN release
Frequently asked questions
What is the difference between epiflows and gwasvcf?
Both compete on the same themes — r, maintenance — within Analytics. epiflows 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.
Is epiflows better than gwasvcf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epiflows 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.
What are the best alternatives to epiflows?
Top epiflows alternatives in Analytics are ranked by recent ship velocity. Browse the "epiflows alternatives" section above for the current picks, or visit /alternatives/epiflows-r for the full list with editorial commentary on each.
What are the best alternatives to gwasvcf?
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.