- Make labelling tool for clips
- Make clip visualiser tool
- Label ~10 clips to make a small evaluation set
- 8/4/2021 - Daniel: Please make sure you have a models/ folder if you want to run the detection classifier.
- 7/6/2021 - Dean: Make labelling tool and labelled clip visualiser.
- 6/6/2021 - Dean: Moved datasets to data/ folder for labelling (please do this locally).
- 4/6/2021 - Welcome to the start of a long nightmare. As everyone's detection algorithm is poor, please use the labels for now for the bounding boxes until a better detection algorithm is created.
Manually label clips starting at clip_number
/frame_number
from source_clips_path
. Outputs copies of images to paths_to_outputs
(e.g. see evaluation/clips). With no arguments, default options will be used.
python labeller.py [ --clip | -c ] clip_number
[ --frame | -f ] frame_number
[ --src | -s ] source_clips_path
[ --dst | -d ] path_to_outputs
$ cd data
$ python labeller.py --clip 2 --frame 3
python watch_clip.py [ --clip | -c ] clip_number
[ --src | -s ] source_clips_path
$ cd data
$ python watch_clip.py --clip 1
Please download and extract the zip files in both:
- VELOCITY ESTIMATION CHALLENGE
- LANE DETECTION CHALLENGE
From TuSimple/tusimple-benchmark#3 by Kivinju (on github)
Then extract the zip files, there now should be 5 folders located at the root of this folder:
- train_set
- test_set
- benchmark_velocity_train
- benchmark_velocity_test
- benchmark_velocity_supp
This is to keep things consistent. Also, please ensure no generated files e.g. generated images are stored on the github. Add the folders to .gitignore ^_^
For train_set as train_set is ~10gb. However, do not use this for the final submission.... (You can use this to start early and dl giant dataset overnight)