← Back to home
Comparison · Analytics

GeneNMF vs soilDBdata

A side-by-side editorial comparison of GeneNMF and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.

GeneNMF vs soilDBdata: at a glance

FeatureGeneNMFsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessingle-cell-genomics, nmf, gene-programs, bioinformaticssoil data, test fixtures, nasis, data package
Last editorial update1h ago7h ago
WebsiteVisit →Visit →

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.

Read the full GeneNMF trajectory →

What is soilDBdata?

soilDBdata exists so soilDB's tests can run without a NASIS connection.

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

Read the full soilDBdata trajectory →

GeneNMF vs soilDBdata: editorial side-by-side

G
GeneNMF
ANALYTICS
0.0

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.

S
soilDBdata
ANALYTICS
0.0

soilDBdata exists so soilDB's tests can run without a NASIS connection.

◆ Current state

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

◆ Where it's heading

Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.

◆ Prediction

The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.

Alternatives to GeneNMF and soilDBdata

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 soilDBdata.

See all GeneNMF alternatives → · See all soilDBdata alternatives →

Recent activity from GeneNMF and soilDBdata

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 11mo agoGeneNMFSingle-sample runs fixed; gene weight definition refined
  3. 1y agoGeneNMFMetaprogram composition exposed and custom signature DBs supported
  4. 1y agoGeneNMFSimilarity heatmap downsampling and meta-program removal
  5. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  6. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  7. 2y agoGeneNMFMeta-programs rebuilt on gene weight vectors and cosine similarity
  8. 2y agoGeneNMFFirst stable release published to CRAN
  9. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  10. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between GeneNMF and soilDBdata?

They serve adjacent needs but don't currently overlap on shipped themes. GeneNMF and soilDBdata are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is GeneNMF better than soilDBdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GeneNMF and soilDBdata are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 soilDBdata?

Top soilDBdata alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDBdata alternatives" section above for the current picks, or visit /alternatives/soildbdata for the full list with editorial commentary on each.