ifzhang/ByteTrack

Use Bytetrack with custom detector

MarigoldDrift opened this issue · 1 comments

Hello! I would like to use Bytetrack with my own custom detector.
I followed the example you gave in your README document, but I wasn't really sure how to interpret the results.

I ran this block of code

from yolox.tracker.byte_tracker import BYTETracker tracker = BYTETracker(args) for image in images: dets = detector(image) online_targets = tracker.update(dets, info_imgs, img_size)

and online_targets returned something like this

[OT_1_(1-567), OT_8_(291-567), OT_10_(337-567)] [OT_1_(1-568), OT_8_(291-568), OT_10_(337-568)] [OT_1_(1-569), OT_8_(291-569), OT_10_(337-569), OT_14_(492-569)] [OT_1_(1-570), OT_8_(291-570), OT_10_(337-570), OT_14_(492-570), OT_18_(557-570)] [OT_1_(1-571), OT_8_(291-571), OT_10_(337-571), OT_14_(492-571)] [OT_1_(1-572), OT_8_(291-572), OT_10_(337-572)] [OT_1_(1-573), OT_8_(291-573), OT_10_(337-573), OT_18_(557-573), OT_14_(492-573)]

I took a closer look and printed out the tlwh attribute of each object, and discovered that every [OT_1_] object has the same tlwh.
From my understanding, shouldn't it be updated every frame to show the new position of the bounding box?

[729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517] [729.42936364 156.09386429 96.1745278 405.98831517]

Thanks!

just a question, how did u get args?