We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
dpt.reshape
The below example demonstrates different behavior in reshape method of NumPy and dpctl:
reshape
import numpy, dpctl, dpctl.tensor as dpt dpctl.__version__ # Out: '0.17.0dev0+325.g0cb2181547' a = dpt.ones((2, 1)) a.shape, a.strides # Out: ((2, 1), (1, 1)) b = dpt.reshape(a, (2, 1)) b.shape, b.strides # Out: ((2, 1), (1, 0)) # the output strides are changed a = numpy.ones((2, 1) a.shape, a.strides # Out: ((2, 1), (8, 8)) b = numpy.reshape(a, (2, 1)) b.shape, b.strides # Out: ((2, 1), (8, 8)) # the output strides are the same as for input array "a"
So, the question here if it's expected that the strides of output array might be changed when reshaping to the same shape?
The text was updated successfully, but these errors were encountered:
gemm_batch
dpnp.matmul
gemm
If shape is same as in array, reshape is a no-op
2829cb7
Closes gh-1664 If copy is not required, and requested shape is the same as the shape of the array, return the array itself.
Successfully merging a pull request may close this issue.
The below example demonstrates different behavior in
reshape
method of NumPy and dpctl:So, the question here if it's expected that the strides of output array might be changed when reshaping to the same shape?
The text was updated successfully, but these errors were encountered: