-
Notifications
You must be signed in to change notification settings - Fork 11
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
Coordinate system of .trc #16
Comments
Ah, I see this comment
|
OK, it's working. I made a quick experiment with keeping all the posture visible at once combined with camera motion estimation. 😀 At the moment I'm using these options:
I remove the filtering to get the raw data to match the image better, as I'm going to do the filtering on my side afterwards anyway, and this is more for visual feedback than measurements I think for now. Interpolation seems always better than filling gaps with the last value when there is motion. I was using |
Hi, sorry I was away from my computer for a few days. I'm glad you figured it out! I plan to add a feature for calibrating the camera (i.e. to obtain coordinates in meters rather than in px), it will come when I have a moment.
Noted! I don't have time for it right now but I'll include this feature as soon as I do :) |
I've just realized that you are the author of Kinovea, which is one of the most widely used tools in biomechanics courses around the world. Congrats on making such a tool free and open-source! Could you keep me updated when you manage to integrate the output with Kinovea? I'll direct people to Kinovea in the doc. |
Yes for sure! I don't know much about .trc format but if they have a provision for exporting raw pixel coordinates it could be interesting as an option. Or document the transform in the readme near the angle conventions. This issue can be closed as far as I'm concerned. Thanks! |
Hi, I just released a new version with the option not to display and calculate angles ( For your interest, in the next few days (hopefully), I'm going to add some calibration option for computing coordinates in meters rather than in pixels. And then if people do not choose this option, they will get raw pixel coordinates rather than this weird *1000 multiplication. |
This looks like an awesome project. I tried it on a few videos and it seems pretty robust
I would like to integrate the output in Kinovea. I'll write a parser for the .trc files it produces.
Could you explain the coordinate system used? I see the .trc says "units" is meters but I'm not sure about where to find the scaling factor in order to remap that to the image size of the video.
The text was updated successfully, but these errors were encountered: