Carl's initial explorations of representing the sensors focused on literal
mappings, but that strategy did not work as he progressed to more
sensors. Comments like "I want the buzzer to be the light" led to oneto-
one mappings. His first attempts made use of statements like note
sensora 5, which would play a note of varying pitch corresponding to the
amount of light sensed. This directly mapped input to output, without
any adjustments in-between. These strategies had to be modified when
he moved to using the motor command, which is binary. Carl expected
the motor to work the same way, but was disappointed to discover that
there are two motor commands, motor-on and motor-off, rather than the
opportunity to set the power of the motor. I explained to him that the
motor is "binary" - that it can only turn on or off (much like the switcha
and switchb commands). Thus he would have to try another method
to use it. This led him back to our first exercise, in which we used a
threshold to have the distance sensor tell him when an object was close.