← Back to home
Comparison · Infra & APIs

JointFPM vs modsem

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

JointFPM vs modsem: at a glance

FeatureJointFPMmodsem
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitystructural-equation-modeling, latent-interactions, lms-estimator, mplus-interop
Last editorial update45m 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 modsem?

modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.

modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.

Read the full modsem trajectory →

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

M
modsem
INFRA · APIS
0.0

modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.

◆ Current state

modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.

◆ Where it's heading

Two things are being closed at once. The modelling gap — composites and formative constructs, categorical estimators, residual covariances in every direction, multigroup and clustered designs — brings modsem toward what commercial Mplus users expect, and the package's Mplus bridge is maintained alongside it, now with unique file IDs and a cleanup argument. The performance gap is the other: memoised H0, parallel E-step, optimized gradients and Hessians for both LMS and QML, all aimed at the distribution-analytic estimators that are expensive by construction. Convention borrowing from lavaan continues in message formatting and standard-error defaults.

◆ Prediction

The 1.0.20 and 1.0.21 releases both spent effort on residual covariances between endogenous and exogenous latent variables across estimation, prediction and standardization, and that thread has not obviously closed. The arrival of a second contributor moving MplusAutomation to Suggests suggests dependency trimming continues.

Alternatives to JointFPM and modsem

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

See all JointFPM alternatives → · See all modsem alternatives →

Recent activity from JointFPM and modsem

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

  1. 1mo agomodsemUnique Mplus file IDs, cleanup argument, LMS gradient refactor
  2. 2mo agomodsemComposite constructs for LMS, plus MC-LMS-CAT and MC-QML-CAT
  3. 3mo agomodsemPrint spacing and a partial-match fix in getSortedEtas()
  4. 4mo agomodsemCategorical argument for Mplus; partial support for the <~ operator
  5. 5mo agomodsemConsistent three-way interaction estimates with rcs=TRUE
  6. 6mo agomodsemSecondary pruning and a forward-difference Hessian mode
  7. 1y agoJointFPMmean_no() promoted to a stable interface
  8. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  9. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  10. 2y agoJointFPMStandardized marginal estimates plus input validation
  11. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between JointFPM and modsem?

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

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

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