Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
RadialMR vs tulpa
A side-by-side editorial comparison of RadialMR and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
RadialMR vs tulpa: at a glance
What is RadialMR?
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().
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.
RadialMR vs tulpa: editorial side-by-side
RadialMR
0.0ANALYTICS
RadialMR's 2026 release corrects degrees of freedom that had been wrong since documentation.
◆ Current state
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().
◆ Where it's heading
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.
◆ Prediction
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.
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 RadialMR 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 RadialMR 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 RadialMR alternatives → · See all tulpa alternatives →
Recent activity from RadialMR and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20h 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
- 1mo agoRadialMRegger_radial() degrees of freedom corrected to n-2
- 3mo agoRadialMRroxygen2 bumped; package-level helpfile added
- 4mo agoRadialMRUnspecified codebase optimizations
- 1y agoRadialMRggplot2 v4 warning removed from plot_radial()
Frequently asked questions
What is the difference between RadialMR 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 RadialMR 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 RadialMR?
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.
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.