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
+16-6Lines changed: 16 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,7 @@ If you use the challenge dataset in your paper, please consider citing OccNet wi
45
45
-[Introduction](#introduction)
46
46
-[News](#news)
47
47
-[Task Definition](#task-definition)
48
+
-[Rules for Occupancy and Flow Challenge](#rules-for-occupancy-and-flow-challenge)
48
49
-[Evaluation Metrics](#evaluation-metrics)
49
50
-[Ray-based mIoU](#evaluation-metrics)
50
51
-[AVE for Occupancy Flow](#evaluation-metrics)
@@ -62,6 +63,17 @@ If you use the challenge dataset in your paper, please consider citing OccNet wi
62
63
63
64
Given images from multiple cameras, the goal is to predict the semantics and flow of each voxel grid in the scene.
64
65
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
+
65
77
<palign="right">(<ahref="#top">back to top</a>)</p>
66
78
67
79
## Evaluation Metrics
@@ -177,12 +189,10 @@ Please refer to [getting_started](docs/getting_started.md) for details.
177
189
178
190
### Submission site
179
191
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)
181
193
182
194
### Submission format
183
195
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
-
186
196
The submission must be a single `dict` with the following structure:
187
197
188
198
```
@@ -194,17 +204,17 @@ submission = {
194
204
'institution / company': "XXXXXXXXXX",
195
205
'country / region': "XXXXXXX",
196
206
'results': {
197
-
[scene_token1]: {
207
+
[sample_token1]: {
198
208
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
199
209
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
200
210
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,
201
211
},
202
-
[scene_token2]: {
212
+
[sample_token2]: {
203
213
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
204
214
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
205
215
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,
206
216
},
207
-
[scene_token3]: {
217
+
[sample_token3]: {
208
218
'pcd_cls' (np.ndarray): predicted class ID of shape (N) and type np.uint8,
209
219
'pcd_dist' (np.ndarray): predicted depth of shape (N) and type np.float16,
210
220
'pcd_flow' (np.ndarray): predicted flow of shape (N, 2) and type np.float16,
0 commit comments