Navigation in the Re-imagined Series: Difference between revisions

From Battlestar Wiki, the free, open content Battlestar Galactica encyclopedia and episode guide
(→‎FTL jump calculations: this was fine. Point of origin redirects to Stargate. Fixing an older screwup)
Line 86: Line 86:
==FTL jump calculations==
==FTL jump calculations==


Based on deduction from information gleaned in "[[Scattered]]", a set of jump coordinates could either be given in [[Wikipedia:Cartesian coordinate system|cartesian]] or [[w:Spherical coordinate system|spherical]] coordinates to specify a point in three-dimensional space.  
Based on deduction from information gleaned in "[[Scattered]]", a set of jump coordinates could either be given in [[w:Cartesian coordinate system|cartesian]] or [[w:Spherical coordinate system|spherical]] coordinates to specify a point in three-dimensional space.  


A possible algorithm for jump calculations would therefore necessitate first and foremost the determination of the exact location of the ship, relative to its intended point of arrival after the jump. This is done by identifying, fixing and triangulating several stars <ref name="tighquote"/>. Next, the ship's position relative to the intended point of arrival would be [[Wikipedia:Point plotting|plotted]] on a three-dimensional coordinate system|Cartesian coordinate system, using the ship as its [[Wikipedia:point of origin]], i.e. (0/0/0).
A possible algorithm for jump calculations would therefore necessitate first and foremost the determination of the exact location of the ship, relative to its intended point of arrival after the jump. This is done by identifying, fixing and triangulating several stars <ref name="tighquote"/>. Next, the ship's position relative to the intended point of arrival would be [[w:Point plotting|plotted]] on a three-dimensional coordinate system, using the ship as its [[w:Origin (mathematics)|point of origin]], i.e. (0/0/0).


Then, the positions of any known stellar bodies and other obstacles would have to be plotted on that coordinate system as well, in order to establish where to jump and where ''not'' to jump.
Then, the positions of any known stellar bodies and other obstacles would have to be plotted on that coordinate system as well, in order to establish where to jump and where ''not'' to jump.

Revision as of 19:33, 18 September 2007

An article from


In the Re-imagined Series, the principles of spaceflight are taken seriously, in that all ships have a logical a process to move in all three axes of movement, and travel at reasonable speeds with methods that don't necessarily duplicate the fantasy flight principles seen in space fantasy, such as Star Wars.

Reaction Control Systems[edit]

In addition to their sublight engines used for interplanetary travel within a solar system, all ships have a centralized way to move the ship to port or starboard, and to yaw and rotate the ship. This requires the use of an RCS, a reaction control system[1].

The reaction control system is designed to provide a spacecraft with guidance and steering. It has two main functions:

  • Delivering small amounts of thrust in any desired direction or combination of directions
  • Providing torque to allow control of rotation (pitch, yaw, and roll).

Reaction control systems are typically used for:

  • Attitude control during entry into an atmosphere until such time as conventional aerodynamic surfaces can be used
  • Station keeping in orbit
  • Close maneuvering and/or docking
  • Orientation control (pointing the nose of the vehicle).

All Colonial vessels utilize RCS for maneuvering and station keeping, although the scale of the systems varies widely.

  • Vipers, Raptors and all smaller craft use "cold" RCS systems, most likely utilizing either an inert gas or possibly a high specific-impulse hypergolic fuel mixture
  • Very large vessels such as battlestars use strategically-mounted sets of very large fuel-burning thrusters, relying on the brute force of such systems to overcome inertia during maneuvers.

Like many other technologies, Cylon attitude control for small craft like Raiders is similar or even identical to the Colonials (Scar).

Basestars don't appear to have any RCS features. This may be an inherent design, as its Raiders and missile systems can be deployed in a 360-degree arc--that is, the basestar can deploy its offensive elements from any direction of the ship.

While basestars have no visible RCS, orientation can be achieved through other means. For examples, reaction wheels use a spinning mass on a spacecraft axis to control attitude. By spinning the reaction wheel in one direction, torque is generated and the spacecraft will rotate in the opposite direction, in accordance with Newton's laws of motion. This system is used on real space platforms, such as the Hubble Space Telescope. However, such systems generate relatively small amounts of torque and they tend to be used in situations where precise orientation takes priority over the need to change orientation rapidly.

Basestars however, have a sublight propulsion system in addition to FTL drives. Basestars can be seen approaching the algae planet in the episode "The Eye of Jupiter". This capability can also be inferred from episodes like "The Captain's Hand" where a basestar is said to be retreating. Its nature however is unknown, as like with the RCS system, no engines are visible on the vessels.


Distances and speeds in the Miniseries[edit]

  • Galactica was approximately 335,540,340 miles from one of the Colonies, ostensibly Caprica, at the start of the Miniseries.

To reach this number, clues are taken from Billy Keikeya, on Colonial Heavy 798, enroute to the battlestar for its decommissioning ceremony. Keikeya tells Laura Roslin that he had sent a copy of her ceremony speech to President Adar for review, but warns that there is a time delay of 30 minutes between Galactica and Adar's actual location, which is confirmed as Caprica City, the seat of the Colonial Government [2].

The speed of light is 186,282 miles per second. If President Adar sent a wireless message from Caprica to Galactica in an attempt to correct Roslin's speech, how long would it take the message to get there? Keikeya gives this answer: 30 minutes. This makes it possible to determine the distance using the equation: d = s(t) (or, distance=speed x time)

(3 x 10^8 m/s) (the speed of light) x 1800 s (30 minutes * 60 seconds/minute) = 5.4 x 10^11 meters or 335, 500, 000 miles

Simplified, the wireless message travels over 335.5 million miles in 30 minutes to Galactica. This is approximately 3.5 astronomical units, or three times the distance between Earth and our sun.

  • Colonial Heavy 798 is traveling at a sublight speed of over 61,000,000 miles per hour to get to Galactica for the decommissioning ceremony.

Right after Billy Keikeya's conversation with Laura Roslin on her speech, the captain of Colonial Heavy 798 speaks on the public address intercom of the starliner, telling the passengers how long their trip to Galactica will take: 5.5 hours. Assuming that the starliner has just left the neighboring space of Caprica and has reached its cruising speed, and given that we know Galactica's distance from Caprica, we can determine Colonial Heavy 798's cruising speed with the same formula as above, now adjusted to calculate speed:

5.4 x 10^11 meters (the distance in meters) / 19800 (5.5 hours x 3600 seconds/hour) =
2.7 x 10^7 meters/sec, or 61, 000, 000 MPH

While Colonial Heavy 798 is moving very fast across space at 61,000,000 miles per hour on its sublight engines, this is only approximately 11 percent of the speed of light, so passenger liners do well in getting from place to place, or colony to colony. To give a real-world comparison, Colonial Heavy 798 could fly from our sun to Earth in about 90 minutes. The light from the sun takes only 8 minutes to arrive on the Earth's surface.

Given the velocities involved, extremely high accelerations must be used to attain them in reasonable (usable) time frames involved for in-system transportation. Such G forces would kill any humans involved unless some means of dampening them were employed. Given that the technology to perform "space-folding"[3] FTL jumps is also available, the technology to manipulate gravity would lie in the same area.

  • Colonial Heavy 798 and it's passengers would lose about 1 minute and 19 seconds during their trip to Caprica (relative to the time observed on Caprica), if they had completed their trip as planned, due to time dilation.
T = T0 / sqrt(1 - v^2/c^2)
  • T0 = 5.5 hours. (as observed by Colonial Heavy 798)
  • d = 335,540,340 miles.
  • v = d/T (as observed by Caprica)
  • c = 670,616,624.4 mph
  • T = 5.52 hours. (1:19 longer observed on Caprica)

Of course, this assumes that Colonial Heavy 798 took the same path to Caprica that its transmission would take. This isn't likely, for various reasons, so the distance is probably off a little.

Alternate calculations for distances and speeds in the Miniseries[edit]

This is an alternative to the above which assumes a thirty light minute distance. A time lag [4] or delay , in the case of a communication signal is both ways. A thirty minute time lag in communication implies that the signal would take fifteen minutes to travel between the two creating a total lag of thirty minutes. In short: It takes thirty minutes for person one to send a message and get a reply back. This would alter the calculations made to the following.

-Galactica's distance from Caprica would be: 167,500,000 miles

(3 x 10^8 m/s) (the speed of light) x 1800 s (15 minutes * 60 seconds/minute) = 2.7 x 10^11 meters or 167,500,000 miles

-The speed of Colonial Heavy 798 would be 305057.07 mph

2.7x 10^11 meters (the distance in meters) / 19800 (5.5 hours x 3600 seconds/hour) = 13,636,363.64 meters/sec, or 305057.07 mph

-This makes the same assumptions as to the route of Colonial Heavy 798 as the initial proposal.


FTL jump calculations[edit]

Based on deduction from information gleaned in "Scattered", a set of jump coordinates could either be given in cartesian or spherical coordinates to specify a point in three-dimensional space.

A possible algorithm for jump calculations would therefore necessitate first and foremost the determination of the exact location of the ship, relative to its intended point of arrival after the jump. This is done by identifying, fixing and triangulating several stars [5]. Next, the ship's position relative to the intended point of arrival would be plotted on a three-dimensional coordinate system, using the ship as its point of origin, i.e. (0/0/0).

