← Back to home
Comparison · Infra & APIs

JointFPM vs ncmR

A side-by-side editorial comparison of JointFPM and ncmR — release velocity, themes, recent moves, and the top alternatives to consider.

JointFPM vs ncmR: at a glance

FeatureJointFPMncmR
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitymicrobiome, ecology, neutral-community-model, shiny
Last editorial update44m ago2h ago
WebsiteVisit →Visit →

What is JointFPM?

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.

Read the full JointFPM trajectory →

What is ncmR?

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.

Read the full ncmR trajectory →

JointFPM vs ncmR: editorial side-by-side

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

N
ncmR
INFRA · APIS
0.0

Three weeks from first CRAN submission to a point-and-click neutral community model

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to JointFPM and ncmR

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.

See all JointFPM alternatives → · See all ncmR alternatives →

Recent activity from JointFPM and ncmR

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agoncmRRow names preserved during file upload conversion
  2. 4mo agoncmRA Shiny app for fitting and plotting neutral community models
  3. 4mo agoncmRScatter plot with fitted curve and confidence interval
  4. 4mo agoncmRFirst CRAN submission: neutral community model fitting in R
  5. 1y agoJointFPMmean_no() promoted to a stable interface
  6. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  7. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  8. 2y agoJointFPMStandardized marginal estimates plus input validation
  9. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between JointFPM and ncmR?

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.

Is JointFPM better than ncmR?

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.

What are the best alternatives to JointFPM?

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.

What are the best alternatives to ncmR?

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.