paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of enpls and gwasvcf — release velocity, themes, recent moves, and the top alternatives to consider.
enpls has not changed its statistics since 2016 — only its website, twice.
enpls implements ensemble partial least squares regression, with variants for feature selection, outlier detection and model applicability. Across the six most recent releases there is not one change to the modeling code. They cover a documentation website, a website URL change, a font stack, code indentation, a CI service, and most recently a GitHub Actions migration with an R CMD check note fix.
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.
enpls implements ensemble partial least squares regression, with variants for feature selection, outlier detection and model applicability. Across the six most recent releases there is not one change to the modeling code. They cover a documentation website, a website URL change, a font stack, code indentation, a CI service, and most recently a GitHub Actions migration with an R CMD check note fix.
The statistical work finished around version 5.6, which added cross-validation fold control and fixed component selection when the maximum was left unspecified. Everything since has kept the package installable and its docs online. The 2025 release arriving the same day as sibling package grex, with the same two fixes, confirms the pattern: these are maintainer sweeps across a portfolio, not attention to enpls specifically.
The next release will almost certainly be another CRAN or tooling fix. Six consecutive infrastructure-only releases across nine years give no basis for expecting new methods.
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 enpls or gwasvcf.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
grex is a lookup table with a version number — it ships when the annotation moves.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
See all enpls 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. enpls 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. enpls 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 enpls alternatives in Analytics are ranked by recent ship velocity. Browse the "enpls alternatives" section above for the current picks, or visit /alternatives/enpls 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.