3.5.4 · D2Complex Numbers

Visual walkthrough — Modulus - z - and argument arg(z)

1,787 words8 min readBack to topic

Step 1 — Draw the plane and place the number

WHAT: we mark the point for a concrete number, say , so (right) and (up).

WHY: before we can talk about "how far" or "which way", we need a place. Every later idea is read straight off this dot.

PICTURE: the blue dot sits 3 units right, 2 units up. The two dashed guide-lines are and — remember them, they become the legs of a triangle in the next step.

Figure — Modulus  - z -  and argument arg(z)
  • ::: the horizontal offset (real part), read on the horizontal axis
  • ::: the vertical offset (imaginary part), read on the vertical axis

Step 2 — Grow the arrow, then measure its length

WHAT: we complete a right triangle. The bottom leg is (horizontal), the side leg is (vertical), and the arrow itself is the hypotenuse (the slanted longest side).

WHY Pythagoras and not something else? We want the straight-line distance from to the dot. Whenever a right angle sits between two known legs, the tool that turns those legs into the slanted distance is Pythagoras' theorem — that is exactly its job. No angle is needed, only the two legs.

PICTURE: the yellow hypotenuse is the arrow; the little square marks the corner that licenses Pythagoras. For : .

Figure — Modulus  - z -  and argument arg(z)

Step 3 — Now ask "which direction?" — the angle appears

WHAT: we mark the angle between the positive real axis (our "east", the zero direction) and the arrow.

WHY a turn, and why anticlockwise? "How far" (Step 2) does not tell you where. Two arrows can both be length yet point to totally different spots. The turn pins down the where. Anticlockwise-from-east is a fixed convention so everyone measures the same angle for the same arrow.

PICTURE: the green wedge is the angle , opening from the horizontal axis up to the arrow. Notice the same right triangle from Step 2 is still here — we are about to read the angle off that triangle.

Figure — Modulus  - z -  and argument arg(z)

Step 4 — Read the angle off the triangle: why sin, cos, tan

WHAT: on the right triangle with angle at the origin, we name the sides relative to :

  • the leg next to (along the axis) has length — call it the adjacent;
  • the leg across from (vertical) has length — the opposite;
  • the arrow (hypotenuse) has length .

WHY these three ratios? Each answers a different question:

  • measures how much of the arrow's length points east (adjacent ÷ hypotenuse).
  • measures how much points up (opposite ÷ hypotenuse).
  • measures pure steepness, up ÷ across — independent of length .

PICTURE: each ratio is highlighted on the same triangle so you see which two sides it compares.

Figure — Modulus  - z -  and argument arg(z)

Step 5 — Why alone is NOT enough (the trap)

WHAT: we draw two arrows — and . They point opposite ways yet share .

WHY it fails: repeats every ( radians). The button can therefore only ever hand back an angle in — the right-hand half of the plane. Anything on the left () comes back wrong by exactly .

PICTURE: two arrows, one blue (QI) one red (QIII), pointing dead opposite — but the naive formula returns the same angle for both. The signs of are the missing witnesses.

Figure — Modulus  - z -  and argument arg(z)

Step 6 — The full fix: every quadrant with its own picture

WHAT & WHY per quadrant (drawn all four, one panel each):

Quadrant signs direction of arrow reason
I up-right already measured from +axis
II up-left angle is obtuse, past the top
III down-left below axis ⇒ negative turn
IV down-right below axis, short of +axis

PICTURE: four arrows, one in each quadrant, each labelled with how is bent into the true argument. Read them like a clock: QI small positive, QII large positive, QIII/QIV negative.

Figure — Modulus  - z -  and argument arg(z)

Step 7 — The degenerate & edge cases

WHAT (each read straight off an arrow):

  • → arrow points east: , .
  • → arrow points west: (the endpoint of the allowed range, so ).
  • → arrow points north: .
  • → arrow points south: .
  • no arrow at all: and is undefined — a point has no direction.

WHY they matter: these are exactly where "compute " chokes (dividing by zero when ). The picture never chokes — you just look at where the arrow points.

PICTURE: the four axis arrows plus the lonely dot at the origin with no direction.

Figure — Modulus  - z -  and argument arg(z)

The one-picture summary

Everything collapses into a single arrow and its right triangle: length from Pythagoras, turn from the side ratios, quadrant fixed by the signs of and .

Figure — Modulus  - z -  and argument arg(z)

Recall Feynman retelling (say it to a 12-year-old)

Stand in the middle of a field and drop a treasure somewhere. How far is it? Draw the straight line to it — that's the arrow, and its length is Pythagoras on your "steps east" and "steps north" (). Which way is it? Face east, then turn anticlockwise until you point at the treasure — that turn is the argument. The shape of the little right triangle already whispers the angle (tall-thin = steep, wide-flat = shallow), and the side ratios cos/sin/tan read the whisper out loud. One warning: tan can't tell front from back — an arrow and its exact opposite look identical to it. So always peek at the signs of east and north to know which quarter of the field you're in, and bend the acute reference angle into place. On the axes, just look where the arrow points; at dead centre there's no arrow, so there's no direction to name.


Recall

comes from which theorem, and why that one?
Pythagoras — it turns the two right-angle legs into the hypotenuse (arrow length) .
Why do we need and (or the signs) and not just ?
repeats every , so it can't tell an arrow from its opposite; the signs of fix the quadrant.
of the negative real axis ()?
, since the principal range includes but not .
Why is undefined?
There is no arrow (length 0), so there is no direction to measure.
Convert QII arrow with reference angle to its argument.
.