Skip to content
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

Why sweep_lidar_info use calibrated_sensor_token of cam_data in gen_info ? #143

Open
chao-SFD opened this issue Jan 5, 2023 · 1 comment

Comments

@chao-SFD
Copy link

chao-SFD commented Jan 5, 2023

Dear authors,
In the gen_info, the calibrated_sensor of sweep_lidar_info use the calibrated_sensor_token of 'CAM_FRONT_LEFT' at the farthest moment.
The code at line 116 is:
sweep_lidar_info['calibrated_sensor'] = nusc.get( 'calibrated_sensor', cam_data['calibrated_sensor_token'])
Is the cam_data should be changed to sweep_lidar_data and use the calibrated_sensor_token of sweep_lidar_data?

I'm looking for your replay.Thanks.

@chao-SFD
Copy link
Author

chao-SFD commented Jan 5, 2023

As the same, the ego_pose of sweep_cam_info use the ego_pose_token of cam_data(key frame), but not the sweep_cam_data.
the code at line 80 is:
sweep_cam_info['ego_pose'] = nusc.get( 'ego_pose', cam_data['ego_pose_token'])
Is the cam_data should be changed to sweep_cam_data? I found the version of bevStereo at https://github.com/Megvii-BaseDetection/BEVStereo/blob/master/scripts/gen_info.py seems to be right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant