Case context: You are building a self-driving car pipeline. The car detection and pedestrian detection components output bounding boxes. The path planning component takes these bounding boxes and plans a trajectory. You want to informally debug the path planning component by comparing it to human-level performance. Your colleague proposes showing a human driver the raw front-facing camera videos to see if they would plan a better path.

Question: Based on the principles of informal pipeline debugging, explain why your colleague's proposal is flawed and how you should structure the human comparison instead.

Sample answer: My colleague's proposal is flawed because it allows the human driver to see raw camera videos. This gives the human access to rich visual features that the path planning component does not receive, such as road boundaries or un-detected obstacles. To structure the comparison correctly, the human should be given only the outputs of the car and pedestrian detection components (the bounding boxes/locations) and asked to plan a path using only that restricted information. This measures how well the planning component performs relative to a human given the same inputs.

Key points:

• Identifies that raw camera video provides extra information not available to the path planner.
• Explains that the human must plan a path using only the outputs from the detection components.
• States that the goal is to compare the component's performance to a human given identical inputs.

Rubric: Learners must identify that showing raw video provides the human with more information than the component receives. They must specify that the correct setup involves providing the human only with the outputs from the detection components.