epsilon greedy candidate selector #109
Open
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.
I implemented a epsilon greedy candidate selector strategy, added it to the API and added some tests (for all candidate selectors).
It is not fully documented yet, but I wanted to make sure that I'm on the right path with the API. I changed it a bit so that
optimize
also accepts aCandidateSelector
subclass directly, so that we can specify further hyperparameters (like the epsilon in this case).What do you think, @LakshyAAAgrawal ? :)
Plan is to add more candidate selection strategies (Softmax, Thompson Sampling, UCB1 etc.) to the repo and compare them to each other.