← Back to home
Comparison · Infra & APIs

JointFPM vs rollupTree

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

JointFPM vs rollupTree: at a glance

FeatureJointFPMrollupTree
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilityrecursive-computation, tree-structures, dag, engine-package
Last editorial update45m 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 rollupTree?

The recursive-computation engine under massProps grows the accessors its consumer needed

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

Read the full rollupTree trajectory →

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

R
rollupTree
INFRA · APIS
0.0

The recursive-computation engine under massProps grows the accessors its consumer needed

◆ Current state

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

◆ Where it's heading

The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.

◆ Prediction

On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.

Alternatives to JointFPM and rollupTree

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

See all JointFPM alternatives → · See all rollupTree alternatives →

Recent activity from JointFPM and rollupTree

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

  1. 6mo agorollupTreeMissing column names in the new row setters
  2. 6mo agorollupTreeRow-level get and set accessors by key and by id
  3. 1y agoJointFPMmean_no() promoted to a stable interface
  4. 1y agorollupTreeMinor vignette improvements
  5. 1y agorollupTreeBadges and GitHub Actions added to the README
  6. 1y agorollupTreedefault_validate_dag() extends validation past strict trees
  7. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  8. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  9. 2y agoJointFPMStandardized marginal estimates plus input validation
  10. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between JointFPM and rollupTree?

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

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

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