Helper python script (w/ style_layer_weights) #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Runner script (test version)
Expand path
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created a helper Python (tested on 3.5.2) script run_neural_style.py to automate output file path and name generation.
python3 run_neural_style.py -style_image styles/style22_750.jpg -content_image input/sample1.jpg -optimizer adam -init image -output_path output -backend cudnn -style_weight 800 -content_weight 200 -style_scale 1.8 -learning_rate 3 -image_size 300 -tv_weight 0.001 -seed 150 -num_iterations 500will create aoutput/style22_750/sample1folder and the result file name will bei500.0cw200_sw600_adam_lr3_sc1.8_tv0.001.jpgThe command-line arguments are similar to the original ones, I've documented the difference in the readme.
Unfortunately, my fork initially was merged with the
style_layer_weightsPR, but that's not a destructive change, so I don't think it's a problem.There are too many commits in my brach with small fixes, so if you want to merge my changes, I'd recommend to merge them as one commit.