HongchengGao's picture
Align task taxonomy and IDs with the updated paper; main evaluation 306
3de3b50 verified
Raw History Blame Contribute Delete
3.93 kB
{
"id": "single-software-execution--cli--blender--task-08--ubuntu",
"snapshot": "Blender-4.2.3",
"instruction": "CSV-Driven Brick Wall `/home/user/Desktop/bricks.csv` holds 100 rows describing 100 bricks; `/home/user/Desktop/template.blend` is an empty scene. Launch Blender by running `blender` from a terminal. At the start of the task, use `/opt/blender/blender` for Blender command-line or background runs when working on `template.blend`.\n\nProduce one joined mesh object named `Wall`, built from 100 brick-shaped cuboids placed at the transforms listed in the CSV, and save the result to `/home/user/Desktop/answer.blend`. ## CSV schema The CSV is UTF-8, comma-separated, no quoting. The first line is the exact header: ``` x,y,z,rx,ry,rz,sx,sy,sz ``` Each of the 100 data rows describes one brick: - `(x, y, z)` — the world-space center of that brick (meters). - `(rx, ry, rz)` — Euler rotation in radians (XYZ order). - `(sx, sy, sz)` — full world-space dimensions of that brick along local X/Y/Z (meters). A brick is a cuboid centered at `(x, y, z)`, rotated by `(rx, ry, rz)`, with outer dimensions `(sx, sy, sz)`. ## Output Save the completed scene to `/home/user/Desktop/answer.blend`. The scene must contain a single mesh object `Wall` that is the union of all 100 bricks as separate, non-overlapping connected components in one mesh datablock. The brick geometries must be baked into the mesh data (i.e. `Wall` itself sits at the world origin with identity rotation and unit scale; per-brick transforms live in the vertex coordinates). ## Requirements 1. `/home/user/Desktop/answer.blend` exists and opens. 2. The scene contains exactly one mesh object named `Wall` with an empty modifier stack. 3. `Wall`'s object location is `(0, 0, 0)` within 1e-5, rotation is zero within 1e-5, scale is `(1, 1, 1)` within 1e-5. 4. `Wall`'s mesh has exactly 600 faces. 5. `Wall`'s mesh has exactly 800 vertices. 6. `Wall`'s mesh splits into exactly 100 connected components (vertex/edge-connected islands). 7. Each connected component's world-space bounding-box center matches one unique CSV row's `(x, y, z)` within 0.01, and every CSV row is matched exactly once. 8. Each matched component's world-space axis-aligned bounding-box dimensions equal the CSV row's `(sx, sy, sz)` within 0.01 on each axis. How you produce `/home/user/Desktop/answer.blend` (Blender UI, a Python script, or otherwise) is up to you; only the final state matters.",
"source": "https://docs.blender.org/manual/en/4.1/; https://docs.blender.org/api/4.1/; https://developer.blender.org/docs/release_notes/4.1/; https://www.loc.gov/preservation/digital/formats/fdd/fdd000507.shtml",
"config": [
{
"type": "upload_file",
"parameters": {
"files": [
{
"local_path": "task-08/init_file/bricks.csv",
"path": "/home/user/Desktop/bricks.csv"
}
]
}
},
{
"type": "upload_file",
"parameters": {
"files": [
{
"local_path": "task-08/init_file/template.blend",
"path": "/home/user/Desktop/template.blend"
}
]
}
}
],
"trajectory": "trajectories/",
"related_apps": [
"blender"
],
"artifact_paths": [
"/home/user/Desktop/answer.blend"
],
"evaluator": {
"postconfig": [
{
"type": "upload_file",
"parameters": {
"files": [
{
"local_path": "task-08/eval.py",
"path": "/home/user/Desktop/eval.py"
}
]
}
}
],
"func": "exact_match",
"result": {
"type": "vm_command_line",
"command": "python3 /home/user/Desktop/eval.py",
"shell": "true"
},
"expected": {
"type": "rule",
"rules": {
"expected": "True\n"
}
}
},
"proxy": false,
"fixed_ip": false,
"possibility_of_env_change": "low"
}