Suggestion: Multiple separate iteration values and different tiled outputs

[ProGamerGov]

The number of iterations used for the upres tiling should be an independent value of the original output's number of iterations. In practice I have found that high iteration counts work well for the original output, while a lower iteration counts work well for the upres tiling. It would be ideal to divide the tiling into 4 separate folders, for iteration 50, 150, 250, and 500 (or whatever values you want). Each of these folders should be used to create their own tiled image output. I find this works best to choose between multiple outputs, because of the unpredictability caused by upres. This is how I normally do things manually, and it doesn't cost extra time or resources due to the fact these iterations are done anyway while the neural network works towards your iteration value.

[0000sir]

That worth a shot

[ProGamerGov]

@0000sir If you see the provided output, you can see the different tiles are extremely visible. With a lower iteration count, this issue could be lessened, or even non-existent. I went for 250 iterations on each tile, but your script only saves the final output current. The work for iteration 50, 100, 150, 200, etc... was done either way, and when I did what the script does manually, I saved these other iterations along the way in case the tiles diverged too much by my target iteration count.

I am not sure how to properly make the script work with the -save_iter command, but this is something that would allow for dealing with poor U-press iteration choices.

[ProGamerGov]

So, by adding the -save_iter iter_value command to the command you paste into the script, you can produce final outputs with different iteration values. Though you need to remove iteration number from the tiles which have an iteration number in their name, so that the script recognizes them as the tiles you want to piece together.

[0000sir]

save different iter_value results to different directory should be a easier way.