Skip to content

Conversation

un-knight
Copy link

I'm working with models/tutorials/image/cifar10/.

There is an error strided_slice() missing 1 required positional argument: 'strides' when I run the command python cifar10_train.py under the version of 0.12.0-rc1. Although the document said strides is optional.

So I replaced strided_slice with slice to make it work as a temporary solution.

I'm working with models/tutorials/image/cifar10/.

There is an error `strided_slice() missing 1 required positional argument: 'strides'` when I run the command `python cifar10_train.py` under the version of 0.12.0-rc1. Although the [document](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/api_docs/python/functions_and_classes/shard8/tf.strided_slice.md) said `strides` is optional.

So I replaced `strided_slice` with `slice` to make it work as a temporary solution.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@un-knight
Copy link
Author

I signed it

@googlebot
Copy link

CLAs look good, thanks!

@daviddao
Copy link
Contributor

Might that be a better solution: http://stackoverflow.com/questions/41195121/tensorflow-strided-slice-missing-argument-strides ? (instead of using tf.slice())

@un-knight
Copy link
Author

Hi! @daviddao, I can't say which one is better, though I had thought about both of the solutions. But the reason why I PR this solution (using tf.slice()) as a temporary solution is that you don't need to consider the value of parameter strides.

@dweekly
Copy link
Contributor

dweekly commented Dec 28, 2016

Looks like this may fix issue #817

@nealwu
Copy link
Contributor

nealwu commented Mar 15, 2017

Thanks! This should be covered by #1063 for 1.0, so I'm going to close.

@nealwu nealwu closed this Mar 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants