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

Performance of FlowNet2-CSS-ft-sd #13

Closed
yxqlwl opened this issue May 15, 2017 · 7 comments
Closed

Performance of FlowNet2-CSS-ft-sd #13

yxqlwl opened this issue May 15, 2017 · 7 comments

Comments

@yxqlwl
Copy link

yxqlwl commented May 15, 2017

After testing FlowNet2-CSS-ft-sd on sintel training dataset, I found that:

  1. On sintel clean, FlowNet2-CSS-ft-sd can produce exact the same AEE (2.08) as reported in <FlowNet 2.0: Evolution of Optical Flow Estimation with Deep Networks>;

  2. However, AEE on sintel final is 3.57, which is higher than the result reported in the paper.

So could you please check the performance of FlowNet2-CSS-ft-sd on sintel final? Thanks~

@brjeon
Copy link

brjeon commented May 15, 2017

Hi yxqlwl,
Have you performed training also with the provided prototxt?

@yxqlwl
Copy link
Author

yxqlwl commented May 15, 2017

Hi,
No I didn't. I only used the provided deploy.prototxt and caffemodel.

@yxqlwl
Copy link
Author

yxqlwl commented May 16, 2017

Has anyone also tested performance of the models on sintel final? Haven't found the bugs in my testing code yet.

@nikolausmayer
Copy link
Contributor

Hi,
We will look into this.

Best,
Nikolaus

@eddy-ilg
Copy link
Collaborator

Thanks for the comment, will check it this week.

@eddy-ilg
Copy link
Collaborator

eddy-ilg commented Jun 6, 2017

We confirm this issue. We originally made a dataset for sceneflow, where we took the sintel flow and disparity datasets together. The CLEAN images of both datasets are exactly the same, however the disparity FINAL images turn out to come without the atmospheric effects. I.e. we tested on Sintel with motion blur but missing the effects like fog.

We apologize for the inconvinience and will fix the numbers in the paper.

@yxqlwl
Copy link
Author

yxqlwl commented Jun 10, 2017

Hi,
That's OK. We hope the performance of FlowNet2 could be further improved.
Best,
ViJay

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

4 participants