paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of EvoPhylo and NWCTrends — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The salmon status-review trend package, maintained one federal review cycle at a time
NWCTrends fits multivariate state-space trend models to Pacific salmon population data and generates the tables and figures used in NOAA Northwest Fisheries Science Center viability and status reviews. Its release history maps onto those review cycles rather than a development calendar: v1.0 carries the 2015 review code, v1.25 the 2020 review, v1.30 the changes since. The 2026 v1.31 is internal restructuring and a dependency swap.
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.
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.
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.
NWCTrends fits multivariate state-space trend models to Pacific salmon population data and generates the tables and figures used in NOAA Northwest Fisheries Science Center viability and status reviews. Its release history maps onto those review cycles rather than a development calendar: v1.0 carries the 2015 review code, v1.25 the 2020 review, v1.30 the changes since. The 2026 v1.31 is internal restructuring and a dependency swap.
Development is driven by reproducibility of a specific government reporting product, so most work goes into making the report generation configurable and the fitting assumptions explicit rather than into new modelling. The 2020 cycle removed hard-coded per-population hacks and made the fitting window an explicit argument; the 2023 cycle moved plot styling into package options and clarified how missing data and zeros are handled in the published tables.
The cadence suggests the next substantive release arrives with the next status review rather than before it, most likely continuing the move of report parameters out of function signatures and into structured configuration.
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 NWCTrends.
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.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
See all EvoPhylo alternatives → · See all NWCTrends alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. EvoPhylo and NWCTrends 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. EvoPhylo and NWCTrends 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 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.
Top NWCTrends alternatives in Analytics are ranked by recent ship velocity. Browse the "NWCTrends alternatives" section above for the current picks, or visit /alternatives/nwctrends-r for the full list with editorial commentary on each.