← Back to home
Comparison · Analytics

fracture vs nmar

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

Shared themes:cran

fracture vs nmar: at a glance

Featurefracturenmar
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesnumeric formatting, fractions, utility package, maintenancesurvey statistics, nonresponse, empirical likelihood, bootstrap
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is fracture?

fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.

A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.

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

fracture vs nmar: editorial side-by-side

F
fracture
ANALYTICS
0.0

fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.

◆ Current state

A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.

◆ Where it's heading

This is a completed utility. Its arc ran from correctness — floating-point rounding, exhaustive tests across millions of fractions — through API tightening, to edge-case tolerance, and then stopped. The 2026 release contains no user-visible change at all; it exists because CRAN's toolchain moved, which is the characteristic maintenance mode of a small package that does one thing correctly.

◆ Prediction

Nothing in these entries suggests new functionality; expect further releases only when R or CRAN policy forces one, as this one did.

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 fracture 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 fracture or nmar.

See all fracture alternatives → · See all nmar alternatives →

Recent activity from fracture and nmar

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

  1. 6mo agonmarBootstrap backend now parallel-aware and configurable
  2. 6mo agofractureObsolete C++11 requirement removed
  3. 7mo agonmarCRAN submission fixes and DOI references
  4. 8mo agonmarNMAR 0.1.0
  5. 4y agofractureNA and Inf inputs handled instead of erroring
  6. 4y agofractureExplicit denominator argument; arguments now named-only
  7. 5y agofractureUnicode fraction formatting and rounding fixes

Frequently asked questions

What is the difference between fracture and nmar?

Both compete on the same themes — cran — within Analytics. fracture 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 fracture better than nmar?

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

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