You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automatic stopping when a certain metric reaches a certain value? #109
First, thank you so much for making this awesome project!
Second, is there currently a way to have OpenEvolve stop when a metric reaches a certain value, for example, when the combined score reaches 1? If not, do you plan on adding it? Thanks!
Great! Would also be nice if you could set if for individual scores too, for example if you are optimizing several things and want to start a separate phase of running at a certain point.
you can always implement specific things like that in the evalutor.py itself. OpenEvolve implementation doesn't know about the individual metrics a particular problem is optimizing for. It is left to the user to define them it only basis itself on the combined_score. e.g. If you want a particular score to trigger early stopping you can set combined_score to 1 when that individual metric is reached to do early stopping.
This is available now: pass --target-score on the command line, or target_score to run_evolution, and the run stops once combined_score reaches that value. To trigger on an individual metric, set combined_score accordingly in your evaluator, as described above. Please reopen if this doesn't cover your case.
Activity
codelion commentedon Jun 26, 2025
Good idea, we can add a config for early stopping on combined_score reaching a particular value.
AriKorpus commentedon Jun 26, 2025
Great! Would also be nice if you could set if for individual scores too, for example if you are optimizing several things and want to start a separate phase of running at a certain point.
codelion commentedon Jun 26, 2025
you can always implement specific things like that in the evalutor.py itself. OpenEvolve implementation doesn't know about the individual metrics a particular problem is optimizing for. It is left to the user to define them it only basis itself on the combined_score. e.g. If you want a particular score to trigger early stopping you can set combined_score to 1 when that individual metric is reached to do early stopping.
AriKorpus commentedon Jun 26, 2025
Oh smart. Good point
codelion commentedon Nov 2, 2026
This is available now: pass
--target-scoreon the command line, ortarget_scoretorun_evolution, and the run stops oncecombined_scorereaches that value. To trigger on an individual metric, setcombined_scoreaccordingly in your evaluator, as described above. Please reopen if this doesn't cover your case.