Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of gwasvcf and hstats — release velocity, themes, recent moves, and the top alternatives to consider.
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.
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
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.
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
The structural work — the hstats_matrix object, quantile approximation, revised plotting — landed in 1.0.0 just outside this window, and nothing since has changed the package's shape. What continues is model-coverage plumbing: mlr3 classification modes, ranger survival behind a survival argument, and factor predictions added in 1.1.0 then removed again in 1.2.0. The most recent releases are compatibility-driven, tracking ggplot2 rather than the interaction statistics.
Expect the next release to be another dependency-compatibility pass or a new model backend working out of the box, rather than new interaction statistics.
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 gwasvcf or hstats.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all gwasvcf alternatives → · See all hstats alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gwasvcf and hstats 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. gwasvcf and hstats 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 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.
Top hstats alternatives in Analytics are ranked by recent ship velocity. Browse the "hstats alternatives" section above for the current picks, or visit /alternatives/hstats for the full list with editorial commentary on each.