Skip to content
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

[RLlib] Issue 23689: tf Initializer has hard-coded float32 dtype. #23741

Merged

Conversation

sven1977
Copy link
Contributor

@sven1977 sven1977 commented Apr 6, 2022

[RLlib] Issue 23689: tf Initializer has hard-coded float32 dtype.

Why are these changes needed?

Issue #23689

Related issue number

Closes #23689

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@avnishn
Copy link
Contributor

avnishn commented Apr 6, 2022

The idea is fine but I guess we'll need some function to convert to the analogous np type.

Copy link
Member

@gjoliver gjoliver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch ...

@gjoliver
Copy link
Member

gjoliver commented Apr 6, 2022

a lot of unit test failure though. I think the default type for dtype may need to be np.float32.

@sven1977
Copy link
Contributor Author

sven1977 commented Apr 7, 2022

Oh, yeah, didn't even think about this. Let's just make float32 the default (instead of None). I do think float64 could also make sense here, so the PR and issue themselves are valid.

@sven1977 sven1977 merged commit 4d285a0 into ray-project:master Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] [RLib] rlib type hardcoding issues
3 participants