Fix update_slice_len calculation in ScatterND
#157
Merged
Conversation
This file contains 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
From the spec: > updates is treated as a (q-1)-dimensional tensor of replacement-slice-values. > Thus, the first (q-1) dimensions of updates.shape must match the first > (q-1) dimensions of indices.shape. The remaining dimensions of updates > correspond to the dimensions of the replacement-slice-values The previous version was wrong, but happened to work for existing test cases.
robertknight
force-pushed
the
scatternd-fix
branch
from
6f14438
to
15f9f88
Compare
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.
From the spec:
The previous version was wrong, but by serendipity happened to work for existing test cases.
Fix fixes a crash in the
ScatterNDop I encountered when testing Piper TTS models (see #155).TODO: