Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
cTMed vs tulpa
A side-by-side editorial comparison of cTMed and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
cTMed vs tulpa: at a glance
What is cTMed?
Continuous-time mediation effects get standardized centrality, six years into steady patch work
cTMed computes direct, indirect and total effects for continuous-time mediation models, with delta-method, Monte Carlo and bootstrap variants of each. Development is a long run of patch releases from the jeksterslab account, roughly every two months, each adding a function or two. The latest adds standardized centrality measures and allows a diagonal sigma across ten standardized estimators.
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.
cTMed vs tulpa: editorial side-by-side
cTMed
2.5ANALYTICS
Continuous-time mediation effects get standardized centrality, six years into steady patch work
◆ Current state
cTMed computes direct, indirect and total effects for continuous-time mediation models, with delta-method, Monte Carlo and bootstrap variants of each. Development is a long run of patch releases from the jeksterslab account, roughly every two months, each adding a function or two. The latest adds standardized centrality measures and allows a diagonal sigma across ten standardized estimators.
◆ Where it's heading
The package is filling out a matrix rather than changing shape: for each effect type there is a delta-method, a Monte Carlo and a bootstrap path, and each release closes another cell. The 2025 releases were largely externally forced — an Armadillo 15.0.x transition at CRAN, a citation addition after the Psychological Methods paper landed — which suggests the statistical core has been settled since the 1.0.6 standardization revision.
◆ Prediction
The diagonal-sigma option has now reached the standardized estimators; extending it to the remaining unstandardized variants is the obvious next cell to fill.
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 cTMed 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 cTMed 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.
Recent activity from cTMed and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h 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
- 29d agocTMedStandardized centrality measures and diagonal-sigma support
- 6mo agocTMedMinor method edits
- 10mo agocTMedPackage citation added for the Psychological Methods paper
- 10mo agocTMedArmadillo 15.0.x compatibility for CRAN
- 1y agocTMedStandardization reworked around the steady-state covariance matrix
- 1y agocTMedBootstrap centrality estimators and MCPhiSigma()
Frequently asked questions
What is the difference between cTMed and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 2.5), 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 cTMed 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 2.5), 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 cTMed?
Top cTMed alternatives in Analytics are ranked by recent ship velocity. Browse the "cTMed alternatives" section above for the current picks, or visit /alternatives/ctmed 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.