qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of r5r and symengine — release velocity, themes, recent moves, and the top alternatives to consider.
r5r's jump to JDK 21 fixed Apple Silicon and broke everyone's toolchain at once.
r5r runs Conveyal's R5 routing engine from R for multimodal travel-time matrices, accessibility measures and isochrones. The current line requires JDK 21 and R5 v7.1, stores the engine jar under a managed user directory, and detects when a chosen date has no transit service instead of returning silent nonsense. Isochrones can now be returned as polygons rather than lines.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
symengine gives R access to the SymEngine computer algebra core for symbolic expressions, matrices and sets. The tracked feed carries the upstream C++ library's releases rather than R-binding changes, so what shows here is core work: parser fixes, locale-independent double parsing, an SOVERSION bump and matrix transpose corrections. Feature growth in the core has slowed considerably since the 0.9 and 0.10 releases.
r5r runs Conveyal's R5 routing engine from R for multimodal travel-time matrices, accessibility measures and isochrones. The current line requires JDK 21 and R5 v7.1, stores the engine jar under a managed user directory, and detects when a chosen date has no transit service instead of returning silent nonsense. Isochrones can now be returned as polygons rather than lines.
Development alternates between tracking upstream R5 and smoothing the rough edges its Java dependency creates. The v2.0 release was the pivotal one: raising the JDK floor was a breaking change, but it is what resolved the Mac ARM incompatibility and unblocked users on modern hardware. Since then the work has returned to routing outputs and error handling.
Expect further upstream R5 tracking plus incremental isochrone and accessibility options; the JDK floor has just been reset, so another runtime break is unlikely soon.
symengine gives R access to the SymEngine computer algebra core for symbolic expressions, matrices and sets. The tracked feed carries the upstream C++ library's releases rather than R-binding changes, so what shows here is core work: parser fixes, locale-independent double parsing, an SOVERSION bump and matrix transpose corrections. Feature growth in the core has slowed considerably since the 0.9 and 0.10 releases.
The upstream core has moved from adding capability — serialization, a first simplify(), set types, matrix expressions, LLVM support — toward maintenance: build fixes, dependency support such as Flint3, and correctness patches. For R users the practical consequence is that new symbolic features arrive only as fast as the binding exposes them, which this feed does not report on.
Expect further upstream maintenance releases tracking LLVM and Flint versions; nothing in these notes signals a new capability push.
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 r5r or symengine.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all r5r alternatives → · See all symengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. r5r and symengine 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. r5r and symengine 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 r5r alternatives in Analytics are ranked by recent ship velocity. Browse the "r5r alternatives" section above for the current picks, or visit /alternatives/r5r-r for the full list with editorial commentary on each.
Top symengine alternatives in Analytics are ranked by recent ship velocity. Browse the "symengine alternatives" section above for the current picks, or visit /alternatives/symengine-r for the full list with editorial commentary on each.