← Back to home
Comparison · Infra & APIs

BayLum vs fdacluster

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

Shared themes:r-package

BayLum vs fdacluster: at a glance

FeatureBayLumfdacluster
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagsfunctional-data-analysis, clustering, r-package, rcpp
Last editorial update30m ago1h ago
WebsiteVisit →Visit →

What is BayLum?

Bayesian luminescence dating that finally replaced its folder-structure input format.

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

Read the full BayLum trajectory →

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 →

BayLum vs fdacluster: editorial side-by-side

B
BayLum
INFRA · APIS
0.0

Bayesian luminescence dating that finally replaced its folder-structure input format.

◆ Current state

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

◆ Where it's heading

Two long-running threads have converged: making JAGS runs survivable (parallel methods, halved MCMC memory, injectable custom models) and making the inputs survivable (YAML config, consistency checks, auto-detected sample names). With the deprecated generators on their way out, the next phase is removal rather than addition. Release cadence is roughly annual and slowing.

◆ Prediction

The deprecated Generate_DataFile(), Generate_DataFile_MG() and LT_RegenDose() are the obvious next casualties; a release that drops them would be the first breaking change since the YAML rework.

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.

Alternatives to BayLum and fdacluster

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

See all BayLum alternatives → · See all fdacluster alternatives →

Recent activity from BayLum and fdacluster

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

  1. 7mo agofdaclusterInteger overflow fixed for large datasets, C++ finiteness checks corrected
  2. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  3. 1y agofdaclusterParallel worker setup and an acronym correction
  4. 1y agofdaclusterInput description arguments and enforced distance-warping compatibility
  5. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  6. 3y agofdaclusterMedian centroids and centroids defined on unioned grids
  7. 3y agofdaclusterNamespace notation and optional dependency guards
  8. 3y agofdaclusterHierarchical clustering, DBSCAN and a shared result class arrive together
  9. 3y agoBayLumMCMC memory halved; density plots for age distributions
  10. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  11. 4y agoBayLumCustom model injection and RNG control for parallel runs
  12. 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data

Frequently asked questions

What is the difference between BayLum and fdacluster?

Both compete on the same themes — r-package — within Infra & APIs. BayLum and fdacluster 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 BayLum better than fdacluster?

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

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

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.