ECO icon indicating copy to clipboard operation
ECO copied to clipboard

About the ECO_HC tracker speed problem.

Open fybaft2012 opened this issue 7 years ago • 7 comments

Hi MD, Thanks for you great work! One thing I need your help, I tested your code on my PC, which is of 24 GB memory, Intel i7-6700 CPU with 3.40GHz x 8, and NVIDIA TITAN X. When I run ECO_HC file, the speed is only about 20 fps - 30fps, but in the paper said it can run at 60 fps, There are big difference between the two, I want to know why it happened and how should I do to run it at 60 fps. Sorry for disturbing you and hope you can help me with it. Thanks!

fybaft2012 avatar Jan 24 '18 09:01 fybaft2012

Hi,

Did you run with params.use_gpu set to false? The ECO_hc code is not optimized for gpu and hence can be slower on gpu due to additional memory transfers.

Secondly, set params.visualization and params.debug to false.

goutamgmb avatar Jan 24 '18 09:01 goutamgmb

Hi, Thank you for answering. Yes bro, I set params.use_gpu = false, params.visualization and params.debug to false already, and the speed is still 23.77 fps then. With OBT sequence 'Bolt'.

fybaft2012 avatar Jan 24 '18 09:01 fybaft2012

That is strange. We got over 65 fps on the Bolt sequence.

Did you get this warning message? 'Error when using the mexResize function. Using Matlab''s interpolation function instead, which is slower'

goutamgmb avatar Jan 24 '18 10:01 goutamgmb

Yes, you are right, I got that warning message, I think because I think the compiled mexResize which you provided does not work on my computer, is it because of that? If so, would you please give me the advice how I can compile my own mexResize file on my pc? By the way, I use Ununtu 16.04 and opecv 2.4 v5, and gcc 4.9.4. Thanks!

fybaft2012 avatar Jan 24 '18 12:01 fybaft2012

Yes, not using mexResize can have significant impact on speed. Have you tried compiling mexResize using external_libs/mexResize/compile.m?

goutamgmb avatar Jan 24 '18 21:01 goutamgmb

Yes, bro. I have tried to compile the mexResize function and it said that it is compiled successfully, but when I use the re-compiled one, it still has that warning message information. I am not sure it is because of the opencv path settings or other reasons? Thank you very much for your patient answer!

fybaft2012 avatar Jan 25 '18 02:01 fybaft2012

Hi goutamgmb, About the mexResize compiling problem, I am still confused. When I use the re-complied mexResize file compiled using openCV 2.4.9 on my Ubuntu, it show it is a Invalid MEX-file mexResize.mexa64. is that because of openCV version issue ? If so, which opencv version I need to use exactly on my ubuntu? Looking forward your help!

fybaft2012 avatar Jan 30 '18 07:01 fybaft2012