-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[BE] Use torch.special.expm1
#141518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BE] Use torch.special.expm1
#141518
Conversation
Instead of `torch.exp(x)-1`, as suggested by TorchFix
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/141518
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 16f8ec8 with merge base b18bbc9 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Instead of `torch.exp(x)-1`, as suggested by TorchFix Pull Request resolved: pytorch#141518 Approved by: https://github.com/kit1980
Instead of `torch.exp(x)-1`, as suggested by TorchFix Pull Request resolved: pytorch#141518 Approved by: https://github.com/kit1980
Instead of
torch.exp(x)-1
, as suggested by TorchFix