1.1.6 · D2Measurement, Vectors & Kinematics

Visual walkthrough — Scalars vs vectors — definition, examples

2,504 words11 min readBack to topic

Step 0 — The one piece of trigonometry we will need: cosine

WHY we introduce it now. Our derivation compares a slanted arrow to a straight baseline. The single number that captures "how much this angle leans along that baseline" is the cosine. We meet it once here so it is never a surprise later.

PICTURE. A right triangle with the angle , its adjacent side and hypotenuse marked, and the three landmark values below.

Figure — Scalars vs vectors — definition, examples
Recall Why cosine can be negative

Past the direction starts leaning backward along the baseline. "Forward" was positive, so "backward" is negative. That sign is the whole engine of the minus-to-plus flip you will see in Step 5.


Step 1 — What is a vector, drawn as an arrow?

WHAT. We take our two quantities — call them and — and draw each as an arrow.

WHY. Because the whole difficulty (from the parent's walking problem) is that direction changes the answer. An arrow is the one picture that stores both size and direction at once, so it is the honest way to represent the quantity.

PICTURE. Two arrows starting from the same dot (their tails touch). The angle between them is (the Greek letter "theta", just a name for that opening angle).

Figure — Scalars vs vectors — definition, examples

Step 2 — What does "adding" two vectors even mean?

WHAT. To add, we slide without turning it, until its tail sits on the head of . Then we draw one new arrow from the tail of to the head of the moved . Its length is .

WHY. "Do , then continue with " is head-to-tail placement — you finish the first walk and start the second from there. The straight arrow home is the net effect, the resultant .

PICTURE. The head-to-tail chain forming a triangle; closes it.

Figure — Scalars vs vectors — definition, examples

Step 3 — The angle inside the triangle is NOT

WHAT. In the head-to-tail triangle, the angle at the join (where 's head meets 's tail) is , not .

WHY. When we slid to the head of , we kept it pointing the same way. But now arrives into that corner and leaves out of it. The two arrows lie along a straight-through path, so the interior corner is the supplement of the original opening angle: it fills up the rest of the straight .

PICTURE. A zoom on the corner: the original and its supplement shown together adding to a straight line.

Figure — Scalars vs vectors — definition, examples

This single fact — supplement, not — is the reason a minus appears mid-derivation and then flips back to a plus. Watch for it.


Step 4 — Why we reach for the Law of Cosines (and not Pythagoras)

WHAT. We name the pieces of our triangle to match the law:

  • side , side ,
  • side (the unknown we want),
  • angle (the interior corner from Step 3, which sits opposite ).

WHY. The formula demands the angle opposite the side you're solving for. closes the triangle, so the corner facing it — the from Step 3 — is exactly the angle to plug in.

PICTURE. The triangle relabelled with mapped onto .

Figure — Scalars vs vectors — definition, examples

Step 5 — Substitute, and turn the minus into a plus

WHAT. Put our labels into the Law of Cosines. Here still means the length :

Term by term, right where each lives:

  • ::: square of the resultant length (what we're solving for)
  • , ::: the "Pythagoras part" — what you'd get if the triangle had a right angle
  • ::: the correction, still holding the supplement angle from Step 3

WHY the next move. That is awkward — it uses the interior angle, but we want the answer in terms of the original angle between the vectors. We use the identity flagged in Step 0 to translate:

WHAT (finish). Substitute the identity:

The minus times the minus becomes a plus. Take the square root (lengths are never negative, so we keep the root), and recall :

PICTURE. The sign-flip shown as a reflection of the correction term, " meets becomes ".

Figure — Scalars vs vectors — definition, examples

That is the parent's formula — no longer stated, now earned.


Step 6 — Check every case (the formula must never surprise you)

A good formula covers all inputs. Let us feed it every angle and watch it behave. Throughout, .

Case (same direction). : The arrows stack in a line — maximum length, plain arithmetic. This is exactly why aligned vectors "act like scalars".

Case (perpendicular). : The correction dies; we fall back to pure Pythagoras. (This is Example 1's triangle in the parent.)

Case (opposite directions). : The arrows fight; the result is their differenceminimum length. If they cancel to .

Case between (e.g. ). , giving — a value smoothly between the extremes.

PICTURE. One figure showing shrinking from down to as opens from to .

Figure — Scalars vs vectors — definition, examples

The one-picture summary

Figure — Scalars vs vectors — definition, examples

Every idea on this page, stacked in one frame: two arrows tail-to-tail (), slid head-to-tail (corner ), closed by , with the law of cosines and the sign-flip turning it into , plus the min/max dial along the bottom.

Recall Feynman retelling — the whole walk in plain words

First, one small tool: on a right triangle, cosine of an angle is just "how much the slanted side leans forward" — a number between and , negative when it leans backward. Keep that in your pocket. Now picture two arrows growing out of the same spot. To add them, I pick up the second arrow, keep it pointing the same way, and stick its tail onto the tip of the first — like taking one walk, then a second walk from where I stopped. The straight line from my start to my finish is the answer arrow, and its length is what I call (same thing as , just fewer bars). That answer is the third side of a triangle. There's a rule for finding a triangle's third side when you know the two other sides and the corner between them — the law of cosines. But there's a twist: the corner inside my triangle isn't the angle I started with; it's what's left over from a straight line, minus my angle. When I feed that in, the cosine flips sign (forward becomes backward), a minus meets a minus, and out pops a plus. That's the famous . Then I just try every angle. Point them the same way and they stack to their full sum. Point them at right angles and it's plain Pythagoras. Point them opposite and they cancel down to their difference. The answer arrow can never be longer than the sum or shorter than the difference — it just dials smoothly between those two as I open the angle. That dial is the whole reason vectors aren't scalars.

Recall Quick self-test

Why does the correction term switch from (law of cosines) to (final formula)? ::: Because the triangle's interior angle is , and flips the sign. What angle gives the longest resultant? ::: , giving . What angle recovers plain Pythagoras? ::: , since . Two vectors of equal length pointing opposite — resultant? ::: Zero (the case with ). What is the relation between and ? ::: They are the same number — the length of ; the bars are optional once it's clear we mean length.


Connections

  • Vector Addition — Triangle & Parallelogram Law — the home of this result; the parallelogram view is the same triangle mirrored.
  • Components of a Vector — the alternative route to the same , splitting each arrow into perpendicular scalar parts.
  • Distance vs Displacement — the special case in action.
  • Speed vs Velocity — where the cancellation shows up on a round trip.
  • Dot and Cross Products — the here is exactly the dot product in disguise.
  • Units and Dimensions, , all carry the same unit through every step.