-
Notifications
You must be signed in to change notification settings - Fork 482
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
TypeError?Need help #56
Comments
Same error. |
Same error. Seeking for help. Thanks! python3 neural_artistic_style.py --subject a.JPG --style images/starry_night.jpg +++++++++++++++++++++++++++++++++++++++++++++ python neural_artistic_style.py --subject a.JPG --style images/starry_night.jpg |
Same error |
make sure that you have installed the right type of imagenet-vgg-verydeep-19.mat file since that what was causing the error for me. |
@TylerBohrer |
@TylerBohrer |
Same error, on mac, NOT using CUDA back end. |
Same Error here on windows, also not using cuda. |
maybe I found my problem, I had to change the numpy module to version 1.11.0 |
Dear andersbll,
I run it , but i got a typeerror.Python3.5
F:\mew\neural_artistic_style-master>python neural_artistic_style.py --subject images/1.jpg --style images/2.jpg
CUDArray: CUDA back-end not available, using NumPy.
Traceback (most recent call last):
File "neural_artistic_style.py", line 138, in
run()
File "neural_artistic_style.py", line 116, in run
args.smoothness)
File "F:\mew\neural_artistic_style-master\style_network.py", line 99, in init
next_subject = layer.fprop(next_subject)
File "F:\mew\neural_artistic_style-master\style_network.py", line 18, in fprop
y = self.conv_op.fprop(x, self.weights.array)
File "C:\Users\iDream\AppData\Local\Programs\Python\Python35\lib\site-packages\cudarray-0.1.dev0-py3.5-win-amd64.egg\cudarray\numpy_backend\nnet\conv.py", line 20, in fprop
convout = ca.empty(convout_shape, dtype=imgs.dtype)
TypeError: 'float' object cannot be interpreted as an integer
I am looking for your favorable reply at your convenience.Thank you.
The text was updated successfully, but these errors were encountered: