n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of filearray and icesSAG — 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.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.
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.
icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.
The package is consolidating onto the shared ices-tools stack rather than carrying its own machinery — authentication moved to icesConnect, validation to icesDatsu, and the icesVocab dependency was dropped once it was no longer needed. Alongside that, redundant graph functions were deprecated and caching was added to reduce load on the server. Releases are infrequent and driven by upstream API changes.
Expect the next release to follow whatever the ICES service or the sibling ices-tools packages change next, rather than introducing new analysis capability of its own.
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 icesSAG.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all filearray alternatives → · See all icesSAG 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 icesSAG 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 icesSAG 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 icesSAG alternatives in Analytics are ranked by recent ship velocity. Browse the "icesSAG alternatives" section above for the current picks, or visit /alternatives/icessag for the full list with editorial commentary on each.