← Back to home
Comparison · Infra & APIs

rgm vs traits.build

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

Shared themes:r-package

rgm vs traits.build: at a glance

Featurergmtraits.build
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesmicrobiome, graphical-models, bayesian-inference, cran-maintenancetrait-databases, data-harmonisation, ecology, provenance
Last editorial update1h ago2d ago
WebsiteVisit →Visit →

What is rgm?

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

Read the full rgm trajectory →

What is traits.build?

The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.

traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.

Read the full traits.build trajectory →

rgm vs traits.build: editorial side-by-side

R
rgm
INFRA · APIS
0.0

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

◆ Current state

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

◆ Where it's heading

Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.

◆ Prediction

The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.

T
traits.build
INFRA · APIS
0.0

The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.

◆ Current state

traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.

◆ Where it's heading

The project's direction is toward provenance and interoperability rather than throughput. Value types grew to carry standard error and standard deviation, the methods table now records what kind of source each dataset came from, and the identifiers table lets a trait value point at a herbarium sheet, a museum accession or a GenBank record. Alongside that, responsibilities have been split with the sibling austraits package, with shared functions moved out under deprecation shims. A published paper and a versioned ontology mark it as infrastructure meant for outside adoption, not just for AusTraits.

◆ Prediction

Expect further schema extensions in the same provenance direction, since the last two releases both added structure for describing where a measurement came from rather than new processing capability.

Alternatives to rgm and traits.build

Other Infra & APIs 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 rgm or traits.build.

See all rgm alternatives → · See all traits.build alternatives →

Recent activity from rgm and traits.build

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

  1. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  2. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  3. 3mo agorgmUnreleased twin of the CRAN recovery release
  4. 1y agotraits.buildTrait values gain specimen and GenBank identifiers
  5. 1y agotraits.buildFunctions move to austraits as the ontology reaches 1.0.0
  6. 2y agorgmFirst release: simulation, estimation and post-processing
  7. 2y agotraits.buildFixes to dataset testing, reports and name standardisation
  8. 2y agotraits.buildAusTraits workflow generalised into a reusable package

Frequently asked questions

What is the difference between rgm and traits.build?

Both compete on the same themes — r-package — within Infra & APIs. rgm and traits.build 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 rgm better than traits.build?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rgm and traits.build 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to rgm?

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

What are the best alternatives to traits.build?

Top traits.build alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "traits.build alternatives" section above for the current picks, or visit /alternatives/traits-build for the full list with editorial commentary on each.