Skip to content

Commit e55a198

Browse files
committed
Update docs
1 parent f3944fd commit e55a198

2 files changed

Lines changed: 17 additions & 7 deletions

File tree

README.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@ If you use the challenge dataset in your paper, please consider citing OccNet wi
4545
- [Introduction](#introduction)
4646
- [News](#news)
4747
- [Task Definition](#task-definition)
48+
- [Rules for Occupancy and Flow Challenge](#rules-for-occupancy-and-flow-challenge)
4849
- [Evaluation Metrics](#evaluation-metrics)
4950
- [Ray-based mIoU](#evaluation-metrics)
5051
- [AVE for Occupancy Flow](#evaluation-metrics)
@@ -62,6 +63,17 @@ If you use the challenge dataset in your paper, please consider citing OccNet wi
6263

6364
Given images from multiple cameras, the goal is to predict the semantics and flow of each voxel grid in the scene.
6465

66+
### Rules for Occupancy and Flow Challenge
67+
68+
* We allow using annotations provided in the nuScenes dataset. During inference, the input modality of the model should be camera only.
69+
* No future frame is allowed during inference.
70+
* In order to check the compliance, we will ask the participants to provide technical reports to the challenge committee and the participant will be asked to provide a public talk about the method after winning the award.
71+
* Every submission provides method information. We encourage publishing code, but do not make it a requirement.
72+
* Each team can have at most one account on the evaluation server. Users that create multiple accounts to circumvent the rules will be excluded from the challenge.
73+
* Each team can submit at most three results during the challenge.
74+
* Faulty submissions that return an error on HuggingFace do not count towards the submission limit.
75+
* Any attempt to circumvent these rules will result in a permanent ban of the team or company from the challenge.
76+
6577
<p align="right">(<a href="#top">back to top</a>)</p>
6678

6779
## Evaluation Metrics
@@ -177,12 +189,10 @@ Please refer to [getting_started](docs/getting_started.md) for details.
177189

178190
### Submission site
179191

180-
Please submit your result on our [evaluation server](https://huggingface.co/spaces/AGC2024-S/occupancy-and-flow-2024). The submission rule can be referred to [here](#rules-for-occupancy-challenge)
192+
Please submit your result on our [evaluation server](https://huggingface.co/spaces/AGC2024-S/occupancy-and-flow-2024). The submission rule can be referred to [here](#rules-for-occupancy-and-flow-challenge)
181193

182194
### Submission format
183195

184-
We define a standardized 3D occupancy prediction result format that serves as an input to the evaluation code. Results are evaluated for each sample. The 3D occupancy prediction results for a the test evaluation set are stored in a folder. The participant needs to zip the results folder and submit it to the official evaluation server.
185-
186196
The submission must be a single `dict` with the following structure:
187197

188198
```
@@ -194,17 +204,17 @@ submission = {
194204
'institution / company': "XXXXXXXXXX",
195205
'country / region': "XXXXXXX",
196206
'results': {
197-
[scene_token1]: {
207+
[sample_token1]: {
198208
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
199209
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
200210
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,
201211
},
202-
[scene_token2]: {
212+
[sample_token2]: {
203213
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
204214
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
205215
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,
206216
},
207-
[scene_token3]: {
217+
[sample_token3]: {
208218
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
209219
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
210220
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,

docs/getting_started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ export CUDA_VISIBLE_DEVICES=0
3737

3838
## Test Submission
3939

40-
1. Fill your information in `projects/mmdet3d_plugin/datasets/nuscenes_occ.py` (Line 215).
40+
1. Fill your information in `projects/mmdet3d_plugin/datasets/nuscenes_occ.py` (Line 231).
4141

4242
2. Test the baseline model on the test split with 8 GPUs, and generate the submission to the official evaluation server.
4343

0 commit comments

Comments
 (0)