Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
epiworldR vs tulpa
A side-by-side editorial comparison of epiworldR and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
epiworldR vs tulpa: at a glance
What is epiworldR?
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.
What is tulpa?
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
epiworldR vs tulpa: editorial side-by-side
epiworldR
0.0ANALYTICS
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
tulpa
7.5ANALYTICS
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
◆ Current state
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
◆ Where it's heading
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
◆ Prediction
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
Alternatives to epiworldR and tulpa
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 tulpa.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all epiworldR alternatives → · See all tulpa alternatives →
Recent activity from epiworldR and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 19h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 9d agotulpaCUDA backend had two definitions; link order decided if it ran
- 9d agotulpaHyperparameter bounds now flag when they leave the node range
- 4mo agoepiworldR0.14.0 addresses an AddressSanitizer finding
- 5mo agoepiworldRWrapper bumped to track a new epiworld version
- 5mo agoepiworldRBuild drops the custom configure script for R's C++17 and OpenMP settings
- 6mo agoepiworldRepiworld bumped to 0.11.2
- 7mo agoepiworldRTests updated at CRAN's request
- 7mo agoepiworldRHospitalizations, outbreak size and active cases exposed to R
Frequently asked questions
What is the difference between epiworldR and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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.
Is epiworldR better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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.
What are the best alternatives to epiworldR?
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.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.