n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of Fulcrum and RadialMR — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | RadialMR |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | mendelian-randomization, radial-plots, correctness-audit, statistical-inference |
| Last editorial update | 9h ago | 50m ago |
| Website | — | Visit → |
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
RadialMR's 2026 release corrects degrees of freedom that had been wrong since documentation.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
This is a package being read closely by its maintainer rather than extended. The 1.2.x line pairs statistical corrections with defensive hardening — an rmr_format class check so unformatted input fails with a clear message, and plotly_radial() dispatching on object class instead of counting list elements. Both are the kind of change made while auditing, not while building.
Expect the audit to continue into the remaining estimator internals and print methods rather than new radial variants; the entries show no feature work queued.
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 Fulcrum or RadialMR.
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 Fulcrum alternatives → · See all RadialMR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.
Top RadialMR alternatives in Analytics are ranked by recent ship velocity. Browse the "RadialMR alternatives" section above for the current picks, or visit /alternatives/radialmr for the full list with editorial commentary on each.