Issues w/ running on Windows about neural-dream HOT 26 OPEN

@ad48hp That issue occurs when the smallest octave image size is too small for the model. A quick test with the GoogleNet Caffe models shows that they require both height and width to higher than 223px.

This will result in an error because one of Octave 1's dimensions is than 223px:

Performing 2 octaves with the following image sizes:
  Octave 1 image size: 208x278
  Octave 2 image size: 348x464

For the example images, I used -num_octaves 2 -octave_scale 0.6 -image_size 512, which resulted in Octave 1's smallest dimension being greater than 223:

Performing 2 octaves with the following image sizes:
  Octave 1 image size: 230x307
  Octave 2 image size: 384x512

Octaves as I understand are pretty much the same thing as the multiscale resolution technique used with style transfer. The -octave_scale value tells the code how much to reduce the image in size, and the -num_octaves tells the code how many times to do that.

from neural-dream.

Seems to work now, though not sure why, but the DeepDreaming is incredibly slow with this one..
On the Caffe linux version, image took few seconds to process, here one octave takes minutes.. (both on CPU)

Could ya look into that ?

This is the script i tried..
Dreamify

from neural-dream.

@ad48hp I'll look into it. Have you tried using -backend mkl when using the CPU at all? That should make it faster.

from neural-dream.

Seems to not go faster.
Also, what's the learning_rate parameter doing here, isn't that supposed to be used only for training phase ?

Can't yet find that one in the dreamify script..

from neural-dream.

The -learning_rate parameter is the same thing as the 'step size' on other DeepDream projects. On Dreamify, it's called step_size. It's the size of the 'jump' or 'step' towards the network's goal. If it's too high you can overshoot, and if it's too low then it will take forever to reach the goal.

If the learning rate is set too high, the image will look like this:

If the learning rate is set too low, then very little if any change will occur on the output image.

Different models can require different learning rates, and you may have to play around with the values to find one that works. PyTorch VGG models for instance will require a really low learning rate, like 0.0055 or something like that. Caffe models tend to work better with learning rates of around 1-5.

from neural-dream.

Okay, seems to be running fine now, maybe the speed gets higher when it's run few times..
I have a request, if ya don't mind, it's quite challenging maybe yet for me to orientate in other people's codes, so it might take some time for me to implement it..

The code i wrote for myself back then was able to pick-up w/ the zooming where it last ended, so let's say i wanted 1000 pictures to be generated, but on 437 i stopped it, and then when i runned it again it continued with 438..

Could ya implement it here, boi ?

from neural-dream.

@ad48hp For the moment you can try this: https://github.com/ProGamerGov/neural-dream/tree/output-image-name. The -output_start_num parameter will let you start the output number at a number of your choosing. I'll probably delete the branch and merge it into the master branch when I have more time, but for the moment all you need is the neural_dream.py file from the branch I linked.

I made the -output_start_num parameter start at the number that you give it, as I wasn't sure if it was better to have it be -output_start_num + 1. It's possible that I may change how it works.

from neural-dream.

How that script worked is that it used path.isfile to search for the last image, and then use it..
Only if no images were present in the output directory, it used the input image..

Check this script yet

from neural-dream.

On Windows, CUDA backend writes "RuntimeError: error in LoadLibraryA"..

I wrote..
'import ctypes
ctypes.cdll.LoadLibrary('caffe2_nvrtc.dll')'
in neural_dream.py after 'import torch'
and now it seems to work..

Src

from neural-dream.

Also, i was able to reproduce the error i wrote you about! ^^
https://github.com/ad48hp/TemporaryFiles/tree/master/NeuralDream

python neural_dream.py -content_image steve-halama-paxhSiyjndU.png -model_file models/googlenet_places205.pth -init image -gpu 0 -num_iterations 600 -octave_iter 50 -octave_scale 0.4 -image_size 576 -learning_rate 6 -zoom 98 -backend cudnn -output_image output2/t.png

Can you reproduce the results ?

from neural-dream.

@ad48hp The parameters don't seem to raise that PyTorch error that you posted above. The content image you are using seems extremely bright, and using -adjust_contrast 99.999 seems to change that, but changes the output look a bit.

from neural-dream.

I meant, i was able to reproduce the issue i wrote about here, oddly enough with the Places205 model path as well..

Img.

Iteration 98

Iteration 201

What's weird is that at the beggining, i wasn't getting those shapes at all and now consistently.. Isn't there some sort of cache that keeps ruining it (i tried to remove the __pycache folders, didn't changed anything so far)..

from neural-dream.

The learning rate that you are using seems like it might be a bit too high. Lowering it to 1.6 resulted in this output at 29 iterations:

Using -lap_scale 4, and a learning rate of 1.6, I got this at 11 iterations:

I've found that the best results sometimes require taking things slow initially, because the network has more time to build the details without overshooting.

from neural-dream.

