tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of ieegio and parglm — release velocity, themes, recent moves, and the top alternatives to consider.
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
ieegio handles file I/O and volume manipulation for intracranial EEG and neuroimaging data in R. Only one release is on record, 0.1.0 from May 2026, so there is no cadence to read yet. Its content is a mix of new volume-authoring capability and format-level correctness fixes.
Under a new maintainer, parglm traded raw speed work for glm parity and memory safety
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
ieegio handles file I/O and volume manipulation for intracranial EEG and neuroimaging data in R. Only one release is on record, 0.1.0 from May 2026, so there is no cadence to read yet. Its content is a mix of new volume-authoring capability and format-level correctness fixes.
The release points at two audiences at once: burn_curve() writes electrode trajectories — depth/sEEG leads, DBS shafts — into a volume from start and end positions in native RAS coordinates, with a merge mode so trajectories compost onto an existing volume rather than overwriting it. Separately, a base R graphics plot method for surfaces provides a path for environments without WebGL, where the default r3js renderer cannot run. Format work covers BCI2000 and BrainVision channel lookup by label and a quaternion handedness fix aligning with FreeSurfer conventions.
A single release gives no basis for predicting cadence. The FreeSurfer alignment and multi-format channel handling suggest interoperability with established neuroimaging toolchains is the near-term priority.
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
The arc runs from performance to trustworthiness. 0.1.9 was a large optimization release — deque-based task queues, fused memory passes, upper-triangle-only Fisher information, thread_local IDs — plus ecosystem integration with sandwich and gtsummary. 0.2.0 then fixed an out-of-bounds write triggered by small block_size values and a path where a non-finite working response could poison the QR decomposition, and brought response-type handling in line with glm().
With the memory-safety issues addressed and glm parity closed for binomial responses, further work is likely to extend family coverage or the benchmark suite rather than revisit the threading model. The C++17 requirement set at 0.1.8 gives room for more aggressive optimization if the maintainer returns to that.
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 ieegio or parglm.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all ieegio alternatives → · See all parglm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. ieegio and parglm 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. ieegio and parglm 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 ieegio alternatives in Analytics are ranked by recent ship velocity. Browse the "ieegio alternatives" section above for the current picks, or visit /alternatives/ieegio for the full list with editorial commentary on each.
Top parglm alternatives in Analytics are ranked by recent ship velocity. Browse the "parglm alternatives" section above for the current picks, or visit /alternatives/parglm for the full list with editorial commentary on each.