3.2.29 · D5Orbital Mechanics & Astrodynamics

Question bank — Gauss's method for Lambert's problem

1,753 words8 min readBack to topic

Before we start, a symbol pantry so no symbol below is unearned:

The two pictures the whole method rests on — the swept sector versus the flat triangle, and the guess-and-correct loop:

Figure — Gauss's method for Lambert's problem
Figure — Gauss's method for Lambert's problem

True or false — justify

The orbit connecting and in a given time is unique.
False as stated — only unique once you also fix the "short way vs long way" branch and the number of full revolutions; geometry + alone leave a directional ambiguity.
If the transfer is nearly flat (small ), the ratio is close to .
True — a thin sector and its triangle enclose almost the same area, so sector/triangle ; this is exactly why the iteration starts at .
The chord between and depends on which orbit connects them.
False is pure geometry of the two points; it is fixed before any orbit is chosen.
enters the constant linearly.
False — it enters as , echoing Kepler's third law (time-squared scaling); treating it linearly gives a wrong and nonsense .
Gauss's two equations are redundant — either one would do.
False — one links geometry to the auxiliary variable, the other links time to it via Kepler's equation; the true orbit is where both hold at once, so you need both.
The auxiliary variable can never be negative.
False — for hyperbolic or fast transfers the "eccentric anomaly" analogue makes (as in the worked example where ); the series is still valid there.
Gauss's method works equally well for a transfer as for a one.
False — as , , so and blow up and the iteration fails; near-antipodal transfers need Battin/Izzo instead.
Once converges, you still have to solve Kepler's equation separately for the velocities.
False — the Lagrange f and g functions give in closed form from ; that is the whole point of using .

Spot the error

" gives the transfer angle, done."
The error: only returns , so it cannot distinguish the short way from the long way ( vs ); you must use the orbit-normal / prograde flag to pick the branch.
"Since carries the time and is bigger, I'll double to double ."
Wrong: , so doubling quadruples , not doubles it.
" is the ratio of triangle area to sector area."
Reversed — it is sector ÷ triangle; the curved sector is the bigger region, so for elliptic short transfers.
"I'll start the iteration at to be safe."
A poor seed: makes diverge (division by zero) and there is no physical zero-area sector; the correct, contraction-friendly seed is .
"For I keep the same signs of and ."
Error: goes negative past , flipping the signs inside and ; you must track that sign, not assume it stays positive.
"The Lagrange coefficient , so if I still get finite from ."
Error: at , and , so the division is singular — the two points coincide directionally and the problem is degenerate.
" (semi-latus rectum) can be read straight off the geometry without ever iterating."
Wrong: the formula contains , which is only known after converges; geometry alone under-determines because it fixes the shape but not the energy/time.

Why questions

Why compare the sector to the triangle rather than to the full ellipse?
The triangle is computable from the given data alone (), giving a fixed known reference; the sector is the unknown swept area, so their ratio isolates exactly the one thing the time-of-flight constrains.
Why does Kepler's second law appear at all in Gauss's derivation?
Kepler's second law says equal areas are swept in equal times (, with the steady area-rate), which is what converts a time input into an area condition — the bridge between the clock and the geometry.
Why is the iteration a fast contraction for typical transfers?
For ordinary short-way arcs sits very near and the update map's slope there is well below in magnitude, so each step shrinks the error by a large factor — 3–5 steps reach .
Why express in a form divided by a length cubed?
That is Kepler's-third-law scaling (period size); packaging time this way makes dimensionless and puts the whole time dependence into one number.
Why do we use the Lagrange f and g functions to get velocities instead of re-solving the orbit?
Because is a linear relation, so inverting it recovers algebraically — no second pass through Kepler's equation.
Why does the series have those specific fractions ?
They come from term-by-term expansion of the elliptic sector-area integral in powers of ; each fraction is the next coefficient in that convergent series, valid because stays small.
Why is Gauss's method the engine behind a Porkchop plot?
A porkchop plot sweeps thousands of departure/arrival date pairs, and each pair is one Lambert solve; a fast, few-iteration method like Gauss makes scanning that whole grid cheap.

Edge cases

What happens to and as ?
Both diverge because sits in their denominators; the method loses accuracy and fails to converge, so switch to a Universal variable formulation solver.
What does exactly correspond to physically?
The sector area equals the triangle area — a degenerate flat (straight-line) transfer where the swept region collapses onto the triangle; real ellipses give slightly above .
What if and point in exactly the same direction ()?
The chord and vanish, , and the "orbit" is undetermined — the endpoints are radially aligned, a degenerate case Gauss's formulas cannot resolve.
What if the two radii are equal, ?
Perfectly fine — the geometry constant simplifies () and the method runs normally; equal radii just mean a symmetric transfer, not a singularity.
What if the required is very large (multiple revolutions)?
Basic Gauss assumes a single arc; multi-revolution transfers introduce extra solution branches, and the single-branch iteration will not find them — you must handle each revolution count separately, as Izzo Lambert solver does.
How does the method behave for a hyperbolic (very fast) transfer?
The eccentric-anomaly analogue and turn negative, but the series still converges for small , so Gauss can handle mildly hyperbolic cases; strongly hyperbolic ones favour the Universal variable formulation.
What if your first-iteration comes out negative, as in the worked example?
That is normal and not an error — it simply means is small or the arc bends the "other way"; keep iterating and still settles (there it converged near ).

Recall Quick self-check
  • Which two things must be fixed before the connecting orbit is unique? ::: The transfer direction (short/long way) and the revolution count.
  • Where does Gauss's method break, and what replaces it? ::: Near ; use Battin's method or Izzo Lambert solver.
  • What single physical law converts the time input into an area condition? ::: Kepler's second law.