This page serves to plan the agenda for the session, then logs the finalized minutes, as well as information necessary for final summary, upon the completion.
START A BIT > Learning Packages > LP2402: 4 Weeks Package with Wire Game 2G > This page
Unexpected incident happened in this starting session, we didn't manage to access the classroom... So then we made a temporary decision to have a group gathering and social activity in a café near by, a nice meeting though!
Nice meeting each other after the new year! And it's so good all participants are back, with good energy, no one missed!
Not able to access the classroom due to the new year holiday maintenance was still on.
We had a reflection that it's a good idea to develop some prepared group activities as plan B, in case we had any risks of changes or incidents like this in the future.
Nothing to note, because we all spent own money at the café.
Group discussion and sharing at the café, interesting ideas and social, some little hints of the new learning package contents and goals.
Nothing as planned in the original agenda happened.
10:00-10:15: Prepare, check-in discussions -> latecomers could miss this without big lose
Check in and prepare
10': Free play, everyone should try at least 1 time of the wire game here, try, feel and experience, find out what is fun, what is disappointing, what can be improved? Ask 1-2 students to share their findings
5': The tutor communicates the purpose and target of this new Learning Package, as well as the schedule.
10:15-10:35: Reflection of wire game project
10': Short reflection on the wire game project last time, the tutor reminds the key knowledge points, while sharing the programming.
How do you detect the touching? (from the physical wire touching, to the programming, digital signals)
How do you count the touching times? (variable numeric type)
10': New knowledge input: Boolean type variable https://makecode.microbit.org/courses/csintro/booleans
10:35-10:50: Reflection of wire game project
15': Wire game 2G requirement discussion
10:50-11:05: Fika break and social
11:05-11:50: Group programming to create a prototype
Open trial for this first time, plan to have each student hosting the programming for 10-15', all others look at the big screen and help out.
Goal is to have an invert-mode working in the device, only 3 requirements
Should be able to change to invert-mode, and can change back, we use button to change mode for now, so to simplify the random changing implementation
In invert-mode, the inverted game mode should be correctly activated
The classic-mode should correctly keep the normal rule
Step-by-step idea, perhaps each student can take one step:
1. let's consider invert-mode, isn't it just a inverted digital signal value? so, please bravely copy-paste the original part of "detecting, counting warning", just change it to be digital signal read as 0
2. Now, get an if-else block, we should fill in if invert-mode, then use the copy-paste bunch, if not, then it's classic-mode, we use the original bunch
3. Now, we need to have a way to know what mode we are in, we recommend to use a variable boolean type to remember this, so we create a new variable as boolean, remember to initialse it in on-start, then we can use this in the if-else condition
4. Now, we want to have a way to change mode, for now, we use button A press to activate classic-mode, and button B for invert-mode, add something displaying in LED to indicate the mode
Now, it seems already done, isn't it? Let's download our program and test, feel what is still to be improved?
If it works fine, we can come back to the code, and remind
the redundancy, prepare for the next session for function concept
if still have time, let's take a further challenge: how to let it change the mode automatically after a random time?