I'm trying to reproduce the test results on the outdoor day 1 dataset you're listing in your paper. However, the code needs approx. 5 seconds to test just one sample (this adds up to 15 hours for the whole outdoor day 1 dataset) I located the issue to be in the estimate_corresponding_gt_flow function, likely because the whole ground truth is moved to an array each time, which consumes a lot of CPU and is generally slow.
Did you experience a similar issue and could you somehow avoid it?
Hi, Thanks for sharing your code!
I'm trying to reproduce the test results on the outdoor day 1 dataset you're listing in your paper. However, the code needs approx. 5 seconds to test just one sample (this adds up to 15 hours for the whole outdoor day 1 dataset) I located the issue to be in the
estimate_corresponding_gt_flowfunction, likely because the whole ground truth is moved to an array each time, which consumes a lot of CPU and is generally slow. Did you experience a similar issue and could you somehow avoid it?Thanks for your help!