Adrian Kretz
Adrian Kretz
@vsaw Our approach works with normal 2D cameras. The only extra information that is necessary is the camera matrix, which you can obtain by calibrating the camera. Using OpenCV for...
@tdurand > May I ask besides a paper do you have a some piece of code to share implementing the paper that has a compatible license with OpenDataCam (ie: not...
@rantgithub I don't think performance should be a big issue, because we're not tracking corner points separately. As you've said, we're just doing geometry based computations and assume that the...
@tdurand Thanks for the hint! However, it seems like that library supports 1D data only. I might just implement one myself, it's not super difficult. One important thing to keep...
@vsaw @tdurand I have started implementing the 3D tracker in a new npm package [3d-vehicles](/akretz/3d-vehicles). Also, I've extended OpenDataCam with a new 3D view in [my fork](/akretz/opendatacam/tree/3d-vehicles). Here's a screenshot...
> Wow 🔥 , impressive progress !! Thank you very much! > Let us know if you need any help.. I had a very quick look at the fork and...
@vsaw Good point, thanks for the hint! I'll see if I can refactor my code to follow the same pattern.
> Should update docs like in #1195 Right, I just saw @flammit beat me to it by 5 min.
> > Can you work with #1195 to make one great PR? > > > > I've submitted a PR to this branch which merges the changes and keep broadcast...
@flammit I've rebased to the current master, solved the conflicts and added the op to the new WebGPU backend.