← Back to home
Comparison · Infra & APIs

retroharmonize vs rgm

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

Shared themes:cran-maintenancer-package

retroharmonize vs rgm: at a glance

Featureretroharmonizergm
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-data, data-harmonization, labelled-data, reproducibilitymicrobiome, graphical-models, bayesian-inference, cran-maintenance
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is retroharmonize?

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

Read the full retroharmonize trajectory →

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 →

retroharmonize vs rgm: editorial side-by-side

R
retroharmonize
INFRA · APIS
0.0

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

◆ Current state

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

◆ Where it's heading

The design bet has been constant since the first release — comprehensive S3 classes that carry labels and missing-value semantics through every transformation, so the harmonization is documented rather than reconstructed. What has changed is where effort goes. Early releases added harmonization functions and a worked Arab Barometer case study; recent ones are code quality and CRAN survival. Note that the version numbering in this feed is not monotonic: 0.1.13 was released roughly nine months before 0.1.7, so version order here does not indicate release order.

◆ Prediction

Having just restored CRAN availability through a refactor rather than a feature, the near-term work is most likely consolidation of the vctrs integration the notes describe rather than new harmonization functions.

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.

Alternatives to retroharmonize and rgm

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 retroharmonize or rgm.

See all retroharmonize alternatives → · See all rgm alternatives →

Recent activity from retroharmonize and rgm

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

  1. 3mo agoretroharmonizeCRAN modernisation release
  2. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  3. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  4. 3mo agorgmUnreleased twin of the CRAN recovery release
  5. 7mo agoretroharmonizeRelease candidate; notes cite code quality with no detail
  6. 2y agorgmFirst release: simulation, estimation and post-processing
  7. 4y agoretroharmonizeImproved documentation
  8. 5y agoretroharmonize0.1.7 With case study on harmonizing Arab Barometer surveys
  9. 5y agoretroharmonizeretroharmonize 0.1.13 is on CRAN
  10. 6y agoretroharmonize0.1.0 Retrospective harmonization of survey data files in R

Frequently asked questions

What is the difference between retroharmonize and rgm?

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

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

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

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.