2: There was a bad guy speeding away from a robbery and the hero had to catch up to him. Were would they meet?
3: There is a bad guy going to crash into a bank and the hero has to diverge the car that the villans are driving. Now the only way they can diverge them is by T-boning them 2 meters away from the bank. The challenging is to start the car at the right moment to crash into the villains at the right time.
So these are the set-ups and each group got to pick the senerio they wanted and had to use any one of the three methods we had have been learning to predict were each car would meet. That was the only clues that were given by the director (Mr. B).
The scenario my group went with was the one were the two cars were coming right at eachother and we had to find the place to put the camera to see the crash. The first thing my group had to find was the speed that each car was going. To do this, we took a meter stick and timed how long each car took to go one meter. This posed some challenges for us, this is because we weren't sure how exact we had to be when placing our "camera". As a result, we timed each car about 4 times each and instead of using the average, (I know, what were we thinking), we went with the median of the speeds. Later, we found out that the camera was represented by a sticky note.
Next, was how we found out were to place the camera. Our group initially started out by breaking into two smaller groups and each of us ran down different ideas. My partner and I decided to with high tech., a graphing calculator. That way is would tell us were the cars would crash at the nearest thousandth. However, what looks to be good in theory doesn't always work out in real life. That showed up here because when we tried to get graph the two equations they intersected at .2 seconds. Now that didn't make any sense because neither car was going 5 meters/second. In retrospect, we forgot about the y intercept of 4 meters on the second car and made each car start at the origin. After repeatly trying to fix that method we gave up and decided to go into the next method. It consisted of using math.
When we started this method, we originally put each equation equal to eachother. This was because if the two cars were going to crash into eachother, that meant that each of their positions were the same. I remembered this fact because we had done something like this in Algebra last year. However, when we did this, we used the "Rate times time equals distance" formula, and even though we had two variables it was still seemed impossible for us to figure it out. Looking back at this problem we should have used the "y=mx+b" equations, that would have given us the answer. Altough hiensight is always a witch like that. Another thing I learned was that I do not work well under pressure. I know this because I now have all of the correct equations after thinking about it for a while, but when we only had one hour to figure everything out, I was not thinking straight.
For an explanation of scenario 3, this blog helped http://ittakesphysics.blogspot.com/
Next was the day we came back from break. Now, decided to give us yet another lab to do . My group deciced to creisen this one "The Car Acceleration Lab". In this lab we had to find the relationship of a high tech. low resistance match box car and its velocity initally, our group would of had to use a marker and a metronome. With the marker we had to mark where the car was after each tick of the metronome. We did however, learn from one of our ealier mistakes that we should measure from the back of the car instead of the front of it. It still didn't help us with keep up with the car, though. That's when Mr. B brought out a tickertape. A tickertape is a device that uses a marker on a wheel to mark on a piece of tape were something is if the tape is being pulled along with it. We did however, run into the problem of how to apply this new ability to the car. We solved this issue by putting the tickertape on a perch right next to the car with one person holding onto the tape, this was to present tagling. After that, we then let the car ride down the slope and repeated this step a total of 5 times.
After getting good data we had to interpret it. The issue that we ran into was the fact that we had to try and find speed without a set amount of time, or so we thought. It wasn't until I had remembered a conversation that we had with the whole class I remembered it doesn't matter what unit you us as long as it was consistant. Therefore, we used each tick as a unit of time, but this caused another problem. This one was that we had to find the relationship of time to velocity and not velocity over time, we also had to count each dot fast and there was over 200 of them. Thefore, we got around each of these issues by counting 15 dots and measured the distance inbetween that grouping, that way we could see the distance traveled, which would give us speed, over a set amount of time. We did however, forgot to count each grouping in an accumulative manner. That caused us to have a really messed up set of data. That is however, all the time we had. We would actually talk about our findings next week as a class, that was going to be interesting. At the end of the day, Mr. B. decided to give us a packet. Note: the speed seemed to increase as the car went down the ramp.
On Friday, we checked the packet (apparently, the one student found the answers online) and everything went fine, except, I learned I have got to watch what units I use on my axises. Little did I know that I had to learn that lesson fast. That is because the packet was really our study guide to the "celebration" we were about to have, it consisted of over 20 problems. You see a celebration is Mr. B's word for test and the fairwell to a chapter.
On the actual test I knew the material quite well (or so I thought) because I finished within the first 10 minutes, but of course I had to check my answers. That was when I discovered I still had issues with motion maps and average velocity. You see, the whole test was set up like a prevous worksheet we had, on it we were given one representation of data and had to create the 3 other ones. The reason I feel that I messed up on the motion maps was because of the counting of the dots. You see, I still hadn't gotten the two concepts of the first dot is 0 seconds and you count each dot and not the arrows. I had issues with this on the review too. I hadn't realized that if a trend stops at 4 seconds then I needed 5 dots, 4 with arrows going in one direction and the last one with a changed direction. I had to use the method of talking to myself in order to get something remotely accutrate. Then the issue with the average velocity was the fact that I had gotten 0 for the velocity and the object was moving, so it didn't make any sense. However, some of my guesses could be right, we will see.
Goal for next week: Stop dominating in my small group