That sucessfully fixed the problem with Places205 !
Sadly, the Places365 seems to do the same problem..

python neural_dream.py -content_image steve-halama-paxhSiyjndU.png -model_file models/googlenet_places365.pth -init image -gpu 0 -num_iterations 600 -octave_iter 24 -octave_scale 0.4 -image_size 576 -learning_rate 0.66 -zoom 98 -backend cudnn -output_image output22/t.png

Iteration 18

Iteration 36

from neural-dream.

@ad48hp I've found that results like those are normally caused by the inputs and parameters that you have chosen. The content image you are using may be affecting the results. You can try adding -channel_mode avg -channels 10 or -channel_mode weak -channels 10 -lap_scale 4 and potentially use a learning rate of around 1.5 if you want.

from neural-dream.

Ha, ya seem to be yet way better at it than me !
Can you look at (implementing) this model ?
https://github.com/vpulab/Semantic-Aware-Scene-Recognition

Under Places365 "Ours" it ends with "tar" but from what i look there's no archive in it, so ya can just remove the 'tar' extension from the filename completely..

from neural-dream.

Also, the NSFW network doesn't seem to work..
AttributeError: 'ResNet_50_1by2_nsfw' object has no attribute 'inception_4d_3x3_reduce'

from neural-dream.

@ad48hp That's because it doesn't have the same layer names as the GoogleNet models. Use the -print_layers command when using the model, or check out the list of layer names here, to see the possible values.

from neural-dream.

I've added the -output_start_num parameter to the master branch, in addition to some other new features and fixes: 9bea997

from neural-dream.

Shouldn't the If channel_mode 'is set to a value other than all, only the first value in the list will be used' part in Readme also include 'ignore' ?

Also, can ya now add one tiny thing, that when the output_start_num is settled to a value greater than 1, it would automatically load the t(output_start_num - 1).png file in the output directory or something like that yet ?

from neural-dream.

@ad48hp Good catch!

I'll have to think about how I'd implement such a feature. For the moment though, it's simple enough to manually find the image highest number.

from neural-dream.

I should mention that if you add before_ to the layer name of a GoogleNet, Inception, or ResNet model, like adding before_ to inception_4d_3x3_reduce to make before_inception_4d_3x3_reduce, the DeepDream layer will be placed before the specified layer and not right after it.

from neural-dream.

Also, this is a thing i believe is not directly relevant to this repository, but for some reason, DeepDream scripts run fast at the beggining, and then, after about 20 minutes of runtime, it slows down tredemounsly, sometimes yet rerunning the app helps temporarily, but after a while, the speed goes terrible again (first about 6 iterations per seconds then drops to about 1 iteration per 3 seconds).. Reported GPU usage is consistently low (even when setting NVIDIA to highest performance setting) and goes slow even with MSI Afterburner..

CPU speed goes from 45% to about 24% after a while..
Process priority of Python didn't seem to change anything yet either..

from neural-dream.

I would expect if there was a memory leak, then usage would increase. I changed a line of code in the update branch that could fix the issue if it was caused by a bug in my code: https://github.com/ProGamerGov/neural-dream/tree/update. If that doesn't resolve it, then there could be something else going on.

from neural-dream.

I'll try the update soon hopefully..
The 'old' version now gave me this after about few hours of running..
Traceback (most recent call last): File "neural_dream.py", line 761, in <module> main() File "neural_dream.py", line 233, in main net(img) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 296, in forward return self.net(self.input_net(input)) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\models\googlenet\googlenetplaces.py", line 275, in forward inception_4d_3x3_reduce = self.inception_4d_3x3_reduce(inception_4c_output) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 534, in __call__ hook_result = hook(self, input, result) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\loss_layers.py", line 138, in forward self.loss = self.dream(output.clone()) * self.strength File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\loss_layers.py", line 104, in forward input = self.lap_pyramid(input) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 134, in forward return self.lap_merge(self.pyramid_list(input)) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 122, in pyramid_list input, hi = self.split_lap(input) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 116, in split_lap gt = self.gauss_blur_hi(input) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 79, in forward return self.guass_blur(input) File "C:\Python38\lib\site-packages\torch\nn\modules\module.py", line 532, in __call__ result = self.forward(*input, **kwargs) File "D:\Cancer\neural-dream_2\neural_dream\dream_utils.py", line 62, in forward input = self.conv(input, weight=self.weight, groups=self.groups) RuntimeError: cuda runtime error (700) : an illegal memory access was encountered at C:/w/1/s/windows/pytorch/aten/src\THCUNN/generic/SpatialDepthwiseConvolution.cu:89

from neural-dream.

That looks like it may be a PyTorch bug:

NVIDIA/apex#319
pytorch/pytorch#21819
https://discuss.pytorch.org/t/cuda-runtime-error-700-illegal-memory-access/71100/9

It doesn't look like anyone has been able to reliably reproduce the error though.

from neural-dream.