mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of massProps and ncmR — release velocity, themes, recent moves, and the top alternatives to consider.
A mass-properties rollup spends a year on documentation and follows its sibling's API
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
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.
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
Every release in the window is documentation, benchmarks, or keeping in step with rollupTree. The inertia tensor and radius-of-gyration uncertainty equations have been reformatted and re-explained three separate times, which suggests the hard part of this package is not the computation but making the covariance treatment legible to the engineers meant to trust it. Development effort clearly sits in the engine underneath, not here.
The pattern is unambiguous: rollupTree ships an API change and massProps follows within a fortnight. Whatever the engine does next is what appears here next, and on this evidence it will arrive as a one-line release note.
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 massProps 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 massProps 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. massProps 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. massProps 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 massProps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "massProps alternatives" section above for the current picks, or visit /alternatives/massprops 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.