You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would hereby like to request a feature that is currently not available. Right now I'm dealing with the issue that when a tracked object is created the class id created with the provided class_id of the detection, but never updated. This causes the following issue: when my yolo model detects for example a car as a person in the first frame and in the second frame decides that it is a actually a car, the class_id of the tracker will be stuck on person. It would be nice if the class_id would be updated accordingly to the class_id provided by the detection.
The text was updated successfully, but these errors were encountered:
I would hereby like to request a feature that is currently not available. Right now I'm dealing with the issue that when a tracked object is created the class id created with the provided class_id of the detection, but never updated. This causes the following issue: when my yolo model detects for example a car as a person in the first frame and in the second frame decides that it is a actually a car, the class_id of the tracker will be stuck on person. It would be nice if the class_id would be updated accordingly to the class_id provided by the detection.
I would hereby like to request a feature that is currently not available. Right now I'm dealing with the issue that when a tracked object is created the class id created with the provided class_id of the detection, but never updated. This causes the following issue: when my yolo model detects for example a car as a person in the first frame and in the second frame decides that it is a actually a car, the class_id of the tracker will be stuck on person. It would be nice if the class_id would be updated accordingly to the class_id provided by the detection.
The text was updated successfully, but these errors were encountered: