Tracking id exchange issues

[JianJingGao]

yolov5 detection header input tracking found that the newly emerged target will use the previously disappeared target id, and it will also exchange ids with other targets. The newly emerged target may have an id of 20, and the new target will also become 20. The original target id will be reset, and the effect looks bad, which is not as good as my original sort code

[yangzhishuai2022]

yolov5 detection header input tracking found that the newly emerged target will use the previously disappeared target id, and it will also exchange ids with other targets. The newly emerged target may have an id of 20, and the new target will also become 20. The original target id will be reset, and the effect looks bad, which is not as good as my original sort code

Hi! I also encountered a similar problem. Have you solved it?

[JianJingGao]

yolov5 detection header input tracking found that the newly emerged target will use the previously disappeared target id, and it will also exchange ids with other targets. The newly emerged target may have an id of 20, and the new target will also become 20. The original target id will be reset, and the effect looks bad, which is not as good as my original sort code

Hi! I also encountered a similar problem. Have you solved it?

No. I'm going to switch to a different algorithm

[MorningHero92]

@JianJingGao @yangzhishuai2022
guys i have same problem. Have you solved it? Or maybe you have found something more suitable?
@noahcao for me, it looks like your tracker doesnt kill tracks and tries to find anything close enough and assign same id to this object. Say, a car with id 1 left the frame, and another car appears in different part of screen - same track_id is assigned.
i tried to figure out solution without success. Maybe we can at least add some distance threshold for this... Im ready to collaborate and i really need your help man