Racing the Clock: Measuring Time and Speed

Watch any closely-fought sprint finish and you will see something remarkable: officials can tell exactly who crossed the line first, even when two runners appear to arrive at the very same instant, timed to a hundredth of a second or finer. That kind of precision is a very recent achievement. For nearly all of human history, nobody had a clock, a watch, or anything resembling the timing gear used at a modern race, and yet people still needed to know when to plant crops, when to gather for a meal, or roughly how long a task had taken. So the natural question is: before any of today's gadgets existed, how did anyone measure time at all? The answer starts with a simple realisation: nature already repeats itself on a reliable schedule. The Sun rises and sets once a day, the Moon runs through its full set of phases on a steady cycle, and the seasons return in the same order every year. Early calendars were built directly on these cycles, with a single day defined by one complete rise-and-set of the Sun. But a calendar alone cannot tell you the time of day, so people needed a second kind of device, one that could track smaller slices of time within a single day.

Four simple devices, independently developed by different civilisations, all managed to slice a single day into smaller, trackable pieces. A sundial uses the Sun itself: as the Sun moves across the sky through the day, the shadow cast by a fixed object swings slowly around, and the shadow's changing position marks the passing hours. An hourglass uses gravity and sand: a fixed quantity of fine sand takes a fixed, repeatable amount of time to trickle from an upper bulb into a lower one through a narrow neck, so watching how much sand remains tells you how much time has passed. A candle clock burns a specially marked candle at a roughly steady rate, so the height the flame has burned down to indicates the time elapsed. Water clocks came in two different designs, and comparing them reveals a genuinely clever piece of engineering. The simpler design lets water drain out of a marked vessel, with the falling water level read against time markings, but this design has a real flaw: as the water level drops, the pressure pushing water out through the opening drops too, so the flow slows down over time, and the same time interval near the end drains less water than the same time interval at the start, making the markings inaccurate unless they are spaced unevenly to compensate. India refined a cleverer alternative: a small bowl with a fine hole in its base is floated on the surface of a much larger reservoir of water. Water seeps in through the tiny hole and the bowl slowly fills, but because the reservoir is so much bigger than the bowl, its water level barely drops as this happens, unlike the simple draining design. That keeps the pressure pushing water through the hole almost constant throughout, so the bowl fills, and eventually sinks, at a much steadier, more predictable rate. This floating-bowl design, known in ancient India as the Ghatika-yantra, was in constant use at Buddhist monasteries, royal courts and town squares for centuries, and every time a bowl sank, the moment was announced aloud with drums, conch shells or a struck gong, so that time was something the whole town could hear, not just see. India's largest and most precise sundial, the Samrat Yantra at Jaipur's Jantar Mantar, still stands today: a 27-metre-tall stone instrument whose shadow moves at roughly one millimetre every second, fine enough to mark intervals as short as two seconds, a UNESCO World Heritage Site built around 300 years ago.

Mechanical clocks, built from weights, gears and springs, had existed since around the fourteenth century, but they drifted badly and needed constant correction. The real breakthrough came from an unrelated observation about swinging objects. Galileo Galilei, watching a lamp swinging gently on its chain, timed its swings against his own pulse and noticed something odd: whether the lamp was swinging through a wide arc or a narrow one, each full swing seemed to take the same amount of time. Testing this with pendulums of different lengths, Galileo concluded that a pendulum's swing time depends on how long the pendulum is, and stays constant for any pendulum of a fixed length, an observation that took decades to turn into a working clock. That final step came from the Dutch scientist Christiaan Huygens, who used exactly this property, a pendulum's steady, repeatable rhythm, to build and patent the first working pendulum clock in the 1650s. It was a genuine leap forward in accuracy compared to anything that came before it, and the pendulum clock remained the world's best timekeeping technology for roughly the next two hundred and fifty years.

You have already met oscillatory motion, in the eraser-on-a-thread activity from the 'Measurement of Length and Motion' chapter in Class 6, and a simple pendulum is exactly that same motion, built more carefully: a small, heavy bob hangs from a rigid support by a long thread. Left alone, it hangs straight down at what is called its mean position. Pull the bob gently to one side and release it, and it swings past the mean position to an extreme position on the far side, swings back through the mean position again to an extreme position on the original side, and returns to the mean position once more; that whole round trip is called one oscillation, and the time it takes to complete one oscillation is called the pendulum's time period. Try measuring this time period yourself, and a practical problem shows up immediately: a single swing happens too fast to time accurately by hand, since your own reaction time starting and stopping a stopwatch is itself a source of error large enough to throw off a one-swing measurement. The fix is straightforward: time 10 full oscillations instead of one, then divide the total time by 10. Your reaction-time error is still there, but it is now a small fraction of a much longer total time, instead of a large fraction of a single short swing, so the calculated time period comes out far more reliable. Repeating the whole measurement three or four times, and checking that the results roughly agree, catches any one-off mistakes too. Carry out this experiment carefully with pendulums of different lengths, keeping everything else the same, and a clear pattern emerges: a longer pendulum has a longer time period, a shorter pendulum has a shorter time period. Now repeat it again, this time keeping the length fixed but swapping in bobs of different mass, and no such pattern appears, the time period barely changes at all. A simple pendulum's time period depends on its length, not on the mass of its bob, and stays constant for any pendulum of a given length at a given location, exactly the property Huygens built his clock around.

Step back and look at every timekeeping device in this chapter together, the sundial's swinging shadow, the water clock's steady drip, the pendulum's swing, and a single underlying idea connects every one of them: a clock, at its core, is nothing more than something that repeats in a reliable, predictable way, counted. That is precisely the definition of periodic motion from Class 6, and it turns out periodic motion is not just an interesting category of movement, it is the entire foundation that timekeeping is built on. Modern clocks push this same idea to an extreme most ancient timekeepers could never have imagined. A quartz clock counts the extremely rapid, extremely regular vibrations of a tiny quartz crystal, and an atomic clock counts natural vibrations occurring within specific atoms, both processes repeating far faster and far more reliably than any pendulum ever could. The improvement in accuracy is difficult to even picture: Huygens' original pendulum clocks could gain or lose as much as 10 seconds over a single day, while today's best atomic clocks lose only about one second over several million years. Every one of these devices, from a swinging temple lamp to a vibrating atom, is doing fundamentally the same job: finding something that repeats reliably, and counting it.

Just as length needed one agreed, fixed-size unit, so does time, and the SI unit of time is the second, symbol s. Larger, more convenient units are built directly on top of it: 60 seconds make one minute (min), and 60 minutes make one hour (h). As with length units, there are some writing conventions worth getting right: second, minute and hour are written in lowercase (unless starting a sentence), their symbols are never pluralised or followed by a full stop mid-sentence, a space always separates the number from the unit, and 'sec' or 'hrs' are not acceptable substitutes for the proper symbols. An ordinary wall clock usually lets you read time down to the nearest second, its smallest marked interval, but plenty of real, everyday situations demand far finer slices of time than that. Competitive sports now time events to a hundredth, or even a thousandth, of a second (a millisecond), which is often the only way to separate a winner from a runner-up. In hospitals, heart monitors track millisecond-scale variations between heartbeats to catch problems a slower reading would miss entirely. Digital audio recordings capture sound thousands of times every single second to play back smoothly, and the processors inside smartphones and computers routinely operate in microseconds, millionths of a second, part of why they can feel almost instantaneous to use.

Picture a group of runners who all start a race from the exact same line, at the exact same moment. After a few seconds they are no longer together, some pull ahead, some fall behind, and the runner who is furthest ahead at any given instant is, by definition, the one who has covered the most distance in that same stretch of time. That single idea, more distance covered in the same amount of time, is exactly what the word speed means. To turn 'faster' from a vague impression into an actual number, compare the distance different objects cover in one unit of time, one second, one minute, or one hour, whichever is convenient. The speed of an object is simply the total distance it covers divided by the total time it takes: Speed = Total distance covered / Total time taken. Since distance is measured in metres and time in seconds, the SI unit of speed is metres per second, written m/s; distance in kilometres and time in hours instead gives kilometres per hour, km/h, a unit you will recognise from every vehicle's dashboard. Suppose a cyclist covers 1.2 km in exactly 4 minutes: converting first to consistent units, 1.2 km is 1200 m, and 4 minutes is 240 s, so the cyclist's speed is 1200 m divided by 240 s, which works out to 5 m/s. Vehicles measure this constantly using two related but different instruments: a speedometer, which shows how fast the vehicle is going right now, in km/h, and an odometer, which instead adds up the total distance the vehicle has travelled, in kilometres, over its whole journey or lifetime, a running record rather than a live reading.

The speed formula rearranges neatly to answer two other natural questions. If you know an object's speed and how long it has been travelling, you can find the distance covered: Total distance covered = Speed x Total time taken. And if you know both the distance and the speed, you can instead find how long the journey took: Total time taken = Total distance covered / Speed. Suppose a delivery van travels at a steady 40 km/h for 3 hours: the distance it covers is 40 km/h multiplied by 3 h, which is 120 km. Or suppose instead a cargo ship needs to cover 300 km at a speed of 20 km/h: the time it takes is 300 km divided by 20 km/h, which is 15 hours. There is an important catch hiding inside every one of these calculations, including the cyclist example earlier: real objects essentially never travel at one perfectly unchanging speed for an entire journey, they speed up, slow down, and pause. What 'total distance divided by total time' actually calculates is an average speed, smoothing out every such variation into a single representative number. Whenever this chapter, or any similar problem, simply says 'speed', what is actually meant, almost always, is this average speed.

Remember linear motion from Class 6, movement along a straight line? Once an object's speed can actually be measured, straight-line motion splits neatly into two further kinds. Picture a car travelling down a long, straight highway: it pulls away from a standstill, speeding up for a while, cruises at a steady, unchanging speed for a long stretch, then slows down and stops at a toll booth. The middle stretch, where the speed never changes, is called uniform linear motion, movement along a straight line at a constant speed. The stretches where it is speeding up or slowing down are non-uniform linear motion, movement along a straight line where the speed keeps changing. There is a simple, practical test that tells the two apart from a table of readings alone, without ever needing to watch the motion happen: check the distance covered in each equal slice of time. An object in uniform motion covers equal distances in every equal interval of time; one in non-uniform motion covers unequal distances instead, sometimes more, sometimes less, from one interval to the next. Suppose two cyclists are each tracked once every 10 minutes: the first covers 3 km, 3 km, 3 km and 3 km in four consecutive 10-minute intervals, equal distances throughout, so that cyclist is in uniform motion. The second covers 3 km, 2 km, 4 km and 3 km in the same four intervals, unequal distances from one interval to the next, so that cyclist is in non-uniform motion, even though both cyclists happen to cover the same total distance, 12 km, in the same total time, 40 minutes. In practice, uniform motion is closer to a useful idealisation than something you will actually observe for long: almost nothing keeps a perfectly constant speed over a real journey of any real length, which is exactly why average speed, not a single unchanging speed, is what most calculations rely on.