← Back to home
Comparison · Analytics

nmar vs singlercapture

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

Shared themes:bootstrapr package

nmar vs singlercapture: at a glance

Featurenmarsinglercapture
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvey statistics, nonresponse, empirical likelihood, bootstrapcapture-recapture, population estimation, zero-truncated models, bootstrap
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is singlercapture?

singleRcapture reached 1.0.0 with no release notes at all — the arc has to be read backwards.

A package for single-source capture-recapture population size estimation: zero-truncated Poisson, geometric and negative binomial regression, Chao and Zelterman mixture models, analytic and bootstrap variance estimation, all behind estimatePopsize(). The 0.2.x line professionalised it — an offset argument, parallel bootstrap and dfbeta, faster semiparametric sampling, a singleRStaticCountData subclass explicitly created so a companion package could fit models from countreg and VGAM, then interaction-term and anova fixes. The 1.0.0 release carries nothing but a link to the compare view.

Read the full singlercapture trajectory →

nmar vs singlercapture: editorial side-by-side

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.

S0.0

singleRcapture reached 1.0.0 with no release notes at all — the arc has to be read backwards.

◆ Current state

A package for single-source capture-recapture population size estimation: zero-truncated Poisson, geometric and negative binomial regression, Chao and Zelterman mixture models, analytic and bootstrap variance estimation, all behind estimatePopsize(). The 0.2.x line professionalised it — an offset argument, parallel bootstrap and dfbeta, faster semiparametric sampling, a singleRStaticCountData subclass explicitly created so a companion package could fit models from countreg and VGAM, then interaction-term and anova fixes. The 1.0.0 release carries nothing but a link to the compare view.

◆ Where it's heading

The direction visible in 0.2.x is outward: refactoring for maintainability, extending to models fitted elsewhere via a subclass, adding a JSS-paper vignette, and pushing coverage towards 90%. That is a package preparing to be cited and extended rather than one still finding its methods. The 1.0.0 tag presumably marks the end of that stabilisation, but the entry itself gives no evidence either way.

◆ Prediction

Not readable from this feed — the 1.0.0 notes are empty, so whether the major version marks an API freeze or a breaking change cannot be determined from the entries shown.

Alternatives to nmar and singlercapture

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

See all nmar alternatives → · See all singlercapture alternatives →

Recent activity from nmar and singlercapture

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

  1. 6mo agonmarBootstrap backend now parallel-aware and configurable
  2. 6mo agosinglercapturesingleRcapture 1.0.0
  3. 7mo agonmarCRAN submission fixes and DOI references
  4. 8mo agonmarNMAR 0.1.0
  5. 1y agosinglercaptureanova and other broken methods fixed
  6. 1y agosinglercaptureInteraction terms fixed; logLik returns gradients and hessians
  7. 2y agosinglercaptureSubclass opens population estimation to countreg and VGAM fits
  8. 4y agosinglercaptureFirst usable release: zero-truncated and mixture estimators

Frequently asked questions

What is the difference between nmar and singlercapture?

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

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

What are the best alternatives to singlercapture?

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