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.

Sign up for GitHub

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

Jump to bottom

Deal with f64 / f32 type mismatch. Add in prio? #17

Open
MxmUrw opened this issue Dec 19, 2022 · 2 comments
Open

Deal with f64 / f32 type mismatch. Add in prio? #17

MxmUrw opened this issue Dec 19, 2022 · 2 comments
Assignees
@MxmUrw

Comments

@MxmUrw
Copy link
Contributor

MxmUrw commented Dec 19, 2022

No description provided.

@MxmUrw MxmUrw converted this from a draft issue Dec 19, 2022
@MxmUrw
Copy link
Contributor Author

MxmUrw commented Dec 19, 2022

Currently prio returns an f64 vector, but we calculate with f32 numbers in our numpy fl example.

@MxmUrw MxmUrw self-assigned this Dec 19, 2022
@MxmUrw MxmUrw moved this from Todo to Subtasks - Next up in Milestone2&3 Dec 19, 2022
@MxmUrw
Copy link
Contributor Author

MxmUrw commented Dec 19, 2022

I now manually cast in the DPSAStrategyWrapper to f32.

@MxmUrw MxmUrw moved this from Subtasks - Next up to Todo in Milestone2&3 Dec 19, 2022
@MxmUrw MxmUrw moved this from Todo to Subtask - Cold Storage in Milestone2&3 Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MxmUrw MxmUrw

Labels
None yet
Projects
Milestone2&3
Status: Subtask - Cold Storage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MxmUrw