simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of nmar and stringx — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A drop-in string API for base R, kept alive by upstream check failures.
stringx reimplements base R's string and date-time functions on top of stringi, aiming for consistent and Unicode-correct behaviour. The visible window holds one behavioural change and five releases that exist because R or stringi moved underneath it. None of the recent notes add capability.
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.
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.
Expect further engines under the same nmar() interface or wider bootstrap support, since the architecture was explicitly refactored to share structure across estimators.
stringx reimplements base R's string and date-time functions on top of stringi, aiming for consistent and Unicode-correct behaviour. The visible window holds one behavioural change and five releases that exist because R or stringi moved underneath it. None of the recent notes add capability.
The package's shape was settled by 0.2.1 and has not changed since; every release in the past three years is either a check failure fixed or a POSIXxt defect. The one substantive note, 0.2.6, records a behaviour change inherited from stringi rather than chosen here - strptime now fills missing fields from today's midnight. That dependence is the defining fact about the feed.
The next release is most likely another compatibility fix timed to an R or stringi update, since four of the six visible releases were exactly that.
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 stringx.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
From a bundled hospital dataset to a live CMS API client.
See all nmar alternatives → · See all stringx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nmar and stringx 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nmar and stringx 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.
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.
Top stringx alternatives in Analytics are ranked by recent ship velocity. Browse the "stringx alternatives" section above for the current picks, or visit /alternatives/stringx for the full list with editorial commentary on each.