← Back to home
Comparison · Infra & APIs

geocomplexity vs rgm

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

Shared themes:r-package

geocomplexity vs rgm: at a glance

Featuregeocomplexityrgm
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesspatial-statistics, r-package, geographically-weighted-regression, rastermicrobiome, graphical-models, bayesian-inference, cran-maintenance
Last editorial update1d ago1h ago
WebsiteVisit →Visit →

What is geocomplexity?

A spatial complexity package that shipped its method, then went quiet

geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.

Read the full geocomplexity 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 →

geocomplexity vs rgm: editorial side-by-side

G
geocomplexity
INFRA · APIS
0.0

A spatial complexity package that shipped its method, then went quiet

◆ Current state

geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.

◆ Where it's heading

The package sits inside Wenbo Lyu's spatial statistics family, where shared functionality migrates into the common sdsfun package rather than being duplicated across dependents. moran_test left geocomplexity for sdsfun in 0.2.0, which is the same consolidation pattern visible across the author's other packages. What remains here is the method-specific surface, and it has not changed in eighteen months.

◆ Prediction

The entries give no signal of planned functional work; on this pattern the next release is as likely to be metadata or another function migration to sdsfun as anything user-visible.

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

See all geocomplexity alternatives → · See all rgm alternatives →

Recent activity from geocomplexity and rgm

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. 4mo agogeocomplexityMaintainer surname spelling corrected for pinyin compliance
  5. 1y agogeocomplexityPackage citation added
  6. 1y agogeocomplexitymoran_test migrates out to the shared sdsfun package
  7. 1y agogeocomplexityGeographical complexity measures and complexity-weighted GWR
  8. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between geocomplexity and rgm?

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

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

Top geocomplexity alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "geocomplexity alternatives" section above for the current picks, or visit /alternatives/geocomplexity 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.