dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
parglm vs tulpa
A side-by-side editorial comparison of parglm and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
parglm vs tulpa: at a glance
What is parglm?
Under a new maintainer, parglm traded raw speed work for glm parity and memory safety
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
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.
parglm vs tulpa: editorial side-by-side
parglm
0.0ANALYTICS
Under a new maintainer, parglm traded raw speed work for glm parity and memory safety
◆ Current state
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
◆ Where it's heading
The arc runs from performance to trustworthiness. 0.1.9 was a large optimization release — deque-based task queues, fused memory passes, upper-triangle-only Fisher information, thread_local IDs — plus ecosystem integration with sandwich and gtsummary. 0.2.0 then fixed an out-of-bounds write triggered by small block_size values and a path where a non-finite working response could poison the QR decomposition, and brought response-type handling in line with glm().
◆ Prediction
With the memory-safety issues addressed and glm parity closed for binomial responses, further work is likely to extend family coverage or the benchmark suite rather than revisit the threading model. The C++17 requirement set at 0.1.8 gives room for more aggressive optimization if the maintainer returns to that.
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 parglm 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 parglm 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 parglm alternatives → · See all tulpa alternatives →
Recent activity from parglm 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
- 1mo agoparglmglm-compatible response types plus out-of-bounds and QR safety fixes
- 2mo agoparglmBuild fixes for macOS SDK and thread pool includes
- 3mo agoparglmAdd missing <thread> include for older Apple SDKs
- 3mo agoparglmThreading overhaul, quasi families, and sandwich/gtsummary compatibility
- 4mo agoparglmNew maintainer takes over; C++17 now required
Frequently asked questions
What is the difference between parglm 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 parglm 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 parglm?
Top parglm alternatives in Analytics are ranked by recent ship velocity. Browse the "parglm alternatives" section above for the current picks, or visit /alternatives/parglm 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.