Angle Converters 4

Angles: Three Competing Systems, One Mathematical Truth

Angle measurement has three parallel systems that coexist uneasily in modern engineering. Degrees (360 to a full circle) come from the Babylonians, who used a base-60 number system and noticed that a circle could be subdivided into six equilateral triangles — each with a 60° angle, hence 6 × 60 = 360. Radians (2π to a full circle) are the mathematically natural unit: one radian is the angle subtended by an arc whose length equals the radius. Calculus cannot differentiate sin(x) in degrees without a chain of π/180 correction factors — which is why every programming language, every engineering simulation, and every physics engine converts to radians internally before doing any math. Gradians (400 to a full circle) were introduced during the French Revolution as part of the metric system's decimal-everything philosophy — 100 gon to a right angle, 400 to a full circle. They survive today in some European surveying equipment and almost nowhere else.

The practical consequence of the degree-radian divide is that a single missing conversion factor can silently break results without producing an obvious error. A CSS rotate() value passed in degrees instead of radians will produce an imperceptibly wrong rotation. A CNC machine running a G-code program where one axis uses degrees and another uses radians will cut scrap metal. Game engines and physics simulations spend non-trivial CPU cycles converting between the angle system they display (degrees, for humans) and the system they compute with (radians, for math).

Angle Conversion Reference

For the full engineering story — from the Babylonian 360 to the CSS spin that broke — see the Angle Conversion Guide.

Common Angle Conversions in Practice

The practical difference between degrees and radians is invisible to most users — until it isn't. A CNC machine programmed with a 0.5° taper that should have been 0.5 radians (28.6°) will scrap the part. A CSS animation that rotates by 1° when the designer intended 1 rad (57.3°) will look subtly wrong but not broken enough to debug. These are the silent errors that make angle conversion the most insidious unit problem in software engineering.

Angle Conversion in the Real World: Four Industries Where Radians vs. Degrees Is a Daily Decision

Aviation: Pilots read heading in degrees on the PFD (Primary Flight Display) — 090 is east, 180 is south. But the AHRS (Attitude and Heading Reference System) computes orientation internally using quaternions in radians. The conversion runs at 50 Hz on the ARINC 429 data bus. A 0.005 degrees rounding error per iteration would accumulate to 18 degrees of drift in one hour — which is why the radian-degree constant in avionics firmware is stored at double precision and never truncated.

Robotics: Every industrial robot arm — FANUC, KUKA, ABB — accepts joint angle commands in degrees from the teach pendant but computes inverse kinematics in radians. The Denavit-Hartenberg parameters that define each joint's coordinate transform are specified in radians. A robot programmed to weld a car frame with joint angles in degrees that should have been radians will crash the torch into the fixture — the error is 57.3x at every joint.

Astronomy: The ALMA Observatory's 66 radio antennas in Chile's Atacama Desert achieve 0.6 arcsecond pointing precision (2.9 x 10^-6 rad). Celestial coordinates are stored as J2000.0 right ascension and declination, converted to radians for the baseline vector computation in the u-v plane, then back to degrees for motor encoder feedback. The conversion constant is a compile-time #define in the Telescope Control System's C++ codebase, validated against 15 years of observing scripts.

Medical Imaging: CT scanner gantry rotation is specified in degrees per second (typically 60-80 degrees/s). But the filtered back-projection reconstruction algorithm — the Radon transform inverse — integrates over 0 to pi radians, not 0 degrees to 180 degrees. The ramp filter mathematics depend on the integration limits being exactly pi radians. A Siemens Somatom Force acquires 1,152 projections per rotation at exactly pi/576 rad spacing — the design makes the spacing an exact rational multiple of pi to eliminate interpolation artifacts in the FFT-based reconstruction.

The Silent Angle Bug: Three Ways Programmers Get Degrees-Radians Wrong

Mistake 1 — CSS transform: CSS rotate() accepts degrees, radians, gradians, and turns — but the default unitless value is interpreted as degrees, not radians. Writing transform: rotate(3.14) rotates by 3.14 degrees (imperceptible), not 3.14 radians (180 degrees). Always include the unit: transform: rotate(180deg) or transform: rotate(3.1416rad).

Mistake 2 — JavaScript Math: Math.sin(), Math.cos(), and Math.tan() expect radians. Passing degrees produces results that are wrong by a factor of 57.3. The fix: Math.sin(degrees * Math.PI / 180). Every JavaScript developer makes this mistake once — the browser shows no error, just subtly wrong values.

Mistake 3 — Python numpy: NumPy's trigonometric functions expect radians. The np.deg2rad() and np.rad2deg() functions exist precisely because this is the most common silent bug in scientific Python. A Jupyter notebook computing FFT phase spectra in degrees instead of radians will produce physically impossible phase values — but no exception is raised.