Why test is_at_cross() with a straight drive before using it in the line follower?
- A.Because line following cannot be tested on a cross
- B.So that if the test fails, the only thing that can be wrong is the cross check — the following code is not even in the program yet
- C.Because set_effort() is faster than arcade()
- D.It makes no difference; either order is the same
Answer Why?
What makes track_to_intersection() stop?
- A.A fixed number of loop passes
- B.is_at_cross() becoming True — both sensors see the cross
- C.The error reaching exactly zero
- D.A timer
Answer Why?
In track_to_intersection(), where is the intersection detected?
- A.In an if/else inside the loop body
- B.In the while condition — the body only steers
- C.After the loop, by checking the last error
- D.In arcade()
Answer Why?
Why does track_to_intersection() end by driving 8.75 cm rather than driving for half a second?
- A.straight() is easier to spell
- B.A distance is the same with a full or flat battery and on any floor; a time would have to be re-tuned constantly
- C.time.sleep() cannot be used with motors
- D.Because 8.75 is a magic number
Answer Why?