← Back to home
Comparison · Analytics

churon vs nmar

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

Shared themes:r package

churon vs nmar: at a glance

Featurechuronnmar
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesonnx runtime, rust bindings, cran compliance, machine learningsurvey statistics, nonresponse, empirical likelihood, bootstrap
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is churon?

churon is spending its entire release history getting a Rust ONNX binding through CRAN.

An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.

Read the full churon trajectory →

What is nmar?

NMAR landed on CRAN with two nonresponse estimators behind one interface, then started tuning it.

Three releases in seven weeks, starting from nothing. The initial CRAN release implements empirical likelihood (Qin, Leung and Shao 2002) and both parametric and nonparametric exponential tilting (Riddles, Kim and Im 2016) for estimating means under nonignorable nonresponse, all reachable through a single nmar() call with formula syntax and direct support for survey.design objects. Since then the work has been operational: a configurable bootstrap backend and stricter input validation.

Read the full nmar trajectory →

churon vs nmar: editorial side-by-side

C
churon
ANALYTICS
0.0

churon is spending its entire release history getting a Rust ONNX binding through CRAN.

◆ Current state

An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.

◆ Where it's heading

Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.

◆ Prediction

Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.

N
nmar
ANALYTICS
0.0

NMAR landed on CRAN with two nonresponse estimators behind one interface, then started tuning it.

◆ Current state

Three releases in seven weeks, starting from nothing. The initial CRAN release implements empirical likelihood (Qin, Leung and Shao 2002) and both parametric and nonparametric exponential tilting (Riddles, Kim and Im 2016) for estimating means under nonignorable nonresponse, all reachable through a single nmar() call with formula syntax and direct support for survey.design objects. Since then the work has been operational: a configurable bootstrap backend and stricter input validation.

◆ Where it's heading

The package is positioning itself as the general interface to nonignorable-nonresponse estimation rather than a reference implementation of one paper — shared architecture across engines, one formula API, and integration with the survey package so weights and stratification come for free. The follow-up releases suggest the next constraint is compute: bootstrap variance estimation is the expensive part, and it now dispatches to future.apply when a parallel plan exists.

◆ Prediction

Expect further engines under the same nmar() interface or wider bootstrap support, since the architecture was explicitly refactored to share structure across estimators.

Alternatives to churon and nmar

Other Analytics 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 churon or nmar.

See all churon alternatives → · See all nmar alternatives →

Recent activity from churon and nmar

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

  1. 6mo agonmarBootstrap backend now parallel-aware and configurable
  2. 7mo agochuronVendored Rust sources bundled for offline CRAN builds
  3. 7mo agochuronort pinned back to rc.10 for CRAN Windows builds
  4. 7mo agochuronVersion bump and wasm fix reverted
  5. 7mo agonmarCRAN submission fixes and DOI references
  6. 8mo agonmarNMAR 0.1.0

Frequently asked questions

What is the difference between churon and nmar?

Both compete on the same themes — r package — within Analytics. churon and nmar 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 churon better than nmar?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. churon and nmar 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 Analytics products to evaluate alongside.

What are the best alternatives to churon?

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

What are the best alternatives to nmar?

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