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

A small issue in render_annotation function

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

@pyaf is already working on this.

Since Sep 17, 2019.

  • #34 by @pyaf — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
python

Research direction

Open lyft_dataset_sdk/lyftdataset.py around lines 1083-1086 and inspect the assertion that ensures boxes contains one item, then review how boxes[0] is passed to view_points. The refactor is done when render_annotation preserves its current output without iterating unnecessarily; verify it with the relevant rendering or dataset tests.

Written by the indexing model from the issue text.

Description

bug

Hey,

In render_annotation function you don't need a for loop (here) as there will always be one box in boxes (we are doing assertion checks for the same). And you are passing boxes[0] to view_points within the loop anyways. (here)

And, this time I wanna fix this by raising a PR, do let me know if I can process with that :)

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.