-
Notifications
You must be signed in to change notification settings - Fork 691
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
Is there a reason why Single Precision versions of functions like leastSquares not exposed? #855
Comments
Honestly, there's no reason other than I started out prioritizing Double and never bothered. Happy to take a PR... |
For my own purposes, I just created a new file and it works. But I am guessing PR would be mean a lot more than that. Here's an example.
|
I would like to work on supporting single precision. But as you have mentioned in other PRs it seems you are busy refractoring the codebase to migrate to scala3. Let me know if it is a good idea to work on it. Or should it wait until then? |
Thanks @dineshdharme! scala3 is already supported since the breeze 2.0 release. I'm not doing any refactoring at all. To be honest, I'm not really going to do any work on breeze myself anymore, but I'm happy to review and merge a PR, answer questions, and even cut a release. |
Hello David, I created a PR for adding Float datatype support for leastSquares calculation. I tried my best. There could be inaccuracies in properly using Scala semantics for types and other issues. |
As the title says, it would be good for single precision versions
which make use of native libraries like mkl, openblas or nvblas
be exposed to the enduser. As these functions are already present
in netlib (https://github.com/luhenry/netlib), it shouldn't be too much of work.
The text was updated successfully, but these errors were encountered: