Data preparation¶
Image datasets¶
For image datasets, we strongly relied on Torchvision and adopted the same structure, therefore you can follow their guidelines.
The dataset used are:
For ImageNet100 and Tiny-ImageNet, we follow the dataset folder structure.
In Eztorch, ImageNet100 is directly handled from the ImageNet folder.
Video datasets¶
Generally, we follow from Pytorchvideo with some adjustments and helpers.
Kinetics400¶
Download and extract the dataset.
Resize the shorter edge size of the videos to 256. Prepare a CSV file that contains the path and the labels.
cd eztorch input_folder="./kinetics_downscaled/train/" output_folder="./kinetics_downscaled/" output_filename="train.json" python run/datasets/create_video_files.py \ --input-folder $input_folder \ --output-folder $output_folder \ --output-filename $output_filename
[Optional] Extract the frames to speed data loading.
cd eztorch input_folder="./kinetics400_downscaled/train/" output_folder="./kinetics400_downscaled_extracted/train/" python run/datasets/process_video.py \ --input-folder $input_folder \ --output-folder $output_folder \ --frames \ --video-quality 1 \ --fps 30
[Optional] Prepare a CSV file that contains the path, the labels and video duration.
cd eztorch input_folder="./kinetics400_downscaled_extracted/train/" output_folder="./kinetics400_downscaled_extracted/" output_filename="train.json" python run/datasets/create_frames_video_files.py \ --input-folder $input_folder \ --output-folder $output_folder \ --output-filename $output_filename
In our code, we do not use the frames extracted as they take more than 1To in storage. However, it could significantly reduce the decoding time, so it might suit you better. To reduce the storage cost, you can increase the parameter --video-quality that is used by ffmpeg for JPEG compression.
Keep in mind that our configuration files do not use the frame decoder but PYAV. Frame decoder is supported and you can take inspiration from Kinetics200 configs. It is also possible to consider other kind of decoders that we do not support such as DECORD and improve over what Eztorch propose.
Kinetics200¶
Do steps 1 and 2 of the preprocessing of Kinetcs400 and create a folder containing symbolic links for videos in Kinetics200. Then perform step 3 of the preprocessing of Kinetics400.
[Optional] Extract the frames to speed data loading.
cd eztorch input_folder="./kinetics200_downscaled/train/" output_folder="./kinetics200_downscaled_extracted/train/" python run/datasets/process_video.py \ --input-folder $input_folder \ --output-folder $output_folder \ --frames \ --video-quality 1 \ --fps 30
[Optional] Prepare a CSV file that contains the path, the labels and video duration. Although steps 2 and 3 are optional, we performed those and our configured scripts for Kinetics200 use a frame decoder. It is possible to update them to use a video decoder in case you do not want to extract the frames.
HMDB51¶
Download and extract the dataset.
[Optional] Extract the frames to speed data loading.
cd eztorch input_folder="./hmdb51/" output_folder="./hmdb51_extracted/" python run/datasets/process_video.py \ --input-folder $input_folder \ --output-folder $output_folder \ --frames \ --video-quality 1 \ --fps 30
[Optional] Prepare a CSV file that contains the path, the labels and video duration.
cd eztorch input_folder="./hmdb51/" output_folder="./hmdb51_extracted/" python run/datasets/create_frames_video_files.py \ --input-folder $input_folder \ --output-folder $output_folder \ --dataset hmdb51
Although steps 2 and 3 are optional, we performed those and our configured scripts for HMDB51 use a frame decoder. It is possible to update them to use a video decoder in case you do not want to extract the frames.
UCF101¶
Download and extract the dataset.
[Optional] Extract the frames to speed data loading.
cd eztorch input_folder="./ucf101/" output_folder="./ucf101_extracted/" python run/datasets/process_video.py \ --input-folder $input_folder \ --output-folder $output_folder \ --frames \ --video-quality 1 \ --fps 25
[Optional] Prepare a CSV file that contains the path, the labels and videos duration.
cd eztorch input_folder="./ucf101/" output_folder="./ucf101_extracted/" python run/datasets/create_frames_video_files.py \ --input-folder $input_folder \ --output-folder $output_folder \ --dataset ucf101
Although steps 2 and 3 are optional, we performed those and our configured scripts for HMDB51 use a frame decoder. It is possible to update them to use a video decoder in case you do not want to extract the frames.
SoccerNet¶
We followed the guide from the challenge 2023 of SoccerNet with some adjustments.
In our code, we use "val" split instead of "valid" split from SoccerNet to keep consistency with other datasets.
Action Spotting¶
Download the dataset and optionally the Baidu features. We downloaded the 224p low resolution.
Extract frames.
cd eztorch fps=2 input_folder="./SoccerNet_AS/" output_folder="./soccernet_as_extracted_${fps}fps/" split=train python run/datasets/extract_soccernet.py \ --input-folder $input_folder \ --output-folder $output_folder \ --fps $fps \ --split $split
The extraction also creates an annotation file for the split.
Precompute labels
radius_label=0.5 dataset_json=... # Path to the JSON. frame_dir=... # Path to the decoded videos. fps=2 cache_dir=... python run/datasets/precompute_soccernet_labels.py \ --radius-label $radius_label \ --data-path $dataset_json \ --path-prefix $frame_dir \ --fps $fps \ --cache-dir $cache_dir
[Optional] Merge annotation files.
split_files=... ... ... output_folder=... output_filename=... python run/datasets/merge_soccernet_annotation_files.py \ --split-files $split_files \ --output-folder $output_folder \ --output_filename $output_filename
[Optional] Merge labels’ folders.
labels_folders=... ... ... output_folder=... python run/datasets/merge_soccernet_annotation_files.py \ --split-folders $labels_folders \ --output-folder $output_folder \
Ball Action Spotting¶
Extract frames.
cd eztorch fps=25 input_folder="./SoccerNet_ball/" output_folder="./soccernet_ball_extracted_${fps}fps/" split=train python run/datasets/extract_soccernet.py \ --input-folder $input_folder \ --output-folder $output_folder \ --fps $fps \ --split $split
Issue¶
If you have trouble making this work or have any questions, open an issue to describe your problem.