← Back to home
Comparison · Infra & APIs

CptNonPar vs robscale

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

CptNonPar vs robscale: at a glance

FeatureCptNonParrobscale
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themeschange-point-detection, nonparametric, defaults, preprocessingrobust-statistics, simd, performance, cran
Last editorial update46m ago23h 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 robscale?

A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.

robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.

Read the full robscale trajectory →

CptNonPar vs robscale: 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
robscale
INFRA · APIS
0.0

A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.

◆ Current state

robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.

◆ Where it's heading

Three releases in a fortnight walk a clear line: expand the public API, submit to CRAN, then tune. The 0.5.4 work is where that tuning shows, and it is unusually specific about hardware, raising sorting-network thresholds after benchmarking and dropping the AVX-512 path entirely in favour of a shorter AVX2-first dispatch chain. The build-fix lists are long, which is what a package fighting compiler and TBB variation across CRAN's platforms looks like.

◆ Prediction

The dispatch hierarchy has been simplified once already; further releases most likely continue narrowing the SIMD surface and hardening the configure step rather than adding estimators. A new estimator would be the surprise.

Alternatives to CptNonPar and robscale

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

See all CptNonPar alternatives → · See all robscale alternatives →

Recent activity from CptNonPar and robscale

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

  1. 4mo agorobscaleSIMD median networks land; AVX-512 dispatch is dropped
  2. 4mo agorobscaleCRAN submission ships 11 robust estimators with bootstrap intervals
  3. 5mo agorobscalescale_robust() dispatcher and four new estimators join the public API
  4. 8mo agoCptNonParData centred and scaled by default before detection
  5. 1y agoCptNonParImportance scores replace p-values; per-lag manual thresholds
  6. 2y agoCptNonParPaper link updated for CRAN checks
  7. 3y agoCptNonParDescription field and example cleanups

Frequently asked questions

What is the difference between CptNonPar and robscale?

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

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

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