simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
ibis.iSDM vs nmar
A side-by-side editorial comparison of ibis.iSDM and nmar — release velocity, themes, recent moves, and the top alternatives to consider.
ibis.iSDM vs nmar: at a glance
What is ibis.iSDM?
A raster-to-terra migration is the only readable change in a feed of merge notes.
ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.
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.
ibis.iSDM vs nmar: editorial side-by-side
ibis.iSDM
0.0ANALYTICS
A raster-to-terra migration is the only readable change in a feed of merge notes.
◆ Current state
ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.
◆ Where it's heading
Direction cannot be read from this feed with any confidence - three of the four visible tags carry nothing beyond merge titles and a full-changelog link. What is visible is a 2023 spent on dependency modernisation and dev-branch merges, ending with a 0.1.1 tag that December and nothing since.
◆ Prediction
These entries do not support a prediction; the notes would have to carry written content before a direction could be read from them.
nmar
0.0ANALYTICS
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.
Alternatives to ibis.iSDM and nmar
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 ibis.iSDM or nmar.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
healthyR.data
From a bundled hospital dataset to a live CMS API client.
See all ibis.iSDM alternatives → · See all nmar alternatives →
Recent activity from ibis.iSDM and nmar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agonmarBootstrap backend now parallel-aware and configurable
- 7mo agonmarCRAN submission fixes and DOI references
- 8mo agonmarNMAR 0.1.0 ⚡
- 2y agoibis.iSDMVersion 0.1.1
- 3y agoibis.iSDMVersion 0.0.7
- 3y agoibis.iSDMVersion 0.0.6
- 3y agoibis.iSDMraster replaced by terra across the package ⚡
Frequently asked questions
What is the difference between ibis.iSDM and nmar?
They serve adjacent needs but don't currently overlap on shipped themes. ibis.iSDM 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.
Is ibis.iSDM better than nmar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ibis.iSDM 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.
What are the best alternatives to ibis.iSDM?
Top ibis.iSDM alternatives in Analytics are ranked by recent ship velocity. Browse the "ibis.iSDM alternatives" section above for the current picks, or visit /alternatives/ibis-isdm for the full list with editorial commentary on each.
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.