Wednesday, April 19, 2017

10-April-2017: Work-Kinetic Energy Theorem

Lab 11Work-Kinetic Energy Theorem

10-April-2017
Idea: Model  the relationship between work and kinetic energy using a cart-pulley system.
Summary:
EXPT 1:
1) Set up a cart, track, motion detector, force sensor, and a pulley attached to a hanging mass as shown below. Recording two separate values at the same time serves the purpose of being able to compare W done by the tension and the cart's change in KE via the Work-Energy theorem.
2) After zeroing the force censor, and leveling the track, we verify that the sensor is accurate by hanging a .5 kg mass over the pulley and confirming that the sensors read 4.9N. Then, we removed the mass and added it to our cart, which came out to 1.18 kg.
3) We then hung 50 grams off the pulley, and hit collect as we released the cart. The purpose of this is to demonstrate that the work done on the cart by the tension in the string must equal the change in kinetic energy of the cart. This gave us graphs of Force x Time, and Velocity x Time.
4) To create a comparison graph, we create new calculated columns for KE, which is found using 0.5*mass*"Velocity"^2, and we overlay it on top of our Force x Time graph. We when crop the graph by deleting past the point where Force is again equal to zero.
5) We obtain the area below the graph for Force x Time, which gives us the amount of work done. We then record this value and determine that it is equal to the value of Kinetic Energy at the same point.
6) Highlighting a larger area of the graph starting from the leftmost end, we again obtain the integral, and the value for Kinetic Energy and compare.
EXPT 2:
1) This time, I remove the pulley and string, and attach to the force sensor a spring instead.
2) I then consider a situation in which I set the position of the unstretched spring to be 0, and any subsequent pulling of the cart toward the motion sensor to be in the positive direction.
3) I then hit record, and simply pull the cart toward the motion sensor at a steady slow pace, until the string is stretched about .60 meters.
4) Thus it gives me a Force vs Position graph, which is the key to calculating the spring constant of the spring.
EXPT 3:
1) This time, I start the cart at a stretched position of .60 meters from the origin, and let go. The resulting graphs of Force vs Position, and KE vs Position would allow me to find work done by the spring and the cart's change in energy.
2) To obtain these graphs but with the data points that I'm interested in (where the cart springs back to the origin) I strike through any data points that occur once the cart goes back to its initial position.
EXPT 4:
1) Finally, we watch a video where a professor demonstrates the force of a stretching rubber band over the stretch of the rubber band. In the video, the graph it generates required multiple back-and-forth passes to obtain an average shape. Finding the area beneath this graph gives me the work done to stretch the rubber band.
2) The system is also attached to a cart, and when the rubber band is released, it passes through two photogates a given distance apart in a given period of time. Using this we can determine the kinetic energy.
3) Altogether, I then compare these two values and judge whether the work is truly equal to the change in kinetic energy.
Analysis EXPT1:
In recording the Force x Position graph, we observed that the force is more or less constant - and subsequently that the KE graph appears to peak at what appears to be a cusp of some sorts. Following our integration of the area below F vs t, and comparing it to the value of KE of the cart recorded at the same point, we observe that they are very similar, with about a 2-10% difference whether it be our first set of intervals, or its longer, second interval. Based upon this, we can reasonably ascertain that work done by the string did indeed equal the change in kinetic energy of the cart for both recorded test cases.
Graphs:
First range of Integration for Force vs Time graph overlayed with KE vs Time
Work #1 (area under curve): 0.1036 J
KE #1 (at the point): 0.105 J

Second range of Integration for Force vs Time graph overlayed with KE vs Time over a longer interval than the first.
Work #2 (area under curve): 0.237 J
KE #2 (at the point): 0.225 J
Analysis EXPT2:
Once we obtained our Force Position graph, we obtained a nice, pretty linear slope. Because the only force present accounted by the sensor would be that of the spring, we determine that F = kx. Because it is a linear graph, we can also determine that k, the spring constant, is the slope. Therefore my graph gives a spring constant of 0.7997 N/m!
Following the integration of our graph, we determine that the work done to stretch the spring about 0.6 m is .07010 J.
Graphs:
Graph of Force vs Position, wherein slope m is the spring constant k.

