← Back to home
Comparison · Infra & APIs

fdacluster vs gkwdist

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

Shared themes:r-package

fdacluster vs gkwdist: at a glance

Featurefdaclustergkwdist
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesfunctional-data-analysis, clustering, r-package, rcppr-package, statistical-distributions, numerical-stability, mle
Last editorial update53m ago2h ago
WebsiteVisit →Visit →

What is fdacluster?

Functional data clustering grew from one algorithm into a comparable suite

fdacluster clusters functional data while separating amplitude from phase variation, aligning curves as part of the clustering rather than before it. The algorithm set covers k-means, hierarchical clustering and DBSCAN, all producing a common caps result object so runs can be compared directly. Version 0.4.0 tightened the interface with is_domain_interval and transformation arguments describing the input data, added compatibility checking between incompatible option combinations, and split the L2 and normalized L2 distances into separate C++ classes to enforce that plain L2 cannot be combined with dilation or affine warping it is not invariant to.

Read the full fdacluster trajectory →

What is gkwdist?

gkwdist keeps finding that its distributions were returning the wrong numbers.

The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.

Read the full gkwdist trajectory →

fdacluster vs gkwdist: editorial side-by-side

F
fdacluster
INFRA · APIS
0.0

Functional data clustering grew from one algorithm into a comparable suite

◆ Current state

fdacluster clusters functional data while separating amplitude from phase variation, aligning curves as part of the clustering rather than before it. The algorithm set covers k-means, hierarchical clustering and DBSCAN, all producing a common caps result object so runs can be compared directly. Version 0.4.0 tightened the interface with is_domain_interval and transformation arguments describing the input data, added compatibility checking between incompatible option combinations, and split the L2 and normalized L2 distances into separate C++ classes to enforce that plain L2 cannot be combined with dilation or affine warping it is not invariant to.

◆ Where it's heading

The trajectory runs from method implementation toward guardrails and portability. Early releases added capability; recent ones prevent misuse and reduce weight - dplyr, forcats, tidyr and purrr removed in 0.4.0, furrr swapped for future.apply - while 0.4.2 is entirely C++ correctness, replacing Armadillo's whole-object finiteness check with scalar std::isfinite and fixing an integer overflow in linear index computation that broke large datasets. Cadence is roughly one release a year.

◆ Prediction

Given that the last two releases were dependency reduction and numerical correctness rather than method work, expect the next to continue in that vein unless a new clustering algorithm is contributed.

G
gkwdist
INFRA · APIS
2.5

gkwdist keeps finding that its distributions were returning the wrong numbers.

◆ Current state

The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.

◆ Where it's heading

Every release in this window is correctness work with an unchanged public API — critical MLE fixes in 1.1.3, a CRAN timing-test patch in 1.1.4, numerical corrections in 1.1.5. The recurring theme is that analytically correct formulas were being defeated by implementation details: name collisions, sign errors returning negative infinity where positive was required, and clamping thresholds that destroyed precision in the tails. Test infrastructure added in 1.1.2 validates analytical derivatives against numerical differentiation, which is how several of these were caught.

◆ Prediction

Expect further validation-driven fixes rather than new distributions, since the derivative-checking suite added earlier is still surfacing defects in existing routines.

Alternatives to fdacluster and gkwdist

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 fdacluster or gkwdist.

See all fdacluster alternatives → · See all gkwdist alternatives →

Recent activity from fdacluster and gkwdist

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

  1. 6d agogkwdistv1.1.5 — Numerical correctness fixes and componentwise derivative validation
  2. 2mo agogkwdistv1.1.4 — CRAN fix: skip timing-based tests on CRAN
  3. 2mo agogkwdistv1.1.3 — Critical MLE Bug Fixes & Numerical Corrections
  4. 7mo agofdaclusterInteger overflow fixed for large datasets, C++ finiteness checks corrected
  5. 7mo agogkwdistAdds analytical derivative validation across all sub-families
  6. 8mo agogkwdistRefactors the C++ backend around stable log-space utilities
  7. 1y agofdaclusterParallel worker setup and an acronym correction
  8. 1y agofdaclusterInput description arguments and enforced distance-warping compatibility
  9. 3y agofdaclusterMedian centroids and centroids defined on unioned grids
  10. 3y agofdaclusterNamespace notation and optional dependency guards
  11. 3y agofdaclusterHierarchical clustering, DBSCAN and a shared result class arrive together

Frequently asked questions

What is the difference between fdacluster and gkwdist?

Both compete on the same themes — r-package — within Infra & APIs. gkwdist is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is fdacluster better than gkwdist?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gkwdist is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to fdacluster?

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

What are the best alternatives to gkwdist?

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