← Back to home
Comparison · Infra & APIs

rgm vs whirl

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

rgm vs whirl: at a glance

Featurergmwhirl
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesmicrobiome, graphical-models, bayesian-inference, cran-maintenancereproducibility, clinical reporting, provenance, logging
Last editorial update1h ago1d 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 whirl?

whirl turned script logging into a standardized provenance artifact regulators can read.

A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.

Read the full whirl trajectory →

rgm vs whirl: 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.

W
whirl
INFRA · APIS
0.0

whirl turned script logging into a standardized provenance artifact regulators can read.

◆ Current state

A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.

◆ Where it's heading

The through-line is the log as evidence rather than as debugging output. Every recent addition either widens what the log proves — which packages were really used, in which language, against which approved list — or narrows what it must not leak. Setting options only through an explicit with_options argument to run() and getting renv library paths right for Quarto both point the same way: reproducible, auditable child sessions with nothing implicit.

◆ Prediction

Expect the approved-package and provenance machinery to keep expanding across languages and environments, since Python approval checks followed the R ones and both feed the same log.

Alternatives to rgm and whirl

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

See all rgm alternatives → · See all whirl alternatives →

Recent activity from rgm and whirl

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. 7mo agowhirlExplicit option passing to child sessions; renv path fix
  5. 11mo agowhirlLogs flag package approval status and exclude secrets
  6. 1y agowhirlwhirl 0.3.0
  7. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between rgm and whirl?

They serve adjacent needs but don't currently overlap on shipped themes. rgm and whirl 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 whirl?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rgm and whirl 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 whirl?

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