Repository navigation
Improve stability of BCE loss calculation for input probabilities close to or exactly 0 or 1 - #1280
Merged
Merged
Conversation
Member
|
Cool, thanks. Maybe we should in addition add a note about using the logits directly instead to the docstring? If you have values that extreme the best thing to do is avoid explicitly computing the probs (use |
Contributor
Author
|
Sounds good, updated docstring as suggested |
awni
reviewed
Jul 23, 2024
awni
approved these changes
Jul 23, 2024
awni
left a comment
Member
There was a problem hiding this comment.
Thanks! Will merge when tests clear.
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.
Proposed changes
Predicted probabilities that are close to, or exactly 0 or 1, may result in
numerical instabilities or undefined values in a Binary Cross-Entropy (BCE)
loss calculation.
Currently, our BCE function will return
nanin such scenarios.If we clip the logs in the BCE loss calculation, we can always return a finite
loss value.
This is indeed the PyTorch approach [1]:
[1] https://pytorch.org/docs/stable/generated/torch.nn.BCELoss.html
This PR suggests and implements this log clipping in the BCE formula.
Implementation
Apply
mx.clip(..., a_min=-100)to themx.log()calculations inthe BCE loss function.
Following
pytorch, and to always obtain a finite loss, clipping is alwaysdone (and uses the same
pytorchclip value of -100).But if desired, we can add a parameter like
clip=TrueNote: both before and after this implementation, a
nanwill still be returnedfor negative input probabilites.
Example
Current behavior:
New behavior:
New behavior matches
pytorch:References
PR that added support for probabilities: #492
Checklist
Put an
xin the boxes that apply.pre-commit run --all-filesto format my code / installed pre-commit prior to committing changes