On Monday/Tuesday students did an interactive QR code museum tour. Essentially, students used iPads to scan QR codes posted around the lab, which would take them to a different type of technology museums currently use. For example, the teams remixed famous works of art with AI, digitally colored in famous paintings, used the MET time machine to see artifacts from different regions and periods in history,  explored the Smithsonian 3D exhibits, built digital puzzles of famous pieces of art, and used augmented reality to bring coloring pages to life. We wanted students to understand that artists and museums are embracing technology to make their art immersive, interactive, and more accesible than ever to the public.

On Thursday/Friday the team did a team building activity called Hats Off! For this activity, the team had to work together to get everyone to put on the same hat. The catch, was they could not use their hands!

As well, on Thursday/Friday the students began to work on robot game strategy by identifying the following for each of the 15 missions: location, how easy or hard it is to navigate to the mission, how the mission is activated, and how many points the mission is worth.

The teams also did a programming block review.

On Saturday, each subteam chose their robot design and communicated with their larger team to ensure there were at least two different robot designs per team. Subteams then either built their robot or began to code their first mission.

This was a short week for both Chicken LEGO and Flying Capybara 3000. Both Monday/Tuesday and Saturday were used for subteams to complete building their robots and to begin to code their first couple of missions. Before subteams begin to program their mission they first do the pseudocode for their mission. The pseudocode is where they write, in normal english, the steps needed for their robot the complete their mission. The pseudocode should make coding the robot easier. As well, coaches highlighted that when solving a mission, subteams should focus on two things:

1. Solving the mission with the attachment the robot currently has.

2. Navigating from home to the mission and back to home.

This way, students can first make modifications to their attachment if neccesary to ensure the robot can solve the mission and then add in the blocks to get to the mission and back to home.

This week the team learned about visual effects as part of their research for the innovation project. The team did a core value activity to ensure they are practicing and implementing the FIRST core values. As well, the team finalized robots and started to solve missions.

On Saturday, Chicken LEGO had a very productive robot game day. Most subteams have solved at least one mission while a few subteams already have two missions solved. Flying Capybara 3000 started their practice with the marble run activity and went on to robot game. Due to absences this team is behind on the robot game. Only one subteam has successfully  solved one mission. Most subteams are still working on their first mission or finalizing the attachment they need to solve their first mission. 

This week the teams learned about sound engineers as part of their research for their innovation project. The teams also worked on their team identity. They used LEGOS to build something which represented them. They modified their team names and team logos. Lastly, the teams continued to work on robot game.

The teams are also beginning to form their team identity for the regional. Chicken LEGO and Flying Capybara  3000 have each been divided into two teams. The teams first used LEGO pieces to together build something which represented them as a team. Next, the teams took their larger team name and modified it slightly to differentiate each team. Lastly, the teams made modifications to the logos.

Lastly, on Saturday both Chicken LEGO and Flying Capybara 3000 spent the practice on robot game. Almost all subteams have at least one mission solved and we have a couple of subteams that are already working on their third mission. The subteams have yet to put these missions into an organized strategy but we are pleased with their progress thus far.