Sensing and Conditions

Active learning works because sensing and conditions demand real-time observation and adjustment. Students see their code’s logic become visible when sprites react—or fail to react—based on clear rules. This hands-on cycle of making, testing, and refining builds both understanding and confidence in conditional logic.

• Year 5
• Computing
• 4 activities
• 20 min–45 min

Learning Objectives

1. Explain how sensor inputs, such as mouse position or color detection, act as triggers for conditional code execution.
2. Analyze the relationship between a specific physical input (e.g., touching a color) and the resulting digital decision made by a program.
3. Construct a program where a sprite's behavior (e.g., movement, costume change) is contingent upon sensing a particular condition.
4. Compare the outcomes of a program when different sensor conditions are met versus when they are not.
5. Identify specific instances where conditional logic based on sensor input is used in interactive applications.

Problem-Based Learning

⏱ 30 min·Pairs

Pair Programming: Mouse Chase Game

Pairs create a sprite that follows the mouse only when within 100 pixels, using 'if touching mouse-pointer?' and 'distance to mouse < 100' conditions. They add a score variable that increases on contact. Test and swap roles to debug.

Prepare & details

Explain how sensors act as the 'eyes' of a computer program.

Facilitation Tip: During Pair Programming, circulate to ensure both partners take turns coding and testing, reinforcing teamwork and shared debugging.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Problem-Based Learning

⏱ 45 min·Small Groups

Small Groups: Color Platform Jumper

Groups program a sprite to jump only when touching a blue color platform, incorporating gravity simulation with forever loops and if-else for direction. Record successes in a shared log. Present one feature to the class.

Prepare & details

Analyze the relationship between a physical input and a digital decision.

Facilitation Tip: In Color Platform Jumper, encourage groups to swap sprites and platforms to test how size and position affect touch detection.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Problem-Based Learning

⏱ 20 min·Whole Class

Whole Class: Condition Debug Relay

Display buggy code on the board; teams suggest fixes for sensing errors like wrong color detection. Vote on best solution, then implement class-wide. Discuss why conditions failed.

Prepare & details

Construct a program for a sprite to only move when it is touching a specific color.

Facilitation Tip: For Condition Debug Relay, provide identical starter code to each small group but vary the condition values so students compare solutions and explain differences.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Problem-Based Learning

⏱ 25 min·Individual

Individual: Sensor Extension Challenge

Each pupil adds two new conditions to their game, like pausing on edge touch or speeding up near mouse. Self-assess with a checklist and peer review.

Prepare & details

Explain how sensors act as the 'eyes' of a computer program.

Facilitation Tip: During Sensor Extension Challenge, ask students to annotate their code with comments that describe each condition’s purpose before they test.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Teaching This Topic

Start by demonstrating how a single if-then block changes behavior when a condition is met versus not met. Avoid explaining sensor logic in abstract terms—instead, let students experience the gap between expectation and reality through immediate testing. Research shows that debugging live code builds stronger conceptual understanding than reading about conditions alone.

What to Expect

By the end of these activities, students will consistently use if-then blocks with precise sensor conditions to control sprite behavior. They will predict outcomes, test hypotheses, and explain why a condition was or was not met during gameplay.

Watch Out for These Misconceptions

Common Misconception

During Pair Programming, watch for students who set vague proximity triggers like 'if near mouse' without defining what 'near' means in pixels.

What to Teach Instead

Guide partners to replace broad terms with concrete code, such as 'if distance to mouse < 50', then ask them to measure and adjust the value collaboratively.

Common Misconception

During Color Platform Jumper, watch for groups that assume edge contacts count as touches without testing partial overlaps.

What to Teach Instead

Have students resize sprites and platforms to see how hit detection behaves at boundaries, then adjust the 'touching color' condition’s tolerance if available.

Common Misconception

During Condition Debug Relay, watch for students who believe outputs change randomly each run, leading to unnecessary retests.

What to Teach Instead

Replay the same input sequence side-by-side with different groups to prove deterministic behavior, then discuss why identical inputs always yield identical outputs.

Assessment Ideas

Quick Check

After Pair Programming, present a modified version of the Mouse Chase code with an incorrect condition (e.g., 'if touching mouse pointer'). Ask students to predict the sprite’s behavior, then test and explain the outcome.

Exit Ticket

After Color Platform Jumper, ask students to write one specific condition their game used and the exact action it triggered, such as 'If touching color green, then jump 100 steps'.

Discussion Prompt

During Condition Debug Relay, pause the activity and ask groups to share how they adjusted their condition values to make the sprite react reliably, focusing on their reasoning for each change.

Extensions & Scaffolding

• Challenge: Add a second condition to the Mouse Chase game so the sprite only moves when the mouse is near AND a key is pressed.
• Scaffolding: Provide pre-written condition blocks with missing values (e.g., 'touching color ___') and ask students to complete and test them.
• Deeper: Introduce a variable that tracks how many times a condition is met, then display it on screen to connect conditions to data collection.

Key Vocabulary

Sensor	A component within a program that detects external information, like the position of the mouse or if a sprite is touching a specific color.
Conditional Statement	A programming structure (often an 'if-then' block) that allows a program to make decisions and execute specific code only when a certain condition is true.
Input	Information provided to a program, often from a user or a sensor, that can influence its behavior.
Trigger	An event or condition that causes a specific action or set of actions to occur within a program.