Range-sensor data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- autonomous-driving
- Domain
- autonomous-driving
Research direction
Start by reviewing the Lyft Level 5 dataset documentation and the BETA_V0 and BETA_PLUS_PLUS sensor descriptions referenced in the issue. Determine whether the requested x/y/z ranges and Velodyne elevation are available for each LiDAR, and document the values or where they can be obtained.
Written by the indexing model from the issue text.
Description
Good afternoon. How are you? I'm sorry for the inconvenience. I am studying perception systems for autonomous vehicles. At this point I'm using the Lyft Level 5 dataset. My goal is to design 3D point clouds to the 2D image plan and so, I intend to achieve depth maps. However, I can't get the data from the sensors used in the BETA_V0 LiDARS (40-beam), BETA_V0 Cameras (1224x1024/2048x864), BETA_PLUS_PLUS LiDARS (64-beam) and BETA_PLUS_PLUS Cameras (1920x1080) cars. To continue my studies I need to obtain the following information for each Lidar of each car (each dataset), the range of each direction of movement:
x_min, x_max, y_min, y_max, z_min, z_max, velodyne elevation.
Could you help me with this information? Or forward my e-mail to someone at Lyft Level 5 who has this information, please? Because I can't get it on the Lyft Level 5 sites. This information is very important for my studies.
I thank you for your attention,
Gledson Melotti.
- Dominant language
- Jupyter Notebook
- Stars
- 390
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lyft/nuscenes-devkit
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
lyft/nuscenes-devkit#106 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
lyft/nuscenes-devkit#105 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
lyft/nuscenes-devkit#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
lyft/nuscenes-devkit#103 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
lyft/nuscenes-devkit#99 ·
All issues in lyft/nuscenes-devkit
Similar issues
-
RingOutlierFilterComponent never sets row_step on its output PointCloud2 (always 0)Possibly taken @JArmandoAnaya claimed this 14 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Thinklab-SJTU/Bench2Drive#235 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
QwenLM/Qwen-Drive-1.0#7 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
autowarefoundation/vision_pilot#412 · 3 comments ·
Maintainers usually reply within 4 days
-
`get_random_location_from_navigation()` returns `None` forever on a navmesh with no sidewalk areasOpen
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
carla-simulator/carla#9871 ·
Maintainers usually reply within 1 day