← Back to home
Comparison · Infra & APIs

JointFPM vs surveytidy

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

JointFPM vs surveytidy: at a glance

FeatureJointFPMsurveytidy
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitysurvey-statistics, tidyverse, dplyr-verbs, metadata-tracking
Last editorial update49m 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 surveytidy?

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

Read the full surveytidy trajectory →

JointFPM vs surveytidy: 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
surveytidy
INFRA · APIS
0.0

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

◆ Current state

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

◆ Where it's heading

The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.

◆ Prediction

Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.

Alternatives to JointFPM and surveytidy

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

See all JointFPM alternatives → · See all surveytidy alternatives →

Recent activity from JointFPM and surveytidy

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

  1. 2mo agosurveytidymutate() syncs metadata for across() recodes
  2. 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
  3. 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
  4. 1y agoJointFPMmean_no() promoted to a stable interface
  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

Frequently asked questions

What is the difference between JointFPM and surveytidy?

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

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

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