https://www.youtube.com/watch?v=waP0_dCD6VU

The link is a test run.

Sam and Jelissa : programmers/testers

Aidan: recorder/ documenter

Aisha and Abby: problem solvers.

Our task was to solve the hypotenuse and direct our robot on the lines of a right angled triangle with the measurements of 2.3 meters and 1.8 meters and 2.92 meters (the hypotenuse that we found). Once tasked we were able to do this….

During the presentation to the class we ended up being tied with about three other bots out of six. We were in the middle of the pack. Our robot was right on, on the first line. Then on the second line we were about 5 centimeters away from the line and we ended 5 centimeters short. Finally on the hypotenuse, we were almost right on the dot where we started.

To accomplish the task we had to start with problem solving, we solved the value for the hypotenuse.

we decided on using the lengths on the bottom left triangle and we put it into the programming for dash. We went forward 100 cm then forward 100 cm then we turned right and went 100 cm then 40 cm and then turned right and went forward 100 cm.

Formula: A2+B2=C2

Aisha and Abby were the problem solvers. The first thing we did was made the 90 degree angle. The angles that created that degree were 1.80 meters and 2.30 meters. Once we did that, we needed to figure out what the what length the hypotenuse was. We squared 1.80 meters and got 3.24 meters. Then we squared 2.30 meters and got 5.29 meters. We added both of the numbers together and ended up with 8.53 meters. After we found the square root of that, the hypotenuse ended up being 2.92 meters.

Jelissa and Sam worked on the programming with dash. We worked together to try and program dash to go around the triangle with our measurements but ended up realizing that wasn’t going to work and had to use guesswork and variables while dealing with dash.

It was challenging dealing with dash he decides when not being told what to do he wanders and does whatever making it hard to decide how and when to start a test when you can't really angle him.

During programming we found out that their was no way to get the exact measurements, we could only go by 15’s but the angles weren’t all 15’s. When we tried to make the bot go back to the starting point it wouldn’t go back because the angle was in between 0 and 15. The bot had to end on either side of the starting point.

The link is a test run.

Sam and Jelissa : programmers/testers

Aidan: recorder/ documenter

Aisha and Abby: problem solvers.

Our task was to solve the hypotenuse and direct our robot on the lines of a right angled triangle with the measurements of 2.3 meters and 1.8 meters and 2.92 meters (the hypotenuse that we found). Once tasked we were able to do this….

During the presentation to the class we ended up being tied with about three other bots out of six. We were in the middle of the pack. Our robot was right on, on the first line. Then on the second line we were about 5 centimeters away from the line and we ended 5 centimeters short. Finally on the hypotenuse, we were almost right on the dot where we started.

To accomplish the task we had to start with problem solving, we solved the value for the hypotenuse.

we decided on using the lengths on the bottom left triangle and we put it into the programming for dash. We went forward 100 cm then forward 100 cm then we turned right and went 100 cm then 40 cm and then turned right and went forward 100 cm.

Formula: A2+B2=C2

Aisha and Abby were the problem solvers. The first thing we did was made the 90 degree angle. The angles that created that degree were 1.80 meters and 2.30 meters. Once we did that, we needed to figure out what the what length the hypotenuse was. We squared 1.80 meters and got 3.24 meters. Then we squared 2.30 meters and got 5.29 meters. We added both of the numbers together and ended up with 8.53 meters. After we found the square root of that, the hypotenuse ended up being 2.92 meters.

Jelissa and Sam worked on the programming with dash. We worked together to try and program dash to go around the triangle with our measurements but ended up realizing that wasn’t going to work and had to use guesswork and variables while dealing with dash.

It was challenging dealing with dash he decides when not being told what to do he wanders and does whatever making it hard to decide how and when to start a test when you can't really angle him.

During programming we found out that their was no way to get the exact measurements, we could only go by 15’s but the angles weren’t all 15’s. When we tried to make the bot go back to the starting point it wouldn’t go back because the angle was in between 0 and 15. The bot had to end on either side of the starting point.

In these pictures you see Dash in the top pictures, the bottom left picture is the triangle and measurements we had to program our robot for, and the bottom right picture is the programming we used for the triangle.