## Tabs

### Law of Sines: Google Cardboard

Earlier this week I created my next Google Cardboard activity with Law of Sines.  I taught law of sines earlier in the year and this was a good way to get students engaged with just a few days left of school.

Here is the worksheet: https://goo.gl/1BY83U

I wanted to take pictures, but my phone was being used during the lesson.

The basic concept is that students are given a distance from the Eiffel Tower.  Then they have to find the angle of measure to the top.  The next thing they have to do is move around (I said 5-6 spaces), but could be moved around further or put in a different location.  They then have to find the angle the second time.  Using the law of sines they can find their new distance to the Eiffel Tower.

They proceed through the activity with a partner and switching half-way.  The math is more difficult than the first Google Cardboard activity I created, because students in order to find the other angle, must use some critical thinking and know that the angle you are measuring is the outside of the triangle you are looking for.

Here is the first example sketched out:

1. Did the students use the photo on this page or did you provide one from google earth?

1. They had to use the Google Cardboard to figure out the angles at two different locations.

2. This looks pretty cool. I have two questions. What files did you use? How did they measure the angles within Google Cardboard?

1. Inside Google Cardboard there is an introduction to where you can see a few famous places. I wanted students to go to the same places so we used that as a reference.

To measure the angles the first year we used a protractor and a piece of string to measure the elevation of the tilt of the iPads. The following years we have been using the compass app in the students phone next to the device to find the angle.

2. Ahhhh. I was picturing this being done with the actual cardboard goggles. Makes more sense now. Thanks!

3. That would be an interesting way.... you got me thinking.

3. This comment has been removed by the author.