-
Notifications
You must be signed in to change notification settings - Fork 247
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
About the ECO_HC tracker speed problem. #24
Comments
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. |
Hi, |
That is strange. We got over 65 fps on the Bolt sequence. Did you get this warning message? |
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. |
Yes, not using mexResize can have significant impact on speed. Have you tried compiling mexResize using external_libs/mexResize/compile.m? |
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? |
Hi goutamgmb, |
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!
The text was updated successfully, but these errors were encountered: