← Back to home
Comparison · Infra & APIs

cvms vs daedalus

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

cvms vs daedalus: at a glance

Featurecvmsdaedalus
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescross-validation, r-package, model-evaluation, visualizationepidemic-modelling, health-economics, npi-policy, ode-solvers
Last editorial update1h ago30m ago
WebsiteVisit →Visit →

What is cvms?

A cross-validation package whose real development has moved to its plotting function

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

Read the full cvms trajectory →

What is daedalus?

An epidemic-economic model teaching its interventions to react to the outbreak itself.

daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.

Read the full daedalus trajectory →

cvms vs daedalus: editorial side-by-side

C
cvms
INFRA · APIS
0.0

A cross-validation package whose real development has moved to its plotting function

◆ Current state

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

◆ Where it's heading

Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.

◆ Prediction

Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.

D
daedalus
INFRA · APIS
0.0

An epidemic-economic model teaching its interventions to react to the outbreak itself.

◆ Current state

daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.

◆ Where it's heading

The arc is toward a model that behaves like a policy simulator rather than a scenario calculator: interventions now have their own state machine, R_t is computed inside the ODE system, and event handling has been pulled out of the output object. Correction releases sit between the feature ones, including an indexing fix the maintainers flag as required for accurate projections. The versioning is patch-level but the changes are structural.

◆ Prediction

With R_t and the next-generation matrix now available in-model, the likely next step is richer response rules keyed to those quantities; the entries give no signal on when a stable 1.0 arrives.

Alternatives to cvms and daedalus

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 cvms or daedalus.

See all cvms alternatives → · See all daedalus alternatives →

Recent activity from cvms and daedalus

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

  1. 2mo agocvmsCoefficient extraction restored for multinom and mixed models
  2. 9mo agodaedalusVersion bump for a symposium preview build
  3. 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
  4. 9mo agodaedalusInterventions now lift in response to live R_t
  5. 10mo agodaedalusWithin-sector contact scaling corrected to quadratic
  6. 10mo agodaedalusIllness-driven absence reworked in the cost model
  7. 10mo agodaedalusMultiple sequential time-limited closures
  8. 11mo agodaedalusState array indexing corrections; earlier projections unreliable
  9. 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
  10. 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
  11. 1y agocvmsTile intensity by row or column percentages
  12. 1y agocvmsMultinom coefficient extraction fix after a parameters update

Frequently asked questions

What is the difference between cvms and daedalus?

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

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

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

What are the best alternatives to daedalus?

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