-
Notifications
You must be signed in to change notification settings - Fork 32
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
use gt annotations to assign labels for each object track #40
Comments
DetZero/data/waymo/waymo_infos_train.pkl , this file will be loaded in the program. You can see the config file waymo_dataset.yaml and code detzero_track/datasets/waymo_dataset.py 49 line |
however, from the results of the tracking module(see the result file DetZero/data/waymo/tracking/tracking-train-20231122-070256.pkl), it can be seen input is the detection result, not the gt_infos? |
I wonder know which is the right path for <PATH_TO_DETECTION_RESULT>,I choose <DetZero/data/waymo/waymo_infos_train.pkl>,and error broke: |
Hello, may I ask how you obtained the file tracking-train-xxxxxxx-xxxxx.pkl? If using <PATH_TO_DETECTION_RESULT>, which refers to the result.pkl generated in the detection phase, it consistently contains the 'val' key, which isn't present in waymo_infos_train.pkl at all, is it? |
Dear authors, thank you for your great work.
When I wanna to run it on Waymo Open Dataset, i have found the problem:
b. run tracking model in target assign mode (use gt annotations to assign labels for each object track)
cd DetZero/tracking/tools &&
python -u run_track.py --cfg_file cfgs/tk_model_cfgs/waymo_detzero_track.yaml --data_path <PATH_TO_DETECTION_RESULT> --workers <WORKER_NUM> --split
In this step, the input is the detection result <PATH_TO_DETECTION_RESULT> , and why is it not DetZero/data/waymo/waymo_infos_train.pkl ?
The text was updated successfully, but these errors were encountered: