Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Front lidar only available for 1/5th of scenes

Open
#4 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Run the provided Python snippet against the Lyft Level 5 dataset and inspect the scene metadata returned by the devkit. Compare the 148 missing front-lidar scenes with the dataset specifications at level5.lyft.com; done means documenting or correcting the explanation of front-lidar availability.

Written by the indexing model from the issue text.

Description

Front lidar data is missing for 4/5th of the scenes. There are 148 scenes out of the 180 without front lidars.

The specs at https://level5.lyft.com/dataset/ say that there are 3 lidars: 'One 40-beam roof LiDAR and two 40-beam bumper LiDARs.'

There is no mention of scenes with only partial lidar data.

You can check these scenes with the following code snippet:

for scene in level5data.scene:
    sample_token = scene['first_sample_token']
    sample = level5data.get('sample', sample_token)
    if 'LIDAR_FRONT_LEFT' not in sample['data'].keys():
       print(scene['name'])
Dominant language
Jupyter Notebook
Stars
390
Forks
99
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lyft/nuscenes-devkit

All issues in lyft/nuscenes-devkit

Similar issues

More Autonomous Driving issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.