Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
E2E-AD authored Aug 30, 2023
1 parent 14aa6e7 commit eecc967
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,12 +67,12 @@ To verify the performance on the nuScenes Dataset, we provide the pretrained mod

Two versions of evaluation metrics are provided: online and offline. The offline version uses pre-stored ground truth and is far faster than online one. The code defaults to offline.

* Training
* Training:
The code we use for training the model is located in the directory AD-MLP/pytorch/bevfusion.zip. To use it, you need to refer to https://github.com/mit-han-lab/bevfusion to configure the nuscenes dataset. As the repository does not include the trajectory prediction part, users can refer to the code from ST-P3 for generating nuscenes trajectories during training. Start the training process with run.py under the folder 'bevfusion':
```
python run.py
```
* Collision rate evaluation
* Collision rate evaluation:
We have observed that the evaluation of model collision rates is sensitive to certain samples. One typical example is when the ego vehicle is in a stationary state, the model often predicts trajectories for the next 3 seconds that are very close to the origin (but not exactly 0). If obstacles exist in the range of [0, 0.5m) in the x,y dimensiosn around the origin, the model's predictions of coordinates with very small absolute values can introduce unstable systematic errors due to the resolution of the occupancy map. To mitigate this issue, we recommend processing the model outputs in the deps/stp3/evaluate_for_mlp.py or at the original model inference stage. For instance, you can set the model's predicted trajectory to zero if the distance from the origin is smaller than a little threshold, e.g. 1e-2m. This approach is similar to the filtering of ground truth trajectories that collide in the original evaluation code, as both methods aim to remove systematic errors. We also suggest reviewing cases where collisions occur.

## Contact
Expand Down

0 comments on commit eecc967

Please sign in to comment.