[CUDA] Fix random generator routines for f32 and f64 to make sure the returned value is in [0, 1) #4243
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
…ed value is in [0, 1)
|
✔️ Deploy Preview for docsite-preview ready! 🔨 Explore the source changes: 596f243 🔍 Inspect the deploy log: https://app.netlify.com/sites/docsite-preview/deploys/62035e4c0affcf0008382812 😎 Browse the preview: https://deploy-preview-4243--docsite-preview.netlify.app |
neozhaoliang
changed the title
…ed value is in [0, 1)
qiao-bo
reviewed
Feb 9, 2022
qiao-bo
approved these changes
Feb 9, 2022
|
The typo is fixed. |
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.
Currently the return value by
ti.random(f32)(orti.random(f64)) has a chance to be equal to 1.0, due to float precision problem. This PR fixes this problem.