Skip to content

Conversation

@robbinsa530
Copy link

Fix issue 325

assert tracked_objects[0].reid_hit_counter is None

# check that after reid_hit_counter_max more updates, object still exists
for _ in range(reid_hit_counter_max + 2):
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+2 because with the bug,

  • After reid_hit_counter_max updates, reid_hit_counter will be 0
  • After reid_hit_counter_max + 1 updates, reid_hit_counter will be -1 but because of the bug, hit_counter will be positive at the end of the update call, so the tracked object will still be returned and alive
  • At the start of the reid_hit_counter_max + 2 update, reid_hit_counter will be -1 and the tracked object will be marked as dead and won't be sent for normal matching

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

reid_hit_counter not reset when track is matched right before becoming dead

1 participant