Skip to content
New issue

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

why the inference results are not aligned with the validation results? #18

Open
GFENGG opened this issue Jan 30, 2024 · 3 comments
Open

Comments

@GFENGG
Copy link

GFENGG commented Jan 30, 2024

Hello, i used the weights saved after the training step to inference, but the results are not aligned with the results generated from the last validation step in training. So what is the reason for this phenomenon?

@ruizhaocv
Copy link
Collaborator

Hi. Typically, this is because the randomly sampled noises are different from the training stage.
Could you please provide more details? Like are you training MotionDirector on a single video or multiple videos?

@GFENGG
Copy link
Author

GFENGG commented Feb 4, 2024

Hi. Typically, this is because the randomly sampled noises are different from the training stage. Could you please provide more details? Like are you training MotionDirector on a single video or multiple videos?

Thanks for your reply, your answer helps, it is maybe different settings between training and inference. I have another question, how is the generalization ability of MotionDirector? For example, if i use a custom dreambooth weight, which is different from training. Can the temporal weights trained from MotionDirector work under this situation?

@ruizhaocv
Copy link
Collaborator

If you use DreamBooth to only finetune the spatial layers, I think it is OK, just like the results shown here. If the temporal layers are also changed, I'm not sure what will happen. You can try it out. Looking forward to your insights.

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

No branches or pull requests

2 participants