-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Slice op: 'starts' and 'ends' values resulted in a negative dimension #28
Comments
@skottmckay helped clarify why my case wrong. basically, I am using starts = [-1], ends=[0]. in original tf.stride_sclice, this is allowed since another parameter stride=[1]. in onnx, -1 will become a concrete valid positive numb before running. ends will not. So I got this error. seems not a bug, more likely I am using in an inproper way. closing this. thanks for the investigation. |
tmccrmck
pushed a commit
to tmccrmck/onnxruntime
that referenced
this issue
Aug 28, 2019
Some Bug fixes and clean up
natke
referenced
this issue
in natke/onnxruntime
Feb 15, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sometime slice need -1 in starts or ends, onnx doc actually allow https://github.com/onnx/onnx/blob/master/docs/Changelog.md#slice-1
So I think this is a bug. This is blocking a real model conversion, could anybody familiar with this take a look? Thanks a lot.
The text was updated successfully, but these errors were encountered: