-
Notifications
You must be signed in to change notification settings - Fork 411
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
Explicit cast to uint8
when bool inputs passed to argsort
in MAP
#983
Conversation
for more information, see https://pre-commit.ci
Codecov Report
@@ Coverage Diff @@
## master #983 +/- ##
=====================================
- Coverage 95% 95% -0%
=====================================
Files 177 177
Lines 7513 7514 +1
=====================================
- Hits 7139 7127 -12
- Misses 374 387 +13 |
…torchmetrics into fix/sorting_error/cuda
uint8
when bool inputs passed to argsort
in MAP (CUDA only)uint8
when bool inputs passed to argsort
in MAP
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.
LGTM
Thanks for getting this turned around so quickly! As #981 is a blocker for the project my team are working on, is there an estimate on when this will be released? |
we can do one during this week, just would also include #985 🐰 |
…983) * Explicit cast to torch.uint8 for bool types on CUDA * Add changelog entry Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Jirka <[email protected]> (cherry picked from commit a5f2e03)
What does this PR do?
Fixes #981
I can confirm that this is a regression from release 0.7.2, IMO: an explicit cast from
torch.bool
totorch.uint8
(on CUDA only) while applyingtorch.argsort
should fix this. Looks like PyTorch doesn't support sorting for boolean dtypes on CUDA devices:https://github.com/pytorch/pytorch/blob/1a7e43be141ce01469d7605075cb1008bf19abd7/aten/src/ATen/native/cuda/Sort.cpp#L80
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