Graph of Force vs Position integrated beneath the line, which gives us the total work done to stretch the spring.
Analysis EXPT3:
This time instead of focusing on the slope of our new Force vs Position graph, we take the integral of the area underneath an arbitrary interval, which gives me the work done by the spring. Comparing it to the value of KE at the same starting point, it lets me see just how close the two are; at most a difference of .5%. Setting up a table let me visualize that for three different positions of the car. Therefore, because the differences in the final values of energy were so minuscule, I could safely conclude that the work done by the spring is equal to the change in kinetic energy of the cart.
Graph/Table:
Comparison of the integral of Force vs Time (work) with Kinetic Energy at the same starting point.
Values of Work and change in Kinetic Energy at various positions of the cart


Analysis EXPT4:
Watching the movie, we notice that the lines drawn by the string vary individually, but with multiple passes of the transfucer, we obtain a graph with a distinct shape. Based upon the shape of this graph we see that once the rubber band pulls the cart to its constant, maximum force, the force decreases steeply and then again stays constant, but not zero. With reference of the scale in intervals 10 Newtons and of .1 meters, we see that force increases from 0 to .26 meters, decreases from .36 to .4 meters, and force is constant at .26 to .36 meters and from .36 on. The area under the graph gives me the work done, which allows me to use the work-energy theorem for the second part of the video.

Using the next part of the video, we record the mass of the cart, the change in position through the photogate, and the time it took to cross the photogates. Because I want to find the final kinetic energy of the cart, I first find the velocity using simple kinematics, and use it to find its final Kinetic Energy.
Once I do, I demonstrate a comparison of my values for work determined using a) the Force vs Position graph and b) KE of the cart. Calculating percent error between the two gives me a surprisingly accurate 1.05%, telling me that 1) Work-Energy is obviously true, and 2) The measurements done to obtain the graph and the speeding cart were accurate to a high degree.
Graph/Calculation/Percent Error
Area under the Force vs Position graph, which gives me approximately 23.65 Joules of work.
Calculation of the cart's final KE. I use kinematics to find the velocity, and subsequently plug it into my equation for KE, giving 23.9 Joules of KE.
Calculation of percent error. As I could see, very accurate.


Conclusions
Uncertainties:
  • With regards to clear areas of uncertainty for Experiments 1-3, the most would be that we did not take into account external sources of force like static friction, in assuming that the only force the force sensors read were tension or spring force. When in reality, the energy lost to friction or a more negligible air resistance, affects our integration for work. However, the fact that there is not a very large discrepancy between the results for W or KE suggests that such forces were very very negligible.
  • Another potential for error comes from our tools, such as:
    • Balancing scale: Introduces an uncertainty in the mass up to .1 grams, affecting our KE calculated column.
    • Assuming that the spring used in the experiments was perfect, when in reality it probably had not stretched exactly to .6 m. In fact, I observed that it appeared to be within 0-1 cm, resulting in a value of the spring constant in Experiment 2 that would be slightly inaccurate.
    • Inaccuracies in the Force Sensor to about a thousandth of a Newton. Even when zeroed whilst laid flat on the surface, it would read values such as 0.002 rather frequently. Though a very small uncertainty, it nevertheless changes the result of Experiments 1-3 ever so slightly.
  • Finally, in regards to the videos in Experiment 4 as previously discussed in my analysis of this part, the graphs drawn by the transfucer were so inaccurate that the professor in the clip ran the device back and forth multiple times to achieve an approximation of what it would actually look like. Therefore, in my calculation of the area under this curve, the final work would inevitably be slightly different from what the system had actually exerted. The same could be said of the speeding cart, as limitations of the tools such as the timer would result in a calculated KE that would not exactly describe reality. However, the fact that the calculated percent error between the two was so tiny demonstrates that this particular uncertainty was not too large of an issue.

Monday, April 17, 2017

05-April-2017: Work and Power

Lab 10: Work and Power
05-April-2017
Idea: Demonstrate the work-energy theorem and power in motion by determining the change in kinetic energy and the work required to move up a certain height, by a) running up a flight of stairs and b) lifting a mass to the same height.
Summary:

1) As seen, the first thing we did was to lift a bag of varying masses in a mass-pulley system, and time how long it took for us to pull it to the top. To obtain the height of the pull, we measured the height of a single step, and multiplied it by the number of individual steps it took to reach the balcony.




























2) Then, we timed ourselves a) walking up the full length of the stairs and b) running up the same length of stairs

3) Using these, we could model the work-energy theorem and subsequently calculate the power it took to achieve these actions.

Data Analysis/Calculations:

In calculating the power it took to lift masses up a height H, I first found the height I was lifting to as previously mentioned, found the force due to gravity on each mass. From that I could find the Work it took to do this, and then by timing the entire process, find the power I'd exerted. 
Calculating this, my data would reflect this: The more work I did in a short time, the more power I output, the more work I do in a far longer time, the less power I output, i.e. as power depends entirely upon the amount of work done over time.

In calculating the work it took to walk and run up the stairs (change in kinetic energy) plus potential energy at the top of the stairs, I needed to obtain my speed, which in order to do, I assumed that the stairs took the form of a triangle with an angle 40 degrees, and second, assumed that my velocity up the stairs was constant. I then also said my starting speed was zero. Using simple kinematics, I obtained a relationship for the vertical component of my velocity using my recorded time and the sine of 40 degrees. I then used that in order to solve for my velocity V along the hypotenuse, again assumed to be the stairs. 
Finally, plugging in these values to my power equation gave me a result that I thought was very reasonable for when I walked up the stairs versus when I ran up the stairs. I expended about 61% less power when I walked up the stairs, even though I had a constant mass of 52kg.
Conclusion:
As I would expect, the faster I was able to get the same mass up the height, the more power I output. Logically, the same was true for the mass: the more mass I had to lift, the more work I did, therefore the more power I had to output. Therefore I could reasonably believe that power depended on both the work done and the time it took to do that work. Thus Power was demonstrated to be equal to the quotient of work and time.
1) In neglecting the kinetic energy in the work I did to lift the masses a height H, based on the fact that I, with a mass 52kg was able to exert 2,213 Joules of work to walk up the stairs in case 2 (WITH a Kinetic Energy and Potential Energy), I can calculate a reasonable percent error by using for the second value only my potential energy up the height H, as shown: 
2) If a microwave oven has a power consumption of 100 Watts, in order to equal this power by climbing the stairs, I would need to climb the following steps per second.

3)If I am cooking in the microwave for a total of 6 minutes, I would have to climb the total flight of steps over 6 minutes to generate enough power to run the microwave.

4) A person can put out 100 watts continuously. A water heater requires 12.5 x  10^6 joules of energy for a 10 minute shower.

This has a power of:

And if I were to gather a group of people to ride generators in order to heat the water in real time, I would require:

Lastly, if I were riding the bike myself, I would have to ride the generator for:


03-April-2017: Centripetal force with a motor

Lab 9Centripetal force with a motor
03-April-2017
Idea: Model a relationship between angular velocity, and the angle at which an object is at, once a spinning motor rotates a hanging mass attached an R distance away from the center.
Summary:
1) In this lab, we had a set up wherein a hanging mass was attached to a meter stick a distance R away from the rotating center, powered by a motor.

2) By increasing the voltage of the machine, we could get a variety of increasing values of rotational velocity.

    - Before we even turned on the machine, we recorded the height of the machine, from its base to the meterstick of length R.

    - Then we measured the radius of the extended part of the m stick.

    - Once we got the machine spinning, we timed 10 rotations, with which we could calculate angular velocity. Next, by scooting a ring stand and marking the vertical height at which the angled string is now at, we could measure its location.

3) Afterwards, we tested 5 cases at increasing power levels.




Data Analysis:
As shown above, we observe that as the power increased, the time it took for the swinging mass to complete one full rotation naturally decreased. Conversely, when we measure the new heights of the ring stand, we observe that it goes higher and higher. We know that angular velocity is the quotient of a full rotation (in radians) with the time it takes for that full rotation.
Naturally, we discover as a result that angular velocity increases with each test case.
In order to find the angle theta of the swinging mass, we set up a triangle with the length of the string as the hypotenuse, and the height of the machine minus the height given by the ring stand, and use an inverse cosine to find the angle. This shows us again, that like angular velocity, the angle theta also increases as the power is increased as shown by our data below.

Afterwards, we had to accomplish the main purpose of the lab which was to create a model that has a relationship between angle Theta and angular velocity Omega.
To do this, we set up the net forces present in both the x and y direction. In the X direction, we observe that there is a horizontal component of tension in the string, and a force due to centripetal motion. In the y direction, there is a force of the string in the vertical component and force due to gravity. Although I do not know the tension in the string, it is present in both the x and y components of force: therefore I could substitute for it in the x direction, and plug it into my forces in the y direction. Doing so gave me a function for omega in terms of varying angles of theta, which let me see that as theta increased, omega also increased nearly proportionally with it.
Data Table/Calculations:
Data set based on the 5 trials. Note that in this table, Omega was calculated using 2*pi/t
How angle Theta was derived using the height of the stand, big H, and the height of the ring stand, little h.

How Angular Velocity was calculated in terms of angle Theta. We note that the radius of the system is not merely  just the radius of the extended meter stick, but combined with the horizontal component of length of the string!
Final Analysis:
By graphing the above function, I obtain a graph that looks like the following, where Omega is in the y axis, and Theta in the x axis. Looking at the graph we can visually recognize that, in general, as theta increases, so does angular velocity, with clear exceptions to the trend thanks to the asymptotes present in tangent theta.

Comparing this to our values of Omega obtained by using our intervals of Time was a matter of plugging in our values of theta, and before doing any percent error calculations, I observed that they are relatively very close to each other. The fact that my results appear to be within a 5-10% range of each other is a good sign that my measurements were relatively sound.

Conclusion:
Following my percent error calculations, I was pleased to find that none of my percent error exceeded 6%.  From this, I could determine that the time I recorded, AND the measurements of length I took, were both accurate at least to the tenths place, which was very good.

In determining the sources of uncertainty, there were a lot to consider.

  1. For one, the spin of the machine was unreliable to a certain extent first due to the unknown fluctuations of power supply, which in turn would directly affect angular velocity, and the second, in a slight wobble in the meter stick holding the hanging mass. This would obviously affect the time it would normally take for a full rotation, and potentially the height recorded by the ring stand: measuring its height at a high point in its wobble would make the recorded height too large, and too short at a low point in a wobble. This would affect our angle Theta.
  2. Finally, apart from that, the rest were from the standard limitations of our measuring tools. The first was uncertainty in our meter sticks, to a tenth of a centimeter, which again, would affect our derivation of angle Theta. The second was in the timers we used, primarily our phones. Because we didn't use a photogate, the times we record for a full interval were naturally going to be really inaccurate. We attempted to compensate for this by averaging the time for 10 full rotations to narrow this uncertainity as best as possible, but it would still affect our angular velocity.

Monday, April 3, 2017

29-Mar-2017: Centripetal Acceleration vs Angular Frequency

Lab 8Centripetal Acceleration vs Angular Frequency
29-Mar-2017
Idea: Model and plot a relationship between Force, mass, radius, and rotational velocity by taking data from a mass on a rotating disk under various conditions.

Summary
1) As a class, we observed a spinning disk, with a mass on a string attached to its center. We recorded data at various masses, lengths of the string (radius), forces, and power settings. We did this via a force sensor attached to the mass, and a photo gate at the edge of the disk, recording the time over 10 revolutions.
2) Then, we had to organize our data in order to create three graphs, whose slopes would give me mass, radius, and m*r, because as it would turn out, our value of omega was not linear enough. In order to do this, we arranged this formula to get my graphs using Excel.


Analysis:
I began to rearrange/organize my data, so that it would fit the cases where 1) mass and the power of the machine were consistent 2) radius and power were consistent and 3) mass and radius are constant. But first, I had to calculate the average time for each individual case by subtracting the first time interval from the time at the 10th, and dividing by 10. Then, I calculated rotational velocity, which was 2*pi over the average time. In addition, for convenience' sake, I converted all of the radius measurements to centimeters. Overall, this is what I observed by organizing my table:
Case 1: As the radius increased, force clearly increased. Omega was constant until the radius of 0.343m.
Case 2: As the mass increased, the force also increased, and Omega was not consistent.
Case 3: As the power increased, the force also increased, and again Omega was not consistent.


Afterwards, I began graphing my data exactly as I described in number 2 of my summary, using each of my test cases. slopes would give me mass, radius, and m*r. Afterwards, I could compare these values to my actual data for mass, radius, and m*r. 
As I could see by comparing these results from that of the table (shown in red), none of my results strayed far from the experimental values. In fact, without yet having done the percent error calculation, most of my results appeared close to within 8%.

After actually doing the percent error calculations for each of the test cases, this was confirmed. I got percent errors of 9.3%, 2.5%, and 1.9%, respectively for each case.

Conclusion/Uncertainty:
Mass and radius were demonstrated to be directly proportional to Force, and thus angular velocity increases as Force increases, and decreases as mass or radius increases. Additionally, I was able to draw from this the notion that my data could still come out somewhat accurate by running multiple cases despite the larges sources of uncertainty. Overall, I discovered that under conditions where angular velocity is too unreliable to use as a constant, I could still somewhat compensate for the uncertainty by solving for the product of its two components, m and r, instead. 
In the end, there were some glaring sources of uncertainty, the largest of which came from the rotating disk itself.
1) First, the disk had a glaring wobble to it, which only got worse as the power was cranked up. The sheer instability definitely affected the force readings on the sensor, as the non-average force readings were all over the place in logger pro. Inaccurate force readings would subsequently hurt the accuracy of my three graphs, as I noticed various outliers within them.
2) Of course, the measurements of the radius had an uncertainty to them, possibly to within 1 cm. Just like the force readings, this too would affect my graphs, but clearly not as severely.
3) In addition, although we assumed that the power would remain constant to what we chose, the power supply naturally has slight uncertainty in its measurement over time. This had consequences to everything in my data table from the time, angular velocity, etc.

22-Mar-2017: Modeling Friction Forces

Lab 7Modeling Friction Forces
22-Mar-2017
Idea: Be able to model friction forces using a mass-pulley or external forces, and use it to predict/derive its various components.

Summary/Analysis
Part 1: Static Frictions

1) First, we hung various masses off a table with a string connected to a block via a pulley.

2)We increased its mass in increments of 10 grams until the block, also increasing in increments of 200 grams per every test case, began to slide. Thus we obtained 4 test cases wherein the block just begins to slide.

3) Using logger pro, I then plotted this data and using a line of best fit, obtained a slope that was my coefficient of static friction over the masses of my four test cases.
 Part 2: Kinetic Friction
1) I attached a calibrated force sensor to the block, and again increased the mass of the block in increments of 200 grams, and recorded the force readings from the sensor.
 2) In Logger Pro, the sensor gave me the following graph, and the line of best fit for each case would give me my forces.
 3) This time, I plotted my previously recorded Force data as well versus the weight of my block (which is the normal force) of the 4 test cases, and the slope of this graph gives the coefficient of kinetic friction.

Part 3: Static Friction From a Sloped Surface
1) I then placed the block on the surface and inclined the board until it slipped, which turned out to be at an angle of 21 degrees. I then used this to calculate the coefficient of static friction between the block and the surface.

 2) When calculated, I got a value of 0.386.

Part 4: Kinetic Friction From Sliding a Block Down An Incline
1) I repeated the same experiment as part 3, except with a motion detector to record the acceleration of the block as it slid down the incline.
2) By finding the slope of the data where it seemed best reliable, I got an acceleration of 1.466 for the block. Using this, and the known angle of the incline, I was able to calculate this coefficient of kinetic friction.

3) Compared to the value of static friction that I got in Part 3, this value of 0.223 is expectedly lower than the coefficient of static friction, which was 0.386. Therefore I believe that this value is very reasonable.

Part 5: Predicting the Acceleration of a Two-Mass System
1) Finally, I set up experiment 1's mass-pulley system but with a motion sensor to record the acceleration, with the block and a single mass of 60 grams hanging off the pulley, so that the system would start moving once I let go of the block. This slope would be my experimental result for acceleration. Logger Pro gave me a value of 0.7627 m/s/s.
2) In order to calculate the acceleration, I set up free body diagrams for the masses and solved for acceleration, and plugging my values for the block and the hanging mass gave me a calculated value of acceleration of 0.828 m/s/s.

Conclusion/Percent Error
In calculating the percent error of my yielded accelerations in Part 5, I used my calculated acceleration vs my experimental value. 0.7627 was my model value, and 0.828 was my calculated value. Using these values, I got a percent error of 8.7%.

1) Initially,  major source of uncertainty would be in the mass-pulley system itself, as the point at which the block would begin to slide were extremely inconsistent. For example, the block would slide at 180 grams, or 145 grams.
2) For Part 5, seeing as I'd gotten a percent error of 8.7%, it was not as accurate as I would have hoped, but it is reasonable considering all of the possible sources of uncertainties in this experiment.From the mass of the block, friction, etc, all of which played into calculating each component of the system.