Closed alexrey88 closed 3 years ago
I don't think we'll be playing around that much with the diff transforms, can it just be a binary flag in opts.data? that would simplify the interface and the code.
What do you think?
@vict0rsch it's already an option in opts.gen.p.apply_diff_augment. You mean that it should be somemewhere else in our opts dict?
Todo: use those transforms in wildfire instead of using PIL to speed up inference
Two main changes:
Link for diff experiment ["m,s"]: NewTransforms=ON vs NewTransforms=OFF.
Link for diff experiment ["p"]: DiffAugm=ON vs DiffAugm=OFF.
(Note: for now, if "m" and "p" are both in
opts.tasks
, the new transforms won't be apply to the input image for the training procedure, they will only be used for discriminator and generator updates of the painter. This is to avoid applying the transforms twice and giving a transformed image as input of the painter).Visual results of the transforms:![val_r_s_10_#3_step_10](https://user-images.githubusercontent.com/54865729/100182080-c2f32f00-2ea9-11eb-96d6-c5c39c84efee.png)