← Back to home
Comparison · Infra & APIs

daedalus vs simDAG

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

daedalus vs simDAG: at a glance

FeaturedaedalussimDAG
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesepidemic-modelling, health-economics, npi-policy, ode-solversr-package, causal-inference, dag-simulation, discrete-event-simulation
Last editorial update29m ago3h ago
WebsiteVisit →Visit →

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 →

What is simDAG?

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

Read the full simDAG trajectory →

daedalus vs simDAG: editorial side-by-side

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.

S
simDAG
INFRA · APIS
2.5

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

◆ Current state

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

◆ Where it's heading

The package has been widening what a simulation can represent rather than deepening any one node. Networks arrived in 0.4.0 so individuals could depend on each other, discrete-event simulation in continuous time arrived in 0.5.0 as an alternative to the discrete-time engine, and 1.0.0 connected the two by letting continuous hazards feed the event-driven path. Alongside that, node types keep accumulating for outcome families the framework could not previously generate.

◆ Prediction

Expect the node library to keep expanding into outcome types the discrete-event engine can now support, though the recent releases suggest upstream dependency churn will keep consuming release slots.

Alternatives to daedalus and simDAG

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

See all daedalus alternatives → · See all simDAG alternatives →

Recent activity from daedalus and simDAG

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

  1. 18d agosimDAGCRAN-retention patch for upstream lme4 breakage
  2. 3mo agosimDAGArbitrary baseline hazards connect node_cox() to discrete-event sims
  3. 4mo agosimDAGTest-only fix for an upstream simr update
  4. 5mo agosimDAGAdds node_polr() for ordinal outcomes and rsurv node support
  5. 7mo agosimDAGAdds continuous-time discrete-event simulation
  6. 9mo agodaedalusVersion bump for a symposium preview build
  7. 9mo agodaedalusInterventions now lift in response to live R_t
  8. 10mo agosimDAGAdds link functions to node types and fixes a broken seed default
  9. 10mo agodaedalusWithin-sector contact scaling corrected to quadratic
  10. 10mo agodaedalusIllness-driven absence reworked in the cost model
  11. 10mo agodaedalusMultiple sequential time-limited closures
  12. 11mo agodaedalusState array indexing corrections; earlier projections unreliable

Frequently asked questions

What is the difference between daedalus and simDAG?

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

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

What are the best alternatives to simDAG?

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