Brain DeCoded with CodeX - Mission 5, Objective 3: Neural Rhythms
Neural Rhythms
Students build a program where neurons take turns firing, then hear and see the rhythm that comes out of neurons inhibiting each other.
Overview
Objective 2 was about how fast one signal travels. This objective is about what happens when several neurons coordinate. When neurons take turns firing, and each one holds the others back while it goes, the result is a rhythm, and rhythm is what walking, breathing, and chewing all run on.
Students build neural_rhythms, which puts that rhythm on the CodeX in two ways at once. The display animates neurons passing a signal back and forth, and the speaker plays a beat in time with it. Because action potential speed depends on diameter, the work from Objective 2 is what sets how fast the rhythm runs.
This objective makes noise. Plan for that before you start.
🎯 Project Goal: Students add code to a program that simulates the rhythm of neurons firing signals.
Learning Targets
- I can explain how motor neurons create a rhythm.
- I can list factors that determine the speed of the rhythm.
Key Concepts
- Coordinated motor neurons take turns firing signals, which creates a rhythm.
- Action potential speed, influenced by neuron diameter, affects rhythm.
Assessment Opportunities
- Exit ticket: give an example of an activity that requires coordinated motor neurons that would create a rhythm.
- Turn in the Activity Guide.
- Complete the program neural_rhythms.
Success Criteria
- Complete the CodeTrek steps
- Program runs correctly without errors
- Activity Guide is completed
Digital Resources
Classroom Materials
- ▸CodeX device and USB cable, one per student
- ▸Laptop/computer with Chrome browser
- ▸Optional: headphones, for the CodeX headphone jack below the speaker
Extensions & Cross-Curricular
dly variable where it changes inside drum_beat().
🔤
Vocabulary
▾
🐍
New Python Code
▾
📐
Standards
▾
Computer Science
- Decide your sound plan before class. Thirty CodeX speakers playing a beat at once is a lot, so know whether you are letting the room run loud, asking for headphones, or working in shifts.
- Run the program yourself first. Knowing what the finished rhythm sounds like and looks like on the display makes it obvious when a student's version is off.
- Decide how students get the Activity Guide. You can print a copy for each student or assign it digitally. They record results in it, so hand it out before they start.
- Have a rhythm example ready for the warm-up. Walking, breathing, and chewing all work, and students give better exit tickets after hearing one modeled.
-
If you plan to offer the code adjustment extension, look at where
dlychanges insidedrum_beat()ahead of time so you can point students at it quickly.
- The program uses the built-in CodeX speaker. If the room gets too noisy, you can suggest students use headphones. The CodeX also has a headphone jack just below the speaker.
- Students should follow the instructions on the Activity Guide and record their results.
- The display animation and the sound are two views of the same thing. Students who cannot hear the pattern can usually see it, which is useful for anyone working in a quiet corner or with headphones off.
- Inhibition is the idea worth slowing down on. Neurons create a rhythm by holding each other back, not by speeding each other up, and that is the part students tend to reverse.
- Extensions and cross-curricular projects are included to enhance the concepts in the objective. You can use the extensions to extend students' learning.
Lesson Outline
Find the rhythm students are already running on.
- Ask: "Name something your body does over and over in a steady beat without you thinking about it."
- Ask: "If your muscles all fired at the same instant instead of taking turns, what would walking look like?"
Set up inhibition before students see it in code.
- Introduce the rhythm generator circuit: neurons that take turns by inhibiting each other.
- Ask two students to model it. One "fires" while holding the other back, then they swap. Repeat until it settles into a beat.
- Connect it to Objective 2. Faster action potentials, from wider neurons, mean a faster rhythm.
- Hand out or assign the Activity Guide.
Students build neural_rhythms and run the simulation.
- Students work through the CodeTrek steps, adding code to neural_rhythms.
-
They set up the sound with
soundmaker.get_tone()andset_pitch(), so the beat plays in time with the animation on the display. - Students run the program, watch the signal move between the neurons, and listen for the beat.
- Students record their results on the Activity Guide as they go.
- Students who finish early take the adjustment extension: resize the rectangles or the signal circle, change the pixels per step, or change the delay.
Short investigation to connect speed back to the biology.
- Have students change the delay and describe what happens to the rhythm.
- Ask which real factor that delay stands in for, and steer them back to action potential speed and neuron diameter.
- Ask what kind of movement would need a fast rhythm, and what would need a slow one.
Close on coordination.
- Exit ticket: each student names an activity that needs coordinated motor neurons and would create a rhythm.
- Read a few out loud and sort them by speed, from slow and steady to fast and repeating.
- Collect the Activity Guides. Preview Objective 4, which moves from rhythm to reflexes and the central pattern generator.