Fixing Nelder-Mead in box optimization #1080
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.
This fixes the issue raised in #912. When Nelder-Mead's initial state is created, some of the points in the simplex lie outside of the box, so that the value of the corresponding logarithm is infinite. Since the barrier parameter is initially zero, this results in the objective's value at those points being zero * Inf = NaN, which trips up the optimizer. Starting out with a small but nonzero barrier parameter instead fixes the issue (resulting in the objective being infinite outside the box) and the code snippets that were given in the aforementioned post now give the correct results. However, this is more of a band-aid than anything else, as it seems reasonable to think that the points in Nelder-Mead's simplex should always satisfy the box constraints. Enforcing this would require changing large portions of the code.