Numba sparse dot: use final precision in intermediate computations#2159
Open
ricardoV94 wants to merge 1 commit into
Open
Numba sparse dot: use final precision in intermediate computations#2159ricardoV94 wants to merge 1 commit into
ricardoV94 wants to merge 1 commit into
Conversation
Numba underpromotes relative to numpy/scipy mixed scalar * array dtypes
ricardoV94
commented
May 20, 2026
| col_idx = x_ind[idx] | ||
| value = x_data[idx] | ||
| value = out_type(x_data[idx]) | ||
| z[row_idx] += value * y[col_idx] |
Member
Author
There was a problem hiding this comment.
these are the branches where we do scalar * array, that numba may underpromote relative to numpy/scipy
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.
Fixes a flaky test (see https://github.com/pymc-devs/pytensor/actions/runs/26150694899/job/76918627812#step:6:5422)
It doesn't cause meaningful slowdown in some benchmarks I did and it matches scipy in precision for mixed dtypes
Numba does scalar int32|64 * array float32 in float32 precision, whereas numpy does it in float64 precision. Similar for discrete * complex64