This model is applicable to a single point particle moving in one dimension either because it's constrained to move that way or because only one Cartesian component is considered. The force, or component of force along this direction, must be constant in time. The Force can be positive (e.g. a rocket) or negative (e.g. gravity). Note: Multi-dimensional motion can often be broken into components, as for the case of projectile motion. where there constant acceleration along one axis. The constnt acceleration model can be used describe the system's motion in any situation where the net force on the system is constant (a point particle subject only to near-earth [gravitation] is a common example). It is a subclass of the One-Dimensional Motion (General) model defined by the constraint da/dt = 0 (i.e. a(t)=constant).
The problem will often explicitly state that the acceleration is constant, or else will indicate this by giving some quantitative information that implies constant acceleration (e.g. a linear plot of velocity versus time). The model is also sometimes useful (in conjunction with Point Particle Dynamics) in dynamics problems when it is clear that the net force is constant in magnitude - in fact if one axis lies along the net force, the perpendicular axes will have no acceleration and hence will exhibit motion with constant velocity.
A single point particle, or a system such as a rigid body or many bodies that is treated as a point particle with position specified by the center of mass. (The c of m involves the MOMENTUM MODEL.)
Error: The XML content could not be parsed. There is a problem at line 5, column 1. Parser message: Unexpected '<' in attribute value
at [row,col {unknown-source}]: [5,1]
- Position as a Function of Time
From the formulas given in the Laws of Change, it is clear that a plot of position vs. time will give a parabola.
If the acceleration is positive the parabola will open upwards. The position at t = ti will be xi , as shown in the graph below (time at the origin is ti ):
In this case the position is positive. The fact that the plot of position vs. time is increased means that the initial velocity, vi , is also positive.
If the acceleration and the initial position xi were the same, but the initial velocity was negative , then the graph of position vs. time would look like this:
The parabola has a minimum value at the time tmin
Unknown macro: {latex} \begin
Unknown macro: {large} [
Unknown macro: {rm t} _
Unknown macro: {rm min}
=
_
Unknown macro: {rm i}
- \frac{{\rm v}_{\rm 1}}
Unknown macro: {rm a}
] \end
This information is intended to familiarize the reader with the shape of the curve and how it behaves. Obviously, if the object starts out at time t = ti its real motion will not be described by the portion of the curve for t < ti, and so an object moving with positive initial velocity and positive acceleration will not have such a "minimum" position - it will move in the same direction, with increasing speed, for all t > ti .
A plot of velocity vs. time for this case looks like this. The position of the intercept with the time axis is tmin :
On the other hand, an object with negative initial velocity vi and positive acceleration will encounter a "minimum" position, at which it will have zero velocity. After slowing to zero it will reverse direction and gather speed with increasing time. (Note that the slope of the graph is the same as in the above case, which is what you expect, since it is determined only by the value of the acceleration.) The intercept of zero velocity occurs, again, at tmin = ti- vi/a. Since vi < 0, the intercept is to the right of ti.
The plots for the case of negative acceleration (a < 0) are similar, only the parabola opens downward in that case.
Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null
Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null
Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null
Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null