← Back to home
Comparison · Analytics

EvoPhylo vs gwasvcf

A side-by-side editorial comparison of EvoPhylo and gwasvcf — release velocity, themes, recent moves, and the top alternatives to consider.

EvoPhylo vs gwasvcf: at a glance

FeatureEvoPhylogwasvcf
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesphylogenetics, bayesian-inference, beast2, mrbayesr, genomics, gwas, bioinformatics
Last editorial update48m ago2h ago
WebsiteVisit →Visit →

What is EvoPhylo?

EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.

EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.

Read the full EvoPhylo trajectory →

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.

Read the full gwasvcf trajectory →

EvoPhylo vs gwasvcf: editorial side-by-side

E
EvoPhylo
ANALYTICS
0.0

EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.

◆ Current state

EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.

◆ Where it's heading

The package's substantive arc ended with the 0.3.2 publication release, which arrived with peer-review revisions and three first-time contributors — the shape of software built to accompany a paper. What follows is thin: a MrBayes plotting correction in 0.3.3, then a two-year gap and a release with no described contents. The August 2025 entry may contain real work, but the notes give a reader nothing to judge.

◆ Prediction

Without release notes on the latest version there is no observable basis for predicting the next move; the two-year gap before it suggests activity tied to specific research needs rather than a maintenance cadence.

G
gwasvcf
ANALYTICS
0.0

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 EvoPhylo 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 EvoPhylo or gwasvcf.

See all EvoPhylo alternatives → · See all gwasvcf alternatives →

Recent activity from EvoPhylo and gwasvcf

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agogwasvcfproxy_match() gains a fallback VCF construction path
  2. 8mo agogwasvcfproxy_match() handles multi-sample VCFs
  3. 11mo agoEvoPhyloEvoPhylo v. 0.3.5
  4. 1y agogwasvcfsqlite3 declared in SystemRequirements
  5. 1y agogwasvcfMessage fix in get_ld_proxies()
  6. 2y agogwasvcfgwasvcf_to_summaryset() bridges to gwasglue2
  7. 3y agoEvoPhyloEvoPhylo 0.3.3 fixes back-rate plots for MrBayes
  8. 3y agoEvoPhyloEvoPhylo 0.3.2 adds BEAST2 support for FBD and rates

Frequently asked questions

What is the difference between EvoPhylo and gwasvcf?

They serve adjacent needs but don't currently overlap on shipped themes. EvoPhylo 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 EvoPhylo better than gwasvcf?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EvoPhylo 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 EvoPhylo?

Top EvoPhylo alternatives in Analytics are ranked by recent ship velocity. Browse the "EvoPhylo alternatives" section above for the current picks, or visit /alternatives/evophylo 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.