← Back to home
Comparison · Infra & APIs

JointFPM vs states

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

JointFPM vs states: at a glance

FeatureJointFPMstates
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitypolitical-science, panel-data, country-codes, datasets
Last editorial update2h 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 states?

State-panel tooling holding steady since its 2020 data and ergonomics release.

states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.

Read the full states trajectory →

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

S
states
INFRA · APIS
0.0

State-panel tooling holding steady since its 2020 data and ergonomics release.

◆ Current state

states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.

◆ Where it's heading

The package has reached the point where its own data and API are settled and the release trigger is upstream churn in the tidyverse. What movement there is goes toward making the two state lists interchangeable, with the microstates coding carried from G&W onto the COW data as the clearest example, rather than toward new datasets.

◆ Prediction

The next release is most likely another compatibility pass; a data refresh would be the signal that the package is active again.

Alternatives to JointFPM and states

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

See all JointFPM alternatives → · See all states alternatives →

Recent activity from JointFPM and states

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

  1. 0y agostatesplot_missing() test fixed for the next ggplot2
  2. 1y agoJointFPMmean_no() promoted to a stable interface
  3. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  4. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  5. 2y agoJointFPMStandardized marginal estimates plus input validation
  6. 2y agoJointFPMBug fixes for differences between mean-event functions
  7. 2y agostatesggplot2 and dplyr deprecation cleanup
  8. 2y agostatesBundled state data stripped to plain data frames
  9. 5y agostatesMicrostate coding for COW data and state_panel() shortcuts
  10. 7y agostatesSimpler defaults for state_panel() and plot_missing()

Frequently asked questions

What is the difference between JointFPM and states?

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

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

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