Then, the positions of any known stellar bodies and other obstacles would have to be plotted on that coordinate system as well, in order to establish where to jump and where not to jump.

Finally, the point of arrival would likewise be plotted. The hard part in making a single jump over long distances, like to Ragnar in the Miniseries, would therefore lie not so much in getting the jump drive to manipulate space properly, as in correctly figuring out where possible obstacles, such as stars, black hole or planetary bodies are located and then adjusting the direction of the jump accordingly, so as to land the ship in a clear volume of space.

Astrometrics[edit]

Main article: Astrometrics

Galactica has an astrometrics lab with optical and x-ray telescopes, that is used to acquire fixes on surrounding stars, which are then used in FTL jump calculations.

Triangulating the Colonies' "Actual Location"[edit]

Lagoon Nebula

In "Home, Part II", the Lagoon Nebula appears in a holographic map in the constellation of Scorpio[6] in the Tomb of Athena.

Galactica's location and the rough location of the Twelve Colonies of Kobol can be deduced with simple logic:

Possible locations

The nebula is shown from the same vantage point as it would appear to an observer on Earth, yet the characters are able to recognize it. This suggests that the Colonies are on a line of sight "behind" Earth's solar system. Otherwise, the nebula would appear in a different shape and size as it is not a symmetrical object.

If one were to follow a straight line from the Lagoon Nebula to Earth, continuing the line through space would place Galactica, and likely the Colonies, somewhere in the Cygnus Arm of the Milky Way galaxy.

To calculate the approximate distance between the Colonies and Earth, using the map to the left, one must first get the distance between the Lagoon Nebula and Earth, 4,100 light-years. One must then determine the distance between the point labeled 'Earth' and the point labeled 'Lagoon Nebula.' Then, one must use this scale and measure the distance between the Colonies and Earth. Then convert it to light years. The approximate distance using this method is 10,250 light-years.


What happened in "Scattered"?[edit]

Schematic Diagram showing the three different sets of jump coordinates

In "Scattered", Galactica and the Fleet execute FTL jumps according to different sets of coordinates. As a consequence, Galactica has to jump back along its original jump vector, to the former point of origin of the two jumps, re-acquire new starfixes and calculate the Fleet's current position.

At first glance, this seems counter-intuitive. Since presumably both sets of jump coordinates are known to Galactica, a simple triangulation of the two jump vectors would produce an alternative third set of jump-coordinates which would allow Galactica to jump to the Fleet directly. A possible explanation is as follows:

The emergency jump coordinates given to the civilian fleet aren't just an older set of correct coordinates. According to Colonel Tigh, in a conversation with his wife, jump calculations need to be regularly updated to compensate for stellar drift and the movement of the ships themselves. Lieutenant Gaeta was supposed to send the updated jump plots to the other ships but forgot to. [5] As a result, the Fleet jumped with a set of coordinates that didn't fit the local space-time conditions. The concept of a blind jump is introduced in the episode "Pegasus". While jumping with a wrong sets of coordinates probably isn't as risky as jumping with no calculations at all, the destination would still be unpredictable.

Galactica has the coordinates that the civilian ships used to make their jumps, but not their actual position. However, in a process that is largely unexplained, Galactica is then able to calculate their real location from the Fleet's emergency jump coordinates, as well as the newly acquired starfixes. This unusual procedure can also explain the abnormally long duration (several hours) of the calculations on the initially un-networked computers, compared to the relatively short amount of time jump calculations usually take.

References[edit]

  1. In the movie, Apollo 13, the Apollo command/service module's reaction control jets are violently activating to control the spacecraft after the famous oxygen tank explosion, which creates an uncontrolled jet for which the RCS tries to compensate.
  2. President Adar's office on Caprica is confirmed in the second Season episode, "Epiphanies". Reinforcing this information, Roslin speaks by wireless to "Jack", a fellow secretary or government official. Jack tells Roslin of the devastation near his location and Adar's speculated whereabouts and actions. Given that wireless transmission ranges in real-time conversation would limit Roslin to be able to speak only with Caprica (the nearest colony), Jack must be on Caprica, and likely in Caprica City to give him any ability to discuss the president's whereabouts.
  3. This nature of the jump technology is confirmed in the Miniseries podcast
  4. time lag defintion on wikipedia (backup available on Archive.org) (in English).
  5. 5.0 5.1 Tigh: "Every watch we update our emergency jump calculations with new star fixes to compensate for inertial drift, and then we transmit them to the rest of the Fleet. This time ours were updated, but theirs weren't. Gaeta was supposed to transmit them to the rest of the Fleet." (Scattered)
  6. In the show, the nebula is placed in the wrong constellation. On Earth, the nebula actually appears in the constellation Sagittarius. The production team has acknowledged this as an error.