dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
tern.mmrm vs tulpa
A side-by-side editorial comparison of tern.mmrm and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
tern.mmrm vs tulpa: at a glance
What is tern.mmrm?
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
tern.mmrm wraps mixed models for repeated measures into the tern tabulation and plotting layer used by teal clinical modules. The visible history ends with three CRAN releases in mid-to-late 2024; before that the feed carries only automated version bumps from 2022, three of which have just been backfilled into the record. The most recent substantive change adds axis limit arguments to the LS-means plot.
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.
tern.mmrm vs tulpa: editorial side-by-side
tern.mmrm
0.0ANALYTICS
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
◆ Current state
tern.mmrm wraps mixed models for repeated measures into the tern tabulation and plotting layer used by teal clinical modules. The visible history ends with three CRAN releases in mid-to-late 2024; before that the feed carries only automated version bumps from 2022, three of which have just been backfilled into the record. The most recent substantive change adds axis limit arguments to the LS-means plot.
◆ Where it's heading
Content per release is thin and largely organisational: a maintainer change, replacing scda with random.cdisc.data in vignettes, and adapting to new {mmrm} versions. The package appears to be in maintenance, tracking its upstream dependency rather than developing independently. The 2022 entries now visible are release-automation commits, not releases in any meaningful sense.
◆ Prediction
Nothing here signals new functionality; the realistic next event is another compatibility release when {mmrm} or {rtables} changes underneath it.
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 tern.mmrm 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 tern.mmrm or tulpa.
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.
AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
NocoDB
Interfaces gets the permissions layer it needed, one release after launching.
See all tern.mmrm alternatives → · See all tulpa alternatives →
Recent activity from tern.mmrm and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17h 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
- 1y agotern.mmrmAxis limits added to the LS-means plot
- 2y agotern.mmrmMaintainer change and scda replaced in vignettes
- 2y agotern.mmrmCRAN 0.3.0 release, mostly workflow housekeeping
- 3y agotern.mmrmAutomated version bump to 0.2.1
- 4y agotern.mmrmPre-release branch merge
- 4y agotern.mmrmCI automation commit, no release content
Frequently asked questions
What is the difference between tern.mmrm 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 tern.mmrm 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 tern.mmrm?
Top tern.mmrm alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.mmrm alternatives" section above for the current picks, or visit /alternatives/tern-mmrm 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.