Repository navigation
[search][optimizers]: added pause/resume from log, modified random forests. - #163
Merged
liamsemeria merged 4 commits intoOct 30, 2026
Merged
Conversation
…le beta decay option, changed the presets
guillon
reviewed
Oct 27, 2026
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
liamsemeria
force-pushed
the
dev/sliam/optimizer-resume
branch
from
October 28, 2026 13:14
6690e13 to
0216a46
Compare
Contributor
Author
|
@guillon updated it to restore from the last batch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
For long runs, the ability to resume a run from a results log was requested. Also the random forests had no filtering to avoid re-evaluating candidates, so it would end up using the same candidates as it converged.
Description
The resuming just starts from a new seed, determined by the number of trials that were executed.
I also changed the presets, since the filtering made the presets behave more similar to each other, and allowed a standard ucb acquisition converge similarly to the current random forests presets.
random-forest-default: used to berandom-forest-explorebut It behaves the best out of the 3 old presetsrandom-forest-ucb: the same random forest parameters as the previous default, but standard ucbrandom-forest-ucb-explore: the same as above but more weight on std dev, could be better forruns with lots of trialsrandom: same as beforeIn terms of differences in performance there isn't a huge difference, but I would recommend using the ucb presets for runs with more than 400 trials.
Discussion
I kept the default to have the decay on the standard deviation in the ucb since it converges a little but faster, but we could change the default to be standard ucb instead.