-
Notifications
You must be signed in to change notification settings - Fork 82
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 for in the wild #21
Comments
Hi @slava-smirnov , Very good question. In my experience, roughly there are three points:
|
hey! thnx for quick response. for 1 and 2 it’s quite clear. I was hoping for some inference time per frame on 3D component part (everything else other than 2D predictions) |
It's a good idea, but currently the key idea of this paper is using kinematic knowedge in the architecture level so I haven't done more in the per frame inference. There is a paper called SPIN which can do an optimization per frame after the first step prediciton, you can follow it to get more inspirations. But I will keep working on this task so I believe it will be more stronger :) |
Got you. I'll share numbers if/whenever I have them. Anyway bringing learned kinematics is a significant contribution! Great job |
hey!
great work! any rough performance benchmarks for in the wild possibly to share? I realise it depends on resolution and duration but if you could share some rough breakdowns that would help a lot
The text was updated successfully, but these errors were encountered: