TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of crossmap and nmar — release velocity, themes, recent moves, and the top alternatives to consider.
crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.
A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.
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 small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.
The package has settled into being a compatible extension rather than an independent one — its release notes read as a mirror of purrr's and furrr's deprecation schedules. Note that the release stamps are unreliable here: several versions were backfilled minutes apart and the 0.3.x tags carry timestamps in reverse version order, so feed position says nothing about what shipped when.
Expect the next release to be driven by another purrr or furrr change rather than new functionality, since that has been the sole trigger for the last four.
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.
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 crossmap or nmar.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all crossmap alternatives → · See all nmar alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. crossmap 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crossmap 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.
Top crossmap alternatives in Analytics are ranked by recent ship velocity. Browse the "crossmap alternatives" section above for the current picks, or visit /alternatives/crossmap for the full list with editorial commentary on each.
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.