HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
daedalus vs mize
A side-by-side editorial comparison of daedalus and mize — release velocity, themes, recent moves, and the top alternatives to consider.
daedalus vs mize: at a glance
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.
What is mize?
A numerical optimization toolkit that has been feature-complete and quiet since 2017
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
daedalus vs mize: editorial side-by-side
daedalus
0.0INFRA · APIS
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.
mize
0.0INFRA · APIS
A numerical optimization toolkit that has been feature-complete and quiet since 2017
◆ Current state
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
◆ Where it's heading
The pattern is a stable library rather than an abandoned one. Fixes address real reports - a bracket_step error when the Schmidt line search exhausts its function evaluation budget, an incorrect gradient count under backtracking with a specified step_down - and the maintainer used one release note to clarify that backtracking behaviour differs depending on whether step_down is supplied, which reads as answering a recurring question. The five and a half year gap between 0.2.4 and 0.2.5 is the clearest signal: the package is maintained on demand, not developed.
◆ Prediction
Expect nothing until an R or CRAN policy change forces another compliance patch, which is what triggered the most recent release.
Alternatives to daedalus and mize
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 mize.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
See all daedalus alternatives → · See all mize alternatives →
Recent activity from daedalus and mize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agomizeCRAN compliance patch after five years of silence
- 9mo agodaedalusVersion bump for a symposium preview build
- 9mo agodaedalusInterventions now lift in response to live R_t ⚡
- 10mo agodaedalusWithin-sector contact scaling corrected to quadratic
- 10mo agodaedalusIllness-driven absence reworked in the cost model
- 10mo agodaedalusMultiple sequential time-limited closures
- 11mo agodaedalusState array indexing corrections; earlier projections unreliable
- 5y agomizeBacktracking line search reporting and documentation fix
- 6y agomizeR-devel compatibility fix for class checking
- 7y agomizeSchmidt line search error when the evaluation budget is exhausted
- 7y agomizeStage check fix for bold driver and backtracking
- 9y agomizeCRAN release 0.1.1
Frequently asked questions
What is the difference between daedalus and mize?
They serve adjacent needs but don't currently overlap on shipped themes. daedalus and mize 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 daedalus better than mize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. daedalus and mize 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 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 mize?
Top mize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mize alternatives" section above for the current picks, or visit /alternatives/mize for the full list with editorial commentary on each.