Fix the Hyperband configuration formula #89
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.
As highlighted in my blogpost [1], the formula used to computer the number of configurations for the successive halving step in hyperband deviates from the paper. In fact, there is an additional rounding operation on the s_max / (s+1) factor. Everything is explained in the blog post.
I also do not know why you are using an int() operator to round the value of n0 because it is originally a ceil operation. I suppose that this is why you need an additional max() in the computation of ns. The code is a bit intricated to me so I guess you can better tell than me. Do not hesitate to tell me if I can be of help or I am wrong.
[1] https://medium.com/data-from-the-trenches/a-slightly-better-budget-allocation-for-hyperband-bbd45af14481