PageSourceSearch

https://quazikb.github.io/orbits/index.html

html quazikb.github.io collected 2026-10-03 09:48:33 UTC 5,725 bytes, 98 lines download raw bytes

1<html>
2<head>
3	<link rel="stylesheet" type="text/css" href="../index.css">
4	<META name="keywords" content="2 body,two body,orbital,mechanics, lagrange points, L1,L2,L3,L4,L5,gravitation,elements"> 
5	<title>Orbital Mechanics</title>
6		<style>
7			body { margin: 0; }
8			canvas { width: 100%; height: 100% }
9		</style>
10<script type="text/x-mathjax-config">
11  MathJax.Hub.Queue(function () {	
12  // Hide MathJax until rendered by putting them in divs of the class "hide_math"
13	var mathdivs = document.getElementsByClassName("hide_math");
14	for (i = 0; i < mathdivs.length; i++) { 
15		mathdivs[i].style.visibility = "";
16	}	
17  });
18</script>
vendor: 1 bytes, line 18
18
19<script 
20   src='https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/MathJax.js?config=TeX-MML-AM_CHTML'>
21</script>
vendor: 1 bytes, line 21
21
22<script src="../js/QZMath.js"></script>
vendor: 1 bytes, line 22
22
23<script src="../js/three.js"></script>
vendor: 1 bytes, line 23
23
24<script src="../js/OrbitControls.js"></script>
24	
25</head>
26<body>
27<div id="wrap">
28
29<h1>Orbital Mechanics</h1>
30<br>
31Orbital mechanics for simplified problems (two massive bodies) are pretty straightforward. However, I've found a lack of good visualizations to play around with so I made this page. Usually the 2-body problem is brought up as the canonical problem in orbital mechanics. This is for good reason, as it's the only type of system that can be easily analyzed. Even though the 2 body problem is simple, it is useful for a large number of real world applications with more bodies if certain assumptions are made, e.g. patched conics. Although all objects with gravity influence each other, the effect of bodies orders of magnitude more massive, or orders of magnitude closer strongly overpowers the effect of smaller and/or further bodies. This can be observed in how the moon and satellites clearly orbit the earth, the earth orbits the sun, and the sun orbits the center of the galaxy. While the sun influences a satellite around earth through gravity, generally it's effect is hard to observe from a reference frame moving with the earth. This is somewhat of an oversimplification, but demonstrates how we intuitively visualize simple orbits as a hierarchy of many separate 2-body problems.
32<br>
33<br>
34In general, when thinking of orbits we tend to picture one object orbiting the other more massive object, just like a satellite around the earth. However this is not true, the earth is also orbiting the satellite! To be more precise, when two objects are in orbit, they both orbit around their center of mass. It only seems like the satellite is orbiting the earth because the earth is so much more massive. The center of mass of the satellite-earth pair is just extremely close to the center of the earth since the earth's mass is so much larger. If two objects of similar mass orbit each other it actually looks a lot more interesting:
35<br>
36<br>
37<div id="cent_text">
38	<div class="slidecontainer"  class="slidecontainer">
39	<br>
40	  <input type="range" min="0" max="99" value="80" class="slider" id="eslider" onchange="eslider.oninput()">
41	  <div id="eslider_txt"  class="slidecontainer">
42	  </div>
43	</div>
44	<div class="slidecontainer"  class="slidecontainer">
45		<br>
46	  <input type="range" min="0" max="100" value="50" class="slider" id="m1slider" onchange="m1slider.oninput()">
47	  <div id="m1slider_txt"  class="slidecontainer">
48	  </div>
49	</div>
50	<div class="slidecontainer">
51		<br>
52	  <input type="range" min="1" max="100" value="80" class="slider" id="hslider" onchange="hslider.oninput()">
53	  <div id="hslider_txt"  class="slidecontainer">
54	  </div>
55	</div>
56	<br>
57	Frame of Reference :
58	<br>
59	<br>
60	<form  class="slidecontainer">
61  <input type="radio" name="bodyfocus" value="CG" checked> CG
62  <input type="radio" name="bodyfocus" value="m1"> m<sub>1</sub>
63  <input type="radio" name="bodyfocus" value="m2"> m<sub>2</sub>  
64	</form> 
65</div>
66<script src="js/twobody.js"></script>
66
67<br>
68<div id="cent_text">
69<i><b>figure 1</b> : 2 bodies of orbiting each other with variable properties.</i>
70</div>
71<br>
72Another point that usually conflicts with our intuition is that orbits are rarely circular. We tend to see diagrams of the planets orbiting the sun and note how circular the orbits look, however in reality the orbits usually have some <i>eccentricity</i>. This means they're elliptic, or in extreme cases hyperbolic. In general orbits can take on the form of any <i>conic section</i>, dependent on the degree of eccentricity. They're usually referred to as trajectories in cases where the "orbital" path is open (has an infinitely long period) such as a parabolic or hyperbolic "orbit".
73<div class="hide_math" style="visibility:hidden">
74	<p>
75	\begin{align}
76	e & = 0 \rightarrow \text{circular orbit}\\
77	0< e & <1 \rightarrow \text{elliptic orbit}\\
78	e & =1 \rightarrow \text{parabolic trajectory}\\
79	e & >1 \rightarrow \text{hyperbolic trajectory}\\
80	\end{align}
81	</p>
82</div>
83Orbits in the solar system are themselves slightly elliptic, nature isn't always as perfect as it seems. In general when working with orbits, we center the problem around one of the bodies rather than what is shown in <b>figure 1</b> where they orbit around the center of mass. <b>figure 1</b> shows what a pair of orbiting bodies look like from an inertial frame of reference, however when working through the math most derivations and problems opt to center on one of the bodies. This doesn't change too much, except that one of the bodies will then be at the "focus" of the path geometry, and the other will be the sole object moving around around. The center of mass itself then seems to orbit around the "fixed" body.
84	<br>
85	<br>
86	<hr>
87<h2>Site Navigation</h2>
88<a href="../index.html">Homepage</a>
89	<br>
90	<br>
91	<hr>
92<div id="copyright_text">
93&copy; 2018 Kevin Bergamin.
94</div>
95</div>
96
97</BODY>
98</HTML>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.