You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,8 @@ SECOND detector.
3
3
4
4
ONLY support python 3.6+, pytorch 1.0.0+. Tested in Ubuntu 16.04/18.04/Windows 10.
5
5
6
+
If you want to train nuscenes dataset, see [this](NUSCENES-GUIDE.md).
7
+
6
8
## News
7
9
8
10
2019-4-1: SECOND V1.6.0alpha released: New Data API, [NuScenes](https://www.nuscenes.org) support, [PointPillars](https://github.com/nutonomy/second.pytorch) support, fp16 and multi-gpu support.
@@ -44,6 +46,15 @@ bev AP:90.38, 88.20, 86.98
44
46
3d AP:89.16, 78.78, 77.41
45
47
```
46
48
49
+
### Performance in NuScenes validation set (NuScenes mini train set)
Note: The batch_size and num_workers in config file is per-GPU, if you use multi-gpu, they will be multiplied by number of GPUs. Don't modify them manually.
200
+
201
+
You need to modify total step in config file. For example, 50 epochs = 15500 steps for car.lite.config and single GPU, if you use 4 GPUs, you need to divide ```steps``` and ```steps_per_eval``` by 4.
202
+
186
203
#### train with fp16 (mixed precision)
187
204
188
205
Modify config file, set enable_mixed_precision to true.
0 commit comments