We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
Thank you for your excellent work. I'm interested in replicating your results using a pretrained model.
However, I noticed that the pretrained weights GitHub repository you provided for Vid2Vid are from https://github.com/junyanz/pytorch-CycleGAN-and-pix2pix instead of https://github.com/NVIDIA/vid2vid which is mentioned in the paper.
Therefore, I want to know which github repo is your Vid2Vid pretrained model use for.
Also, I would appreciate it if you could provide some instructions for using the pretrained weights you provided (https://drive.google.com/file/d/1hWV1rL9sKQJXsV7hPbLxHa8gSmyuMOky/view?usp=drive_link) because I would like to know whether there are some arguments different from the original repo when using it.
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Thank you for your excellent work. I'm interested in replicating your results using a pretrained model.
However, I noticed that the pretrained weights GitHub repository you provided for Vid2Vid are from https://github.com/junyanz/pytorch-CycleGAN-and-pix2pix instead of https://github.com/NVIDIA/vid2vid which is mentioned in the paper.
Therefore, I want to know which github repo is your Vid2Vid pretrained model use for.
Also, I would appreciate it if you could provide some instructions for using the pretrained weights you provided (https://drive.google.com/file/d/1hWV1rL9sKQJXsV7hPbLxHa8gSmyuMOky/view?usp=drive_link) because I would like to know whether there are some arguments different from the original repo when using it.
Thanks
The text was updated successfully, but these errors were encountered: