simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of nmar and rtrek — 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 Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
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.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.
Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.
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 rtrek.
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.
A drop-in string API for base R, kept alive by upstream check failures.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nmar and rtrek 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 rtrek 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 rtrek alternatives in Analytics are ranked by recent ship velocity. Browse the "rtrek alternatives" section above for the current picks, or visit /alternatives/rtrek for the full list with editorial commentary on each.