-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Gaussian nll loss scalar variance support #138931
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
Gaussian nll loss scalar variance support #138931
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138931
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (1 Unrelated Failure)As of commit 6da0ea9 with merge base de34f58 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
7e35745 to
50ba45c
Compare
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: 3 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
Seems like CI is failing |
I think it wasn't liking the fact I had used |
|
@mikaylagawarecki I've updated the PR which should fix the failing CI, if you would be able to re-trigger that workflow if you're happy with the update? |
|
Thanks! I think the only remaining failure is the bc-lint here: https://github.com/pytorch/pytorch/actions/runs/11784651031/job/32831020347?pr=138931#step:2:833 |
Hi @mikaylagawarecki, would you be able to take a look at this comment if you get a chance? I believe adding that label (following the docs here) and rerunning the bc-lint check should fix the last remaining failing check. Thanks! 🙏 |
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
7c7cc82 to
6da0ea9
Compare
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: 3 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
Hi @mikaylagawarecki - sorry to bother you again (and hopefully last time!). |
|
@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 |
Fixes pytorch#138747 Adds support for `variance` being a Tensor or a float in `gaussian_nll_loss` to avoid a cpu-gpu sync point in the loss function, when the variance is a static tensor like `<scalar>*torch.ones_like(input)` Pull Request resolved: pytorch#138931 Approved by: https://github.com/mikaylagawarecki
Fixes #138747
Adds support for
variancebeing a Tensor or a float ingaussian_nll_lossto avoid a cpu-gpu sync point in the loss function, when the variance is a static tensor like<scalar>*torch.ones_like(input)