Remove incorrect empty anchor justification #701
Merged
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.
The second point in the current version of the docs should not be possible because if it was (empty anchor returned and the prediction always changes, regardless of perturbation), the empty anchor would have precision ~0 and hence would not be returned in the first place. In fact, if the prediction does change a lot regardless of the perturbation, the data point is likely near the decision boundary and the algorithm will try longer and longer anchors to find something that satisfies the precision threshold.