tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of filearray and paleobuddy — release velocity, themes, recent moves, and the top alternatives to consider.
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.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
paleobuddy simulates diversification, fossil records and phylogenetic trees, with rates that can be arbitrary functions of time — its founding idea, implemented through rexp.var() generalizing exponential and Weibull draws. The 1.1.0 release adds state-dependent speciation and extinction simulation at roughly MuHiSSE generality, and lets simulations stop at a target number of extant species instead of conditioning on time.
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.
paleobuddy simulates diversification, fossil records and phylogenetic trees, with rates that can be arbitrary functions of time — its founding idea, implemented through rexp.var() generalizing exponential and Weibull draws. The 1.1.0 release adds state-dependent speciation and extinction simulation at roughly MuHiSSE generality, and lets simulations stop at a target number of extant species instead of conditioning on time.
Releases track the maintainer's publications rather than a product cadence — 1.0.0 accompanied the MEE manuscript, 1.0.0.1 exists purely as a Zenodo citation anchor, and 1.1.0 is stated as going with a paper on SSE model accuracy for trees including fossil data. That framing sets the direction: the package grows whichever capability the next study needs to test. The stated SSE limits, no quantitative traits and no cladogenetic transitions, mark exactly where that boundary currently sits.
Quantitative traits and cladogenetic transitions are named as missing, which makes them the obvious next targets, though on this history the timing will follow a paper rather than a roadmap.
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 filearray or paleobuddy.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all filearray alternatives → · See all paleobuddy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. filearray and paleobuddy 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. filearray and paleobuddy 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 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.
Top paleobuddy alternatives in Analytics are ranked by recent ship velocity. Browse the "paleobuddy alternatives" section above for the current picks, or visit /alternatives/paleobuddy for the full list with editorial commentary on each.