paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of EvoPhylo and filearray — 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 on-disk array layer under RAVE spends its releases hunting segfaults.
filearray stores large arrays on disk and reads them back with little memory overhead, serving as the storage substrate for the RAVE intracranial EEG stack. The 0.2.2 release fixes out-of-bound indexing that caused segfaults along certain margins and an ASAN-flagged signed integer overflow in the load path. The user-facing API has been stable since 0.1.6.
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.
filearray stores large arrays on disk and reads them back with little memory overhead, serving as the storage substrate for the RAVE intracranial EEG stack. The 0.2.2 release fixes out-of-bound indexing that caused segfaults along certain margins and an ASAN-flagged signed integer overflow in the load path. The user-facing API has been stable since 0.1.6.
This is infrastructure whose release history reads as a memory-safety log: unprotected C++ variables, buffer sizes exceeding array length, allocations one byte short, endianness on big-endian platforms, and now out-of-bound margins caught by sanitizers. The one sustained feature direction is reducing the cost of operating on arrays too large for memory — lazy operator evaluation through a proxy class, fmap-style application, and marginal collapse. Portability work has steadily removed hard requirements, dropping the C++11 declaration and swapping OpenMP for TinyThreads to get parallelism on macOS.
Expect continued sanitizer-driven patches rather than new interfaces; the three-year gap before 0.2.2 suggests releases now arrive only when a crash or a CRAN check demands one.
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 filearray.
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 filearray 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 filearray 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 filearray 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 filearray alternatives in Analytics are ranked by recent ship velocity. Browse the "filearray alternatives" section above for the current picks, or visit /alternatives/filearray-r for the full list with editorial commentary on each.