← Back to home
Comparison · Infra & APIs

CHNOSZ vs multimark

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

CHNOSZ vs multimark: at a glance

FeatureCHNOSZmultimark
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgeochemistry, thermodynamics, phase-diagrams, r-packagecapture-recapture, mcmc, maintenance, cran
Last editorial update38m ago2h ago
WebsiteVisit →Visit →

What is CHNOSZ?

A geochemistry thermodynamics engine that changed its units and its database schema in one release.

CHNOSZ computes thermodynamic properties and phase diagrams for geochemical systems, backed by OBIGT, its bundled thermodynamic database. It releases roughly once a year with a short highlights note pointing at a full changelog elsewhere. Since the 2.0.0 reset, work has been curation and communication: new species in OBIGT, a FAQ vignette, a rewritten introduction, and more readable diagram labels.

Read the full CHNOSZ trajectory →

What is multimark?

Five years of compiler and CRAN fixes on a capture-recapture package.

multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.

Read the full multimark trajectory →

CHNOSZ vs multimark: editorial side-by-side

C
CHNOSZ
INFRA · APIS
0.0

A geochemistry thermodynamics engine that changed its units and its database schema in one release.

◆ Current state

CHNOSZ computes thermodynamic properties and phase diagrams for geochemical systems, backed by OBIGT, its bundled thermodynamic database. It releases roughly once a year with a short highlights note pointing at a full changelog elsewhere. Since the 2.0.0 reset, work has been curation and communication: new species in OBIGT, a FAQ vignette, a rewritten introduction, and more readable diagram labels.

◆ Where it's heading

2.0.0 was the structural break — Joules replacing calories as the default output of subcrt(), a required E_units column, a new model column, and the removal of a legacy scaling convention for heat-capacity coefficients. Everything since has built on that settled foundation rather than disturbing it. The direction of the last two releases is toward coverage of specific mineral systems, rare earths and uranyl among them, and toward making the package approachable, which suggests a maintainer courting new users rather than reworking the engine.

◆ Prediction

The next release most likely continues OBIGT curation for particular element systems plus vignette work; the highlights format gives no signal of engine-level changes pending.

M
multimark
INFRA · APIS
0.0

Five years of compiler and CRAN fixes on a capture-recapture package.

◆ Current state

multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.

◆ Where it's heading

This is preservation rather than development. The one substantive entry, in 2021, corrected an MCMC error in multimarkClosedSCR() serious enough that the author told users to revisit past analyses; everything since has been keeping the C code compiling across platforms. Release intervals now stretch to years.

◆ Prediction

Expect the pattern to hold, with a release whenever a toolchain or upstream dependency forces one and no change to the samplers.

Alternatives to CHNOSZ and multimark

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 CHNOSZ or multimark.

See all CHNOSZ alternatives → · See all multimark alternatives →

Recent activity from CHNOSZ and multimark

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

  1. 8mo agomultimarkBrobdingnag sum import dropped after upstream removal
  2. 1y agoCHNOSZOBIGT gains rare earth and uranyl species; intro vignette rewritten
  3. 2y agoCHNOSZMosaic diagrams accept grouped basis species as variables
  4. 3y agoCHNOSZJoules become the default and the OBIGT schema is rebuilt
  5. 3y agomultimarkr-devel error fixed at CRAN's request
  6. 3y agomultimarkLinux compilation warnings cleared
  7. 4y agomultimarkFedora build error fixed at CRAN's request
  8. 4y agomultimarkMCMC detection-probability bug fixed in multimarkClosedSCR()
  9. 4y agomultimarkUnused parallelism dependencies removed

Frequently asked questions

What is the difference between CHNOSZ and multimark?

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

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

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

What are the best alternatives to multimark?

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