← Back to home
Comparison · Analytics

nmar vs randomwalk

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

Shared themes:r package

nmar vs randomwalk: at a glance

Featurenmarrandomwalk
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvey statistics, nonresponse, empirical likelihood, bootstrapwebassembly, shinylive, webr, simulation
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 randomwalk?

randomwalk spent every release getting an R simulation to run in the browser, not on a server.

A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.

Read the full randomwalk trajectory →

nmar vs randomwalk: 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.

R
randomwalk
ANALYTICS
0.0

randomwalk spent every release getting an R simulation to run in the browser, not on a server.

◆ Current state

A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.

◆ Where it's heading

The package is being built as a browser artifact first and an R package second: the readme, the vignettes and the release notes all point at a hosted dashboard rather than at library(). The last release completes that by making the compiled WebAssembly build installable by anyone via webr::install(), which turns the deployment work into something reusable outside this project. Version numbers are unreliable here — v0.2.0 was published two weeks after v1.0.2 — so read the dates, not the tags.

◆ Prediction

With the webR repository published, the next work most likely moves back to the simulation itself, though the entries give no direct evidence of planned features.

Alternatives to nmar and randomwalk

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 randomwalk.

See all nmar alternatives → · See all randomwalk alternatives →

Recent activity from nmar and randomwalk

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

  1. 6mo agonmarBootstrap backend now parallel-aware and configurable
  2. 7mo agonmarCRAN submission fixes and DOI references
  3. 8mo agonmarNMAR 0.1.0
  4. 8mo agorandomwalkPackage published as an installable webR binary repository
  5. 8mo agorandomwalkTermination validation removes isolated pixels from simulations
  6. 8mo agorandomwalkAsync dashboard with crew workers running under WebR
  7. 9mo agorandomwalkBrowser dashboard working end to end
  8. 9mo agorandomwalkMissing plot dependency and parameter display fixed
  9. 9mo agorandomwalkDashboard mounts WebAssembly from GitHub releases

Frequently asked questions

What is the difference between nmar and randomwalk?

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

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

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