It’s time for our quadrennial bonus day! This go-round I am in Hawaii, which means I will be among the last in the world to experience the rare glory of February 29th. It also means that the lone drawback of this holiday, namely that it doesn’t extend June or October instead of gloomy February, is moot for me! Before I head to the beach, I have to take this once-in-four-years opportunity to talk about the time dimension of my weather modeling work.
Leap year is the perfect window for a discussion of time. Of course, the reason that we have an extra day every four years is that the Earth completes its orbit of the sun in roughly 365.2422 days. Since it’s not an even 365.25 days, we skip leap year every 100 years, except if the year is divisible by 400, then we observe it (as we did in 2000). Because Earth’s solar orbit is affected by the moon and other planetary bodies, the length of a solar year can, in fact, vary slightly. Complicating the math further, the average day now lasts for 24.0000006 hours since the second is now defined atomically rather than astronomically. The calendar is oh-so-gradually creeping forward (one could argue that this would be solved with universal adoption of the controversial-but-perhaps-overly-maligned leap second), but this won’t become a noticeable issue for another couple thousand years.
Why do I care about any of this? The angle of the sun is an important variable in the heat balance of Earth’s surface, a core ingredient to all weather models. The leap year phenomenon causes the solar zenith (and corresponding sunrise/sunset times) to change a little bit from year to year. The annual sinusoidal movements created by the gravity of the sun and moon are summed up by the solar zenith equation, below, which does not consider the leap year variance. For the sake of exactitude, I modify my N input with a leap year correction term; this basically sets the N+10 intercept to the exact time of day that the winter solstice occurred the previous year, either on December 20th, 21st, or 22nd.
An exact expression of dates and times is also important when integrating data from numerous agencies and historical records. Data calls generally return the observation time along with the corresponding time zone information for the polled location, which is helpful. I then use the datetime package in Python to do the conversions for me – this normalizes every data input to the computer’s internal Unix time, which counts seconds since 0:00 GMT, January 1, 1970. Beyond preventing Y2K fears from being realized, this standardization (along with UTC time expression) has become absolutely crucial to how the world operates today, from telecommunications to air traffic control. Certainly beats the alternative of mass confusion resulting from differing conceptions of time, like the 300+ years when the world ran on both Julian and Gregorian calendars.
For most of my readers, this is probably more than you ever wanted to know about tracking time. I sincerely apologize, with the caveat that this day would not exist without the observations of early astronomers and many concerted efforts to standardize the calendar. It’s a bonus day, hopefully that means I get a pass!