-
Notifications
You must be signed in to change notification settings - Fork 122
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
About MOT dataset PREV #129
Comments
I also found this piece of code confusing. There's another edge case that might result in the same I'm curious if it's an issue to have a future or identical frame as the previous frame. I would also be interested in the rationale behind this code. Cheers! |
hi @Maxvgrad I want to use TrackFormer for multi-object tracking with my own dataset. According to the instructions, I need to create a COCO-style annotation file and extend it with fields like seq_length, first_frame_image_id, and track_id for multi-object tracking. I'm unsure how to prepare my dataset with these extensions and how to use the generate_coco_from_mot.py script. Could you guide me on how to structure my dataset and generate the necessary COCO-style annotations for TrackFormer? |
@Tsai-chia-hsiang btw it seems like this logic is mentioned in the paper
|
Oh, ok, I see. |
At
trackformer/src/trackformer/datasets/mot.py
Lines 56 to 59 in e468bf1
Here, I would like to ask why the
prev_frame_id needs
may take the subsequent frame ID.For example:
and the
It will become
random.randint(85, 95)
and can generateprev_frame_id = 91
and it is actually the next frame.In the next few lines
trackformer/src/trackformer/datasets/mot.py
Lines 61 to 64 in e468bf1
It seems that it didn't deal with the relationship between preceding and subsequent frames, and keys in ``target` ' also don't provide the frame number information.
Why the
prev_image
andprev_target
may be the information about the later frame while it is named PREVIOUS?Thanks.
The text was updated successfully, but these errors were encountered: