-
Notifications
You must be signed in to change notification settings - Fork 457
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
Unable to use pub_test.py with v1.0-test! #22
Comments
This is not an error. The test set annotation is not available (need to submit to test server). There is no immediate function to see the visualization result for tracking. To see the detection output, you can comment out the if statement here
and the devkit will plot some images. Though, the visualization in the devkit is not that good (doesn't really give a sense of your detection quality without gt annotations) so you probably want to use other tools to visualize the detection/tracking in camera view / 3d. |
This function is useful to look at to visualize the object in camera view. https://github.com/nutonomy/nuscenes-devkit/blob/274725ae1b3a2d921725016e3f4b383b8b218d3a/python-sdk/nuscenes/nuscenes.py#L903 |
Thanks! |
@tianweiy The predicted bounding boxes co-ordinates are with respect to the lidar frame. Before transforming them to a particular camera, we need to first determine which camera's translation and rotation matrix we should use. The render_annotation() function from the nuScenes devkit takes as input the annotation token token with which the image path is known and the bounding boxes are plotted. But in our case I was wondering how can we determine to which camera we transform the co-ordinates of the predicted bounding box and plot the bounding boxes after that? |
@YoushaaMurhij @iamsiddhantsahu @tianweiy i trying to run a inference code but unable to find a command to run the inference on nuscenes but I found the above mentioned command in which had mentioned about tools/dist_test.py but in configs i am not able to find " nusc_centerpoint_voxelnet_dcn_0075voxel_flip_testset.py" can you please share some insights on this |
Thanks for the interest. We have some basic updates to the codebase recently. You can replace the original config with
The other commands are the same to generate nuScenes results. For Waymo models, we are not able to share it publicly due to license agreement, you can send me an email to access those models. Please provide the necessay informations mentioned here |
I used tools/dist_test.py to get the predictions.pkl for the validation-set to use them for tracking |
yeah, to fix the bug, change the config to the following
you need to use the json files and zip it and then submit to the server |
Thank you for your fast and clear answer! |
have you first tested the model on val? (dist_test.py without the --testset flag) |
if val is ok, please send me an email with your generated json file so that I can take a look |
The val is OK. I will send you an e-mail! |
I tried :
@tianweiy Do I need to modify the config for the testset tracking ? |
I think the file is already generated in the folder. You need to submit to server for evaluation. |
Otherwise please attach full log. Especially where does this error come from which line of code |
I can see .pkl and .json in the folder. I zipped .json and submitted to detection task. Thank you for your response and good luck with your coming work :) |
Yeah zip the json and submit to the tracking server |
Sorry, but submitting the .json to the tracking server is giving a Failed status. The same .json gave normal results on the detection server. What I am doing wrong? |
is the json file called "tracking_result.json" ? |
wait that means tracking is not running. Please attach all outputs after you run pub_test.py |
I think I found it. the files are there regarding the previous error. Thanks! |
I am facing this error because I am trying to evaluate on the testing set. How to view the predictions after running dist_test.py?
First, I ran :
python tools/dist_test.py configs/centerpoint/nusc_centerpoint_voxelnet_dcn_0075voxel_flip_testset.py --work_dir work_dirs/nusc_centerpoint_voxelnet_dcn_0075voxel_flip_testset --checkpoint work_dirs/nusc_centerpoint_voxelnet_dcn_0075voxel_flip_testset/epoch_20.pth --speed_test --testset
after that :
bash tracking_scripts/centerpoint_voxel_1440_dcn_flip_testset.sh
The text was updated successfully, but these errors were encountered: