questions on double_size and some blurred results

[mcahny]

questions on double_size and some blurred results

[mcahny]

Hi all, thanks for your interest. To answer your questions,

The double_size case was trained with the mask where the hole region is filled with the value 0.5, and non-hole regions with 1.0. There is no special reason behind this choice.

About the fixed-size hole, your results look reasonable and I can reproduce that on the bear video.
My understanding on this result are based on these points:

• VINet can be divided into 1) an image-level encoder-decoder network, and 2) additional reference encoders that support the target frame inpainting.
• 1 performs the standard image inpainting and is supposed to be able to "hallucinate" on the never visible region.
• 2 performs "copy-and-paste" from neighbor frames onto the target frame hole region.
• While VINet is supposed to be good at both, the empirical results imply that training did not balance well between the both, and mainly focused on "copy-and-paste" learning. This would have led to poor "hallucination" performance and thus blurry results with fixed holes.

[ytongW]

Could you tell me how to change the size of output image?
when I changed the size of input image directly, I got this error.
RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 1. Got 32 and 64 in dimension 3 at /opt/conda/conda-bld/pytorch_1525909934016/work/aten/src/THC/generic/THCTensorMath.cu:111
if I resize the output image, then the image will get very blurred.
Thanks for your time!

[AjithPanja]

Yeah, I too noticed the blurry part while running the code with Bear video.
I would be really grateful if you could clarify my doubt 😅. From my understanding, the known pixels from the previous and future frames are filled, but how blind spot pixels are filled? (Eg. A trashcan in the same place throughout the video, If the trashcan has to be removed how it's pixels will be filled?)