Add paper and code repository links to dataset card

#2
by nielsr HF Staff - opened
Files changed (1) hide show
  1. README.md +8 -5
README.md CHANGED
@@ -1,20 +1,23 @@
1
  ---
 
 
2
  license: cc-by-nc-4.0
 
 
3
  task_categories:
4
  - robotics
5
  - visual-question-answering
6
- language:
7
- - en
8
  tags:
9
  - robotic-bin-packing
10
  - benchmark
11
  - vision-language-model
12
  - closed-loop-control
13
  - packlab
14
- size_categories:
15
- - n<1K
16
  ---
17
 
 
 
 
18
  ## πŸ“Œ Benchmark Summary
19
 
20
  **PackLab-Bench** is a standardized benchmark for evaluating closed-loop robotic bin packing policies. It contains 60 test cases organized into easy, medium, and hard difficulty levels.
@@ -105,4 +108,4 @@ print(easy.iloc[0].to_dict().keys())
105
 
106
  PackLab-Bench is released under **CC BY-NC 4.0** for research and non-commercial benchmarking use.
107
 
108
- Users should validate generated packing actions before deploying them on real robotic hardware. Physical execution requires appropriate safety checks, collision handling, and supervision.
 
1
  ---
2
+ language:
3
+ - en
4
  license: cc-by-nc-4.0
5
+ size_categories:
6
+ - n<1K
7
  task_categories:
8
  - robotics
9
  - visual-question-answering
 
 
10
  tags:
11
  - robotic-bin-packing
12
  - benchmark
13
  - vision-language-model
14
  - closed-loop-control
15
  - packlab
 
 
16
  ---
17
 
18
+ **Paper**: [PackLab: A Comprehensive Framework for Developing, Training, and Evaluating MLLMs in Robotic Bin Packing](https://huggingface.co/papers/2609.23784)
19
+ **Code**: [https://github.com/Correr-Zhou/PackLab](https://github.com/Correr-Zhou/PackLab)
20
+
21
  ## πŸ“Œ Benchmark Summary
22
 
23
  **PackLab-Bench** is a standardized benchmark for evaluating closed-loop robotic bin packing policies. It contains 60 test cases organized into easy, medium, and hard difficulty levels.
 
108
 
109
  PackLab-Bench is released under **CC BY-NC 4.0** for research and non-commercial benchmarking use.
110
 
111
+ Users should validate generated packing actions before deploying them on real robotic hardware. Physical execution requires appropriate safety checks, collision handling, and supervision.