This repository was archived by the owner on Nov 17, 2023. It is now read-only.
Decouple dtype from shape for Random multinomial#15980
Merged
Merged
Conversation
Contributor
|
Test? |
Contributor
Author
|
I tested locally for from #15941 |
Contributor
|
Ok so this fixes a broken nightly test case? |
marcoabreu
approved these changes
Aug 24, 2019
Contributor
Author
|
@marcoabreu It doesn't fix a broken nightly test. The issue we encountered while writing nightly test for large vector (2**32) Currently, behavior of random.multinomial is to expect shape and dtype to agree. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Currently, if we pass shape >2**32 to random multinomial
It fails with this error
dtype' does not have a sufficient precision to represent the indices of the input array.It's wrong for an operator to expect the shape to fall within the limits of dtype. Reason - they are not related.
even if default dtype is float32, it shouldn't be restrict the shape space to 2**32.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.
Changes
Removed the check for shape to be within the MAX INT limit
Comments
Must be made to ensure shape and dtype are decoupled.