Skip to content
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

Detection age not updated after merging tracked objects #318

Open
nmichlo opened this issue May 3, 2024 · 0 comments
Open

Detection age not updated after merging tracked objects #318

nmichlo opened this issue May 3, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@nmichlo
Copy link

nmichlo commented May 3, 2024

Describe the bug

With re-id enabled, detection age is not updated when objects are merged. It makes sense that detection ages should always be sequential in nature, but after merging tracked objects, the detection age can be arbitrary / is left over from the previous tracked object.

NOTE: the order of detections in the past detections list is also not correctly maintained / merged. It seems like past detections should be kept in-order.

To Reproduce
N/A

Expected behavior

The detection ages should be updated to be relative to the start age of the tracked object that the detections are merged into. I.e. the detection ages should follow on sequentially.

Screenshots or videos
N/A

Environment (please complete the following information):

  • OS: [e.g. Ubuntu 20.04]
  • Python version: [e.g. 3.9.10]
  • Norfair version: [e.g. 1.0.0]

Additional context
N/A

@nmichlo nmichlo added the bug Something isn't working label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant