Session 9: Code & Measurement – Exploring Distances with the Robot
Session Architect: Muhammad Bilal
Duration: 50-60 minutes
Equipment Required:
- M3D Robotics kit with a scale or ruler for measuring distances.
- Laptops with Scratch pre-installed.
- Different types of surfaces (e.g., smooth, rough, slippery materials like carpet, tile, plastic).
- Paper and pencils for students to document their findings.
Learning Objectives:
- Understand the relationship between coding instructions and real-world measurements.
- Measure the distance the robot travels using different step sizes in code.
- Explore how different surfaces affect the robot’s movement.
- Develop problem-solving skills by analyzing and adjusting code based on physical measurements.
Resources:
Scratch Code for the session:
Grade 4 Session 9.sb3 (131.3 KB)
1. Introduction to Measurements and Coding (10 minutes)
Activity:
Begin by introducing the concept of measurements and how coding can be used to control real-world distances. Explain that today, the students will program their robot to move a certain distance and measure how far it goes.
Instructions:
- Start with an engaging explanation:
“We use measurements every day! When you want to know how tall you are, you measure yourself. But how do you think we can use code to make our robot move a certain distance?”
-
Show students a ruler or scale and explain how they’ll be using it to measure how far their robot moves with different step sizes.
-
Explain that the Move _ Steps block in Scratch controls how far the robot moves, and today they will measure how accurate those steps are in real life.
Teacher’s Role:
- Provide simple real-world examples of measurements (e.g., measuring height, distance, or speed).
- Explain how the robot’s movements can be measured and linked back to the code they write.
2. Measuring Movement (15 minutes)
Activity:
Students will code the robot to move specific distances using the Move _ Steps block. They will measure how far the robot actually moves and compare it to the step size they used in the code.
Instructions:
-
Guide students in writing code to move the robot forward:
- Start with Move 1 Step and have students measure the actual distance using a ruler or scale.
- Then, code the robot to Move 3 Steps, Move 5 Steps, etc.
-
Students will record the distances the robot moves for each step size and compare them.
Teacher’s Role:
- Assist students in measuring the distance traveled by the robot.
- Encourage students to observe patterns:
“Does the robot move exactly the same distance every time? What happens when you increase the steps?”
3. Experimenting with Surfaces (15 minutes)
Activity:
Students will now program the robot to move over different types of surfaces (e.g., smooth, rough, slippery) and measure how the surface affects the distance the robot moves.
Instructions:
-
Guide students to set up different surfaces for the robot to move on (e.g., a piece of carpet, tile, or plastic).
-
Have students code the robot to Move 5 Steps on each surface and measure how far it actually travels on each one.
-
Ask students to compare the results:
“Did the robot travel the same distance on the carpet as it did on the tile? If not, why do you think that is?”
Teacher’s Role:
- Help students understand how different surfaces can affect friction and the robot’s movement.
- Encourage students to think about why the robot moves differently on each surface.
4. Challenge: Programming for Accuracy (15 minutes)
Activity:
Students will now create their own challenges where the robot must navigate to a specific distance or area using their code. They will need to adjust the step size in Scratch based on what they learned about measurements and surface conditions.
Instructions:
-
Give students a target distance to reach (e.g., “Make your robot move exactly 30 cm”).
-
Students will write code to try to get the robot to move exactly that distance by using the measured value of how far the robot moves in 1 step and figuring our the number of steps through that.
-
If the robot overshoots or doesn’t go far enough, students will need to adjust their code (e.g., changing the number of steps) to correct the distance.
-
Once they master this challenge, encourage them to create their own challenges (e.g., moving a specific distance across different surfaces).
Teacher’s Role:
- Guide students as they refine their code, encouraging them to test and adjust for accuracy.
- Provide support by explaining how surface type and friction may affect their results.
5. Reflection and Wrap-Up (5-10 minutes)
Activity:
Students will reflect on what they learned about the relationship between coding and physical measurements. They will discuss how they adjusted their code to achieve the correct distance and how different surfaces affected the robot’s movement.
Reflection Questions:
- “What did you notice about how far the robot moves when you use different step sizes?”
- “Did the robot move differently on smooth surfaces compared to rough ones? If yes, what could be the reason?”
Teacher’s Role:
- Lead the reflection discussion, helping students think critically about how they used measurements and coding together.
- Celebrate their problem-solving and analytical skills, reinforcing how coding connects to the real world.
Learning Outcome:
By the end of the session, students will have a deeper understanding of how coding controls real-world measurements. They will have experimented with step sizes, surfaces, and programming challenges, learning how to adjust their code to achieve accurate results.