-
Notifications
You must be signed in to change notification settings - Fork 19.4k
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
Feature request: keras.ops.linalg.lstsq #19678
Comments
Yes, that's in scope and it seems straightforward. I'm curious, what are you building that requires all these niche linalg ops? |
I've investigated this, and it's actually impossible to achieve consistency across backends for the We could make the function only return Looking at code in the wild I could only find samples that used |
yeah I think it makes sense to only return |
For reference, TensorFlow's I added the API, only returning |
Can this be added? It seems like it should be straightforward to implement, as it's just a thin wrapper around a SVD (in JAX at least https://github.com/google/jax/blob/main/jax/_src/numpy/linalg.py#L1368-L1406), and y'all already have SVD implemented.
The text was updated successfully, but these errors were encountered: