← Back to home
Comparison · Infra & APIs

CptNonPar vs rollupTree

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

CptNonPar vs rollupTree: at a glance

FeatureCptNonParrollupTree
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themeschange-point-detection, nonparametric, defaults, preprocessingrecursive-computation, tree-structures, dag, engine-package
Last editorial update48m ago2h ago
WebsiteVisit →Visit →

What is CptNonPar?

Nonparametric change point detection swaps p-values for importance scores.

CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.

Read the full CptNonPar 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 →

CptNonPar vs rollupTree: editorial side-by-side

C
CptNonPar
INFRA · APIS
0.0

Nonparametric change point detection swaps p-values for importance scores.

◆ Current state

CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.

◆ Where it's heading

The package is tightening the statistical interface it exposes: p-values gave way to importance scores across all three detection functions, manual thresholds became specifiable per lag, and the latest release makes centring and scaling the default preprocessing step. Each change folds a decision the user previously had to make into the package itself.

◆ Prediction

Expect further work on defaults and reporting around the existing MOJO estimators rather than a new detection method.

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

See all CptNonPar alternatives → · See all rollupTree alternatives →

Recent activity from CptNonPar 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. 8mo agoCptNonParData centred and scaled by default before detection
  4. 1y agorollupTreeMinor vignette improvements
  5. 1y agorollupTreeBadges and GitHub Actions added to the README
  6. 1y agoCptNonParImportance scores replace p-values; per-lag manual thresholds
  7. 1y agorollupTreedefault_validate_dag() extends validation past strict trees
  8. 2y agoCptNonParPaper link updated for CRAN checks
  9. 3y agoCptNonParDescription field and example cleanups

Frequently asked questions

What is the difference between CptNonPar and rollupTree?

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

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

Top CptNonPar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CptNonPar alternatives" section above for the current picks, or visit /alternatives/cptnonpar 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.