Closed songtianhui closed 1 year ago
I find that not only tens of videos has inconsistent number of frames. Large amount of test set videos raise error. video_811, video_10172, video_11151, video_7808, video_10182, video_11071, video_5387, video_6036...... This makes me worried, I don't know whether it is the data problem or my software problem.
Hi,
Sorry this is an issue on the data side. Some of the test videos are cut at certain points, there was a problem with the annotations where we had incorrect values for the 'num_frames' in the metadata and didn't cut some of the later tracks.
I've uploaded a new version of the annotations: https://storage.googleapis.com/dm-perception-test/zip_data/sot_test_annotations_challenge2023.zip
This should be correct for all videos and tracks. Thank you for raising this!
Everything is well! Thanks very much for correction!
Sorry, I still meet some mismatch of videos. It is not much, I collect some of them: video_2458, video_476, video_11146, video_4763, video_5060, video_8811, video_2926, video_5277, video_6365, video_6483, video_2919. Most of them only differs one or two frames. It is possible that the cv2 library cause some error. I can make compensation such as padding the video with the last frame. But I should confirm the standard the number of frames in my report result, align with the metadata or video reads?
I think this might be an issue with OpenCV, I've looked into it further and reuploaded the file in the same location (https://storage.googleapis.com/dm-perception-test/zip_data/sot_test_annotations_challenge2023.zip) please let me know if the videos line up with the metadata if you can!
Otherwise for slight differences use the metadata value and not the video reads. Thanks.
Ok. Thank you.
Hi, I met some problems in the data of single object tracking task.
video_2935
, the metadatanum_frames: 467
, butAnd this mismatch occurs not very few, in the test phrase about tens of videos raise this error, such as
video_10363
,video_2790
. Some of them only differs 1 or 2 frames, but some differs hundreds of frames. How can I compensate it?frame_ids
is weird. Still invideo_2935
, I show the whole annotation info:The number of frames is 467, however in track of id 12, the
frame_ids
is660
, which is impossible.I am very confused about these issues and I think it will affect the running pipeline and results. Can you please check them?