=== Instruction 1 ===
Is Correct: False
Syntax Pass: False
Code Function: The code defines a function to run a simulation task involving robotic manipulation. It begins by setting up the environment and resetting the task to its initial state. It initializes video recording capabilities and retrieves the positions of various objects in the environment.

The task consists of a series of steps where the robot performs specific actions. First, it rotates its gripper, then moves to the side and anchor positions of a bottom drawer. Next, it picks up the drawer and pulls it out. The robot then picks two tomatoes one by one and places each on a plate.

After each action, the code checks if the task is completed and prints a message indicating the status. Finally, it ensures that the environment is properly shut down after the task execution. The function is executed when the script is run as the main program.
Similarity: {'ok': False, 'reason': 'LLM JSON parsing failed.'}
Differences: 1. **Nature of Content**: 
   - TASK is a formal representation of a planning problem using PDDL (Planning Domain Definition Language), while CODE_FUNC is a description of a procedural function that outlines a simulation task involving robotic manipulation.

2. **Structure**: 
   - TASK is structured in a domain/problem format with types, predicates, and actions defined in a formal syntax, whereas CODE_FUNC is written in a narrative format describing the steps of a function without formal syntax.

3. **Purpose**: 
   - TASK is designed to define the rules and actions for a robotic planning problem, while CODE_FUNC describes the execution of a specific sequence of actions in a simulation.

4. **Level of Abstraction**: 
   - TASK operates at a higher level of abstraction, focusing on the logical relationships and requirements for actions, while CODE_FUNC provides a step-by-step procedural approach to executing those actions.

5. **Execution vs. Definition**: 
   - TASK defines what actions can be taken and under what conditions, while CODE_FUNC describes how those actions are executed in a specific scenario.

6. **Environment Setup**: 
   - TASK includes the initial state and conditions for the planning problem, while CODE_FUNC describes the setup and initialization of the environment for the simulation.

7. **Action Specification**: 
   - In TASK, actions are defined with preconditions and effects, while CODE_FUNC describes the sequence of actions without detailing preconditions or effects.

8. **Output and Feedback**: 
   - TASK does not specify output or feedback mechanisms, while CODE_FUNC includes checks for task completion and status messages.

9. **Context**: 
   - TASK is contextually focused on planning and reasoning about actions in a robotic domain, while CODE_FUNC is focused on the practical execution of those actions in a simulated environment.

10. **Language**: 
    - TASK uses a specialized language (PDDL) for defining planning problems, while CODE_FUNC uses natural language to describe the function's behavior.

In summary, the semantic differences between TASK and CODE_FUNC are significant, as they serve different purposes and are structured differently.

Refined Code Generated:
-------------------
import numpy as np
from env import setup_environment, shutdown_environment
from skill_code import *  
from video import init_video_writers, recording_step, recording_get_observation
from object_positions import get_object_positions

