Orbital elements: Difference between revisions

Content added Content deleted
(various rephrasing + changing 'l' to 'L' in order to avoid confusion with 1)
(rephrasing)
Line 7: Line 7:
<big> '''<tt>L</tt>''' </big>, <big> '''e''' </big> and <big> '''angle''' </big> are respectively called ''semi-latus rectum'', ''eccentricity'' and ''true anomaly''. The eccentricity and the true anomaly are two of the six so-called [[wp:orbital elements|orbital elements]] often used to specify an orbit and the position of a point on this orbit.
<big> '''<tt>L</tt>''' </big>, <big> '''e''' </big> and <big> '''angle''' </big> are respectively called ''semi-latus rectum'', ''eccentricity'' and ''true anomaly''. The eccentricity and the true anomaly are two of the six so-called [[wp:orbital elements|orbital elements]] often used to specify an orbit and the position of a point on this orbit.


The four other parameters are the ''semi-major axis'', the ''longitude of the ascending node'', the ''inclination'' and the ''argument of periapsis''.
The four other parameters are the ''semi-major axis'', the ''longitude of the ascending node'', the ''inclination'' and the ''argument of periapsis''. An other parameter, called the ''gravitational parameter'', along with dynamical considerations described further, also allows for the determination of the speed of the orbiting object.


The semi-major axis is half the distance between [[wp:perihelion and aphelion|perihelion and aphelion]]. It is often noted <big> '''a'''</big>, and it's not too hard to see how it's related to the semi-latus-rectum:
The semi-major axis is half the distance between [[wp:perihelion and aphelion|perihelion and aphelion]]. It is often noted <big> '''a'''</big>, and it's not too hard to see how it's related to the semi-latus-rectum:
Line 14: Line 14:


The longitude of the ascending node, the inclination and the argument of the periapsis specify the orientation of the orbiting plane with respect to a reference plane defined with three arbitrarily chosen reference distant stars.
The longitude of the ascending node, the inclination and the argument of the periapsis specify the orientation of the orbiting plane with respect to a reference plane defined with three arbitrarily chosen reference distant stars.

The gravitational parameter is the coefficent GM in Newton's gravitational force. It is sometimes noted <tt>µ</tt> and will be chosen as one here for the sake of simplicity:

<big> µ = GM = 1 </big>


Those six parameters, along with dynamical considerations explained below, allow for the determination of both the position and the speed of the orbiting object in [[wp:cartesian coordinates|cartesian coordinates]], those two vectors constituting the so-called [[wp:orbital state vectors|orbital state vectors]].
Those six parameters, along with dynamical considerations explained below, allow for the determination of both the position and the speed of the orbiting object in [[wp:cartesian coordinates|cartesian coordinates]], those two vectors constituting the so-called [[wp:orbital state vectors|orbital state vectors]].


The aforementioned dynamical considerations imply the so-called [[wp:vis-viva equation|vis-viva equation]]:
As mentioned, dynamical considerations allows for the determination of the speed. They result in the so-called [[wp:vis-viva equation|vis-viva equation]]:


<big>v<sup>2</sup> = GM(2/r - 1/a)</big>
<big>v<sup>2</sup> = GM(2/r - 1/a)</big>


This only gives the magnitude of the speed. The direction is easily determined since it's tangent to the conic.
<tt>GM</tt> is the gravitational parameter sometimes noted <tt>µ</tt>. It will be chosen as one here for the sake of simplicity:

<big> µ = GM = 1 </big>


The purpose of this task is to show how to perform this conversion from orbital elements to orbital state vectors in your programming language.
The purpose of this task is to show how to perform this conversion from orbital elements to orbital state vectors in your programming language.


TODO: pick an example from a reputable source, and bring the algorithm description onto this site. (Restating those pages in concise a fashion comprehensible to the coders and readers of this site will be a good exercise.)
TODO: pick an example from a reputable source, and bring the algorithm description onto this site. (Restating those pages in concise a fashion comprehensible to the coders and readers of this site will be a good exercise.)