qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
Comparison · Analytics
filearray vs ggdemetra
A side-by-side editorial comparison of filearray and ggdemetra — release velocity, themes, recent moves, and the top alternatives to consider.
filearray vs ggdemetra: at a glance
What is filearray?
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.
What is ggdemetra?
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
filearray vs ggdemetra: editorial side-by-side
filearray
0.0ANALYTICS
The on-disk array layer under RAVE spends its releases hunting segfaults.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
ggdemetra
0.0ANALYTICS
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
◆ Current state
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
◆ Where it's heading
The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.
◆ Prediction
Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.
Alternatives to filearray and ggdemetra
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 ggdemetra.
constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
austraits
The R client for AusTraits spends its releases chasing the dataset it reads.
fossilsim
A fossil-record simulator that quietly grew a trait-evolution engine.
tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all filearray alternatives → · See all ggdemetra alternatives →
Recent activity from filearray and ggdemetra
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agofilearraySegfault on out-of-bound margins fixed
- 2y agoggdemetrasiratio() fix when TRAMO-SEATS exports no seasonal component
- 2y agoggdemetraraw() replaces y_forecast(); new init_ggplot() helper
- 2y agoggdemetraRe-tagged moments later as 0.2.7
- 3y agofilearrayLazy operator evaluation and macOS parallelism
- 3y agoggdemetraSI ratio plotting functions land
- 3y agofilearraySequential read bug in fmap corrected
- 4y agofilearrayPartition limit removed by opening files on demand
- 4y agofilearrayHeader signatures and symbolic link detection
- 4y agofilearrayFlush timing left to the operating system
- 5y agoggdemetrats2df() conversion helper and geom_outlier date fix
- 6y agoggdemetrageom_arima no longer recomputes the model
Frequently asked questions
What is the difference between filearray and ggdemetra?
They serve adjacent needs but don't currently overlap on shipped themes. filearray and ggdemetra 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.
Is filearray better than ggdemetra?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. filearray and ggdemetra 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.
What are the best alternatives to filearray?
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.
What are the best alternatives to ggdemetra?
Top ggdemetra alternatives in Analytics are ranked by recent ship velocity. Browse the "ggdemetra alternatives" section above for the current picks, or visit /alternatives/ggdemetra for the full list with editorial commentary on each.