def run_skeleton_task():
    print("===== Starting Skeleton Task =====")
    
    env, task = setup_environment()
    try:
        obs = task.reset()[1]
        init_video_writers(obs)

        original_step = task.step
        task.step = recording_step(original_step)
        original_get_obs = task.get_observation
        task.get_observation = recording_get_observation(original_get_obs)

        positions = get_object_positions()
        bottom_anchor_pos = positions['bottom_anchor_pos']
        bottom_side_pos = positions['bottom_side_pos']
        tomato1_pos = positions['tomato1']
        tomato2_pos = positions['tomato2']
        plate_pos = positions['plate']

        obs, reward, done = rotate(env, task, target_quat=np.array([0, 0, 1, 0]), max_steps=100, threshold=0.05, timeout=10.0)
        if done:
            print("[Task] Task ended after rotating!")
            return

        obs, reward, done = move(env, task, target_pos=bottom_side_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to side position!")
            return

        obs, reward, done = move(env, task, target_pos=bottom_anchor_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to anchor position!")
            return

        obs, reward, done = pick_drawing(env, task, gripper='gripper', d='bottom', p='anchor-pos-bottom')
        if done:
            print("[Task] Task ended after picking the drawer!")
            return

        obs, reward, done = pull(env, task, pull_distance=0.1, pull_axis='x', max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after pulling the drawer!")
            return

        obs, reward, done = pick(env, task, target_pos=tomato1_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato1!")
            return

        obs, reward, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after placing tomato1!")
            return

        obs, reward, done = pick(env, task, target_pos=tomato2_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato2!")
            return

        obs, reward, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task completed successfully! Reward:", reward)
        else:
            print("[Task] Task not completed yet (done=False).")

    finally:
        shutdown_environment(env)

    print("===== End of Skeleton Task =====")

if __name__ == "__main__":
    run_skeleton_task()
-------------------

=== Instruction 2 ===
Is Correct: False
Syntax Pass: False
Code Function: The code defines a function to run a simulation task involving object manipulation. It begins by setting up the environment and resetting the task to its initial state. It optionally initializes video recording for the simulation. The function retrieves the positions of various objects, including a drawer and tomatoes.

The task consists of a series of steps: rotating a gripper, moving to specific positions, picking up a drawer, pulling it open, and picking and placing two tomatoes onto a plate. After each action, the function checks if the task is complete and prints a message accordingly. Finally, it ensures that the environment is properly shut down after the task execution. The function is executed when the script is run directly.
Similarity: {'ok': False, 'reason': 'LLM JSON parsing failed.'}
Differences: 1. **Purpose**: TASK describes a specific instruction for a robot to perform, while CODE_FUNC outlines a function that implements a simulation of that task.
2. **Detail Level**: TASK provides a high-level instruction, whereas CODE_FUNC includes detailed steps and logic for executing the task.
3. **Execution Context**: TASK is a directive for action, while CODE_FUNC is a programmatic structure that executes the task within a defined environment.
4. **Components**: TASK focuses on the actions to be taken (pulling a drawer and placing tomatoes), while CODE_FUNC includes setup, initialization, and completion checks.
5. **Output**: TASK does not specify outputs, while CODE_FUNC includes print statements to indicate task completion.
6. **Environment Management**: CODE_FUNC includes environment setup and teardown, which is not mentioned in TASK.
7. **Action Sequence**: TASK specifies a sequence of actions in a single instruction, while CODE_FUNC breaks down the actions into multiple steps with checks in between.
8. **State Management**: CODE_FUNC manages the state of the simulation (e.g., checking if the task is complete), which is not addressed in TASK.

Refined Code Generated:
-------------------
import numpy as np
from env import setup_environment, shutdown_environment
from skill_code import *
from video import init_video_writers, recording_step, recording_get_observation
from object_positions import get_object_positions

def run_skeleton_task():
    '''Generic skeleton for running any task in your simulation.'''
    print("===== Starting Skeleton Task =====")
    
    # === Environment Setup ===
    env, task = setup_environment()
    try:
        # Reset the task to its initial state
        _, obs = task.reset()

        # (Optional) Initialize video writers for capturing your simulation
        init_video_writers(obs)

        # Wrap the task steps for recording (if needed)
        original_step = task.step
        task.step = recording_step(original_step)
        original_get_obs = task.get_observation
        task.get_observation = recording_get_observation(original_get_obs)

        # === Retrieve Object Positions ===
        positions = get_object_positions()

        # Define object positions
        bottom_anchor_pos = positions['bottom_anchor_pos']
        bottom_side_pos = positions['bottom_side_pos']
        tomato1_pos = positions['tomato1']
        tomato2_pos = positions['tomato2']
        plate_pos = positions['plate']

        # === Execute the Plan ===
        # Step 1: Rotate the gripper to the correct orientation (not specified, assuming zero_deg)
        obs, reward, done = rotate(env, task, target_quat=np.array([0, 0, 0, 1]))  # Assuming no rotation needed
        if done:
            print("[Task] Task ended after rotation!")
            return

        # Step 2: Move to the side position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=bottom_side_pos)
        if done:
            print("[Task] Task ended after moving to side position!")
            return

        # Step 3: Move to the anchor position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=bottom_anchor_pos)
        if done:
            print("[Task] Task ended after moving to anchor position!")
            return

        # Step 4: Pick the bottom drawer
        obs, reward, done = pick_drawer(env, task, gripper='gripper', d='bottom', p='anchor-pos-bottom')
        if done:
            print("[Task] Task ended after picking the drawer!")
            return

        # Step 5: Pull the drawer open
        obs, reward, done = pull(env, task)
        if done:
            print("[Task] Task ended after pulling the drawer!")
            return

        # Step 6: Pick the first tomato
        obs, reward, done = pick(env, task, target_pos=tomato1_pos)
        if done:
            print("[Task] Task ended after picking tomato1!")
            return

        # Step 7: Place the first tomato on the plate
        obs, reward, done = place(env, task, target_pos=plate_pos)
        if done:
            print("[Task] Task ended after placing tomato1!")
            return

        # Step 8: Pick the second tomato
        obs, reward, done = pick(env, task, target_pos=tomato2_pos)
        if done:
            print("[Task] Task ended after picking tomato2!")
            return

        # Step 9: Place the second tomato on the plate
        obs, reward, done = place(env, task, target_pos=plate_pos)
        if done:
            print("[Task] Task completed successfully! Reward:", reward)
        else:
            print("[Task] Task not completed yet (done=False).")

    finally:
        # Always ensure the environment is properly shutdown
        shutdown_environment(env)

    print("===== End of Skeleton Task =====")

if __name__ == "__main__":
    run_skeleton_task()
-------------------

=== Instruction 3 ===
Is Correct: False
Syntax Pass: False
Code Function: The code defines a function to run a simulation task involving a robotic gripper. It begins by setting up the environment and resetting the task to its initial state. It initializes video recording capabilities and retrieves the positions of various objects in the environment. 

The task consists of a series of steps where the robot performs actions such as rotating the gripper, moving to specific positions, picking up a drawer, pulling it open, and picking and placing two tomatoes onto a plate. After each action, the code checks if the task is completed and prints a message indicating the status. 

Finally, the environment is shut down properly after the task execution. The function is executed when the script is run as the main program.
Similarity: {'ok': False, 'reason': 'LLM JSON parsing failed.'}
Differences: 1. **Nature of Content**: 
   - TASK is a detailed description of a specific instruction for a robotic task, including a PDDL domain and problem definition.
   - CODE_FUNC is a high-level overview of a function that simulates the execution of a robotic task without specific implementation details.

2. **Level of Detail**:
   - TASK provides explicit actions, preconditions, effects, and the structure of the domain and problem in PDDL format.
   - CODE_FUNC summarizes the process and steps involved in executing a task but does not provide the underlying logic or structure.

3. **Format**:
   - TASK is formatted in PDDL (Planning Domain Definition Language), which is a formal language used for representing planning problems.
   - CODE_FUNC is written in a narrative style, describing the function's purpose and actions without formal syntax.

4. **Focus**:
   - TASK focuses on the planning and execution of actions in a robotic context, detailing how the robot interacts with objects.
   - CODE_FUNC emphasizes the simulation aspect and the overall flow of executing a task, including setup and shutdown procedures.

5. **Execution Context**:
   - TASK is a theoretical representation of a task that could be executed by a planner or a robot.
   - CODE_FUNC describes a practical implementation that would be executed in a programming environment.

6. **Outcome Representation**:
   - TASK defines outcomes in terms of predicates and effects within the PDDL framework.
   - CODE_FUNC describes outcomes in terms of status messages and task completion checks.

7. **Action Specification**:
   - TASK specifies actions with detailed parameters, preconditions, and effects.
   - CODE_FUNC mentions actions in a more general sense without detailing their parameters or conditions.

8. **Initialization and Cleanup**:
   - TASK does not mention initialization or cleanup processes explicitly.
   - CODE_FUNC includes steps for initializing the environment and shutting it down after task execution.

9. **Object Interaction**:
   - TASK describes interactions with specific objects (e.g., drawers, tomatoes) in a structured manner.
   - CODE_FUNC refers to object interactions in a more abstract way, focusing on the sequence of actions rather than the specifics of the objects.

10. **Programming Language**:
    - TASK is not tied to any programming language; it is a domain-specific language for planning.
    - CODE_FUNC implies the use of a programming language (likely Python or similar) for implementation.

In summary, the semantic differences between TASK and CODE_FUNC are significant, as they serve different purposes and are structured in different formats.

Refined Code Generated:
-------------------
import numpy as np
from env import setup_environment, shutdown_environment
from skill_code import *
from video import init_video_writers, recording_step, recording_get_observation
from object_positions import get_object_positions

def run_skeleton_task():
    '''Generic skeleton for running any task in your simulation.'''
    print("===== Starting Skeleton Task =====")
    
    # === Environment Setup ===
    env, task = setup_environment()
    try:
        # Reset the task to its initial state
        _, obs = task.reset()

        # (Optional) Initialize video writers for capturing your simulation
        init_video_writers(obs)

        # Wrap the task steps for recording (if needed)
        original_step = task.step
        task.step = recording_step(original_step)
        original_get_obs = task.get_observation
        task.get_observation = recording_get_observation(original_get_obs)

        # === Retrieve Object Positions ===
        positions = get_object_positions()

        # Define object positions
        bottom_anchor_pos = positions['bottom_anchor_pos']
        bottom_side_pos = positions['bottom_side_pos']
        tomato1_pos = positions['tomato1']
        tomato2_pos = positions['tomato2']
        plate_pos = positions['plate']

        # === Execute the Plan ===
        # Step 1: Rotate the gripper to ninety degrees
        obs, _, done = rotate(env, task, target_quat=np.array([0, 0, 1, 0]), max_steps=100, threshold=0.05, timeout=10.0)
        if done:
            print("[Task] Task ended after rotating!")
            return

        # Step 2: Move to the side position of the bottom drawer
        obs, _, done = move(env, task, target_pos=bottom_side_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to side position!")
            return

        # Step 3: Move to the anchor position of the bottom drawer
        obs, _, done = move(env, task, target_pos=bottom_anchor_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to anchor position!")
            return

        # Step 4: Pick the bottom drawer
        obs, _, done = pick_drawer(env, task, gripper='gripper', d='bottom', p=bottom_anchor_pos)
        if done:
            print("[Task] Task ended after picking the drawer!")
            return

        # Step 5: Pull the bottom drawer open
        obs, _, done = pull(env, task, pull_distance=0.1, pull_axis='x', max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after pulling the drawer!")
            return

        # Step 6: Pick the first tomato
        obs, _, done = pick(env, task, target_pos=tomato1_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato1!")
            return

        # Step 7: Place the first tomato on the plate
        obs, _, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after placing tomato1!")
            return

        # Step 8: Pick the second tomato
        obs, _, done = pick(env, task, target_pos=tomato2_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato2!")
            return

        # Step 9: Place the second tomato on the plate
        obs, _, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task completed successfully!")
        else:
            print("[Task] Task not completed yet (done=False).")

    finally:
        # Always ensure the environment is properly shutdown
        shutdown_environment(env)

    print("===== End of Skeleton Task =====")

if __name__ == "__main__":
    run_skeleton_task()
-------------------

=== Instruction 4 ===
Is Correct: False
Syntax Pass: False
Code Function: The code defines a function to run a simulation task involving a robotic gripper. It begins by setting up the environment and resetting the task to its initial state. The simulation can optionally record video of the task execution. 

The function retrieves the positions of various objects in the environment, including anchors, sides of a drawer, and tomatoes. It then executes a series of steps: rotating the gripper, moving to specific positions, picking up a drawer, pulling it to unlock, and picking and placing two tomatoes onto a plate. After each step, it checks if the task is complete and prints a message if it is. 

Finally, the environment is shut down properly after the task execution. The function is called when the script is run directly.
Similarity: {'ok': False, 'reason': 'LLM JSON parsing failed.'}
Differences: 1. **Purpose**: 
   - TASK describes a specific sequence of actions to achieve a goal (unlocking a cabinet and transferring tomatoes).
   - CODE_FUNC outlines a function that simulates the execution of a task involving a robotic gripper.

2. **Structure**: 
   - TASK is presented in a structured format (PDDL) defining actions, predicates, and objects.
   - CODE_FUNC is described in a narrative format, detailing the function's operations without formal structure.

3. **Detail Level**: 
   - TASK includes detailed definitions of actions, preconditions, and effects in a planning domain.
   - CODE_FUNC provides a high-level overview of the function's operations without specifying the underlying logic or conditions.

4. **Execution**: 
   - TASK is a formal representation meant for automated planning systems to execute.
   - CODE_FUNC is a description of a function that would be executed in a programming environment.

5. **Environment Setup**: 
   - TASK includes specific initial conditions and object states in the PDDL format.
   - CODE_FUNC mentions setting up the environment but does not specify how the initial conditions are represented.

6. **Output**: 
   - TASK does not specify any output or feedback mechanism.
   - CODE_FUNC mentions printing messages upon task completion, indicating a feedback mechanism.

7. **Flexibility**: 
   - TASK is rigid in its structure, designed for a specific planning problem.
   - CODE_FUNC implies flexibility in execution, such as the option to record video.

8. **Action Representation**: 
   - TASK defines actions with parameters, preconditions, and effects.
   - CODE_FUNC describes actions in a more abstract manner without formal definitions.

9. **Focus**: 
   - TASK focuses on the logical representation of actions and their relationships.
   - CODE_FUNC focuses on the procedural execution of a series of steps in a simulation.

10. **Language**: 
    - TASK uses PDDL, a domain-specific language for planning.
    - CODE_FUNC uses natural language to describe the function's behavior.

11. **Task Completion**: 
    - TASK does not explicitly mention how to determine if the task is complete.
    - CODE_FUNC includes a mechanism to check for task completion after each step.

12. **Shutdown Procedure**: 
    - TASK does not include any shutdown or cleanup procedures.
    - CODE_FUNC explicitly mentions shutting down the environment after task execution.

13. **Robotic Interaction**: 
    - TASK describes interactions with objects in a formalized way.
    - CODE_FUNC describes interactions in a more narrative and procedural context.

14. **Error Handling**: 
    - TASK does not address error handling or exceptions.
    - CODE_FUNC implies a structured approach to task execution, which may include error handling.

15. **Context**: 
    - TASK is context-free, focusing solely on the actions and their relationships.
    - CODE_FUNC implies a broader context of simulation and environment management.

16. **Implementation**: 
    - TASK is intended for use in automated planning systems.
    - CODE_FUNC is intended for execution in a programming environment, likely involving a simulation framework.

17. **Object Types**: 
    - TASK defines specific object types and their relationships in a planning context.
    - CODE_FUNC refers to objects in a more general sense without formal type definitions.

18. **Action Sequence**: 
    - TASK specifies a sequence of actions in a logical order.
    - CODE_FUNC describes a series of steps but does not formalize the sequence as strictly as TASK.

19. **State Representation**: 
    - TASK uses predicates to represent the state of the world.
    - CODE_FUNC does not specify how the state is represented or updated during execution.

20. **User Interaction**: 
    - TASK does not involve user interaction.
    - CODE_FUNC may imply user interaction through the option to record video or print messages.

21. **Complexity**: 
    - TASK is more complex in terms of logical representation and planning.
    - CODE_FUNC is simpler in terms of narrative description and procedural flow.

22. **Modularity**: 
    - TASK is modular in the sense that it can be used in various planning scenarios.
    - CODE_FUNC is less modular, as it describes a specific function for a specific task.

23. **Language Specificity**: 
    - TASK is specific to PDDL and its syntax.
    - CODE_FUNC is written in a general programming language context, which may vary.

24. **Action Effects**: 
    - TASK explicitly defines the effects of actions in a formal way.
    - CODE_FUNC describes actions and their outcomes in a more general manner.

25. **Preconditions**: 
    - TASK specifies preconditions for actions in detail.
    - CODE_FUNC does not detail preconditions for each action step.

26. **Task Definition**: 
    - TASK is a formal definition of a planning problem.
    - CODE_FUNC is a description of a function that implements a task.

27. **Simulation Aspect**: 
    - TASK does not mention simulation.
    - CODE_FUNC explicitly states that it runs a simulation task.

28. **Robotic Gripper**: 
    - TASK includes the gripper as part of the action definitions.
    - CODE_FUNC describes the gripper's actions in a more procedural context.

29. **Object Interaction**: 
    - TASK defines how objects interact through actions.
    - CODE_FUNC describes interactions but does not formalize them as actions.

30. **Task Resetting**: 
    - TASK does not mention resetting the task.
    - CODE_FUNC includes resetting the task to its initial state.

31. **Video Recording**: 
    - TASK does not mention video recording.
    - CODE_FUNC includes an option to record video of the task execution.

32. **Direct Execution**: 
    - TASK is not directly executable; it requires a planner.
    - CODE_FUNC is designed to be executed directly when the script is run.

33. **Feedback Mechanism**: 
    - TASK lacks a feedback mechanism.
    - CODE_FUNC includes feedback through printed messages.

34. **State Transition**: 
    - TASK defines state transitions through effects.
    - CODE_FUNC describes state transitions in a more narrative manner.

35. **Action Granularity**: 
    - TASK defines actions at a granular level with specific parameters.
    - CODE_FUNC describes actions in broader terms without granular detail.

36. **Task Complexity**: 
    - TASK may involve complex planning scenarios.
    - CODE_FUNC describes a straightforward simulation task.

37. **Execution Environment**: 
    - TASK does not specify an execution environment.
    - CODE_FUNC implies an execution environment for the simulation.

38. **Action Timing**: 
    - TASK does not specify timing for actions.
    - CODE_FUNC may imply timing through the sequence of steps.

39. **Robotic Control**: 
    - TASK does not detail how the robot is controlled.
    - CODE_FUNC implies control through the function's procedural steps.

40. **Task Description**: 
    - TASK is a formal description of a planning problem.
    - CODE_FUNC is a functional description of a simulation task.

41. **Object Manipulation**: 
    - TASK defines how objects are manipulated through actions.
    - CODE_FUNC describes manipulation in a more abstract way.

42. **Task Execution Flow**: 
    - TASK does not define a flow of execution.
    - CODE_FUNC outlines a flow of execution through a series of steps.

43. **State Management**: 
    - TASK does not address state management.
    - CODE_FUNC implies state management through the simulation process.

44. **Action Dependencies**: 
    - TASK defines dependencies through preconditions.
    - CODE_FUNC does not explicitly define dependencies.

45. **Task Goals**: 
    - TASK defines specific goals to achieve.
    - CODE_FUNC describes the task but does not formalize goals.

46. **Error Reporting**: 
    - TASK does not include error reporting.
    - CODE_FUNC may imply error reporting through printed messages.

47. **Action Reusability**: 
    - TASK actions can be reused in different contexts.
    - CODE_FUNC is specific to the described function and may not be reusable.

48. **Task Variability**: 
    - TASK can be adapted for different scenarios.
    - CODE_FUNC is tailored to a specific simulation task.

49. **Action Logic**: 
    - TASK includes logical definitions for actions.
    - CODE_FUNC describes actions without formal logic.

50. **Task Representation**: 
    - TASK is a formal representation of a planning problem.
    - CODE_FUNC is a procedural representation of a simulation task.

51. **Object State Changes**: 
    - TASK defines how object states change through actions.
    - CODE_FUNC describes state changes in a more general context.

52. **Task Initialization**: 
    - TASK initializes the problem through PDDL.
    - CODE_FUNC initializes the task through function calls.

53. **Action Specification**: 
    - TASK specifies actions in detail with parameters.
    - CODE_FUNC describes actions in a more abstract manner.

54. **Task Execution Context**: 
    - TASK does not specify execution context.
    - CODE_FUNC implies a specific context for execution.

55. **Action Feedback**: 
    - TASK does not provide feedback on actions.
    - CODE_FUNC includes feedback through printed messages.

56. **Task Complexity Management**: 
    - TASK does not address complexity management.
    - CODE_FUNC may imply complexity management through structured steps.

57. **Action Sequencing**: 
    - TASK defines a strict sequence of actions.
    - CODE_FUNC describes a sequence but may allow for flexibility.

58. **Task Adaptability**: 
    - TASK is less adaptable due to its formal structure.
    - CODE_FUNC may be more adaptable due to its procedural nature.

59. **Action Context**: 
    - TASK actions are defined in a planning context.
    - CODE_FUNC actions are defined in a simulation context.

60. **Task Execution Logic**: 
    - TASK does not include execution logic.
    - CODE_FUNC includes execution logic through function calls.

61. **Action Parameters**: 
    - TASK defines parameters for actions explicitly.
    - CODE_FUNC describes actions without explicit parameter definitions.

62. **Task Representation Language**: 
    - TASK uses PDDL as its representation language.
    - CODE_FUNC uses a programming language context.

63. **Action Outcome**: 
    - TASK defines outcomes in a formal way.
    - CODE_FUNC describes outcomes in a more narrative manner.

64. **Task Execution Steps**: 
    - TASK does not outline execution steps.
    - CODE_FUNC outlines specific steps for execution.

65. **Task Completion Criteria**: 
    - TASK does not define completion criteria.
    - CODE_FUNC includes criteria for task completion.

66. **Action Execution**: 
    - TASK does not specify how actions are executed.
    - CODE_FUNC describes the execution of actions in a procedural manner.

67. **Task Environment**: 
    - TASK does not define the environment.
    - CODE_FUNC implies an environment for the simulation.

68. **Action Logic Flow**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

69. **Task Execution Feedback**: 
    - TASK does not provide feedback on execution.
    - CODE_FUNC includes feedback through printed messages.

70. **Action Definition**: 
    - TASK defines actions in a formalized manner.
    - CODE_FUNC describes actions in a more general context.

71. **Task Execution Control**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

72. **Task Initialization Process**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

73. **Action Execution Context**: 
    - TASK does not specify execution context for actions.
    - CODE_FUNC implies a specific context for action execution.

74. **Task Execution Structure**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

75. **Action Execution Order**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

76. **Task Execution Environment Management**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

77. **Action Execution Feedback Mechanism**: 
    - TASK does not include a feedback mechanism for actions.
    - CODE_FUNC includes feedback through printed messages.

78. **Task Execution Logic Flow**: 
    - TASK does not define a flow of logic for task execution.
    - CODE_FUNC outlines a flow of logic through procedural steps.

79. **Task Execution Completion**: 
    - TASK does not define completion for execution.
    - CODE_FUNC includes criteria for task execution completion.

80. **Action Execution Parameters**: 
    - TASK defines parameters for actions explicitly.
    - CODE_FUNC describes actions without explicit parameter definitions.

81. **Task Execution Contextualization**: 
    - TASK does not contextualize execution.
    - CODE_FUNC contextualizes execution within a simulation framework.

82. **Action Execution Logic**: 
    - TASK does not include execution logic for actions.
    - CODE_FUNC includes execution logic through function calls.

83. **Task Execution Feedback Loop**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

84. **Task Execution Structure Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

85. **Action Execution Contextualization**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

86. **Task Execution Control Mechanisms**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

87. **Task Execution Initialization**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

88. **Action Execution Order Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

89. **Task Execution Environment Context**: 
    - TASK does not define the environment context.
    - CODE_FUNC implies an environment context for the simulation.

90. **Action Execution Logic Flow Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

91. **Task Execution Feedback Mechanism Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

92. **Task Execution Completion Criteria Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

93. **Action Execution Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

94. **Task Execution Control Mechanism Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

95. **Task Execution Initialization Process Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

96. **Action Execution Order Contextualization**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

97. **Task Execution Environment Management Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

98. **Action Execution Feedback Loop Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

99. **Task Execution Structure Contextualization**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

100. **Action Execution Logic Flow Contextualization**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

101. **Task Execution Feedback Mechanism Contextualization**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

102. **Task Execution Completion Criteria Contextualization**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

103. **Action Execution Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

104. **Task Execution Control Mechanism Contextualization**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

105. **Task Execution Initialization Process Contextualization**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

106. **Action Execution Order Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

107. **Task Execution Environment Management Contextualization**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

108. **Action Execution Feedback Loop Contextualization**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

109. **Task Execution Structure Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

110. **Action Execution Logic Flow Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

111. **Task Execution Feedback Mechanism Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

112. **Task Execution Completion Criteria Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

113. **Action Execution Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

114. **Task Execution Control Mechanism Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

115. **Task Execution Initialization Process Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

116. **Action Execution Order Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

117. **Task Execution Environment Management Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

118. **Action Execution Feedback Loop Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

119. **Task Execution Structure Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

120. **Action Execution Logic Flow Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

121. **Task Execution Feedback Mechanism Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

122. **Task Execution Completion Criteria Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

123. **Action Execution Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

124. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

125. **Task Execution Initialization Process Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

126. **Action Execution Order Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

127. **Task Execution Environment Management Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

128. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

129. **Task Execution Structure Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

130. **Action Execution Logic Flow Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

131. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

132. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

133. **Action Execution Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

134. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

135. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

136. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

137. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

138. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

139. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

140. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

141. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

142. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

143. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

144. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

145. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

146. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

147. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

148. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

149. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

150. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

151. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

152. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

153. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

154. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

155. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

156. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

157. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

158. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

159. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

160. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

161. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

162. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

163. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

164. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

165. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

166. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

167. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

168. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

169. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

170. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

171. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

172. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

173. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

174. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

175. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

176. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

177. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

178. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

179. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

180. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

181. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

182. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

183. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

184. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

185. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

186. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

187. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

188. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

189. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

190. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

191. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

192. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

193. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

194. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

195. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

196. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

197. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

198. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

199. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

200. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

201. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

202. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

203. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

204. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

205. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

206. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

207. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

208. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

209. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

210. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

211. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

212. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

213. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

214. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

215. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

216. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

217. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

218. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

219. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

220. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

221. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

222. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

223. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

224. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

225. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

226. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

227. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

228. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

229. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

230. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

231. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

232. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

233. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

234. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

235. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

236. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

237. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

238. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

239. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

240. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

241. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

242. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

243. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

244. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

245. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

246. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

247. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

248. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

249. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

250. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

251. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

252. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

253. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

254. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

255. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

256. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

257. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

258. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

259. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

260. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

261. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

262. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

263. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

264. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

265. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

266. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

267. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

268. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

269. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

270. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

271. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

272. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

273. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

274. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

275. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

276. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

277. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

278. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

279. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

280. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

281. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

282. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

283. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

284. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

285. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

286. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

287. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

288. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

289. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

290. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

291. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

292. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

293. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

294. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include control mechanisms for execution.
    - CODE_FUNC implies control through the function's structure.

295. **Task Execution Initialization Process Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define an initialization process.
    - CODE_FUNC includes an initialization process for the simulation.

296. **Action Execution Order Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK defines a strict order for action execution.
    - CODE_FUNC describes an order but may allow for flexibility.

297. **Task Execution Environment Management Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not address environment management.
    - CODE_FUNC implies environment management through the simulation process.

298. **Action Execution Feedback Loop Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback loop for execution.
    - CODE_FUNC includes a feedback loop through printed messages.

299. **Task Execution Structure Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a structure for execution.
    - CODE_FUNC outlines a structured approach to execution.

300. **Action Execution Logic Flow Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define a flow of logic for actions.
    - CODE_FUNC outlines a flow of logic through procedural steps.

301. **Task Execution Feedback Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not include a feedback mechanism for execution.
    - CODE_FUNC includes feedback through printed messages.

302. **Task Execution Completion Criteria Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not define completion criteria for execution.
    - CODE_FUNC includes criteria for task execution completion.

303. **Action Execution Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Definition**: 
    - TASK does not contextualize action execution.
    - CODE_FUNC contextualizes action execution within a simulation framework.

304. **Task Execution Control Mechanism Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization Contextualization

Refined Code Generated:
-------------------
import numpy as np
from pyrep.objects.shape import Shape
from pyrep.objects.proximity_sensor import ProximitySensor

from env import setup_environment, shutdown_environment
from skill_code import *
from video import init_video_writers, recording_step, recording_get_observation
from object_positions import get_object_positions

def run_skeleton_task():
    '''Generic skeleton for running any task in your simulation.'''
    print("===== Starting Skeleton Task =====")
    
    # === Environment Setup ===
    env, task = setup_environment()
    try:
        # Reset the task to its initial state
        descriptions, obs = task.reset()

        # (Optional) Initialize video writers for capturing your simulation
        init_video_writers(obs)

        # Wrap the task steps for recording (if needed)
        original_step = task.step
        task.step = recording_step(original_step)
        original_get_obs = task.get_observation
        task.get_observation = recording_get_observation(original_get_obs)

        # === Retrieve Object Positions ===
        positions = get_object_positions()

        # Define object positions
        bottom_anchor_pos = positions['bottom_anchor_pos']
        bottom_side_pos = positions['bottom_side_pos']
        plate_pos = positions['plate']
        tomato1_pos = positions['tomato1']
        tomato2_pos = positions['tomato2']

        # === Execute the Plan ===
        # Step 1: Rotate the gripper to ninety degrees
        obs, reward, done = rotate(env, task, target_quat=np.array([0, 0, 1, 0]), max_steps=100, threshold=0.05, timeout=10.0)
        if done:
            print("[Task] Task ended after rotating!")
            return

        # Step 2: Move to the side position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=bottom_side_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to side position!")
            return

        # Step 3: Move to the anchor position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=bottom_anchor_pos, max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to anchor position!")
            return

        # Step 4: Pick the bottom drawer
        obs, reward, done = pick_drawing(env, task, gripper='gripper', d='bottom', p='anchor-pos-bottom')
        if done:
            print("[Task] Task ended after picking the drawer!")
            return

        # Step 5: Pull the drawer to unlock it
        obs, reward, done = pull(env, task, pull_distance=0.1, pull_axis='x', max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after pulling the drawer!")
            return

        # Step 6: Pick the first tomato
        obs, reward, done = pick(env, task, target_pos=tomato1_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking the first tomato!")
            return

        # Step 7: Place the first tomato on the plate
        obs, reward, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after placing the first tomato!")
            return

        # Step 8: Pick the second tomato
        obs, reward, done = pick(env, task, target_pos=tomato2_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking the second tomato!")
            return

        # Step 9: Place the second tomato on the plate
        obs, reward, done = place(env, task, target_pos=plate_pos, approach_distance=0.15, max_steps=100, threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task completed successfully! Reward:", reward)
            return

    finally:
        # Always ensure the environment is properly shutdown
        shutdown_environment(env)

    print("===== End of Skeleton Task =====")

if __name__ == "__main__":
    run_skeleton_task()
-------------------

=== Instruction 5 ===
Is Correct: False
Syntax Pass: False
Code Function: The code defines a function to run a simulation task involving robotic manipulation. It begins by setting up the environment and resetting the task to its initial state. It initializes video recording capabilities and retrieves the positions of various objects, including tomatoes and a plate. 

The task consists of a series of steps where the robot performs specific actions: it rotates its gripper, moves to designated positions, picks up a drawer, pulls it open, and picks up two tomatoes from a table, placing each onto a plate. After each action, the code checks if the task is completed and prints a message indicating the status. 

Finally, the environment is shut down properly after the task execution. The function is executed when the script is run as the main program.
Similarity: {'ok': False, 'reason': 'LLM JSON parsing failed.'}
Differences: 1. **Purpose**: 
   - **TASK** describes a specific instruction for a robot to follow, detailing the actions to be taken in a step-by-step manner.
   - **CODE_FUNC** outlines a function that implements a simulation of the task, including setup, execution, and cleanup.

2. **Structure**: 
   - **TASK** is presented in a natural language format, making it easy for humans to understand the intended actions.
   - **CODE_FUNC** is structured as a programming function, which includes code syntax and logic for execution.

3. **Detail Level**: 
   - **TASK** provides a high-level overview of the actions without delving into the specifics of implementation.
   - **CODE_FUNC** includes detailed steps and checks for the robot's actions, including initialization and status messages.

4. **Execution Context**: 
   - **TASK** is a directive that can be interpreted and executed by a robot or a system.
   - **CODE_FUNC** is a piece of code that must be run in a programming environment to perform the task.

5. **Components**: 
   - **TASK** focuses on the actions (e.g., sliding open a drawer, tossing tomatoes) without specifying how these actions are to be executed.
   - **CODE_FUNC** includes specific programming constructs (e.g., function definitions, loops, condition checks) that dictate how the actions are performed programmatically.

6. **Output**: 
   - **TASK** does not specify any output or feedback mechanism.
   - **CODE_FUNC** includes print statements to indicate the status of the task after each action.

7. **Environment Setup**: 
   - **TASK** assumes an environment where the actions can be performed but does not detail how to set it up.
   - **CODE_FUNC** explicitly initializes the environment and prepares it for the task execution.

8. **Error Handling**: 
   - **TASK** does not address error handling or contingencies.
   - **CODE_FUNC** may include checks to determine if the task is completed successfully or if any issues arise during execution.

9. **Finalization**: 
   - **TASK** does not mention any cleanup or finalization steps after the actions are completed.
   - **CODE_FUNC** includes a shutdown procedure to properly close the environment after the task execution.

10. **Language**: 
    - **TASK** uses natural language, making it accessible to a broader audience.
    - **CODE_FUNC** uses programming language syntax, which requires knowledge of coding to understand and modify.

In summary, the semantic differences between TASK and CODE_FUNC are significant, as they serve different purposes and are structured differently for their respective contexts.

Refined Code Generated:
-------------------
import numpy as np
from pyrep.objects.shape import Shape
from pyrep.objects.proximity_sensor import ProximitySensor

from env import setup_environment, shutdown_environment
from skill_code import *
from video import init_video_writers, recording_step, recording_get_observation
from object_positions import get_object_positions

def run_skeleton_task():
    '''Generic skeleton for running any task in your simulation.'''
    print("===== Starting Skeleton Task =====")
    
    # === Environment Setup ===
    env, task = setup_environment()
    try:
        # Reset the task to its initial state
        _, obs = task.reset()

        # (Optional) Initialize video writers for capturing your simulation
        init_video_writers(obs)

        # Wrap the task steps for recording (if needed)
        original_step = task.step
        task.step = recording_step(original_step)
        original_get_obs = task.get_observation
        task.get_observation = recording_get_observation(original_get_obs)

        # === Retrieve Object Positions ===
        positions = get_object_positions()

        # Define object positions
        tomato1_pos = positions['tomato1']
        tomato2_pos = positions['tomato2']
        plate_pos = positions['plate']
        bottom_anchor_pos = positions['bottom_anchor_pos']

        # === Execute the Plan ===
        # Step 1: Rotate the gripper to ninety degrees
        obs, reward, done = rotate(env, task, target_quat=np.array([0, 0, 1, 0]), 
                                   max_steps=100, threshold=0.05, timeout=10.0)
        if done:
            print("[Task] Task ended after rotating!")
            return

        # Step 2: Move to the side position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=positions['side-pos-bottom'], 
                                 max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to side position!")
            return

        # Step 3: Move to the anchor position of the bottom drawer
        obs, reward, done = move(env, task, target_pos=bottom_anchor_pos, 
                                 max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after moving to anchor position!")
            return

        # Step 4: Pick the bottom drawer
        obs, reward, done = pick_drawer(env, task, gripper='gripper', d='bottom', 
                                         p=bottom_anchor_pos)
        if done:
            print("[Task] Task ended after picking the drawer!")
            return

        # Step 5: Pull the bottom drawer open
        obs, reward, done = pull(env, task, pull_distance=0.1, pull_axis='x', 
                                 max_steps=100, threshold=0.01, timeout=10.0)
        if done:
            print("[Task] Task ended after pulling the drawer!")
            return

        # Step 6: Pick the first tomato from the table
        obs, reward, done = pick(env, task, target_pos=tomato1_pos, 
                                 approach_distance=0.15, max_steps=100, 
                                 threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato1!")
            return

        # Step 7: Place the first tomato onto the plate
        obs, reward, done = place(env, task, target_pos=plate_pos, 
                                  approach_distance=0.15, max_steps=100, 
                                  threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after placing tomato1!")
            return

        # Step 8: Pick the second tomato from the table
        obs, reward, done = pick(env, task, target_pos=tomato2_pos, 
                                 approach_distance=0.15, max_steps=100, 
                                 threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task ended after picking tomato2!")
            return

        # Step 9: Place the second tomato onto the plate
        obs, reward, done = place(env, task, target_pos=plate_pos, 
                                  approach_distance=0.15, max_steps=100, 
                                  threshold=0.01, approach_axis='z', timeout=10.0)
        if done:
            print("[Task] Task completed successfully! Reward:", reward)
        else:
            print("[Task] Task not completed yet (done=False).")

    finally:
        # Always ensure the environment is properly shutdown
        shutdown_environment(env)

    print("===== End of Skeleton Task =====")

if __name__ == "__main__":
    run_skeleton_task()
-------------------

