Upload current ExeWorldBench dataset (part 2)

t1/task_image/004/004.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+004
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/004/004.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/004/frame/004_000.png, /xxx/ExeWorldBench/t1/task_image/004/frame/004_001.png, /xxx/ExeWorldBench/t1/task_image/004/frame/004_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/004
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/004. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/004/004.py
+* /xxx/ExeWorldBench/t1/task_image/004/004.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/005/005.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+005
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/005/005.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/005/frame/005_000.png, /xxx/ExeWorldBench/t1/task_image/005/frame/005_001.png, /xxx/ExeWorldBench/t1/task_image/005/frame/005_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/005
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/005. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/005/005.py
+* /xxx/ExeWorldBench/t1/task_image/005/005.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/006/006.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+006
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/006/006.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/006/frame/006_000.png, /xxx/ExeWorldBench/t1/task_image/006/frame/006_001.png, /xxx/ExeWorldBench/t1/task_image/006/frame/006_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/006
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/006. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/006/006.py
+* /xxx/ExeWorldBench/t1/task_image/006/006.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/007/007.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+007
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/007/007.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/007/frame/007_000.png, /xxx/ExeWorldBench/t1/task_image/007/frame/007_001.png, /xxx/ExeWorldBench/t1/task_image/007/frame/007_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/007
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/007. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/007/007.py
+* /xxx/ExeWorldBench/t1/task_image/007/007.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/008/008.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+008
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/008/008.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/008/frame/008_000.png, /xxx/ExeWorldBench/t1/task_image/008/frame/008_001.png, /xxx/ExeWorldBench/t1/task_image/008/frame/008_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/008
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/008. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/008/008.py
+* /xxx/ExeWorldBench/t1/task_image/008/008.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/009/009.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+009
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/009/009.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/009/frame/009_000.png, /xxx/ExeWorldBench/t1/task_image/009/frame/009_001.png, /xxx/ExeWorldBench/t1/task_image/009/frame/009_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/009
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/009. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/009/009.py
+* /xxx/ExeWorldBench/t1/task_image/009/009.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/010/010.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+010
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/010/010.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/010/frame/010_000.png, /xxx/ExeWorldBench/t1/task_image/010/frame/010_001.png, /xxx/ExeWorldBench/t1/task_image/010/frame/010_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/010
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/010. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/010/010.py
+* /xxx/ExeWorldBench/t1/task_image/010/010.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/011/011.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+011
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/011/011.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/011/frame/011_000.png, /xxx/ExeWorldBench/t1/task_image/011/frame/011_001.png, /xxx/ExeWorldBench/t1/task_image/011/frame/011_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/011
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/011. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/011/011.py
+* /xxx/ExeWorldBench/t1/task_image/011/011.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/012/012.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+012
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/012/012.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/012/frame/012_000.png, /xxx/ExeWorldBench/t1/task_image/012/frame/012_001.png, /xxx/ExeWorldBench/t1/task_image/012/frame/012_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/012
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/012. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/012/012.py
+* /xxx/ExeWorldBench/t1/task_image/012/012.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t1/task_image/013/013.txt

@@ -0,0 +1,82 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+013
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/013/013.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/013/frame/013_000.png, /xxx/ExeWorldBench/t1/task_image/013/frame/013_001.png, /xxx/ExeWorldBench/t1/task_image/013/frame/013_002.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t1/task_image/013
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/013. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/013/013.py
+* /xxx/ExeWorldBench/t1/task_image/013/013.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.