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

Fix issue #754 #1035

Conversation

rolson24
Copy link
Contributor

Description

New version of this PR (#1034) with one commit and requested changes.

This change addresses this issue: (#754)
update_with_detections now returns the original detections that were tracked by ByteTrack with their original bboxes, masks, class_ids, data fields and with updated track_ids. Detections that were not tracked this frame are not included in the returned detections.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality) - Segmentation tracking

How has this change been tested, please provide a testcase or example of how you tested the change?

I have tested this change by running object tracking for both object detection and segmentation in this colab notebook

segmentation_tracking

Any specific deployment considerations

Tracking docs should be updated to reflect that ByteTrack can now do segmentation tracking.

Docs

  • Docs updated? What were the changes:

@rolson24
Copy link
Contributor Author

See this comment (#1034 (comment)) about a question on possible change to the implementation.

@SkalskiP
Copy link
Collaborator

Hi @rolson24 👋🏻 ! Thanks a lot for your contribution. This is exactly what we needed. I'm super happy with this update.

@SkalskiP
Copy link
Collaborator

Btw @rolson24, if you are feeling strong and have time, maybe try to work on this issue.

@rolson24 rolson24 mentioned this pull request Mar 26, 2024
1 task
@rolson24
Copy link
Contributor Author

Hi @SkalskiP

I made a silly mistake in this PR with using enumerate to get the index of each track, because I forgot to test the new version. I have submitted another PR that fixes the issue. So sorry about this, I will try to remember to re-test every time before I submit a PR.

rolson24 added a commit to rolson24/supervision that referenced this pull request Mar 26, 2024
fix bug from PR roboflow#1035

change update_with_tensors to not return tracks with track_id < 0

reset the track_id counter when initializing a new ByteTrack object
rolson24 added a commit to rolson24/supervision that referenced this pull request Mar 26, 2024
fix bug from PR roboflow#1035

change update_with_tensors to not return tracks with track_id < 0

reset the track_id counter when initializing a new ByteTrack object

update docstring
rolson24 added a commit to rolson24/supervision that referenced this pull request Mar 26, 2024
fix bug from PR roboflow#1035

change update_with_tensors to not return tracks with track_id < 0

reset the track_id counter when initializing a new ByteTrack object

update docstring
rolson24 added a commit to rolson24/supervision that referenced this pull request Mar 26, 2024
fix tuple unpacking bug in PR roboflow#1035

Fix bug with detections with un-initialized tracker_ids
rolson24 added a commit to rolson24/supervision that referenced this pull request Mar 26, 2024
fix bug from PR roboflow#1035

change update_with_tensors to not return tracks with track_id < 0

reset the track_id counter when initializing a new ByteTrack object

update docstring

Fix other bug from PR roboflow#1035
onuralpszr pushed a commit that referenced this pull request Mar 28, 2024
fix tuple unpacking bug in PR #1035

Fix bug with detections with un-initialized tracker_ids
@rolson24 rolson24 mentioned this pull request Apr 27, 2024
1 task
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.

2 participants