pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of JointFPM and ncmR — release velocity, themes, recent moves, and the top alternatives to consider.
Recurrent-event modelling settles, with mean_no() promoted to stable.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
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.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.
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 JointFPM or ncmR.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all JointFPM 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. JointFPM 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. JointFPM 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 JointFPM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JointFPM alternatives" section above for the current picks, or visit /alternatives/jointfpm 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.