This page is the toolbox. Before you can read Lambert's problem or the parent Gauss's method note, you need every symbol below. We build each from nothing: plain words → a picture → why the topic needs it. Do not skip; every later symbol leans on an earlier one.
The central body sits at a special point called the focus. Every orbit we discuss has the central body at one focus of its ellipse — that is Kepler's first law, and we simply take it as given here.
The picture: look at figure s01. The orange dot is the focus. Two magenta arrows, r1 and r2, reach out to two positions of the spacecraft — an earlier one and a later one.
Why the topic needs it: Lambert's problem is stated in terms of these two arrows. They are the known data. Everything else is squeezed out of them.
The symbol ν (Greek "nu") is the true anomaly — the angle of the spacecraft measured around its orbit. So Δν (the change in true anomaly) and θ are the same thing: the swept angle.
The picture: in figure s01 the violet wedge between the two magenta arrows is θ.
Why the topic needs it:θ tells you how "spread out" the two points are around the central body. A tiny θ means they are almost in line; a large θ means the spacecraft went most of the way round.
We know the two arrows, but not yet the angle between them. The tool that extracts an angle from two arrows is the dot product.
The cos (cosine) here is the cosine function: for an angle, it is a number between −1 and +1 that says how much two arrows "agree" in direction. cos0∘=1 (same direction), cos90∘=0 (perpendicular), cos180∘=−1 (opposite).
Draw a straight line directly connecting the two spacecraft positions. That straight segment is the chord c.
The picture: figure s02. The focus, tip of r1, and tip of r2 form a triangle. The two arrows are two sides; the chord c is the third side (the orange straight line).
Why we need c: it is a pure-geometry summary of "how far apart the two endpoints are." The chord appears in every serious Lambert solver.
Why the topic needs the triangle: it is the flat stand-in for the curved region the planet actually sweeps. Gauss compares the curved region to this flat one.
The planet does not travel along the straight chord. It travels along the curved orbit. So the region it truly sweeps out is bounded by the two arrows and the curve — a "pie slice." That is the elliptic sector.
The picture: figure s03. The violet region is the true elliptic sector (bounded by the curved orbit). The magenta dashed region is the flat triangle (bounded by the chord). The sector is always a little fatter than the triangle because the curve bulges outward.
Why we need both: Gauss's whole trick is one number,
y≡area of trianglearea of sector.
When the orbit barely bends (small θ), the curve is almost the chord, sector ≈ triangle, so y≈1. That is the sensible first guess the algorithm starts from.
Here h is the specific angular momentum — a fixed number for a given orbit measuring how fast area is swept. It relates to orbit shape through h=μp (both symbols defined next).
Why we need it: the shape of an orbit and the speed along it both depend on how hard the central body pulls. In canonical units the parent note sets μ=1 to keep the arithmetic clean.
Where it enters: inside the time constant m∝μΔt2 — bigger gravity pulls the planet round faster, so it changes the time budget.
Why we need it: once Gauss's iteration lands on the right geometry, p is the number we extract, and from p come the Lagrange f and g functions that hand back the velocities. It is the "answer knob" of the whole method.
The true anomaly ν from section 2 is the real, physical angle. But solving the timing cleanly needs a different bookkeeping angle, the eccentric anomaly E — the angle you'd measure if you stretched the ellipse into a circle. It appears in Kepler's equation, the equation that links angle to time on an orbit.
The picture: back in figure s03, a bigger bend of the curve = a bigger x = a fatter sector = a bigger y. They rise together.
These two are just pre-computed numbers built from the data, so the iteration doesn't recompute them each loop.
Notice cos(θ/2) in both denominators. When θ→180∘ (the two points nearly opposite the focus), θ/2→90∘ and cos(θ/2)→0 — so ℓ and m blow up to infinity. This is exactly where Gauss's method fails, and why near-antipodal transfers need the Universal variable formulation or the Izzo Lambert solver instead.