WEBVTT FILE

1
00:00:00.000 --> 00:00:05.680
Remember that Y2K thing a few years ago? Where 
everyone was afraid the world was going to end  

2
00:00:05.680 --> 00:00:14.360
because computer programmers saved space by 
putting dates as… 77 for 1977, 85 for 1985,  

3
00:00:14.360 --> 00:00:19.880
Or 90 for 1990? But then it became clear 
that when the year 2000 finally rolled  

4
00:00:19.880 --> 00:00:25.920
around all of the computers would think 
it was actually 00. Or the year 1900. 

5
00:00:25.920 --> 00:00:32.520
Well, it turns out Hubble has something similar, 
only Hubble’s clock restarts every 6,213 days,  

6
00:00:32.520 --> 00:00:38.560
18 hours. 48 minutes. and 31.875 
seconds. Or roughly every 17  

7
00:00:38.560 --> 00:00:42.920
years for those of you who like counting.
That’s because Hubble’s computers have a  

8
00:00:42.920 --> 00:00:48.040
different way of tracking time than we have here 
on the ground. You’d think it would be as simple  

9
00:00:48.040 --> 00:00:52.880
as synching our ground clocks with Hubble’s 
personal timepiece, but you’d be surprised. 

10
00:00:52.880 --> 00:00:59.000
Hubble’s onboard clock is a 32 bit elapsed time 
counter. So instead of Hubble counting up seconds,  

11
00:00:59.000 --> 00:01:05.440
days, months, and years like a calendar as we know 
it, Hubble counts every 125 milliseconds, or 1/8th  

12
00:01:05.440 --> 00:01:14.960
of a second for those of you who like counting.
Using 32 bits, up to 4,294,967,295 increments  

13
00:01:14.960 --> 00:01:20.520
can be stored. Once that final bit is hit 
however, everything restarts again from the top. 

14
00:01:20.520 --> 00:01:26.920
So to clarify; when Hubble was first deployed 
on April 24th, 1990. Its clock began counting up  

15
00:01:26.920 --> 00:01:33.480
every 1/8th of a second from April 24, 1990. And 
for every one of those 1/8ths of a second Hubble’s  

16
00:01:33.480 --> 00:01:42.920
binary counter got one step closer to its maximum 
of 4,294,967,295 before restarting back to zero. 

17
00:01:42.920 --> 00:01:48.360
This actually happened already, Hubble had 
its first clock rollover back on April 29,  

18
00:01:48.360 --> 00:01:58.200
2007. So from 1990 to 2007 is 17 years. And 
then from 2007 to 2024 is another 17 years.  

19
00:01:58.200 --> 00:02:06.960
So this will be Hubble’s second clock rollover.
When you do the math, 4,294,967,295 multiplied  

20
00:02:06.960 --> 00:02:13.400
by 0.125 (or 1/8th of a second) divided 
by 60 seconds, divided by 60 minutes,  

21
00:02:13.400 --> 00:02:21.360
divided by 24 hours equals 6,213.78 days! 
Our magic number of around 17 years! 

22
00:02:21.360 --> 00:02:25.840
That’s all because Hubble’s initial requirements, 
back when it was being designed and built in  

23
00:02:25.840 --> 00:02:32.520
the 1970’s and 80’s, specified a base mission 
period of 10 years with a 15 year operational  

24
00:02:32.520 --> 00:02:39.960
goal. Therefore, the 32-bit clock design with 
rollovers every 17 years met those requirements. 

25
00:02:39.960 --> 00:02:45.360
But why does this even matter? Why not just let 
the numbers roll over on their own every 17 years  

26
00:02:45.360 --> 00:02:50.680
and start things from the top again? Well, if 
we tried that things would get pretty weird! 

27
00:02:50.680 --> 00:02:55.680
That’s because Hubble would suddenly think 
it was 17 years younger. It would think it  

28
00:02:55.680 --> 00:03:01.840
was back at that first clock rollover we just 
talked about that happened on April 29, 2007. 

29
00:03:01.840 --> 00:03:07.640
If Hubble thought it was 17 years ago, it would be 
very confusing. Hubble’s antennas would point in  

30
00:03:07.640 --> 00:03:12.920
the wrong direction when trying to send data or 
receive commands from a communication satellite  

31
00:03:12.920 --> 00:03:18.600
that was somewhere else. Because Hubble would 
think everything in space was in the same place  

32
00:03:18.600 --> 00:03:25.280
it was 17 years prior. Hubble would even think it 
was in a different place. And even more dangerous,  

33
00:03:25.280 --> 00:03:30.520
Hubble would think that the Sun was in a different 
place, and if Hubble looks at the Sun, that could  

34
00:03:30.520 --> 00:03:37.560
be very, very bad for its delicate instruments!
The fact that the second clock rollover 34 years  

35
00:03:37.560 --> 00:03:42.240
after Hubble’s initial deployment is now 
upon us is yet another testament to the  

36
00:03:42.240 --> 00:03:47.440
dedication and ingenuity of everyone 
who built, upgraded, and continues to  

37
00:03:47.440 --> 00:03:52.960
maintain Hubble as the premier astronomical 
observatory we have come to know and love. 

38
00:03:52.960 --> 00:03:57.360
Back before the new millennium, computer 
engineers around the world updated things  

39
00:03:57.360 --> 00:04:02.240
to have all four numbers of the year instead of 
just the last two, so we managed to keep that  

40
00:04:02.240 --> 00:04:08.400
Y2K bug from actually destroying everything.
And just like we managed to avoid any mishaps  

41
00:04:08.400 --> 00:04:14.400
with that issue, our team of Hubble engineers on 
the ground have sent up new routines to ensure  

42
00:04:14.400 --> 00:04:21.880
that our trusty space telescope could successfully 
rollover its clock without dropping back 17 years. 

43
00:04:21.880 --> 00:04:29.720
That way Hubble can keep doing its amazing 
work until the next clock rollover in 2041!

44
00:04:29.720 --> 00:04:44.150
"Follow us on social media @NASAHubble"