tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of filearray and geodist — 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.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
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.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
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 geodist.
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 geodist 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 geodist 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 geodist 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 geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.