Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Some bad results on kid-running case #17

Open
STLAND-admin opened this issue Jul 6, 2023 · 2 comments
Open

Some bad results on kid-running case #17

STLAND-admin opened this issue Jul 6, 2023 · 2 comments

Comments

@STLAND-admin
Copy link

STLAND-admin commented Jul 6, 2023

Hi zhengqi!

I tried to train the kid-running case but get some bad results, the only change is the chunk_size and N_rand to fit my GPU memory.
image
So I am also working on the problem and want to know if you can release the Kid-running checkpoint, I didn't find it with those links you offered.

update-------------------------------------------------------------------------------------------------------------
Well, I tried to increase the size of the above two parameters. The results seem much better. However, there are still some artifacts in some view.

kid-artifact-10
kid-artifact-42

Do you have the same problem in your checkpoints or training process? If not, would you please offer the checkpoints?

Thanks!

@zhengqili
Copy link
Contributor

zhengqili commented Jul 12, 2023

Hi. I observed such artifacts before for some of videos I tried. Usually it's due to insufficient initialization, bad source view feature selections, or small sampling pixel size. For this example, using default hyper-parameters is less likely to produce such artifacts. However, I can share the checkpoints I trained if you are interested.

@STLAND-admin
Copy link
Author

Yes, it will be nice if you can share the checkpoints, my email is [email protected]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants