[CVPR 2023 Best Paper Award] Planning-oriented Autonomous Driving
active 2025-03-15 → 2026-07-02 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 475 days from 2025-03-15 to 2026-07-02. Pushes: 3 total, peak 1 in a day. Pull requests: 6 total, peak 3 in a day. Issues: 20 total, peak 2 in a day. Comments: 45 total, peak 3 in a day. Stars: 348 total, peak 6 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| sephyli | 5 | 1 | 3 | 1 |
| dsamvoel | 3 | 0 | 0 | 3 |
| xingzhezuomeng | 3 | 0 | 0 | 2 |
| gjhnb18 | 3 | 0 | 0 | 3 |
| deffery | 3 | 0 | 0 | 2 |
| AmoAonA | 2 | 0 | 0 | 0 |
| zzh-yun | 2 | 0 | 0 | 2 |
| NukaCC | 2 | 0 | 0 | 0 |
| 0w0h0y | 2 | 0 | 0 | 1 |
| xli-li | 2 | 0 | 0 | 2 |
| DK-DARKmatter | 1 | 0 | 0 | 1 |
| zhoujiawei3 | 1 | 0 | 0 | 0 |
| CHJK-reinforce | 1 | 0 | 0 | 1 |
| gmyFighting | 1 | 0 | 0 | 0 |
| Tonny24Wang | 1 | 0 | 0 | 1 |
| zhaoxincai | 1 | 0 | 0 | 1 |
| FergusChan-cx | 1 | 0 | 0 | 1 |
| StoneShuyao | 1 | 0 | 0 | 0 |
| ssuralcmu | 1 | 0 | 0 | 0 |
| rookie0109 | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#251arcer6662026-04-16 02:13🚀 Release Notes for UniAD v2.X
- Issue comment#264zhaoxincai2026-03-01 04:01eval bev error
- Issue comment#150deepak-vij2026-01-07 23:03Why samples_per_gpu is set to 1?
- Issue#260xiangze2025-12-09 00:14An error inside mmcv/runner/dist_utils.py
- Issue#259gmyFighting2025-12-03 09:192.0 nuplan
- Issue comment#258kmsngh2025-11-25 05:50Dependency Conflict: PyTorch 2.0 requires mmcv-full>=1.7.2, but mmdet3d requires mmcv-full<1.7.2
- Issue comment#254llbbyy1232025-11-13 15:11安装networkx==2.5的时候报错
- Issue comment#2560w0h0y2025-11-13 12:11v2.0 checkpoint does not match the model
- Issue#2560w0h0y2025-11-13 12:11v2.0 checkpoint does not match the model
- Issue comment#255xli-li2025-11-12 03:31An error occurred while evaluating the example
- Issue comment#255xli-li2025-11-12 03:30An error occurred while evaluating the example
- Issue comment#252sephyli2025-10-29 04:34Failed when downloading mmcv-full using cuda11.8 and torch2.3.0
- Pull request#251sephyli2025-10-29 03:03
- Pull request#251sephyli2025-10-29 03:03
- Pull request#251sephyli2025-10-29 03:03
- Issue comment#245CHJK-reinforce2025-10-29 02:04Failed to compile mmcv v1.6.0 under CUDA 11.8 & Pytorch 2.x
- Issue comment#234zzh-yun2025-10-15 08:01Why predict past trajectory in the tracker former
- Issue comment#230zzh-yun2025-09-29 07:37TypeError: cannot pickle 'dict_keys' object and training can only use one gpu.
- Issue comment#249wzh5062025-09-25 10:34RuntimeError:DataLoader worker (pid 33959) is killed by signal: Killed.indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue#249deffery2025-09-23 06:56RuntimeError:DataLoader worker (pid 33959) is killed by signal: Killed.indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue#248ZaiyiHu2025-09-22 08:41Is there any ways to speed up the inference stage?
- Issue comment#62deffery2025-09-22 07:37Dataloader worker killed with runtime error.
- Issue comment#54Jason077092025-09-22 01:54RuntimeError: cusolver error: CUSOLVER_STATUS_INTERNAL_ERROR, when calling `cusolverDnCreate(handle)`
- Issue comment#230deffery2025-09-11 01:21TypeError: cannot pickle 'dict_keys' object and training can only use one gpu.
- Issue#247WuYiYiYi2025-09-09 06:53UniAD Implementation on the Navsim
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 348 stars here means stars gained during the window, not the repo's star count.