mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of GeoThinneR and ncmR — release velocity, themes, recent moves, and the top alternatives to consider.
Spatial thinning grows a result object, and the API breaks to make room for it
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
Three weeks from first CRAN submission to a point-and-click neutral community model
ncmR fits the neutral community model to microbiome and ecological abundance data. The whole feed is three weeks long: fit_ncm() and summary methods at 0.1.0 on 1 April, a scatter plot with fitted curve and confidence interval at 0.2.0, then a Shiny application wrapping both at 0.3.0, then a row-name bugfix. It is a new package moving fast in its first month.
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
The package is moving from a function that returns an answer to a tool that returns something you can interrogate. Multiple thinning trials are first-class — you can ask for the largest, fetch a specific one, summarise one — and the recent work is about making the choice among tied candidates controllable rather than random. Dependency discipline runs alongside: the R-tree method was dropped when its package was not on CRAN, and spatial coverage degrades to NA rather than failing when s2 is missing.
The priority mechanism now covers all three strategies and the last release was an overflow fix in the local kd-tree path at large sizes, so scale is where the pressure is. More work on the distance methods at large N is the likelier next step than another strategy.
ncmR fits the neutral community model to microbiome and ecological abundance data. The whole feed is three weeks long: fit_ncm() and summary methods at 0.1.0 on 1 April, a scatter plot with fitted curve and confidence interval at 0.2.0, then a Shiny application wrapping both at 0.3.0, then a row-name bugfix. It is a new package moving fast in its first month.
The direction is toward users who do not write R. Version 0.2.0 added plotting, 0.3.0 wrapped fitting and plotting in Shiny modules, and the same release deleted the Unicode plotting helpers introduced one version earlier because the dependency they existed for was removed. That willingness to throw away a week-old API suggests the surface is still being negotiated rather than settled.
With a fitting module and a plotting module in the app, the remaining gap is getting results back out — export of fitted parameters or figures from the Shiny session. The bugfix at 0.3.1 was in file upload, which is where a GUI's problems usually start.
Other Infra & APIs 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 GeoThinneR or ncmR.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all GeoThinneR alternatives → · See all ncmR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GeoThinneR and ncmR 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. GeoThinneR and ncmR 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 Infra & APIs products to evaluate alongside.
Top GeoThinneR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GeoThinneR alternatives" section above for the current picks, or visit /alternatives/geothinner for the full list with editorial commentary on each.
Top ncmR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ncmR alternatives" section above for the current picks, or visit /alternatives/ncmr for the full list with editorial commentary on each.