Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of epiworldR and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | epiworldR | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | r-package, epidemiology, agent-based-simulation, cran | gis, esri-migration, offline-maps, field-data-capture |
| Last editorial update | 1h ago | 12h ago |
| Website | Visit → | — |
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
Almost every release here is a version bump of the underlying epiworld C++ library, wrapped and pushed to CRAN. The substantive R-side work is narrow and consistent: exposing simulation outputs that were already computed but not reachable from R — outbreak size, active cases, hospitalizations and their savers. The newest release addresses an AddressSanitizer finding, which is the kind of thing CRAN checks surface on a compiled package.
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.
Almost every release here is a version bump of the underlying epiworld C++ library, wrapped and pushed to CRAN. The substantive R-side work is narrow and consistent: exposing simulation outputs that were already computed but not reachable from R — outbreak size, active cases, hospitalizations and their savers. The newest release addresses an AddressSanitizer finding, which is the kind of thing CRAN checks surface on a compiled package.
The R package's job is staying current with the simulator and satisfying CRAN, not evolving its own interface. What direction it has shows in which model outputs get exposed next, and in a steady tidy-up of the build — the custom configure script was dropped in favour of R's built-in C++17 and OpenMP settings, and test coverage has been filled in across several releases with automated assistance.
Expect the next release to track another epiworld version bump, with any R-side addition most likely being one more exposed metric or saver, following the pattern of get_hospitalizations and get_outbreak_size.
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.
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 epiworldR or Fulcrum.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all epiworldR alternatives → · See all Fulcrum 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 epiworldR alternatives in Analytics are ranked by recent ship velocity. Browse the "epiworldR alternatives" section above for the current picks, or visit /alternatives/epiworldr for the full list with editorial commentary on each.
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.