← Back to home
Comparison · Infra & APIs

JointFPM vs prospectr

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

JointFPM vs prospectr: at a glance

FeatureJointFPMprospectr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilityspectroscopy, signal-processing, preprocessing, calibration-sampling
Last editorial update35m ago3h 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 prospectr?

prospectr spent its biggest release in years fixing spectra it had been quietly mangling.

prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.

Read the full prospectr trajectory →

JointFPM vs prospectr: 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.

P
prospectr
INFRA · APIS
0.0

prospectr spent its biggest release in years fixing spectra it had been quietly mangling.

◆ Current state

prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.

◆ Where it's heading

The recent work is corrective rather than additive, and several items changed results silently before being caught. continuumRemoval() derived its convex-hull boundary offset from a fixed one-wavelength assumption that broke for fine-resolution spectra or non-nanometre units; cochranTest() passed an invalid argument name to prcomp() and produced incorrect principal component scores; readASD() silently dropped spectra in one branch of its text path. Two file readers were leaking connections. Alongside that runs a smaller thread of decoupling preprocessing steps from each other, most visibly detrend() gaining an snv argument so polynomial detrending can run without the SNV transform that Barnes et al. bundled with it.

◆ Prediction

The detrend() decoupling is the only recent addition and it fits a broader pipeline-composition direction, so similar separation of other bundled preprocessing steps is the plausible next move. The misspelled substraction argument now carries a deprecation warning, which schedules its removal for a future release.

Alternatives to JointFPM and prospectr

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 prospectr.

See all JointFPM alternatives → · See all prospectr alternatives →

Recent activity from JointFPM and prospectr

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

  1. 1mo agoprospectrdetrend() can run without a prior SNV transformation
  2. 2mo agoprospectrContinuum removal, SNV and cochranTest corrected; readers stop leaking
  3. 1y agoJointFPMmean_no() promoted to a stable interface
  4. 1y agoprospectrread_nircal() sample ID field fix
  5. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  6. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  7. 2y agoJointFPMStandardized marginal estimates plus input validation
  8. 2y agoJointFPMBug fixes for differences between mean-event functions
  9. 3y agoprospectrNon-UTF8 sample IDs no longer become NA
  10. 4y agoprospectrkenStone() bug fix
  11. 4y agoprospectrread_nircal() execution failure fixed

Frequently asked questions

What is the difference between JointFPM and prospectr?

They serve adjacent needs but don't currently overlap on shipped themes. JointFPM and prospectr 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 prospectr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. JointFPM and prospectr 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 prospectr?

Top prospectr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "prospectr alternatives" section above for the current picks, or visit /alternatives/prospectr for the full list with editorial commentary on each.