Update node-movings-things-tracker version in ODC once "Different box representation in tracker" is fixed
See original GitHub issueHello everyone,
OpenDataCam uses the x
, y
properties of detection boxes to refer to the center point, while the computations used in node-moving-things-tracker use the top left corner as reference point instead. This results in a wrong IoU being calculated. This issue becomes apparent when you set the iouLimit
to some high value and then the tracker fails a lot more often than when you compute the correct IoU. The solution would be to either convert between both representations when passing data between ODC and the tracker or to use the same representation everywhere. In the latter case, the following lines would need to be modified to use the center point as reference:
https://github.com/opendatacam/node-moving-things-tracker/blob/474f50a4b9c9fdaba5e2bc89085498c0b6848445/utils.js#L10-L13 https://github.com/opendatacam/node-moving-things-tracker/blob/474f50a4b9c9fdaba5e2bc89085498c0b6848445/utils.js#L38-L41 https://github.com/opendatacam/node-moving-things-tracker/blob/474f50a4b9c9fdaba5e2bc89085498c0b6848445/main.js#L139-L140
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top GitHub Comments
I’ve created a new issue in https://github.com/opendatacam/node-moving-things-tracker/issues/24 to track the implementation.
This issue will be renamed to remind us to update the node-moving-things depedancy in Opendatacam.
❤