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
How many iterations does FlownetC need? #3
Comments
On which test set are you evaluating? Can you share the EPE you got (and maybe the flow image)? Which learning rate did you use? For the chairs schedule in the config template, you can train for at least 500K iterations for best results. |
I use flying chairs as training set as well as test set. I got EPE 4.55 after 200k iterations. I start with lr 1e-4 and half it after the first 100k iterations. About the detailed loss weight:
Here are some examples: |
Do you plan to train on a different dataset using chairs as a pretraining or will you train on flying chairs only? If you only train on this dataset, i would suggest training again, this time using ternary_weight = 1.0 and commenting out photo_weight for better results. As we did not do a parameter search for optimal chairs performance, the optimal smoothness weight might also be different. But disabling photo_weight alone may improve results a lot. |
Thanks for your reply. I do use chairs as the pretraining. I am confused about your suggestion. Do you mean the photo loss is not preferred by your network? I thought it is a good guide before, this why I uncomment it in the config file. I will try following your suggestions. |
Well, the ternary census term is generally more robust. photo_weigth enables brightness constancy. |
I do as you suggested. I can see a clear loss jumping during the first 100k iterations. I will keep training. Thanks a lot. |
I have trained 130400 iterations with batch_size 8 on flying chairs dataset. The predicted flows on test set are still not good. Should I continue or switched to FlownetCS?
The text was updated successfully, but these errors were encountered: