WEBVTT - Redefining the Second

0:00:00.160 --> 0:00:07.160
<v Speaker 1>Brought to you by Toyota Let's go places. Welcome to

0:00:07.360 --> 0:00:15.080
<v Speaker 1>Forward Thinking. Hei there, and welcome to Horrid Thinking, the

0:00:15.200 --> 0:00:17.960
<v Speaker 1>podcast that looks at the future and says underneath the

0:00:17.960 --> 0:00:19.880
<v Speaker 1>big clock. At the corner of Fifth Avenue and twenty

0:00:19.880 --> 0:00:21.599
<v Speaker 1>two Street, I stuta and waited for a girl I

0:00:21.680 --> 0:00:23.960
<v Speaker 1>knew at the spot where we agreed to meet. It

0:00:24.040 --> 0:00:28.680
<v Speaker 1>was four minutes of two. I'm Jonathan Strickland and I'm

0:00:28.760 --> 0:00:32.040
<v Speaker 1>Lauren Folk. Bob and our third co host, Joe McCormick

0:00:32.240 --> 0:00:34.440
<v Speaker 1>is not with us today in his place as an

0:00:34.440 --> 0:00:38.560
<v Speaker 1>extraordinarily long quote. Yes, I I figured, since we would

0:00:38.640 --> 0:00:42.680
<v Speaker 1>save time, would Joe not introducing himself, I would take

0:00:42.800 --> 0:00:46.040
<v Speaker 1>that time and repurpose it for an even longer quote

0:00:46.400 --> 0:00:49.240
<v Speaker 1>from one of my favorite bands of all time. Fair Enough.

0:00:49.280 --> 0:00:50.680
<v Speaker 1>You know, some day we should really put together a

0:00:50.680 --> 0:00:53.240
<v Speaker 1>playlist of all of the songs that would have mentioned.

0:00:53.880 --> 0:00:58.600
<v Speaker 1>Some of them are not safe for work. Like I

0:00:58.640 --> 0:01:01.360
<v Speaker 1>try to, I try to avoid those, but sometimes when

0:01:01.400 --> 0:01:05.840
<v Speaker 1>I I get a little, I get a little rambunctious, punch,

0:01:06.160 --> 0:01:08.360
<v Speaker 1>a little bungee. At the end of the week, Vim

0:01:08.360 --> 0:01:11.600
<v Speaker 1>and Vinegar, and especially when it's like two minutes before

0:01:11.640 --> 0:01:14.080
<v Speaker 1>we're supposed to start recording, and I realized, hey, I

0:01:14.080 --> 0:01:15.959
<v Speaker 1>don't have a song lyric to go at the front

0:01:15.959 --> 0:01:17.760
<v Speaker 1>of the show. I have to admit that every single

0:01:17.760 --> 0:01:21.640
<v Speaker 1>time Joe and I are are podcasting alone with without

0:01:21.680 --> 0:01:23.560
<v Speaker 1>you and what you will be doing very soon, we

0:01:23.680 --> 0:01:26.640
<v Speaker 1>will because you are going on vacations. I will. I'll

0:01:26.640 --> 0:01:29.280
<v Speaker 1>be cruising around. That is I believe where Joe is

0:01:29.400 --> 0:01:33.320
<v Speaker 1>right now, although he could be following my footsteps to Europa.

0:01:34.000 --> 0:01:36.119
<v Speaker 1>Every time that Joe and I are in the studio alone,

0:01:36.240 --> 0:01:39.480
<v Speaker 1>like we we always it's like knol hits record, Null

0:01:39.520 --> 0:01:41.840
<v Speaker 1>are super producer, and then one or the other of

0:01:41.920 --> 0:01:45.160
<v Speaker 1>us goes, we haven't chosen a quote yet? Why did

0:01:45.240 --> 0:01:49.160
<v Speaker 1>Jonathan start that? As like a standard way of opening

0:01:49.160 --> 0:01:50.960
<v Speaker 1>the show. What I should do is also go back

0:01:51.000 --> 0:01:53.960
<v Speaker 1>and find the first episode where I did that and

0:01:54.040 --> 0:01:58.120
<v Speaker 1>just start writing down, like how many times has have

0:01:58.320 --> 0:02:01.920
<v Speaker 1>you used the same four songs? Right? I know that

0:02:02.040 --> 0:02:04.120
<v Speaker 1>I know that there are certain songs I've used more

0:02:04.160 --> 0:02:06.560
<v Speaker 1>than once, and in fact, I almost started this one

0:02:06.680 --> 0:02:10.120
<v Speaker 1>with a song I'm pretty sure I've used before. But

0:02:10.400 --> 0:02:13.360
<v Speaker 1>all of that put aside, we're wasting time and time

0:02:13.440 --> 0:02:16.720
<v Speaker 1>is precious. Time is so precious. Every second counts in

0:02:16.880 --> 0:02:21.240
<v Speaker 1>every millisecond, every nanosecond counts, and we were learning that

0:02:21.639 --> 0:02:23.880
<v Speaker 1>what we think of as a second may not actually

0:02:23.960 --> 0:02:28.799
<v Speaker 1>be a second. No, well kind of okay. So so

0:02:28.960 --> 0:02:32.040
<v Speaker 1>news broke at the end of May, the year which

0:02:32.080 --> 0:02:35.320
<v Speaker 1>we are recording this, in that researchers had created a

0:02:35.360 --> 0:02:39.480
<v Speaker 1>new clock so much more precise than existing clocks that

0:02:39.560 --> 0:02:42.280
<v Speaker 1>were like maybe going to have to change the definition

0:02:42.280 --> 0:02:45.080
<v Speaker 1>of a second. And that got us thinking about the

0:02:45.160 --> 0:02:48.360
<v Speaker 1>history and the future of time keeping, right, And this

0:02:48.440 --> 0:02:50.720
<v Speaker 1>also means, by the way that we have to redefine

0:02:50.800 --> 0:02:54.320
<v Speaker 1>what a second is, by its very nature, we're eventually

0:02:54.360 --> 0:02:56.239
<v Speaker 1>gonna have to readefine one, a New York minute really

0:02:56.280 --> 0:03:02.680
<v Speaker 1>mass fair enough. It's not that our idea of what

0:03:02.760 --> 0:03:05.880
<v Speaker 1>a New York minute or or a second is wrong.

0:03:05.919 --> 0:03:09.080
<v Speaker 1>A second is a second. It's the machines that we

0:03:09.200 --> 0:03:12.040
<v Speaker 1>used to tell time that are that are wrong or

0:03:12.120 --> 0:03:16.359
<v Speaker 1>at the very least imprecise. So okay, you know how

0:03:16.400 --> 0:03:19.480
<v Speaker 1>like how like digital clocks that aren't connected to the internet,

0:03:19.520 --> 0:03:22.080
<v Speaker 1>like like the clock in your car, or an analog

0:03:22.200 --> 0:03:26.040
<v Speaker 1>risk to watcher a wall clock, you know, analog meaning

0:03:26.120 --> 0:03:29.079
<v Speaker 1>like has hands and gears, like like it's the kind

0:03:29.080 --> 0:03:31.240
<v Speaker 1>of clock where you look at it and then you think,

0:03:31.760 --> 0:03:34.240
<v Speaker 1>I remember, I used to know how to tell time

0:03:34.280 --> 0:03:36.840
<v Speaker 1>this way. When I was first writing these notes, I

0:03:37.000 --> 0:03:41.200
<v Speaker 1>I originally started to type old fashioned and then stopped

0:03:41.280 --> 0:03:44.120
<v Speaker 1>myself because where I felt so anxious and where you

0:03:44.160 --> 0:03:46.280
<v Speaker 1>could at least say, like when Mickey's big hand is

0:03:46.320 --> 0:03:49.480
<v Speaker 1>on the two and his little hand is on the three.

0:03:50.280 --> 0:03:52.600
<v Speaker 1>But but so these clocks that aren't connected to the

0:03:52.640 --> 0:03:57.440
<v Speaker 1>interwebs slowly go off time, right, And that's because the

0:03:57.480 --> 0:04:02.640
<v Speaker 1>mechanisms that drive them aren't white measuring seconds correctly, and

0:04:02.680 --> 0:04:06.080
<v Speaker 1>the difference slowly adds up until it's noticeable to even

0:04:06.120 --> 0:04:08.640
<v Speaker 1>our very slow brains. Right. And we could be talking

0:04:08.800 --> 0:04:13.880
<v Speaker 1>about fractions of a second of an error, but eventually

0:04:13.880 --> 0:04:16.120
<v Speaker 1>those fractions of a second add up to a second,

0:04:16.160 --> 0:04:18.600
<v Speaker 1>and eventually those seconds add up to a minute. Now,

0:04:18.640 --> 0:04:21.200
<v Speaker 1>this takes a lot of time, depending on how precise

0:04:21.279 --> 0:04:25.040
<v Speaker 1>that clock happens to be, But even even if you're

0:04:25.040 --> 0:04:29.039
<v Speaker 1>talking super small errors, it does add up over time,

0:04:29.160 --> 0:04:32.320
<v Speaker 1>oh absolutely. And while it may not be terribly important

0:04:32.400 --> 0:04:36.680
<v Speaker 1>to us, there are mechanical applications or digital applications rather,

0:04:36.720 --> 0:04:39.920
<v Speaker 1>in which it becomes very very important. Yes, and uh,

0:04:40.839 --> 0:04:45.680
<v Speaker 1>clocks these days are are even even old fashioned analog

0:04:45.800 --> 0:04:48.720
<v Speaker 1>clocks are really pretty good at doing what they do.

0:04:49.240 --> 0:04:53.400
<v Speaker 1>But that has not always been as precise the case. Yeah,

0:04:53.400 --> 0:04:55.560
<v Speaker 1>As it turns out, if we want to talk about

0:04:56.160 --> 0:05:00.359
<v Speaker 1>the way we are now being able to to find

0:05:00.360 --> 0:05:04.040
<v Speaker 1>a second and keep that time as precisely as we

0:05:04.200 --> 0:05:07.839
<v Speaker 1>currently know how to do it, behoods us to look

0:05:07.920 --> 0:05:13.320
<v Speaker 1>back into our distant past and learn about the history

0:05:13.360 --> 0:05:17.039
<v Speaker 1>of time keeping. Ah. Yeah, because the concept of a

0:05:17.160 --> 0:05:22.000
<v Speaker 1>second is, like in the Grand scheme of humanity, relatively new. Yeah, yeah,

0:05:22.080 --> 0:05:25.320
<v Speaker 1>especially when it comes to time. In fact, the original

0:05:25.800 --> 0:05:28.800
<v Speaker 1>version of a second had more to do with geography

0:05:28.920 --> 0:05:33.120
<v Speaker 1>than with time passing. So you know, I was gonna

0:05:33.360 --> 0:05:36.760
<v Speaker 1>bust out the way Back Machine, but I don't know.

0:05:36.880 --> 0:05:38.360
<v Speaker 1>Do you think I could handle a trip all the

0:05:38.360 --> 0:05:40.960
<v Speaker 1>way back to ancient Egypt? I mean, we haven't taken

0:05:41.000 --> 0:05:43.280
<v Speaker 1>it that far back in a long time. We I

0:05:43.440 --> 0:05:45.320
<v Speaker 1>don't think I've ever taken it that far back. Do

0:05:45.360 --> 0:05:47.440
<v Speaker 1>you think it's safe to be in the way Back

0:05:47.520 --> 0:05:50.240
<v Speaker 1>machine and talk about time that much? Do you think

0:05:50.240 --> 0:05:51.840
<v Speaker 1>it's going to get mad at you could get a

0:05:51.839 --> 0:05:54.080
<v Speaker 1>little time you want? You know what? You only live

0:05:54.160 --> 0:06:04.279
<v Speaker 1>once into the way back machine. You go, okay, all right,

0:06:04.320 --> 0:06:07.159
<v Speaker 1>now we just have to here's the problem. The all

0:06:07.160 --> 0:06:09.279
<v Speaker 1>the digits are hieroglyphs when you want to go to

0:06:09.279 --> 0:06:13.480
<v Speaker 1>ancient Egypt. So it's let's see it's this is ticked

0:06:13.480 --> 0:06:20.480
<v Speaker 1>off kitty cat uh uh, snakehead person and block. All right,

0:06:22.520 --> 0:06:24.320
<v Speaker 1>I got it right in the first try. Okay, So

0:06:25.040 --> 0:06:29.480
<v Speaker 1>here we are back in ancient Egypt. Now, to be fair,

0:06:30.200 --> 0:06:34.039
<v Speaker 1>we believe that timekeeping may go back further than the

0:06:34.080 --> 0:06:37.240
<v Speaker 1>ancient Egyptians, but it's so uncertain that I don't even

0:06:37.240 --> 0:06:40.880
<v Speaker 1>trust the way back machine. Yeah, there are there's a

0:06:40.880 --> 0:06:45.680
<v Speaker 1>possibility that the Sumerians had this covered pretty much right,

0:06:45.680 --> 0:06:48.640
<v Speaker 1>but we don't have any evidence of the Sumerians actually

0:06:48.680 --> 0:06:53.360
<v Speaker 1>building any sort of time keeping device of any sort. Also,

0:06:53.440 --> 0:06:57.600
<v Speaker 1>my cuneiform is really rusty. Yeah, I I I'm barely

0:06:57.800 --> 0:07:01.120
<v Speaker 1>hanging on with the hieroglyphs as it is. So one

0:07:01.160 --> 0:07:04.120
<v Speaker 1>thing that we should mention though about those Sumerians. They

0:07:04.160 --> 0:07:07.520
<v Speaker 1>had something that will later on factor in importantly in

0:07:07.560 --> 0:07:12.200
<v Speaker 1>the timekeeping discussion. They loved the number sixty a lot,

0:07:12.880 --> 0:07:15.119
<v Speaker 1>like a whole bunch. Yeah, the Egyptians loved the number

0:07:15.120 --> 0:07:18.960
<v Speaker 1>twelve and the Sumerians loved the number sixty, and sixty

0:07:19.000 --> 0:07:20.840
<v Speaker 1>is kind of a cool number. It makes it really

0:07:20.880 --> 0:07:23.240
<v Speaker 1>easy to deal with certain fractions because there's so many

0:07:23.320 --> 0:07:26.640
<v Speaker 1>numbers that are uh that sixty is divisible by so

0:07:26.800 --> 0:07:29.880
<v Speaker 1>one through six all of those are divisible, or sixties

0:07:29.920 --> 0:07:33.360
<v Speaker 1>divisible by all those uh ten, twelve, fifteen, twenty, and thirty,

0:07:33.400 --> 0:07:36.200
<v Speaker 1>which starts to sound familiar when you start thinking about clocks.

0:07:36.640 --> 0:07:39.000
<v Speaker 1>And so this, this this base of six kind of

0:07:39.040 --> 0:07:42.400
<v Speaker 1>concept is something that was adopted by a lot of

0:07:42.480 --> 0:07:46.960
<v Speaker 1>civilizations from that time and and and location. Right, the Babylonians,

0:07:47.000 --> 0:07:50.160
<v Speaker 1>they said, hey, you know, we didn't dig everything you

0:07:50.200 --> 0:07:55.520
<v Speaker 1>Sumerians did, but we like this sexygesimal base system. Uh

0:07:55.600 --> 0:07:59.280
<v Speaker 1>So we're gonna use that for our astronomy. Astronomical calculations.

0:07:59.280 --> 0:08:01.560
<v Speaker 1>We're gonna when we're exploring stuff in the sky and

0:08:01.560 --> 0:08:04.920
<v Speaker 1>we're describing how it moves and the relationship of different

0:08:04.960 --> 0:08:07.320
<v Speaker 1>stars to one another. This is the bass system we're

0:08:07.360 --> 0:08:09.280
<v Speaker 1>gonna use because it makes it very easy to to

0:08:09.400 --> 0:08:12.040
<v Speaker 1>divide by all these different numbers. Sharing kind of based

0:08:12.080 --> 0:08:14.480
<v Speaker 1>on that. The Greeks also picked it up, yes, and

0:08:14.560 --> 0:08:17.920
<v Speaker 1>so that ended up being very important further down the line.

0:08:18.520 --> 0:08:21.880
<v Speaker 1>But we'll rejoin that, because that's like medieval Europe, y'all.

0:08:21.960 --> 0:08:24.040
<v Speaker 1>When we have to get to the point we're applying

0:08:24.040 --> 0:08:26.360
<v Speaker 1>it to time. So if they weren't using it to

0:08:26.400 --> 0:08:28.960
<v Speaker 1>describe time, what were they using it for. Well, besides

0:08:29.000 --> 0:08:32.440
<v Speaker 1>the astronomical calculations, they were starting to talk about using

0:08:32.520 --> 0:08:40.280
<v Speaker 1>it to describe geometric features and also the describing geography itself. Yeah,

0:08:40.360 --> 0:08:43.959
<v Speaker 1>not not just space geography, but geography right here on Earth. Yes, yes,

0:08:44.080 --> 0:08:46.520
<v Speaker 1>so that you could be able to say things like

0:08:46.720 --> 0:08:49.280
<v Speaker 1>where one place is in relation to this other place,

0:08:49.280 --> 0:08:51.480
<v Speaker 1>other than just all right, you're gonna go down this

0:08:51.720 --> 0:08:54.080
<v Speaker 1>road away for about five minutes, and then you're going

0:08:54.120 --> 0:08:57.880
<v Speaker 1>to take a rat turn the yield crisp crane. If

0:08:57.920 --> 0:09:00.880
<v Speaker 1>you see a guy playing a banjo, you gone too far,

0:09:01.720 --> 0:09:05.280
<v Speaker 1>turn around, come back. Yeah, that's that. I wish that

0:09:05.320 --> 0:09:08.160
<v Speaker 1>I knew the ancient Greek for crispy cream, yeah, or

0:09:08.200 --> 0:09:12.680
<v Speaker 1>banjo at any rate. Uh. The sexogasmal system was used

0:09:12.679 --> 0:09:16.319
<v Speaker 1>to help define these things and arrest knees. Use the

0:09:16.360 --> 0:09:19.160
<v Speaker 1>system to divide a circle into sixty parts to create

0:09:19.160 --> 0:09:24.839
<v Speaker 1>a geographic system of latitude. Um Hipparchus normalized these lines,

0:09:24.880 --> 0:09:27.280
<v Speaker 1>making them parallel because before they were kind of wavy.

0:09:27.440 --> 0:09:30.880
<v Speaker 1>The essentially well arrest the knees used them to connect

0:09:30.960 --> 0:09:34.760
<v Speaker 1>places that he thought were particularly interesting, which didn't necessarily

0:09:34.800 --> 0:09:36.760
<v Speaker 1>mean they went in a straight line. They might lean

0:09:36.800 --> 0:09:38.480
<v Speaker 1>a little to the right, like, hey, this place is

0:09:38.520 --> 0:09:39.800
<v Speaker 1>kind of cool, you might want to check that out.

0:09:39.880 --> 0:09:44.520
<v Speaker 1>D Yeah. So Hipparcus was like, no, we're gonna normalize

0:09:44.520 --> 0:09:46.600
<v Speaker 1>this stuff, make it a lot easier. And he also

0:09:46.640 --> 0:09:49.760
<v Speaker 1>developed a system of longitude, which had three hundred sixty degrees.

0:09:50.040 --> 0:09:52.880
<v Speaker 1>Then you have Claudius Ptolemy, who expanded on this and

0:09:53.000 --> 0:09:56.640
<v Speaker 1>subdivided the three sixty degrees of latitude and longitude into

0:09:56.720 --> 0:10:00.680
<v Speaker 1>smaller segments. So he divided each degree into sixty parts,

0:10:00.760 --> 0:10:04.640
<v Speaker 1>and each of those sixty parts he's subdivided into sixty

0:10:04.800 --> 0:10:07.720
<v Speaker 1>smaller parts. Okay, so so so that's where you get

0:10:07.800 --> 0:10:10.680
<v Speaker 1>that's where you get minutes and seconds, right. The first

0:10:11.120 --> 0:10:16.240
<v Speaker 1>the larger subdivisions were known as the partists minute prima,

0:10:16.480 --> 0:10:20.320
<v Speaker 1>or the minutes, and then you had the second ones,

0:10:20.400 --> 0:10:24.079
<v Speaker 1>known as the partisan minute secunda or second minute, or

0:10:24.160 --> 0:10:26.840
<v Speaker 1>later just second. But it would take more than a

0:10:26.880 --> 0:10:30.359
<v Speaker 1>thousand years for that stuff to be actually applied towards timekeeping.

0:10:30.360 --> 0:10:33.720
<v Speaker 1>It was really applied toward map making and geography. Okay,

0:10:33.760 --> 0:10:37.080
<v Speaker 1>but so I mean around the same time ish stuff

0:10:37.160 --> 0:10:40.240
<v Speaker 1>was happening with early forms of clocks, Yes, sort of

0:10:40.679 --> 0:10:42.920
<v Speaker 1>the Egyptians. You know, if we look around right here,

0:10:43.120 --> 0:10:45.040
<v Speaker 1>you just look a little bit over to the right. Okay,

0:10:45.200 --> 0:10:48.760
<v Speaker 1>you notice there's that big tall obelisk over there, all right,

0:10:48.800 --> 0:10:52.520
<v Speaker 1>So that obelisk, it's for a real important reason. It's

0:10:52.600 --> 0:10:55.400
<v Speaker 1>there to tell you when it's in the early part

0:10:55.400 --> 0:10:57.880
<v Speaker 1>of the day versus the later part of the day. Yeah,

0:10:57.960 --> 0:11:01.319
<v Speaker 1>in case you're not aware that it's now later than

0:11:01.360 --> 0:11:05.079
<v Speaker 1>it was earlier. You can look at the shadow. I've

0:11:05.080 --> 0:11:08.280
<v Speaker 1>taken naps where I've gotten up really confused. So actually

0:11:08.360 --> 0:11:10.400
<v Speaker 1>that that could be very helpful that moment where you

0:11:10.440 --> 0:11:13.240
<v Speaker 1>wake up and you aren't even aware of which pyramids

0:11:13.280 --> 0:11:17.080
<v Speaker 1>you're sleeping, like what time of day it is. So yeah,

0:11:17.080 --> 0:11:21.040
<v Speaker 1>these are were very basic clocks. They essentially divided the

0:11:21.120 --> 0:11:24.880
<v Speaker 1>day up into before noon and afternoon, but they also

0:11:24.920 --> 0:11:28.120
<v Speaker 1>would show when the longest or shortest day of the

0:11:28.200 --> 0:11:29.880
<v Speaker 1>year happened to be. If it was the longest day

0:11:29.880 --> 0:11:31.640
<v Speaker 1>of the year, the shadow would be shorter. It was

0:11:31.679 --> 0:11:33.600
<v Speaker 1>the shortest day of the the year, the shadow would be longer,

0:11:34.520 --> 0:11:38.679
<v Speaker 1>so you could tell kind of the time of year. Yeah,

0:11:38.720 --> 0:11:40.679
<v Speaker 1>so you'd be like, wow, it's really cold out. Also,

0:11:40.760 --> 0:11:45.680
<v Speaker 1>shortest day of the year. Interesting. Um, So the sun

0:11:45.720 --> 0:11:49.560
<v Speaker 1>dial itself would show up in fred BC. So this

0:11:49.640 --> 0:11:52.600
<v Speaker 1>is like two thousand years after those obelisks were the

0:11:52.640 --> 0:11:56.880
<v Speaker 1>early stages of timekeeping. Now these this is also courtesy

0:11:56.920 --> 0:11:59.960
<v Speaker 1>of the Egyptians. So we're just gonna stay here then

0:12:00.120 --> 0:12:03.040
<v Speaker 1>chat about it. The device, the sun dials, had multiple

0:12:03.040 --> 0:12:05.199
<v Speaker 1>divisions on it to help divide up the day a

0:12:05.240 --> 0:12:08.720
<v Speaker 1>little bit better. Also, once you got to noon, you

0:12:08.800 --> 0:12:11.520
<v Speaker 1>had to turn the sun dial a hundred eighty degrees

0:12:11.600 --> 0:12:15.320
<v Speaker 1>around so it would continue to keep time properly. So

0:12:15.440 --> 0:12:18.160
<v Speaker 1>this is the first instance of having to wind a

0:12:18.240 --> 0:12:22.120
<v Speaker 1>clock so that it keeps time. Um. So the Egyptians

0:12:22.120 --> 0:12:25.199
<v Speaker 1>divide the daylight hours into twelve segments. They were really

0:12:25.240 --> 0:12:28.360
<v Speaker 1>big on that number twelve, remember, which is fortunate since

0:12:28.840 --> 0:12:30.920
<v Speaker 1>again sixty is divisible by twelve, so that will come

0:12:30.960 --> 0:12:34.040
<v Speaker 1>in hand you later. So they thought, let's divide up

0:12:34.040 --> 0:12:37.520
<v Speaker 1>the day into twelve, the daylight hours into twelve segments.

0:12:37.840 --> 0:12:40.560
<v Speaker 1>So there became twelve periods or hours of daylight in

0:12:40.600 --> 0:12:44.600
<v Speaker 1>a day. But since the amount of daylight changes throughout

0:12:44.600 --> 0:12:47.760
<v Speaker 1>the year, then the the length of an hour changed

0:12:47.920 --> 0:12:51.600
<v Speaker 1>throughout the year. Okay, So so light time was was

0:12:52.240 --> 0:12:57.040
<v Speaker 1>twelve hours to twelve periods, and then nighttime was night.

0:12:57.160 --> 0:13:00.600
<v Speaker 1>Nighttime at first was nothing. Nighttime was just not the

0:13:00.720 --> 0:13:04.280
<v Speaker 1>day was just go go home. It's just like there's

0:13:04.320 --> 0:13:06.880
<v Speaker 1>nothing to do. Go to sleep. You know, there's no

0:13:08.960 --> 0:13:11.920
<v Speaker 1>you don't have Netflix, we have only so much oil

0:13:12.000 --> 0:13:15.520
<v Speaker 1>to burn. Go to sleep. So yeah, and at first

0:13:15.600 --> 0:13:19.240
<v Speaker 1>nighttime was nothing. But then the astronomers in Egypt, they

0:13:19.280 --> 0:13:22.000
<v Speaker 1>began to develop tools where they were studying the movement

0:13:22.000 --> 0:13:25.880
<v Speaker 1>of stars, and they divided up the night hour nighttime

0:13:26.040 --> 0:13:29.240
<v Speaker 1>hours into twelve as well. So you had twelve nighttime

0:13:29.280 --> 0:13:32.000
<v Speaker 1>hours twelve daytime hours for a total of twenty four

0:13:32.280 --> 0:13:35.080
<v Speaker 1>periods in a day. Right, And they again were not

0:13:35.400 --> 0:13:38.000
<v Speaker 1>fixed length, right, It all depended on what time of year.

0:13:38.080 --> 0:13:41.800
<v Speaker 1>So literally, in the summer you had longer hours than

0:13:41.840 --> 0:13:44.520
<v Speaker 1>you did in the winter. So time did not pass

0:13:44.600 --> 0:13:48.080
<v Speaker 1>the same way from a from the perspective of counting

0:13:48.120 --> 0:13:51.240
<v Speaker 1>the hours, it passed the same way in a different sense.

0:13:51.240 --> 0:13:55.719
<v Speaker 1>If you're not concerned about what quote unquote time is it, uh,

0:13:56.200 --> 0:13:59.640
<v Speaker 1>that's trying to think about going about your day like

0:13:59.720 --> 0:14:03.200
<v Speaker 1>that is very confounding to me. Well, as it turned out,

0:14:03.520 --> 0:14:06.440
<v Speaker 1>most people back then really just need to know is

0:14:06.480 --> 0:14:08.880
<v Speaker 1>it early enough for me to do work? Is it

0:14:09.000 --> 0:14:10.640
<v Speaker 1>getting to the point where it's going to be too

0:14:10.720 --> 0:14:12.960
<v Speaker 1>hot to do work? Is it the time to eat?

0:14:13.360 --> 0:14:15.760
<v Speaker 1>Is it the time to not be awake anymore? Really

0:14:15.880 --> 0:14:17.760
<v Speaker 1>was pretty you know, there weren't a whole lot of

0:14:17.800 --> 0:14:20.320
<v Speaker 1>evites that people had to respond to with yes, no,

0:14:20.520 --> 0:14:24.400
<v Speaker 1>or maybe. They were really kind of simple in that way. Now,

0:14:24.880 --> 0:14:27.240
<v Speaker 1>the Greeks were the first to introduce the idea of

0:14:27.320 --> 0:14:30.200
<v Speaker 1>fixed length hours, but they did this so that they

0:14:30.200 --> 0:14:33.880
<v Speaker 1>could make astronomical calculations. They didn't do it so that

0:14:33.920 --> 0:14:37.200
<v Speaker 1>people would keep regular time. In fact, most people didn't

0:14:37.320 --> 0:14:41.840
<v Speaker 1>bother with that. They stuck with the more casual variable

0:14:41.880 --> 0:14:45.320
<v Speaker 1>our system, and in fact that would hold true until

0:14:45.360 --> 0:14:49.080
<v Speaker 1>the Middle Ages. Um, but that's not the only type

0:14:49.080 --> 0:14:51.160
<v Speaker 1>of clock that was around at this time. Oh yeah.

0:14:51.680 --> 0:14:55.760
<v Speaker 1>Also right here in ancient Egypt, where we absolutely are,

0:14:56.440 --> 0:15:02.600
<v Speaker 1>were water clocks that were probably developed here. Again, you know,

0:15:02.840 --> 0:15:05.720
<v Speaker 1>like it's basically whatever you dig up is your evidence

0:15:05.800 --> 0:15:08.280
<v Speaker 1>for what was developed when and if it didn't survive

0:15:08.400 --> 0:15:13.800
<v Speaker 1>then you Yeah, but so one was water clock was

0:15:13.800 --> 0:15:17.520
<v Speaker 1>definitely found in a Menhotep, the first tomb, dating from

0:15:17.520 --> 0:15:23.840
<v Speaker 1>around five b C. And uh, they water clocks covered

0:15:24.040 --> 0:15:29.040
<v Speaker 1>a few of sundials or or astronomy clocks pitfalls because

0:15:29.080 --> 0:15:33.280
<v Speaker 1>you could use them when it was cloudy, crazy um,

0:15:33.360 --> 0:15:36.080
<v Speaker 1>and you could also use them as stop watches. The

0:15:36.080 --> 0:15:38.200
<v Speaker 1>Greeks would later pick up on them too, though not

0:15:38.360 --> 0:15:41.480
<v Speaker 1>until around like three b C we think, and they

0:15:41.520 --> 0:15:45.360
<v Speaker 1>called them clip sidras, which I love, which basically means

0:15:45.400 --> 0:15:48.680
<v Speaker 1>water thieves. And it's interesting they're called water thieves. It's

0:15:48.720 --> 0:15:55.160
<v Speaker 1>specifically because of the physical way the clock keeps time, right, yeah, yeah,

0:15:55.160 --> 0:15:57.080
<v Speaker 1>So so the idea here is that you've got a

0:15:57.240 --> 0:16:00.960
<v Speaker 1>stone bowl with a very small hole near the bottom

0:16:01.120 --> 0:16:04.480
<v Speaker 1>through which water would flow hypothetically a kind of sort

0:16:04.480 --> 0:16:07.400
<v Speaker 1>of more or less constant rate. You put this, You

0:16:07.440 --> 0:16:09.680
<v Speaker 1>put this bowl with a hole in it inside a

0:16:09.720 --> 0:16:13.280
<v Speaker 1>larger basin that's filled with water, and the water will

0:16:13.400 --> 0:16:17.520
<v Speaker 1>slowly fill the bowl if if, if the inside of

0:16:17.520 --> 0:16:19.920
<v Speaker 1>the bowl is then marked with lines, you can tell

0:16:20.000 --> 0:16:23.680
<v Speaker 1>the rough passage of hours by watching the water mark. Yeah,

0:16:23.680 --> 0:16:26.960
<v Speaker 1>I've seen a similar one where it was again going

0:16:27.000 --> 0:16:29.640
<v Speaker 1>back to the Egyptian times, where you had a container

0:16:29.680 --> 0:16:31.360
<v Speaker 1>with a very small hole in it, and it would

0:16:31.360 --> 0:16:34.840
<v Speaker 1>allow water to flow through one container into a second container.

0:16:34.840 --> 0:16:37.040
<v Speaker 1>And the second container have a bobber in it. Oh,

0:16:37.040 --> 0:16:39.600
<v Speaker 1>sure that had a water mark that could tell you, Yeah,

0:16:39.640 --> 0:16:42.120
<v Speaker 1>you look at the bobber and you'd say, all right, so, uh,

0:16:42.520 --> 0:16:45.280
<v Speaker 1>three marks have gone by. We're going to call those hours.

0:16:45.320 --> 0:16:48.920
<v Speaker 1>But keep in mind that these devices also weren't precise

0:16:49.040 --> 0:16:53.200
<v Speaker 1>time keeping devices. A rough idea. Yeah, and and I'm

0:16:53.240 --> 0:16:55.160
<v Speaker 1>sure that I mean, you know, as water war would

0:16:55.240 --> 0:16:58.200
<v Speaker 1>change the shape of the whole of the given device,

0:16:58.440 --> 0:17:00.800
<v Speaker 1>your your concept of a pure it of time would

0:17:00.840 --> 0:17:05.199
<v Speaker 1>would also change. But okay, so, uh supposedly devices very

0:17:05.280 --> 0:17:08.480
<v Speaker 1>much like this. We're used to time speeches in courts

0:17:08.520 --> 0:17:12.600
<v Speaker 1>of law circa four thirty BC in Athens, so even

0:17:13.320 --> 0:17:18.359
<v Speaker 1>and ancient Greece we told our politicians, yo, hey, shut

0:17:18.440 --> 0:17:23.880
<v Speaker 1>up for serious, come on, man, sit down, John They

0:17:23.960 --> 0:17:26.120
<v Speaker 1>and okay, I think I think we're going to finally

0:17:26.160 --> 0:17:28.640
<v Speaker 1>have to leap ahead a little bit. Or do I mean,

0:17:28.720 --> 0:17:30.080
<v Speaker 1>I mean, do you want do you want to save

0:17:30.119 --> 0:17:32.000
<v Speaker 1>it for medieval times or do you want to you

0:17:32.040 --> 0:17:34.240
<v Speaker 1>know what? We we can save it for medieval times.

0:17:34.480 --> 0:17:38.520
<v Speaker 1>I'm a little partial to medieval times, Okay, fair enough,

0:17:38.520 --> 0:17:42.199
<v Speaker 1>fair enough, so so I'll just mention that that these

0:17:42.440 --> 0:17:46.640
<v Speaker 1>water clocks went mechanical after a few hundred years by

0:17:46.640 --> 0:17:49.760
<v Speaker 1>by letting water the Grecian water clocks, I should say,

0:17:49.880 --> 0:17:53.159
<v Speaker 1>by letting water drip measuredly into a chamber like you

0:17:53.200 --> 0:17:55.800
<v Speaker 1>were just talking about, you can you can raise not

0:17:55.880 --> 0:17:58.919
<v Speaker 1>just a little bobbin, but like a floating piston, and

0:17:58.960 --> 0:18:02.159
<v Speaker 1>therefore do simple work like like pushing a marker or

0:18:02.240 --> 0:18:04.919
<v Speaker 1>even a gear to turn a pointer. And so between

0:18:05.000 --> 0:18:07.960
<v Speaker 1>like one d b c E and five hundred CE,

0:18:08.440 --> 0:18:11.520
<v Speaker 1>Greeks and Romans both we're trying to make the flow

0:18:11.560 --> 0:18:14.760
<v Speaker 1>more constant by regulating the water pressure. And as a

0:18:14.760 --> 0:18:17.360
<v Speaker 1>result of that, some of the devices that they were

0:18:17.440 --> 0:18:19.880
<v Speaker 1>making could like ring a bell or a gong when

0:18:19.880 --> 0:18:21.800
<v Speaker 1>the water would hit a certain point, or they would

0:18:21.840 --> 0:18:25.240
<v Speaker 1>even like push a mechanism to open little decorative hatches

0:18:25.359 --> 0:18:28.560
<v Speaker 1>containing small figurines that would dance around or or move

0:18:28.800 --> 0:18:33.879
<v Speaker 1>astronaut astrological models. Yeah. Um, And And meanwhile in China,

0:18:34.560 --> 0:18:37.640
<v Speaker 1>mechanical water clocks were also in use from around two

0:18:37.720 --> 0:18:42.480
<v Speaker 1>hundred through around thirt hundred CE, including at least one

0:18:43.000 --> 0:18:46.919
<v Speaker 1>that used this big old water wheel like story and

0:18:46.960 --> 0:18:51.480
<v Speaker 1>a half tall water wheel to power dozens of elaborate

0:18:51.560 --> 0:18:54.280
<v Speaker 1>sounds and mechanisms that would dance around and do weird

0:18:54.280 --> 0:18:57.240
<v Speaker 1>little stuff. Man, and I thought the uh, the church

0:18:57.320 --> 0:19:01.560
<v Speaker 1>near my neighborhood, whenever it's noon or six pm, it

0:19:01.640 --> 0:19:05.040
<v Speaker 1>goes pretty much bonkers with its chimes. I imagine it

0:19:05.080 --> 0:19:08.879
<v Speaker 1>had to be even more spectacular with something along those lines,

0:19:09.520 --> 0:19:13.600
<v Speaker 1>although maybe not necessarily quite as regular, Yeah, I would

0:19:13.640 --> 0:19:16.560
<v Speaker 1>imagine not, but still still a party. Yeah. Yeah, So

0:19:16.680 --> 0:19:18.400
<v Speaker 1>let's get back in the way back machine. We're gonna

0:19:18.440 --> 0:19:22.600
<v Speaker 1>actually jump ahead to medieval Europe and we'll we'll get

0:19:22.600 --> 0:19:26.960
<v Speaker 1>out there. So did you bring your nose? Come on,

0:19:27.560 --> 0:19:31.440
<v Speaker 1>I worked the Renaissance Festival. I've been to dragon Con.

0:19:31.800 --> 0:19:35.680
<v Speaker 1>I can handle medieval Europe. Here we go, Here we go.

0:19:43.200 --> 0:19:49.280
<v Speaker 1>Welcome to medieval Europe. Huzzah. Where food is on a stick.

0:19:50.000 --> 0:19:52.920
<v Speaker 1>And this doesn't look like the Resaissance festival and all.

0:19:53.000 --> 0:19:55.880
<v Speaker 1>This is kind of awful. Yeah, I don't see any

0:19:55.960 --> 0:20:00.560
<v Speaker 1>chicken fried bacon. There's actually awful in the street in Soul.

0:20:00.760 --> 0:20:03.639
<v Speaker 1>That's the kind of awful this is anyway, So it's

0:20:03.680 --> 0:20:07.040
<v Speaker 1>worse than our pus Field trip. Yeah, that was man.

0:20:07.440 --> 0:20:10.960
<v Speaker 1>You never thought you'd look back on that with like nostalgia.

0:20:11.440 --> 0:20:15.760
<v Speaker 1>But here we are in fourteenth century medieval Europe. This

0:20:15.800 --> 0:20:19.920
<v Speaker 1>is about the time where mechanical clocks began to become

0:20:19.960 --> 0:20:24.240
<v Speaker 1>a thing. And at those in those early clocks, they

0:20:24.280 --> 0:20:29.600
<v Speaker 1>had our markings. Uh, some had minute markings, but none

0:20:29.600 --> 0:20:33.840
<v Speaker 1>of them had second markets. And uh. So it would

0:20:33.880 --> 0:20:38.400
<v Speaker 1>actually take about a couple hundred years really sixteenth century

0:20:38.520 --> 0:20:42.200
<v Speaker 1>medieval Europe where you started seeing minutes as a standard

0:20:42.400 --> 0:20:45.040
<v Speaker 1>marking of time. And this is where we take that

0:20:45.160 --> 0:20:48.639
<v Speaker 1>concept we talked about with the geography, and it was

0:20:48.680 --> 0:20:52.440
<v Speaker 1>converted into a time keeping concept. The idea of well,

0:20:52.480 --> 0:20:56.199
<v Speaker 1>we've got these these twelve periods of daylight and twelve

0:20:56.240 --> 0:21:00.000
<v Speaker 1>periods of nighttime that the uh, the Egyptians had proposed.

0:21:00.119 --> 0:21:05.200
<v Speaker 1>The Greeks had formalized that into actual fixed length hours,

0:21:05.320 --> 0:21:08.760
<v Speaker 1>uh for their calculations. We're gonna do that for the

0:21:08.760 --> 0:21:12.199
<v Speaker 1>purposes of keeping time. Then we're going to subdivide that.

0:21:12.440 --> 0:21:15.119
<v Speaker 1>And because they were working with twelves and twenty fours,

0:21:15.119 --> 0:21:18.840
<v Speaker 1>they said, how about we look at sixty. We're looking at,

0:21:18.960 --> 0:21:22.680
<v Speaker 1>you know, a division of sixty smaller increments that make

0:21:22.760 --> 0:21:29.520
<v Speaker 1>up one full hour, and then eventually you think about

0:21:29.520 --> 0:21:31.119
<v Speaker 1>that long enough and you realize, all right, well we

0:21:31.160 --> 0:21:34.159
<v Speaker 1>can subdivide that even further. A minute is still a

0:21:34.160 --> 0:21:36.840
<v Speaker 1>pretty long amount of time depending on what you need

0:21:36.880 --> 0:21:40.760
<v Speaker 1>to do. Right, some things, a minute's no time at all, right,

0:21:40.840 --> 0:21:43.680
<v Speaker 1>If if it's something really fun that you love to do.

0:21:44.000 --> 0:21:47.680
<v Speaker 1>Maybe you're riding on a horse, jousting your Henry the eighth,

0:21:48.200 --> 0:21:51.080
<v Speaker 1>a minute is like no time at all. But maybe

0:21:51.240 --> 0:21:54.480
<v Speaker 1>you're being accused of witchcraft, being dunked under the water.

0:21:54.640 --> 0:21:57.160
<v Speaker 1>A minute's a really long time. At that point you're

0:21:57.160 --> 0:21:59.480
<v Speaker 1>going like, can we break this period up a little bit?

0:21:59.440 --> 0:22:01.280
<v Speaker 1>And maybe we and look at like a fifteen second

0:22:01.320 --> 0:22:04.200
<v Speaker 1>interval if you're gonna be you know, slowly like drowning me,

0:22:04.400 --> 0:22:07.920
<v Speaker 1>like i'd like to can we negotiate this at all?

0:22:08.640 --> 0:22:11.560
<v Speaker 1>So they looked at the round face of the clock

0:22:11.600 --> 0:22:13.840
<v Speaker 1>that they had designed, and the division of the day

0:22:13.960 --> 0:22:16.640
<v Speaker 1>into really twelve segments. You can think of twenty four,

0:22:16.680 --> 0:22:19.560
<v Speaker 1>but really most clocks are twelve segments, right, And then

0:22:19.560 --> 0:22:21.720
<v Speaker 1>we just amend either a M or p M in

0:22:21.720 --> 0:22:24.600
<v Speaker 1>our brains to denote whether it's in the morning or

0:22:24.680 --> 0:22:28.199
<v Speaker 1>it's in the evening UH, and they adopted that sexic

0:22:28.280 --> 0:22:31.560
<v Speaker 1>asimal system, and each hour was divided by sixty and

0:22:31.600 --> 0:22:34.720
<v Speaker 1>two minutes and dividenes again in sixty into seconds. And

0:22:34.760 --> 0:22:37.080
<v Speaker 1>this was the first time we really had a definition

0:22:37.119 --> 0:22:40.399
<v Speaker 1>of a second in terms of timekeeping. UH and and

0:22:40.480 --> 0:22:43.880
<v Speaker 1>all of this, I imagine was also partially driven by

0:22:44.000 --> 0:22:47.080
<v Speaker 1>just the mechanical complexity of clocks in the capacity. But

0:22:47.240 --> 0:22:50.080
<v Speaker 1>because a mechanical clock, if if you guys aren't familiar

0:22:50.119 --> 0:22:52.480
<v Speaker 1>with the inner workings of a of your basic wall

0:22:52.480 --> 0:22:54.600
<v Speaker 1>clock or watch or something like that, is based on

0:22:54.800 --> 0:22:59.160
<v Speaker 1>a coiled spring that you apply tension to buy either

0:22:59.240 --> 0:23:02.879
<v Speaker 1>winding it or exposing into some kind of electricity like

0:23:02.920 --> 0:23:07.359
<v Speaker 1>electrical pulses. And and then UH in the case of

0:23:07.359 --> 0:23:11.600
<v Speaker 1>these these earlier clocks, the capacity of gears that you

0:23:11.640 --> 0:23:16.280
<v Speaker 1>attached to the spring to to react in in regular movements. Yeah,

0:23:16.280 --> 0:23:18.600
<v Speaker 1>it's kind of like a transmission, you know. You use

0:23:18.680 --> 0:23:23.240
<v Speaker 1>smaller gears and larger gears to dictate exactly how frequently

0:23:23.320 --> 0:23:25.720
<v Speaker 1>a gear will turn within a given amount of time,

0:23:25.960 --> 0:23:29.080
<v Speaker 1>assuming that in fact the clock is wound, and then

0:23:29.160 --> 0:23:34.520
<v Speaker 1>you get the mechanical UH performance where it rotates once

0:23:34.560 --> 0:23:38.959
<v Speaker 1>an hour. For that you know, for the uh, the

0:23:38.960 --> 0:23:42.680
<v Speaker 1>the little the little mickey arm, yes, and and so so.

0:23:42.720 --> 0:23:46.440
<v Speaker 1>As as the spring making and gear making techniques became

0:23:46.480 --> 0:23:49.040
<v Speaker 1>more complex, I'm sure that people started going like, surely

0:23:49.080 --> 0:23:51.560
<v Speaker 1>we can make this more complicated, let's put some seconds

0:23:51.600 --> 0:23:53.679
<v Speaker 1>in there. And in fact, you know, for a lot

0:23:53.720 --> 0:23:57.440
<v Speaker 1>of people's seconds weren't really that important, not yet anyway.

0:23:57.720 --> 0:24:00.040
<v Speaker 1>As much as I joked about the whole dunking of

0:24:00.080 --> 0:24:04.119
<v Speaker 1>people to see if they're witches or not, that was

0:24:04.200 --> 0:24:07.640
<v Speaker 1>not really on the forefront of people's minds in that

0:24:07.720 --> 0:24:13.280
<v Speaker 1>particular scenario. Yeah, but the second was really um thought

0:24:13.280 --> 0:24:18.000
<v Speaker 1>of as important for making those astronomical calculations, and in fact,

0:24:18.880 --> 0:24:21.800
<v Speaker 1>we attempted to standardize it with the International System of

0:24:21.920 --> 0:24:26.960
<v Speaker 1>Units and the The definition for a very long time

0:24:27.040 --> 0:24:29.720
<v Speaker 1>was that a second is a fraction of a mean

0:24:29.960 --> 0:24:33.080
<v Speaker 1>solar day in a tropical year. But all of that

0:24:33.160 --> 0:24:36.320
<v Speaker 1>changed in nineteen sixty seven. So I think we should

0:24:36.320 --> 0:24:38.280
<v Speaker 1>probably just jump the way back machine, go back to

0:24:38.320 --> 0:24:43.840
<v Speaker 1>the studio. Okay, Okay, that's that's fair. I don't I

0:24:44.080 --> 0:24:46.640
<v Speaker 1>I'm pretty much done with history for the day. Yeah,

0:24:46.760 --> 0:24:48.760
<v Speaker 1>I think we can talk a little bit about the

0:24:48.760 --> 0:24:51.720
<v Speaker 1>the nineteen sixties, but um, you know, we don't need

0:24:51.760 --> 0:24:55.239
<v Speaker 1>to go there. That's not that long ago, all right,

0:24:55.320 --> 0:25:08.800
<v Speaker 1>and the smells will be barely exciting. Yeah, okay, we're back, man.

0:25:08.960 --> 0:25:15.880
<v Speaker 1>I just realized we've seen the Beatles another time. Yeah, yeah, sure,

0:25:15.920 --> 0:25:17.560
<v Speaker 1>sure we can. We can always rev it up again.

0:25:18.119 --> 0:25:21.720
<v Speaker 1>Uh okay. Actually, before we talk about the nineteen sixties,

0:25:21.760 --> 0:25:24.040
<v Speaker 1>I need to talk for a second about for a

0:25:24.200 --> 0:25:31.400
<v Speaker 1>second about the nineteen forties, because there was a physics

0:25:31.400 --> 0:25:35.600
<v Speaker 1>professor at Columbia University by the name of Isidor Rabbi.

0:25:35.920 --> 0:25:38.960
<v Speaker 1>I think I'm saying that right. Uh. And anyway, he

0:25:39.080 --> 0:25:43.320
<v Speaker 1>proposed that a very precise clock could be constructed by

0:25:43.400 --> 0:25:48.760
<v Speaker 1>measuring the vibration of atoms, and as far back as

0:25:48.760 --> 0:25:52.000
<v Speaker 1>the ninetties had been experimenting with with this discovery that

0:25:52.240 --> 0:25:55.600
<v Speaker 1>when some atoms are exposed to some wavelengths of electro

0:25:56.040 --> 0:26:01.600
<v Speaker 1>magnetic energy, those atoms vibrate very, very consistently, So you

0:26:01.640 --> 0:26:05.479
<v Speaker 1>can measure the oscillations and then use those to build

0:26:05.640 --> 0:26:07.920
<v Speaker 1>a standard for the passage of time. And what is

0:26:07.960 --> 0:26:11.280
<v Speaker 1>actually happening here is that if you have the right

0:26:11.359 --> 0:26:15.600
<v Speaker 1>frequency of energy hitting a particular type of atom, it

0:26:15.680 --> 0:26:20.400
<v Speaker 1>excites the electrons in that atom to higher energy bands

0:26:20.480 --> 0:26:23.800
<v Speaker 1>and then those electrons will come back down to their

0:26:23.840 --> 0:26:27.600
<v Speaker 1>normal energy band. That's the vibration there. But if you're

0:26:27.600 --> 0:26:31.480
<v Speaker 1>talking about a resonant frequency, that in that we talked

0:26:31.480 --> 0:26:34.080
<v Speaker 1>about resonance before resonance is this idea that you have

0:26:34.160 --> 0:26:38.080
<v Speaker 1>found a frequency that resonates with a particular material. In

0:26:38.080 --> 0:26:40.640
<v Speaker 1>this case we're talking about atoms, and it makes them

0:26:41.160 --> 0:26:44.919
<v Speaker 1>vibrate themselves. So, for example, we see this in the

0:26:44.920 --> 0:26:48.360
<v Speaker 1>macro level with the opera singer singing that note that

0:26:48.720 --> 0:26:51.679
<v Speaker 1>is resonant with a particular crystal glass, and it causes

0:26:51.720 --> 0:26:54.560
<v Speaker 1>the glass to shatter. Uh same sort of thing. Instead

0:26:54.600 --> 0:26:57.080
<v Speaker 1>of shattering atoms, you're just making them wiggle on wiggle,

0:26:57.520 --> 0:27:00.879
<v Speaker 1>very precisely, and very quickly, very very quickly, as it

0:27:00.920 --> 0:27:03.280
<v Speaker 1>turns out. So, based on all of this, in nineteen

0:27:03.320 --> 0:27:06.359
<v Speaker 1>sixty seven, the International System of Units wound up changing

0:27:06.359 --> 0:27:09.960
<v Speaker 1>their definition of a second to the vibe to a

0:27:10.000 --> 0:27:13.680
<v Speaker 1>particular vibration of the ces um atom or a scum

0:27:13.680 --> 0:27:16.600
<v Speaker 1>atom a given sazon atom at any given time um

0:27:16.640 --> 0:27:21.240
<v Speaker 1>and these suckers vibrate so consistently at when exposed a

0:27:21.240 --> 0:27:23.919
<v Speaker 1>certain wavelengths of light, and uh so a second was

0:27:23.960 --> 0:27:28.320
<v Speaker 1>defined as nine billion, one ninety two million, six hundred

0:27:28.440 --> 0:27:33.800
<v Speaker 1>thirty one thousand, seven hundred and seventy cycles of those vibrations. Well,

0:27:33.880 --> 0:27:38.440
<v Speaker 1>there's your problem. I lose track right around four billion.

0:27:39.000 --> 0:27:42.440
<v Speaker 1>I just lose interest. But now that's amazing. The thought

0:27:42.520 --> 0:27:47.880
<v Speaker 1>of being able to to define a second as something

0:27:47.920 --> 0:27:53.040
<v Speaker 1>that is more than nine billion vibrations of a particular atom.

0:27:53.080 --> 0:27:56.000
<v Speaker 1>Now you might wonder, how the heck can you turn

0:27:56.119 --> 0:27:59.679
<v Speaker 1>that into an atomic clock? Yeah, how do you measure that?

0:27:59.680 --> 0:28:04.160
<v Speaker 1>That's pretty weird. So I'm gonna do my best to

0:28:04.200 --> 0:28:08.760
<v Speaker 1>describe this. Please keep in mind I was a liberal

0:28:08.880 --> 0:28:11.960
<v Speaker 1>arts major. So here we go. First, the thing that

0:28:12.080 --> 0:28:14.879
<v Speaker 1>these are the earlier atomic clocks I'm going to talk about.

0:28:14.920 --> 0:28:17.480
<v Speaker 1>Now we have a different type of atomic clock will

0:28:17.480 --> 0:28:20.960
<v Speaker 1>be chatting about shortly, and then and even more advanced

0:28:21.000 --> 0:28:24.280
<v Speaker 1>type of clock to talk about the future of the second.

0:28:24.880 --> 0:28:28.920
<v Speaker 1>But first, you would heat caesium so that atoms would

0:28:28.960 --> 0:28:33.359
<v Speaker 1>boil off of the gas typically, and you would pass

0:28:33.440 --> 0:28:36.200
<v Speaker 1>that down a tube that's maintained at a high vacuum.

0:28:36.960 --> 0:28:39.600
<v Speaker 1>So then you would use magnetic fields to sort through

0:28:39.960 --> 0:28:42.920
<v Speaker 1>the caesium atoms and passing the ones with the right

0:28:43.040 --> 0:28:44.880
<v Speaker 1>energy state to the next level. So in other words,

0:28:45.240 --> 0:28:49.560
<v Speaker 1>you're separating out ions from from regular caesium atoms, and

0:28:49.600 --> 0:28:51.520
<v Speaker 1>you want just the specific ones that are going to

0:28:51.520 --> 0:28:54.600
<v Speaker 1>react to the microwave radiation you're going to pass through it.

0:28:55.400 --> 0:28:58.760
<v Speaker 1>So once you've sorted them and all the ones that

0:28:58.800 --> 0:29:01.760
<v Speaker 1>you want are going the right pathway, the atoms will

0:29:01.760 --> 0:29:04.240
<v Speaker 1>then pass through a microwave field that has a varying

0:29:04.280 --> 0:29:09.840
<v Speaker 1>frequency within an extremely narrow range of frequencies. One of

0:29:09.880 --> 0:29:14.960
<v Speaker 1>the frequencies within that range is that magic nine billion, million,

0:29:15.000 --> 0:29:20.680
<v Speaker 1>six seven seventy hurts that corresponds with the vibrations of

0:29:20.720 --> 0:29:24.000
<v Speaker 1>the caesium atom. So when a caesium atom encounters a

0:29:24.000 --> 0:29:28.360
<v Speaker 1>microwave at that frequency, it changes its energy state. It wiggles,

0:29:29.000 --> 0:29:33.520
<v Speaker 1>and the atoms continue on, and another magnetic field separates

0:29:33.520 --> 0:29:36.000
<v Speaker 1>out those that had their energy state altered by the

0:29:36.000 --> 0:29:38.800
<v Speaker 1>microwaves and the ones that did not have their energy

0:29:38.880 --> 0:29:42.360
<v Speaker 1>state altered, so the wigglers versus the non wigglers exactly,

0:29:42.640 --> 0:29:46.120
<v Speaker 1>and a detector picks up those atoms the wigglers, and

0:29:46.160 --> 0:29:49.160
<v Speaker 1>that output is data that is proportional to the number

0:29:49.200 --> 0:29:52.600
<v Speaker 1>of caesium atoms striking it. In other words, the output

0:29:52.720 --> 0:29:56.400
<v Speaker 1>says how many atoms were wigglers. And then that way

0:29:56.440 --> 0:30:00.040
<v Speaker 1>you can actually start to tune your device so it

0:30:00.360 --> 0:30:03.600
<v Speaker 1>is closer to the proper frequency, and you'll see that

0:30:03.680 --> 0:30:06.480
<v Speaker 1>number go up. That that number goes because you'll hit

0:30:06.560 --> 0:30:08.640
<v Speaker 1>more ces um adams with the right frequency. You start

0:30:08.680 --> 0:30:12.080
<v Speaker 1>to narrow it down until you get just the right tuning,

0:30:12.360 --> 0:30:15.760
<v Speaker 1>and once you're there, you're you stop. You have you

0:30:15.800 --> 0:30:18.760
<v Speaker 1>have reached the point where you are creating the pulse

0:30:18.920 --> 0:30:23.440
<v Speaker 1>that is a second each time um and then you

0:30:23.640 --> 0:30:25.520
<v Speaker 1>So what you would do is you take your frequency

0:30:26.120 --> 0:30:28.800
<v Speaker 1>number that you had arrived at and the number of

0:30:29.040 --> 0:30:31.680
<v Speaker 1>uh that that really big number we've said a few

0:30:31.720 --> 0:30:34.200
<v Speaker 1>times already, and when you divide the two, it should

0:30:34.280 --> 0:30:37.480
<v Speaker 1>end up being one. That means one second. Right, So

0:30:37.880 --> 0:30:40.160
<v Speaker 1>it's it's a little weird to think about, but yes,

0:30:40.480 --> 0:30:43.040
<v Speaker 1>it all comes down to how many of those wigglers

0:30:43.080 --> 0:30:44.880
<v Speaker 1>are you picking up? And as you pick up more

0:30:44.920 --> 0:30:47.320
<v Speaker 1>and more, you get these pulses that end up being

0:30:47.480 --> 0:30:54.000
<v Speaker 1>exactly or at least mostly exactly one second. It turns

0:30:54.000 --> 0:30:56.960
<v Speaker 1>out that as we get better at measuring things, our

0:30:57.160 --> 0:31:00.960
<v Speaker 1>definition of what exactly is changes. Now. I love that.

0:31:01.880 --> 0:31:05.680
<v Speaker 1>So atomic time keeping created a new approach called coordinated

0:31:05.880 --> 0:31:09.400
<v Speaker 1>universal time, which, despite the fact that would usually make

0:31:09.440 --> 0:31:13.880
<v Speaker 1>the acronym cut cut, it's actually U t C. That's

0:31:13.880 --> 0:31:17.640
<v Speaker 1>what's universal time coordinated. I guess. In the United States,

0:31:17.880 --> 0:31:21.240
<v Speaker 1>we depend upon the U. S. Naval Observatories, master Clock,

0:31:21.320 --> 0:31:24.120
<v Speaker 1>and the National Institutes of Standards and Technology in Boulder,

0:31:24.160 --> 0:31:27.960
<v Speaker 1>Colorado to regulate our time. They're the ones telling us

0:31:28.000 --> 0:31:31.240
<v Speaker 1>what time it is. In other words, so interesting fact

0:31:31.800 --> 0:31:36.360
<v Speaker 1>U t C and astronomical time don't quite match up.

0:31:36.800 --> 0:31:42.560
<v Speaker 1>So we've got a second that is very precise. But

0:31:42.880 --> 0:31:45.160
<v Speaker 1>when you change it to the real world and the

0:31:45.200 --> 0:31:48.560
<v Speaker 1>way that the Earth rotates, it doesn't. The Earth does

0:31:48.600 --> 0:31:52.920
<v Speaker 1>not rotate according to our beautiful math. In other words,

0:31:52.960 --> 0:31:56.000
<v Speaker 1>so once in a while, I can't trust it for anything.

0:31:56.040 --> 0:31:58.400
<v Speaker 1>I know it's I mean, i'd leave, but it's where

0:31:58.440 --> 0:32:01.600
<v Speaker 1>I've got all my stuff. So it turns out like

0:32:01.720 --> 0:32:03.600
<v Speaker 1>every now and again, we have to throw in a

0:32:03.680 --> 0:32:08.600
<v Speaker 1>leap second, leap second, leap second every ten years or so,

0:32:08.720 --> 0:32:11.720
<v Speaker 1>You've got about eight minutes out of that entire decade

0:32:11.960 --> 0:32:14.440
<v Speaker 1>where you where some of those minutes, those eight minutes

0:32:14.680 --> 0:32:18.520
<v Speaker 1>they actually have sixty one seconds as opposed to sixty seconds. Okay,

0:32:18.600 --> 0:32:22.640
<v Speaker 1>So is so is this because are these clocks aren't

0:32:22.880 --> 0:32:25.800
<v Speaker 1>quite precise enough. Even though we've gotten this precision down

0:32:25.880 --> 0:32:28.360
<v Speaker 1>to the vibration of an atom, they're they're just not

0:32:30.200 --> 0:32:33.000
<v Speaker 1>as precise as they could be. Well, that's that's definitely

0:32:33.080 --> 0:32:36.600
<v Speaker 1>part of the problem, because as time goes on, the

0:32:36.880 --> 0:32:41.000
<v Speaker 1>slight imprecision of these clocks becomes more and more noticeable,

0:32:41.040 --> 0:32:44.480
<v Speaker 1>and you have to correct for that. And it's really

0:32:44.560 --> 0:32:48.479
<v Speaker 1>interesting that such a thing could, even like it's so

0:32:48.520 --> 0:32:51.400
<v Speaker 1>hard to imagine something so small we're talking about the

0:32:51.440 --> 0:32:55.400
<v Speaker 1>difference of nanoseconds here could actually matter that much. It's

0:32:55.440 --> 0:32:57.840
<v Speaker 1>almost like if you were to look at, say, an aunt,

0:32:58.320 --> 0:33:01.400
<v Speaker 1>and you've said that little any ant couldn't do anything

0:33:01.400 --> 0:33:04.200
<v Speaker 1>to me, and then you saw ten million ants and

0:33:04.240 --> 0:33:07.040
<v Speaker 1>you thought, so when there are ten million of them,

0:33:07.080 --> 0:33:09.120
<v Speaker 1>they actually do matter. It's sort of the same with

0:33:09.160 --> 0:33:12.440
<v Speaker 1>these name seconds. Uh. But let's talk a little bit

0:33:12.480 --> 0:33:16.280
<v Speaker 1>about a slightly newer version of atomic clock, the microwave

0:33:16.480 --> 0:33:20.600
<v Speaker 1>fountain clock, which does not involve putting one of those

0:33:20.640 --> 0:33:24.960
<v Speaker 1>little fountains from like a uh, like a bookstore or

0:33:25.000 --> 0:33:27.760
<v Speaker 1>something inside a microwave. Don't do that. That's not how

0:33:27.800 --> 0:33:30.239
<v Speaker 1>you're gonna get a microwave fountain clock. That's how you're

0:33:30.240 --> 0:33:34.440
<v Speaker 1>gonna get a broken microwave. So they use a slightly

0:33:34.440 --> 0:33:38.400
<v Speaker 1>different method, but they still depend upon caesium atoms and microwaves.

0:33:38.440 --> 0:33:41.320
<v Speaker 1>So you take caesium gas and you introduce it into

0:33:41.360 --> 0:33:44.520
<v Speaker 1>a chamber that has six lasers, all mounted at right

0:33:44.560 --> 0:33:46.520
<v Speaker 1>angles to each other. So you've got like up and

0:33:46.600 --> 0:33:49.360
<v Speaker 1>down and uh and like some on the on the

0:33:49.360 --> 0:33:52.800
<v Speaker 1>actual walls point and inwards. It looks like a James

0:33:52.840 --> 0:33:57.520
<v Speaker 1>Bond trap, but instead of saying no misr caes um,

0:33:57.560 --> 0:34:00.960
<v Speaker 1>I expect you to die, the lasers are actually slowing

0:34:01.080 --> 0:34:03.920
<v Speaker 1>down the movement of those caesium atoms. Okay, so it's

0:34:03.920 --> 0:34:07.040
<v Speaker 1>an atom trap, not at James Bond trap exactly. And

0:34:07.280 --> 0:34:11.040
<v Speaker 1>we also know that movement and heat are essentially the

0:34:11.080 --> 0:34:13.960
<v Speaker 1>same thing. Right as adams move, there are there warm.

0:34:14.000 --> 0:34:15.879
<v Speaker 1>When you start to slow them down, they cool down.

0:34:16.800 --> 0:34:19.160
<v Speaker 1>So the goal is to cool them down to close

0:34:19.200 --> 0:34:23.960
<v Speaker 1>to absolute zero. Once they're at that point, they are

0:34:24.160 --> 0:34:26.839
<v Speaker 1>forming into kind of balls of atoms. So you've got

0:34:26.880 --> 0:34:31.839
<v Speaker 1>these little caesium gas balls that are suspended because they've

0:34:31.840 --> 0:34:34.560
<v Speaker 1>been slowed down so much, and then you use a

0:34:34.560 --> 0:34:38.800
<v Speaker 1>couple of lasers to push them up into a microwave chamber.

0:34:38.920 --> 0:34:42.440
<v Speaker 1>This is the fountain action. So if you imagine a fountain,

0:34:42.440 --> 0:34:45.160
<v Speaker 1>that's that's just shooting straight up, the water shoot straight up.

0:34:45.400 --> 0:34:49.400
<v Speaker 1>In this case, lasers are pushing that caesium ball up

0:34:49.440 --> 0:34:53.400
<v Speaker 1>into the microwave chamber. And then those particular lasers, the

0:34:53.400 --> 0:34:56.399
<v Speaker 1>ones that are pushing the caesium atoms, turn off. Then

0:34:56.440 --> 0:34:59.799
<v Speaker 1>you've got microwaves within that chamber. Some of the microwaves

0:34:59.800 --> 0:35:03.319
<v Speaker 1>are at the proper frequency to make caesium vibrate, and

0:35:03.360 --> 0:35:07.480
<v Speaker 1>when they do encounter the caesium atoms, the atoms will

0:35:08.160 --> 0:35:12.560
<v Speaker 1>change energy states. And as those caesium atoms leave the

0:35:12.560 --> 0:35:17.080
<v Speaker 1>microwave chamber, they encounter yet another laser. We love our lasers.

0:35:18.040 --> 0:35:20.520
<v Speaker 1>Caesium atoms that have been altered by the proper resonant

0:35:20.520 --> 0:35:24.919
<v Speaker 1>frequency fluoresce. They light up and a detector makes note

0:35:24.920 --> 0:35:27.080
<v Speaker 1>of that, and then the system is dialed in. So

0:35:27.160 --> 0:35:29.600
<v Speaker 1>it sounds very similar to the old atomic clock, right.

0:35:30.120 --> 0:35:34.080
<v Speaker 1>They dial it in until that maximum fluorescence is achieved,

0:35:34.239 --> 0:35:36.840
<v Speaker 1>and that defines the natural resonance frequency of the caesium

0:35:36.840 --> 0:35:41.319
<v Speaker 1>atoms and can be used to define a second But

0:35:41.360 --> 0:35:45.600
<v Speaker 1>they these also as accurate as they are, they do

0:35:46.600 --> 0:35:52.640
<v Speaker 1>not keep time perfectly forever. Yeah, they do lose time

0:35:53.320 --> 0:35:57.560
<v Speaker 1>over time. And uh, and we're talking about like a

0:35:57.640 --> 0:36:01.279
<v Speaker 1>nanosecond a month, which seems nothing. I mean, I was

0:36:01.280 --> 0:36:04.600
<v Speaker 1>going to waste it anyway. I was probably spending that

0:36:04.640 --> 0:36:09.040
<v Speaker 1>playing bulled. I was probably playing Overwatch. Okay, uh, but

0:36:09.040 --> 0:36:11.719
<v Speaker 1>but but it does but it does that up eventually

0:36:11.760 --> 0:36:16.160
<v Speaker 1>and and especially digitally, so nonetheless, Okay, we should say

0:36:16.160 --> 0:36:19.080
<v Speaker 1>that the atomic clocks are are really cool for a

0:36:19.160 --> 0:36:22.120
<v Speaker 1>number of reasons. I think a number one because they

0:36:22.160 --> 0:36:29.040
<v Speaker 1>are what keeps our our geo syncritous orbiting satellites basically

0:36:29.200 --> 0:36:31.720
<v Speaker 1>not running into each other. Right. Yeah, when you're talking

0:36:31.719 --> 0:36:35.120
<v Speaker 1>about things like satellites, like communication satellites, or you're talking

0:36:35.120 --> 0:36:39.919
<v Speaker 1>about GPS satellites, you need to have extremely precise time

0:36:40.000 --> 0:36:43.040
<v Speaker 1>keeping in order for those operations to to work properly.

0:36:43.600 --> 0:36:46.520
<v Speaker 1>And in fact, this comes with a whole host of

0:36:46.600 --> 0:36:51.239
<v Speaker 1>problems and challenges. Um, but you're looking at an accuracy

0:36:51.280 --> 0:36:54.040
<v Speaker 1>that needs to be down to billionths of a second.

0:36:54.160 --> 0:36:56.839
<v Speaker 1>So when you have like a nanosecond error in there,

0:36:56.920 --> 0:37:01.360
<v Speaker 1>that's actually a big deal. So each GPS satellite actually

0:37:01.400 --> 0:37:03.840
<v Speaker 1>has four atomic clocks on board, and there are twenty

0:37:03.840 --> 0:37:07.800
<v Speaker 1>four GPS satellites in orbit, and uh a GPS receiver

0:37:07.880 --> 0:37:10.960
<v Speaker 1>on the ground can determine its location by triangulating broadcast

0:37:10.960 --> 0:37:14.759
<v Speaker 1>signals sent from multiple GPS satellites. And then what does

0:37:14.840 --> 0:37:16.520
<v Speaker 1>is it looks at the time stamp on each of

0:37:16.520 --> 0:37:19.240
<v Speaker 1>those factors in how long would it take the signal

0:37:19.320 --> 0:37:22.520
<v Speaker 1>to travel from that time stamp and where you would be.

0:37:22.840 --> 0:37:25.319
<v Speaker 1>You actually have two answers to that, but one of

0:37:25.320 --> 0:37:28.560
<v Speaker 1>them happens to be inside the Earth, So your GPS

0:37:29.280 --> 0:37:33.160
<v Speaker 1>usually ignores that answer. Generally, Yeah, it's like, all right,

0:37:33.640 --> 0:37:36.279
<v Speaker 1>obviously can't be that one, so you have to be here.

0:37:37.280 --> 0:37:40.440
<v Speaker 1>But knowing that you have these potentials for errors, you

0:37:40.560 --> 0:37:46.480
<v Speaker 1>actually that that translates into a less precise positioning. When

0:37:46.480 --> 0:37:48.719
<v Speaker 1>you're getting your read out, it may be accurate to

0:37:48.800 --> 0:37:52.000
<v Speaker 1>just a few meters, which is fine if you're traveling

0:37:52.000 --> 0:37:54.440
<v Speaker 1>around and you're driving and you know, generally speaking, you're

0:37:54.480 --> 0:37:57.480
<v Speaker 1>not gonna have an issue where you're suddenly realizing need

0:37:57.520 --> 0:38:00.359
<v Speaker 1>to turn a mile back. Share it, but it does

0:38:00.400 --> 0:38:04.320
<v Speaker 1>explain why. For example, if you have your WiFi off,

0:38:04.400 --> 0:38:07.799
<v Speaker 1>your GPS may think that you're on the other side

0:38:07.800 --> 0:38:10.040
<v Speaker 1>of a bridge that you haven't crossed yet, or something

0:38:10.080 --> 0:38:12.680
<v Speaker 1>like that or yeah, or I'll read you the same

0:38:12.760 --> 0:38:15.960
<v Speaker 1>instruction off twice because it's just glitching as to where

0:38:16.040 --> 0:38:19.000
<v Speaker 1>precisely your your car is. Or if you're using something

0:38:19.040 --> 0:38:23.799
<v Speaker 1>like a car service app and you see where you

0:38:23.840 --> 0:38:25.840
<v Speaker 1>are and you know where you are based like you

0:38:25.880 --> 0:38:27.799
<v Speaker 1>see where you are on the map and you see

0:38:27.800 --> 0:38:30.080
<v Speaker 1>where you are in real life, and you realize that

0:38:30.080 --> 0:38:32.440
<v Speaker 1>if you pen the point that it shows you on

0:38:32.480 --> 0:38:34.440
<v Speaker 1>the map, you're gonna have to walk another block to

0:38:34.480 --> 0:38:36.480
<v Speaker 1>get to that car. You're like, no, I want to

0:38:36.520 --> 0:38:42.400
<v Speaker 1>be right. Those apps are particularly bad at that. I

0:38:42.440 --> 0:38:44.799
<v Speaker 1>don't know what the issue is. I don't know if

0:38:44.800 --> 0:38:47.080
<v Speaker 1>it's on the app side or if it's my phone's GPS.

0:38:47.200 --> 0:38:53.160
<v Speaker 1>But anyway, So, one of the cool things about space

0:38:53.280 --> 0:38:55.439
<v Speaker 1>and satellites in time is that you have to take

0:38:55.480 --> 0:39:00.360
<v Speaker 1>into account both special and general relativity. That's always sighting

0:39:00.440 --> 0:39:07.000
<v Speaker 1>because it messes with dime. So right, okay, because because

0:39:07.640 --> 0:39:11.240
<v Speaker 1>satellites are are are moving relative to a single point

0:39:11.280 --> 0:39:13.839
<v Speaker 1>on the ground. Yes, well, and if you're talking about

0:39:13.840 --> 0:39:17.160
<v Speaker 1>a geosynchronous satellite, it's moving. It's moving like if you

0:39:17.200 --> 0:39:19.080
<v Speaker 1>were looking up you would always see it, right if

0:39:19.080 --> 0:39:21.080
<v Speaker 1>you were directly below it, which means it actually has

0:39:21.120 --> 0:39:23.560
<v Speaker 1>to travel faster. It's going a further distance in the

0:39:23.600 --> 0:39:25.759
<v Speaker 1>same amount of time, so it's traveling faster than the

0:39:25.760 --> 0:39:28.680
<v Speaker 1>air's rotation share the same way that a track runner

0:39:28.800 --> 0:39:31.360
<v Speaker 1>on the outer side of the track is going to

0:39:31.480 --> 0:39:33.080
<v Speaker 1>have to run a little bit faster than the inner

0:39:33.120 --> 0:39:36.600
<v Speaker 1>truck crowder to keep up. Exactly. So you start to think,

0:39:36.600 --> 0:39:39.759
<v Speaker 1>all right, we're talking about time dilation here, how does that?

0:39:40.520 --> 0:39:43.000
<v Speaker 1>How big a problem is that? It's pretty huge. So

0:39:43.080 --> 0:39:45.120
<v Speaker 1>we just talked about how a nanosecond a month was

0:39:45.120 --> 0:39:47.800
<v Speaker 1>a big deal. First of all, you have to look

0:39:47.880 --> 0:39:51.520
<v Speaker 1>at special relativity. That's the one with the time dilation effect.

0:39:51.520 --> 0:39:54.000
<v Speaker 1>That's when you're talking about the speed that ends up

0:39:54.480 --> 0:39:58.200
<v Speaker 1>about seven micro seconds of difference. That means the clocks

0:39:58.320 --> 0:40:02.600
<v Speaker 1>aboard the satellite, due to special relativity, we'll move seven

0:40:02.680 --> 0:40:07.359
<v Speaker 1>micro seconds slower than a clock on the ground. Kay,

0:40:08.160 --> 0:40:10.240
<v Speaker 1>So that means you have to figure that out factor

0:40:10.280 --> 0:40:14.279
<v Speaker 1>that in except you also have to remember about general relativity.

0:40:14.520 --> 0:40:17.000
<v Speaker 1>The general relativity tells us that the satellite is orbiting

0:40:17.040 --> 0:40:19.080
<v Speaker 1>high above the Earth, where the curvature of space time

0:40:19.239 --> 0:40:22.400
<v Speaker 1>is less than what we experience here on the Earth's surface.

0:40:23.600 --> 0:40:26.960
<v Speaker 1>Exactly the Earth is a giant mass. For us, it's

0:40:26.960 --> 0:40:29.000
<v Speaker 1>a giant mass. For the Sun, it's nothing, but for

0:40:29.080 --> 0:40:31.399
<v Speaker 1>us it's for us, it's pretty big. Again, it's where

0:40:31.440 --> 0:40:34.640
<v Speaker 1>we keep all our stuff. So there's a pretty big mass. Uh.

0:40:34.680 --> 0:40:37.840
<v Speaker 1>And so that it so. So a clock here on

0:40:37.840 --> 0:40:40.400
<v Speaker 1>on on the ground, the clock on my on my wrist,

0:40:40.440 --> 0:40:44.479
<v Speaker 1>if I had such a thing, would be it would

0:40:44.480 --> 0:40:47.040
<v Speaker 1>actually be going faster. It would be going faster because

0:40:47.080 --> 0:40:50.000
<v Speaker 1>of the curvature of spacetime, so it would actually be

0:40:50.040 --> 0:40:53.920
<v Speaker 1>going your wristwatch clock would be going slower than the

0:40:53.960 --> 0:40:57.400
<v Speaker 1>one that's aboard the satellite. So special relativity says that

0:40:57.440 --> 0:41:00.000
<v Speaker 1>the clock aboard the satellite is gonna go a little

0:41:00.040 --> 0:41:01.759
<v Speaker 1>slower than ours. Right, that's the whole idea that if

0:41:01.760 --> 0:41:03.520
<v Speaker 1>you were to travel it near the speed of light

0:41:03.800 --> 0:41:07.080
<v Speaker 1>and came back, time would have passed less. Time would

0:41:07.120 --> 0:41:09.200
<v Speaker 1>have seemed to have passed to you than to everybody

0:41:09.200 --> 0:41:13.399
<v Speaker 1>on Earth. But according to general relativity, it's the clock

0:41:13.400 --> 0:41:18.120
<v Speaker 1>and the satellite is going faster exactly, so microseconds, so

0:41:18.160 --> 0:41:20.799
<v Speaker 1>you have to, yes, exactly, You've got to take the

0:41:20.800 --> 0:41:23.680
<v Speaker 1>seven microseconds where it would have been going slower, and

0:41:23.719 --> 0:41:26.000
<v Speaker 1>the forty five microseconds where it would be going faster,

0:41:26.280 --> 0:41:29.000
<v Speaker 1>and you come up with thirty eight microseconds distance difference,

0:41:29.320 --> 0:41:32.960
<v Speaker 1>and so GPS systems take this into account. I know,

0:41:33.040 --> 0:41:35.320
<v Speaker 1>I just had GPS systems and I'm like saying, a

0:41:35.440 --> 0:41:37.359
<v Speaker 1>t M machine and pin number, But it doesn't matter.

0:41:37.440 --> 0:41:40.319
<v Speaker 1>That's not what I was cringing at. Just the math

0:41:40.600 --> 0:41:43.560
<v Speaker 1>caught up with me. Yeah, thirty eight microseconds difference, so

0:41:43.600 --> 0:41:46.640
<v Speaker 1>you have to account for that. And we're looking for

0:41:46.680 --> 0:41:50.319
<v Speaker 1>an accuracy down to twenty to thirty nanoseconds. So nanoseconds

0:41:50.320 --> 0:41:53.440
<v Speaker 1>are much smaller than microseconds. It's a big deal. And

0:41:53.520 --> 0:41:56.320
<v Speaker 1>and and real errors would pile up due to these

0:41:56.400 --> 0:41:59.400
<v Speaker 1>due to these mistakes exactly. So if we did not

0:41:59.480 --> 0:42:03.920
<v Speaker 1>correct for us, on the first day, we'd be thinking, uh,

0:42:04.000 --> 0:42:08.000
<v Speaker 1>all right, well this isn't great, but it's you know,

0:42:08.080 --> 0:42:11.160
<v Speaker 1>it's it's it's usable. And then as the day goes

0:42:11.200 --> 0:42:14.080
<v Speaker 1>on would be thinking, wow, this is this is getting

0:42:14.200 --> 0:42:16.720
<v Speaker 1>less cool. And then the next day we'd be thinking

0:42:17.160 --> 0:42:21.000
<v Speaker 1>this is completely inaccurate, because the errors would be enough

0:42:21.360 --> 0:42:26.960
<v Speaker 1>to account for a ten kilometer error per day. Yeah,

0:42:27.000 --> 0:42:30.080
<v Speaker 1>so these little bits of time really make a big difference,

0:42:31.120 --> 0:42:33.480
<v Speaker 1>which is why you want to have a really precise

0:42:33.520 --> 0:42:37.000
<v Speaker 1>timekeeping device. Um. So, one way that they correct for

0:42:37.040 --> 0:42:41.160
<v Speaker 1>this is they actually make sure that the clocks aboard

0:42:41.200 --> 0:42:44.920
<v Speaker 1>the satellites tick at a slightly slower rate before putting

0:42:44.960 --> 0:42:48.239
<v Speaker 1>them up in orbit, because then general relativity will take

0:42:48.239 --> 0:42:50.080
<v Speaker 1>care of the rest and they'll start ticking at the

0:42:50.160 --> 0:42:53.000
<v Speaker 1>rate that they should be taking at, which is kind

0:42:53.000 --> 0:42:54.440
<v Speaker 1>of like you know that sort of thing where you've

0:42:54.480 --> 0:42:57.640
<v Speaker 1>already planned for the thing to go wrong, Like you're

0:42:57.640 --> 0:43:00.160
<v Speaker 1>not trying to stop the thing from going wrong. You're

0:43:00.160 --> 0:43:03.040
<v Speaker 1>just like, well, yeah, well this is gonna happen, so

0:43:03.200 --> 0:43:05.279
<v Speaker 1>here you go. This is what my life is now.

0:43:05.400 --> 0:43:08.440
<v Speaker 1>It's just how the that's just how physics work, y'all. Yeah,

0:43:08.719 --> 0:43:12.640
<v Speaker 1>uh okay, but that's not even atomic. Clocks are not

0:43:12.719 --> 0:43:16.000
<v Speaker 1>even the most precise type of clock that human people

0:43:16.160 --> 0:43:18.680
<v Speaker 1>have created. I know where you're going, and I'm already crying.

0:43:18.920 --> 0:43:21.560
<v Speaker 1>I know what. I'm sorry you and you got to

0:43:21.600 --> 0:43:24.920
<v Speaker 1>the notes faster than I could, so it's your fault. Really. Yeah, alright,

0:43:24.960 --> 0:43:30.240
<v Speaker 1>So the clock that inspired us to do this episode

0:43:30.600 --> 0:43:34.440
<v Speaker 1>is a type of optical clock. Optical clocks, and I

0:43:34.600 --> 0:43:37.160
<v Speaker 1>looking at the clock on my wrist, hypothetically, if I

0:43:37.239 --> 0:43:41.600
<v Speaker 1>had such a using optics right now. Uh, these use

0:43:42.440 --> 0:43:46.960
<v Speaker 1>these depend very heavily on lasers, and again with the lasers.

0:43:47.000 --> 0:43:50.080
<v Speaker 1>So we had in our notes how they work. And

0:43:50.160 --> 0:43:52.759
<v Speaker 1>I almost just put a frowny face sticks to it

0:43:53.600 --> 0:43:57.760
<v Speaker 1>because I started reading how this works, and it's so

0:43:58.000 --> 0:44:02.840
<v Speaker 1>complicated that, first of all, I gotta be upfront, I

0:44:02.880 --> 0:44:05.480
<v Speaker 1>do not understand it. All right, that's just me being

0:44:05.680 --> 0:44:07.960
<v Speaker 1>I'm being straight with you guy. Yeah, yeah, neither of

0:44:08.000 --> 0:44:11.640
<v Speaker 1>us are laser physicists. Yeah, I'm not a laser scientist. Okay,

0:44:12.520 --> 0:44:16.520
<v Speaker 1>I'm not a second scientist either. But they're very, very complicated,

0:44:16.560 --> 0:44:18.520
<v Speaker 1>and as I was reading it, I just realized that

0:44:18.840 --> 0:44:22.680
<v Speaker 1>it would take me probably weeks of study to really

0:44:22.760 --> 0:44:26.800
<v Speaker 1>get a basic understanding what's going on here. But uh,

0:44:26.840 --> 0:44:29.719
<v Speaker 1>they work with lasers and adams and specific frequencies. And

0:44:29.760 --> 0:44:33.719
<v Speaker 1>here's the problem. It's so technical. Uh there are phrases

0:44:33.840 --> 0:44:38.719
<v Speaker 1>like optical frequency standards, forbidden transitions. I didn't know there

0:44:38.760 --> 0:44:43.759
<v Speaker 1>were such things Doppler broadening and optical clockwork. And I'm

0:44:43.800 --> 0:44:46.520
<v Speaker 1>pretty sure I don't understand any of it. Oh yeah,

0:44:46.560 --> 0:44:49.560
<v Speaker 1>forbidden transition sounds like something out of Welcome to night

0:44:49.600 --> 0:44:54.000
<v Speaker 1>Vale more than exactly so okay, but but can you

0:44:54.239 --> 0:44:57.800
<v Speaker 1>can you give us like the very very very basic yes.

0:44:58.000 --> 0:45:04.200
<v Speaker 1>So optical clocks they don't necessarily rely on Just let

0:45:04.200 --> 0:45:05.719
<v Speaker 1>me put it this way. There are different types of

0:45:05.719 --> 0:45:09.640
<v Speaker 1>optical clocks, and they work on different types of particles. Right, So,

0:45:09.960 --> 0:45:16.719
<v Speaker 1>with atomic clocks, were typically talking about either caesium or rubidium. Uh, yeah,

0:45:16.760 --> 0:45:18.640
<v Speaker 1>I think it's rubidium. But at any rate, we're only

0:45:18.640 --> 0:45:21.560
<v Speaker 1>talking about those. The optical clocks there are a lot

0:45:21.680 --> 0:45:25.480
<v Speaker 1>more options, so you can talk about certain atoms or

0:45:25.520 --> 0:45:29.520
<v Speaker 1>ions or even molecules depending upon the type of optical

0:45:29.560 --> 0:45:33.120
<v Speaker 1>clock you've got set up. And the optical clocks can

0:45:33.160 --> 0:45:36.160
<v Speaker 1>correct for caesium clock drift, which is good. So they

0:45:36.200 --> 0:45:38.960
<v Speaker 1>are more precise. They can divide time up into ever

0:45:39.120 --> 0:45:44.359
<v Speaker 1>smaller amounts um, and they are really I mean that's

0:45:44.400 --> 0:45:46.640
<v Speaker 1>really important because the more precise you get, the more

0:45:46.680 --> 0:45:51.600
<v Speaker 1>accurate your timekeeping is. But what they're essentially doing is

0:45:51.800 --> 0:45:55.560
<v Speaker 1>slowing these atoms and ions and molecules down to microwave

0:45:55.600 --> 0:45:59.480
<v Speaker 1>frequency standards, which is similar to what the caesium atomic

0:45:59.520 --> 0:46:03.920
<v Speaker 1>clock us. Uh So the idea being that light frequencies

0:46:03.960 --> 0:46:06.880
<v Speaker 1>are way too fast. Uh, they're much faster than the

0:46:06.880 --> 0:46:10.920
<v Speaker 1>micro Even with that nine billion number, that's slow compared

0:46:10.960 --> 0:46:14.919
<v Speaker 1>to what the light frequencies are. UM, so it's it's

0:46:15.040 --> 0:46:17.160
<v Speaker 1>important to use it to slow it down to these

0:46:17.200 --> 0:46:20.080
<v Speaker 1>microwave amounts. But it means that you can actually create

0:46:20.480 --> 0:46:24.160
<v Speaker 1>what's kind of called like an optical comb frequency, and

0:46:24.239 --> 0:46:28.960
<v Speaker 1>you are able to subdivide those frequencies further and further

0:46:29.000 --> 0:46:30.719
<v Speaker 1>and further, which is what allows us to look at

0:46:30.880 --> 0:46:33.960
<v Speaker 1>smaller and smaller fractions of a second and make more

0:46:34.040 --> 0:46:38.239
<v Speaker 1>and more precise clocks. And we have literally reached the

0:46:38.320 --> 0:46:42.799
<v Speaker 1>limit of my understanding. Okay, okay, but part of my

0:46:43.040 --> 0:46:46.880
<v Speaker 1>understanding of them is more top level than that. You

0:46:46.960 --> 0:46:49.120
<v Speaker 1>just went way deeper than I did. Um but uh

0:46:49.400 --> 0:46:50.960
<v Speaker 1>but but I'm but I'm aware of the idea that

0:46:51.000 --> 0:46:54.399
<v Speaker 1>they're not considered as dependable as atomic clocks, and that's

0:46:54.440 --> 0:46:57.279
<v Speaker 1>why they have not been been used to switch over

0:46:57.680 --> 0:47:00.560
<v Speaker 1>the definition of a second as of yet. Yeah, they're

0:47:00.600 --> 0:47:07.040
<v Speaker 1>incredibly complicated machines and there are a lot of potential

0:47:07.080 --> 0:47:09.879
<v Speaker 1>points of failure, so if something goes wrong, the whole

0:47:09.880 --> 0:47:14.080
<v Speaker 1>system doesn't work right, and things go wrong. Technology doesn't

0:47:14.080 --> 0:47:16.880
<v Speaker 1>always work, especially young technology where you're you know, this

0:47:16.920 --> 0:47:20.360
<v Speaker 1>is still relatively young technology where you're trying to develop something.

0:47:20.400 --> 0:47:23.120
<v Speaker 1>And because it's a delicate system and it's very complicated,

0:47:23.160 --> 0:47:26.080
<v Speaker 1>and downtime is a factor. Uh. That means you have

0:47:26.120 --> 0:47:30.800
<v Speaker 1>to actually account for time required to fix the clock,

0:47:30.840 --> 0:47:33.839
<v Speaker 1>which means that like like like like hours or even days. Yeah.

0:47:33.960 --> 0:47:37.680
<v Speaker 1>And so while it's offline, you you aren't you don't

0:47:37.680 --> 0:47:42.399
<v Speaker 1>have time, yeah, unless unless you pair to this type

0:47:42.440 --> 0:47:44.680
<v Speaker 1>of system with another type of system, which is what

0:47:45.040 --> 0:47:48.960
<v Speaker 1>essentially is up with this new clock that we mentioned

0:47:49.000 --> 0:47:52.000
<v Speaker 1>at the very top of the podcast years and years ago.

0:47:52.280 --> 0:47:56.000
<v Speaker 1>It seems like it seems like another lifetime Lauren. Yeah.

0:47:56.040 --> 0:47:58.960
<v Speaker 1>So this, uh, the story came from a research team

0:47:59.120 --> 0:48:01.880
<v Speaker 1>out of the National a Trology Institute of Germany and

0:48:01.960 --> 0:48:06.560
<v Speaker 1>metrology that's a science of measurement and and and while

0:48:06.640 --> 0:48:10.360
<v Speaker 1>there are branches of this institute all around the world,

0:48:10.800 --> 0:48:14.880
<v Speaker 1>I think there's something so fitting was the Germans, especially

0:48:14.920 --> 0:48:19.600
<v Speaker 1>for time. It's just again it's stereotypical, but you just think,

0:48:19.680 --> 0:48:26.320
<v Speaker 1>like you know, piseyah. So the specific type of clock

0:48:26.440 --> 0:48:31.240
<v Speaker 1>that they were working with is a strontium optical lattice clock.

0:48:31.400 --> 0:48:34.319
<v Speaker 1>By the way, there are research institutes in the United

0:48:34.360 --> 0:48:37.719
<v Speaker 1>States that also are working on this same technology, and

0:48:38.160 --> 0:48:41.080
<v Speaker 1>that's the actual optical clock. The optical lattice is pretty

0:48:41.120 --> 0:48:43.520
<v Speaker 1>much what sounds like. It's an arrangement of lasers that

0:48:43.560 --> 0:48:48.080
<v Speaker 1>are meant to manipulate those atoms of strontium. So again

0:48:48.560 --> 0:48:52.600
<v Speaker 1>back to the James Bond slash mission impossible kind of trap. Uh.

0:48:52.680 --> 0:48:57.080
<v Speaker 1>They use a second device to help account for time

0:48:57.120 --> 0:49:01.520
<v Speaker 1>whenever the lattice clock goes off line, and that is

0:49:01.640 --> 0:49:07.560
<v Speaker 1>a maser. Yeah, it sounds like it, but in fact,

0:49:07.600 --> 0:49:12.640
<v Speaker 1>maser's predate lasers, mazers were Masers were discovered or created

0:49:12.719 --> 0:49:16.280
<v Speaker 1>in the lab before lasers were. They're similar to a laser.

0:49:16.440 --> 0:49:20.239
<v Speaker 1>It is a microwave amplification by stimulated emission of radiation.

0:49:20.880 --> 0:49:22.400
<v Speaker 1>So it used to be an acronym. Now it's just

0:49:22.440 --> 0:49:26.680
<v Speaker 1>a word, just like laser. Uh. Masers operate at microwave frequencies,

0:49:26.680 --> 0:49:29.520
<v Speaker 1>which again are not as high as laser frequencies and

0:49:29.560 --> 0:49:33.880
<v Speaker 1>little light frequencies, which means that because their frequencies are

0:49:33.920 --> 0:49:36.719
<v Speaker 1>are are lower. I keep saying slower, but I really

0:49:36.719 --> 0:49:39.080
<v Speaker 1>should just say lower. I know all the physicists out there,

0:49:39.120 --> 0:49:43.120
<v Speaker 1>I've been cringing. I apologize to you guys, but it

0:49:43.160 --> 0:49:45.440
<v Speaker 1>means that because you have a lower frequency, you have

0:49:45.480 --> 0:49:47.960
<v Speaker 1>a lower level of precision. It's kind of like, you

0:49:48.000 --> 0:49:50.040
<v Speaker 1>know again, Like the way I would think of it is,

0:49:50.120 --> 0:49:54.319
<v Speaker 1>imagine that you have um a measuring cup, and uh

0:49:54.360 --> 0:49:56.760
<v Speaker 1>and I you have a measuring cup, I've got a bucket,

0:49:57.320 --> 0:50:00.239
<v Speaker 1>and we each have to say how much water is

0:50:00.320 --> 0:50:03.360
<v Speaker 1>in a pool. And so it's gonna take us a

0:50:03.360 --> 0:50:05.480
<v Speaker 1>long time to figure this out. But you're gonna be

0:50:05.520 --> 0:50:07.680
<v Speaker 1>a lot more precise with your answer than I will,

0:50:07.840 --> 0:50:10.920
<v Speaker 1>although you'll get to your answer quicker than I will, relatively.

0:50:10.960 --> 0:50:13.440
<v Speaker 1>So I didn't say how big the pool was. If

0:50:13.440 --> 0:50:15.080
<v Speaker 1>it's a big enough pool, then both of us have

0:50:15.200 --> 0:50:18.520
<v Speaker 1>just wasted our lives at any rate. The same idea

0:50:18.600 --> 0:50:21.359
<v Speaker 1>with the mazer. With the lower frequency, it can take

0:50:21.480 --> 0:50:24.400
<v Speaker 1>less precise measurements. So what the team did was they

0:50:24.480 --> 0:50:26.600
<v Speaker 1>used the maser to cover for the downtime when the

0:50:26.600 --> 0:50:28.759
<v Speaker 1>optical clock was offline. And the way they did this

0:50:28.840 --> 0:50:32.560
<v Speaker 1>was they then they applied an optical frequency comb to

0:50:32.680 --> 0:50:36.040
<v Speaker 1>divide the maser's measurements into smaller units, similar to that

0:50:36.080 --> 0:50:38.920
<v Speaker 1>to the optical clocks. So while the optical clock was

0:50:38.960 --> 0:50:42.640
<v Speaker 1>still working, they tuned the mazer's frequency so that the

0:50:42.680 --> 0:50:46.080
<v Speaker 1>output most closely resembled that of the optical clock once

0:50:46.120 --> 0:50:50.320
<v Speaker 1>fed through this comb. Yeah. So they're like, well, the mazer,

0:50:50.480 --> 0:50:53.560
<v Speaker 1>while we know it cannot take as precise measurements as

0:50:53.560 --> 0:50:57.359
<v Speaker 1>the optical clock, if we apply this optical comb to it,

0:50:57.800 --> 0:51:00.560
<v Speaker 1>we can kind of fake it, sort of. And as

0:51:00.560 --> 0:51:04.560
<v Speaker 1>long as we have attuned the two together, then we

0:51:04.600 --> 0:51:06.600
<v Speaker 1>can at least depend on this until we can get

0:51:06.640 --> 0:51:08.239
<v Speaker 1>the other one working. Sure. Yeah, and then when the

0:51:08.239 --> 0:51:11.400
<v Speaker 1>optical clock comes back online, then you re a tune everything,

0:51:11.440 --> 0:51:13.319
<v Speaker 1>make sure it's all flowing together and kind of cut

0:51:13.360 --> 0:51:16.120
<v Speaker 1>the difference. Yeah. Yeah, and then you might call people.

0:51:16.120 --> 0:51:22.080
<v Speaker 1>I'm like, hey, I'm going to need that six nanoseconds back. Sorry, sorry, sorry, David,

0:51:23.920 --> 0:51:25.960
<v Speaker 1>We're gonna have to docu six nano seconds for it.

0:51:26.040 --> 0:51:28.920
<v Speaker 1>You took too long for your lunch now. But so so,

0:51:28.960 --> 0:51:32.080
<v Speaker 1>in in this experiment that this team published about recently,

0:51:32.160 --> 0:51:35.560
<v Speaker 1>they ran a test of the system for twenty five days,

0:51:36.040 --> 0:51:39.279
<v Speaker 1>and the optical clock did indeed experience downtime up to

0:51:39.360 --> 0:51:41.920
<v Speaker 1>two days at a go. But at the end of

0:51:41.920 --> 0:51:46.200
<v Speaker 1>the trial their system was just under zero point to

0:51:46.880 --> 0:51:51.080
<v Speaker 1>nanoseconds off. And there's a kind of flashy number that

0:51:51.160 --> 0:51:54.439
<v Speaker 1>the press has latched onto and and it's an extrapolation

0:51:54.440 --> 0:51:57.640
<v Speaker 1>of that, which is that. Okay, So assuming that the

0:51:57.640 --> 0:52:00.600
<v Speaker 1>system wouldn't like degrade over a longer lane of time,

0:52:01.400 --> 0:52:04.320
<v Speaker 1>and assuming that we could have somehow started running it

0:52:04.480 --> 0:52:06.719
<v Speaker 1>at the beginning of the universe as we know it

0:52:06.920 --> 0:52:10.520
<v Speaker 1>a k a. Like fourteen billion years ago, when time

0:52:10.560 --> 0:52:14.279
<v Speaker 1>became a thing. Yes, um it, this clock would have

0:52:14.360 --> 0:52:20.520
<v Speaker 1>lost only about a hundred seconds over those fourteen billions years. So,

0:52:20.520 --> 0:52:28.000
<v Speaker 1>so less than two minutes billion billion, pretty precise. Yeah.

0:52:28.040 --> 0:52:30.200
<v Speaker 1>And and and at tom the clocks are pretty good

0:52:30.200 --> 0:52:32.959
<v Speaker 1>at that thing too, like relatively but but they but

0:52:32.960 --> 0:52:34.360
<v Speaker 1>but it beats him out by a factor of like

0:52:34.360 --> 0:52:39.000
<v Speaker 1>a hundred. Yeah. So ultimately, does this mean about the

0:52:39.040 --> 0:52:44.800
<v Speaker 1>future of time keeping, the future of seconds themselves? Well, well, okay,

0:52:44.880 --> 0:52:47.360
<v Speaker 1>the definition of the SI unit isn't just going to

0:52:47.520 --> 0:52:50.960
<v Speaker 1>change overnight. Yeah. In fact, the researchers on this project

0:52:51.080 --> 0:52:53.399
<v Speaker 1>said that it would be at least a decade out

0:52:53.880 --> 0:52:57.719
<v Speaker 1>for that to change, partially because the technology, right, it's

0:52:57.719 --> 0:52:59.480
<v Speaker 1>so young. And we talked about all the fact that

0:52:59.480 --> 0:53:01.839
<v Speaker 1>they're all these different style of optical clocks. They don't

0:53:01.840 --> 0:53:04.600
<v Speaker 1>all use strontium. They may use something else, and we

0:53:04.680 --> 0:53:07.839
<v Speaker 1>haven't figured out yet which one is quote unquote the

0:53:07.880 --> 0:53:10.840
<v Speaker 1>best one to go with, as in, the most reliable,

0:53:11.320 --> 0:53:13.759
<v Speaker 1>the most precise, that has yet to be decided. This

0:53:13.800 --> 0:53:17.120
<v Speaker 1>is still a very early form of research, so it

0:53:17.160 --> 0:53:19.960
<v Speaker 1>may turn out that it will take a decade for

0:53:20.000 --> 0:53:22.080
<v Speaker 1>that to shake out and for us to say, all right,

0:53:22.200 --> 0:53:24.719
<v Speaker 1>this is the optical clock that is best to use

0:53:24.840 --> 0:53:26.640
<v Speaker 1>that we're going with, and this is what a second

0:53:26.840 --> 0:53:32.359
<v Speaker 1>is now. And okay, so so when we do accomplish that,

0:53:32.880 --> 0:53:37.560
<v Speaker 1>we'll we'll have more accurate clocks. Yeah, but practically what

0:53:37.680 --> 0:53:40.399
<v Speaker 1>will that do for us? Lots of stuff. Well, first

0:53:40.440 --> 0:53:44.040
<v Speaker 1>of all, we hear it forward thinking. We always stress

0:53:44.160 --> 0:53:47.680
<v Speaker 1>that pure research ultimately benefits us in ways that we

0:53:47.760 --> 0:53:50.480
<v Speaker 1>cannot anticipate. Oh absolutely, I mean, and you know, like

0:53:50.480 --> 0:53:53.279
<v Speaker 1>like hurrah for the spirit of scientific inquiry and in

0:53:53.400 --> 0:53:56.640
<v Speaker 1>the advancement of physics and all that rad stuff. But

0:53:57.800 --> 0:54:00.600
<v Speaker 1>but okay, like like really, technically, we're not doing all

0:54:00.600 --> 0:54:04.040
<v Speaker 1>of us, all of this for us, right, human beings

0:54:04.200 --> 0:54:07.200
<v Speaker 1>don't miss the nanoseconds that the current you know, gold

0:54:07.239 --> 0:54:12.600
<v Speaker 1>standard atomic clocks are accidentally shaving off. That means that yes,

0:54:13.840 --> 0:54:16.359
<v Speaker 1>in the spirit of Joe being and not being here,

0:54:16.360 --> 0:54:20.279
<v Speaker 1>but in his spirit we're doing this for a robotic overlords. Yeah. Yeah,

0:54:20.320 --> 0:54:22.920
<v Speaker 1>So it turns out like the besides the satellite systems

0:54:22.960 --> 0:54:24.640
<v Speaker 1>that we depend upon, we have a lot of systems

0:54:24.680 --> 0:54:29.040
<v Speaker 1>here on Earth that are really important to coordinate with timekeeping,

0:54:29.320 --> 0:54:33.160
<v Speaker 1>including things like our electric grid. But obviously, if we're

0:54:33.160 --> 0:54:36.680
<v Speaker 1>going to have more and more technology interacting with one another,

0:54:36.719 --> 0:54:40.600
<v Speaker 1>talking to one another, uh, causing things to happen within

0:54:40.719 --> 0:54:44.520
<v Speaker 1>our world, timekeeping becomes incredibly important. Obviously, Like if I

0:54:44.640 --> 0:54:47.080
<v Speaker 1>if I am walking into a room and I want

0:54:47.160 --> 0:54:51.319
<v Speaker 1>a specific outcome to happen through my technology, I want

0:54:51.360 --> 0:54:53.359
<v Speaker 1>that to happen while I'm walking into the room, not

0:54:53.680 --> 0:54:55.680
<v Speaker 1>five minutes after I walked into the room, or five

0:54:55.719 --> 0:54:58.919
<v Speaker 1>minutes after I walked out of the room. Sure, if

0:54:58.920 --> 0:55:02.560
<v Speaker 1>you if you have a GPS system that's controlling your

0:55:03.040 --> 0:55:06.960
<v Speaker 1>autonomous vehicle and another person's autonomous vehicle, you want those

0:55:07.040 --> 0:55:09.040
<v Speaker 1>GPS satellites to be able to hone in on you

0:55:09.080 --> 0:55:12.560
<v Speaker 1>well enough to to to not crash them together. Right,

0:55:12.560 --> 0:55:14.799
<v Speaker 1>If you have a system that is and like an

0:55:14.800 --> 0:55:17.720
<v Speaker 1>external system that's controlling a lot of vehicles, you could

0:55:17.840 --> 0:55:21.319
<v Speaker 1>in theory, reduce traffic to nothing, right, because you could

0:55:21.480 --> 0:55:24.160
<v Speaker 1>you could have the cars moving impossibly close to one

0:55:24.160 --> 0:55:29.240
<v Speaker 1>another incredibly safely. But if your timekeepings off, that suddenly

0:55:29.360 --> 0:55:31.959
<v Speaker 1>becomes a lot of bumping and rubbing on the road.

0:55:32.320 --> 0:55:35.759
<v Speaker 1>Time and distance are still linked and uh or or

0:55:35.800 --> 0:55:39.200
<v Speaker 1>for another example. So back in February, we did an

0:55:39.239 --> 0:55:43.319
<v Speaker 1>episode about how machines run the stock market. Computers are

0:55:43.440 --> 0:55:47.120
<v Speaker 1>very precisely running the stock market these days, making these

0:55:47.160 --> 0:55:51.320
<v Speaker 1>trades at fractions of fractions of a second. The episode

0:55:51.360 --> 0:55:53.960
<v Speaker 1>is called show me the zero zero one zero zero

0:55:54.000 --> 0:55:56.719
<v Speaker 1>one zero zero if you'd like to go look for it.

0:55:56.760 --> 0:55:59.200
<v Speaker 1>I believe that code actually stands for the dollar sign.

0:55:59.440 --> 0:56:01.520
<v Speaker 1>That's adorable. Yeah, I think I actually looked that up.

0:56:02.320 --> 0:56:04.880
<v Speaker 1>That's how much of a dork I am. But but

0:56:04.960 --> 0:56:08.200
<v Speaker 1>so obviously this kind of precision and timekeeping will will

0:56:08.239 --> 0:56:11.320
<v Speaker 1>totally matter to to these computers and to to others

0:56:11.360 --> 0:56:14.800
<v Speaker 1>like them. You know, just think, Jonathan, how many interactions

0:56:14.840 --> 0:56:18.160
<v Speaker 1>and transactions you could complete in a few extra nano

0:56:18.200 --> 0:56:21.880
<v Speaker 1>seconds every day? Man, my Amazon wish list is gonna

0:56:21.920 --> 0:56:26.520
<v Speaker 1>be sick. Yeah, so we're we've been joking around a

0:56:26.520 --> 0:56:30.680
<v Speaker 1>lot and talking kind of about this. This somewhat odd

0:56:30.719 --> 0:56:32.840
<v Speaker 1>idea of a second secon time is such a weird

0:56:32.920 --> 0:56:36.759
<v Speaker 1>thing right to talk about in a objective, definitive way

0:56:36.800 --> 0:56:39.759
<v Speaker 1>when we also are aware that it is relative. It

0:56:39.880 --> 0:56:43.000
<v Speaker 1>makes it really kind of mind bindy to to go

0:56:43.040 --> 0:56:45.759
<v Speaker 1>on about this. And uh, ultimately, if we get to

0:56:45.800 --> 0:56:48.839
<v Speaker 1>a future where people are zooming around the galaxy at

0:56:49.560 --> 0:56:52.600
<v Speaker 1>ridiculous speeds, this kind of precise timekeeping will also be

0:56:52.680 --> 0:56:56.760
<v Speaker 1>important so that we can have any form of communication

0:56:57.000 --> 0:56:59.560
<v Speaker 1>that might be possible as long as they're still you know,

0:56:59.719 --> 0:57:05.000
<v Speaker 1>with reachable distances, um and Yeah, if they're going to

0:57:05.000 --> 0:57:07.239
<v Speaker 1>be the speed of light, then you're you're never going

0:57:07.280 --> 0:57:09.600
<v Speaker 1>to catch up to them, Like the message will always

0:57:09.640 --> 0:57:12.480
<v Speaker 1>be behind them until they stop. And then what will

0:57:12.520 --> 0:57:14.520
<v Speaker 1>happen is they'll travel at the speed of light and

0:57:14.560 --> 0:57:17.080
<v Speaker 1>they'll be like twenty seven light years away and then

0:57:17.080 --> 0:57:19.360
<v Speaker 1>they'll stop and then they'll say you forgot your underwear.

0:57:19.400 --> 0:57:23.760
<v Speaker 1>I'm like, dude, no, I'm just thinking of how have

0:57:23.800 --> 0:57:27.160
<v Speaker 1>that bump in your inbox when you finally right down

0:57:29.640 --> 0:57:32.600
<v Speaker 1>and then all of a sudden it's like, oh my gosh,

0:57:32.600 --> 0:57:36.360
<v Speaker 1>and it's all adds. So this was fun to talk

0:57:36.400 --> 0:57:39.600
<v Speaker 1>about something like this, and we really look forward to

0:57:39.640 --> 0:57:43.520
<v Speaker 1>tackling other interesting topics like this in the future. If

0:57:43.520 --> 0:57:46.800
<v Speaker 1>you guys have any suggestions for future topics, maybe there's

0:57:46.840 --> 0:57:49.360
<v Speaker 1>something you've always wondered. How is that going to be? What?

0:57:49.360 --> 0:57:51.400
<v Speaker 1>What will that be like in the future? Let us know.

0:57:51.520 --> 0:57:54.680
<v Speaker 1>Send us an email. The address is FW thinking at

0:57:54.720 --> 0:57:57.680
<v Speaker 1>how Stuff Works dot com, or you can drop us

0:57:57.680 --> 0:58:01.160
<v Speaker 1>a line on social media. On Twitter, we are FW thinking.

0:58:01.480 --> 0:58:03.960
<v Speaker 1>If you search f w thinking over on Facebook, our

0:58:03.960 --> 0:58:05.840
<v Speaker 1>profile will pop right up. You can leave us a

0:58:05.840 --> 0:58:08.400
<v Speaker 1>message there. We'll be happy to hear from you, and

0:58:08.440 --> 0:58:17.120
<v Speaker 1>we will talk to you again really soon. For more

0:58:17.160 --> 0:58:20.160
<v Speaker 1>on this topic in the future of technology, visit forward

0:58:20.160 --> 0:58:34.840
<v Speaker 1>thinking dot com, brought to you by Toyota. Let's Go Places,