dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
GeneNMF vs tulpa
A side-by-side editorial comparison of GeneNMF and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
GeneNMF vs tulpa: at a glance
What is GeneNMF?
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
GeneNMF applies non-negative matrix factorization to single-cell expression data to find gene programs, then consolidates programs recurring across samples into meta-programs. Version 0.6.0 replaced the consolidation method: instead of reducing each program to a gene set and taking a consensus, it retains full gene weight vectors and compares them by cosine similarity. Later releases have built reporting and control around that core — a metaprogram composition matrix showing which samples contributed, custom signature databases for enrichment testing, and the ability to drop meta-programs from results.
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.
GeneNMF vs tulpa: editorial side-by-side
GeneNMF
0.0ANALYTICS
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
◆ Current state
GeneNMF applies non-negative matrix factorization to single-cell expression data to find gene programs, then consolidates programs recurring across samples into meta-programs. Version 0.6.0 replaced the consolidation method: instead of reducing each program to a gene set and taking a consensus, it retains full gene weight vectors and compares them by cosine similarity. Later releases have built reporting and control around that core — a metaprogram composition matrix showing which samples contributed, custom signature databases for enrichment testing, and the ability to drop meta-programs from results.
◆ Where it's heading
The package is moving from producing meta-programs to letting users interrogate and constrain how they were formed. Composition matrices, the drop function and downsampled similarity heatmaps all serve inspection rather than derivation. The parameters added alongside the 0.6.0 rewrite — specificity weighting, cumulative weight thresholds, confidence defined as the fraction of programs containing a gene — turn what were fixed internal choices into stated, tunable ones.
◆ Prediction
Recent releases have been fixes and compatibility work rather than method changes, so the core approach appears settled. The dependency on an RcppML version not on CRAN is the loose end most likely to force the next release.
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 GeneNMF 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 GeneNMF 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 GeneNMF alternatives → · See all tulpa alternatives →
Recent activity from GeneNMF 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
- 11mo agoGeneNMFSingle-sample runs fixed; gene weight definition refined
- 1y agoGeneNMFMetaprogram composition exposed and custom signature DBs supported
- 1y agoGeneNMFSimilarity heatmap downsampling and meta-program removal
- 2y agoGeneNMFMeta-programs rebuilt on gene weight vectors and cosine similarity ⚡
- 2y agoGeneNMFFirst stable release published to CRAN
Frequently asked questions
What is the difference between GeneNMF 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 GeneNMF 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 GeneNMF?
Top GeneNMF alternatives in Analytics are ranked by recent ship velocity. Browse the "GeneNMF alternatives" section above for the current picks, or visit /alternatives/genenmf 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.