WEBVTT - How Weather Models Work

0:00:04.440 --> 0:00:12.440
<v Speaker 1>Technology with tech Stuff from stuff works dot com. Welcome

0:00:12.520 --> 0:00:16.160
<v Speaker 1>to tech Stuff. I am your host, Jonathan Strickland. I'm

0:00:16.160 --> 0:00:19.560
<v Speaker 1>a senior writer with how stuff works dot com and

0:00:19.600 --> 0:00:22.239
<v Speaker 1>I'm so glad you could join me today here on

0:00:22.320 --> 0:00:25.360
<v Speaker 1>tech Stuff, we like to cover all things technological and

0:00:25.680 --> 0:00:28.680
<v Speaker 1>explain how they work and why they're important. And for

0:00:28.720 --> 0:00:31.480
<v Speaker 1>the last couple of episodes, we've really been focusing on

0:00:31.600 --> 0:00:36.400
<v Speaker 1>meteorology and weather forecasting and the types of technology that

0:00:36.440 --> 0:00:39.280
<v Speaker 1>we used to try and predict the weather. UH. In

0:00:39.400 --> 0:00:42.440
<v Speaker 1>the first episode in this series, we concentrated mainly on

0:00:42.479 --> 0:00:45.760
<v Speaker 1>the science of weather itself, and that's important to understand

0:00:45.800 --> 0:00:49.479
<v Speaker 1>because you begin to pick up on how complicated a

0:00:49.840 --> 0:00:54.200
<v Speaker 1>system whether actually is, especially when you start expanding out

0:00:54.320 --> 0:00:57.240
<v Speaker 1>from a small region to a larger region to a

0:00:57.280 --> 0:01:01.640
<v Speaker 1>global region and you see how interdependent all of these

0:01:01.640 --> 0:01:05.800
<v Speaker 1>different regions are on each other, the brain starts to

0:01:05.880 --> 0:01:08.560
<v Speaker 1>swim a bit. In Part two, we looked at the

0:01:08.680 --> 0:01:14.560
<v Speaker 1>various sensors and tools used to capture information about what

0:01:14.800 --> 0:01:18.360
<v Speaker 1>is going on with the weather. These are the tools

0:01:18.440 --> 0:01:22.559
<v Speaker 1>that meteorologists use in order to feed that information into

0:01:22.640 --> 0:01:27.200
<v Speaker 1>their various weather models. So UH, Today's episode is going

0:01:27.240 --> 0:01:30.120
<v Speaker 1>to focus on those weather models. These are based on

0:01:30.160 --> 0:01:33.720
<v Speaker 1>our understanding of the behavior of weather under different conditions,

0:01:33.760 --> 0:01:36.640
<v Speaker 1>and it's what gives us the confidence to make predictions

0:01:36.640 --> 0:01:41.920
<v Speaker 1>of what will happen next. Now that being said, predictions,

0:01:42.080 --> 0:01:45.080
<v Speaker 1>as we all know, are not guarantees. I'm sure there

0:01:45.120 --> 0:01:47.920
<v Speaker 1>are many of you who have walked out of your

0:01:47.920 --> 0:01:51.640
<v Speaker 1>homes with confidence, dressed in your best clothing, only to

0:01:51.720 --> 0:01:55.720
<v Speaker 1>be plagued by an unexpected downpour at an inopportune time,

0:01:55.880 --> 0:01:58.840
<v Speaker 1>turning into Charlie Brown with that one rain cloud just

0:01:59.000 --> 0:02:02.559
<v Speaker 1>directly overhead. Or you might be one of those people

0:02:02.880 --> 0:02:05.800
<v Speaker 1>that have convinced him or herself that if you have

0:02:05.920 --> 0:02:09.000
<v Speaker 1>an umbrella in your hand, it virtually guarantees that not

0:02:09.120 --> 0:02:12.840
<v Speaker 1>a single drop of rain will fall, that you, by

0:02:12.960 --> 0:02:17.000
<v Speaker 1>virtue of holding the umbrella, have prevented rain from happening.

0:02:17.320 --> 0:02:20.200
<v Speaker 1>As it turns out, predicting the weather is really hard

0:02:20.520 --> 0:02:22.440
<v Speaker 1>for a lot of reasons, though the biggest one is

0:02:22.440 --> 0:02:26.280
<v Speaker 1>that weather is just an incredibly complicated system affected by

0:02:26.360 --> 0:02:29.640
<v Speaker 1>hundreds of variables, and those variables may have a lesser

0:02:29.760 --> 0:02:33.760
<v Speaker 1>or greater effect in different situations. That means there's a

0:02:33.760 --> 0:02:36.959
<v Speaker 1>lot of potential outcomes for any given scenario, and until

0:02:37.000 --> 0:02:40.079
<v Speaker 1>we have a really comprehensive understanding of what's going on

0:02:40.240 --> 0:02:43.440
<v Speaker 1>at all times in our atmosphere. Weather predictions will be

0:02:43.440 --> 0:02:49.200
<v Speaker 1>based primarily on statistical probabilities, not certainties. Before we really

0:02:49.440 --> 0:02:51.960
<v Speaker 1>had a handle on all of those variables, and to

0:02:52.040 --> 0:02:54.880
<v Speaker 1>be honest, we don't completely have a full handle on

0:02:54.919 --> 0:02:58.600
<v Speaker 1>them right now. We based weather predictions off of empirical

0:02:58.720 --> 0:03:03.560
<v Speaker 1>rules that we formed observation. So, in other words, generally speaking,

0:03:03.639 --> 0:03:05.840
<v Speaker 1>if you woke up and looked outside the window and

0:03:05.840 --> 0:03:08.000
<v Speaker 1>you thought, hey, it looks like it might rain today,

0:03:08.080 --> 0:03:09.840
<v Speaker 1>because a couple of weeks ago I looked out the

0:03:09.840 --> 0:03:12.320
<v Speaker 1>window and it looked just like this and it rained

0:03:12.440 --> 0:03:15.519
<v Speaker 1>that day, well that's about as complex as it got.

0:03:15.639 --> 0:03:18.240
<v Speaker 1>I mean, you might have a weather map, like a

0:03:18.320 --> 0:03:21.560
<v Speaker 1>literal map, and you have some things you've written down

0:03:21.560 --> 0:03:23.640
<v Speaker 1>on it. You know that to the west of you

0:03:24.560 --> 0:03:27.919
<v Speaker 1>there's a low pressure system, so you might start using

0:03:27.960 --> 0:03:31.440
<v Speaker 1>that as a guide for what could end up happening.

0:03:31.880 --> 0:03:34.320
<v Speaker 1>But it wasn't a very precise science. It wasn't what

0:03:34.360 --> 0:03:38.200
<v Speaker 1>people were calling a rational approach. It was an empirical approach,

0:03:39.240 --> 0:03:41.480
<v Speaker 1>and over time we began to understand that weather is

0:03:41.480 --> 0:03:46.520
<v Speaker 1>dictated by a host of very complex variables. So meteorologists

0:03:46.520 --> 0:03:51.000
<v Speaker 1>are gathering all of this data about air pressure, temperature, windspeed,

0:03:51.080 --> 0:03:53.920
<v Speaker 1>weather patterns that are nearby, and tons of other factors.

0:03:54.920 --> 0:03:59.440
<v Speaker 1>These things are changing quickly and constantly, meaning it's important

0:03:59.440 --> 0:04:03.640
<v Speaker 1>to look over those observations regularly and adjust projections. And

0:04:03.680 --> 0:04:06.800
<v Speaker 1>if you're not lucky, you may only have a few

0:04:06.840 --> 0:04:11.680
<v Speaker 1>observation stations placed in strategic locations within your particular region,

0:04:12.040 --> 0:04:18.120
<v Speaker 1>which gives you a limited on resolution. So weather forecasting

0:04:18.160 --> 0:04:23.000
<v Speaker 1>is a lot like your displays or your televisions resolutions.

0:04:23.080 --> 0:04:27.040
<v Speaker 1>Very important resolution is all about how many points of

0:04:27.160 --> 0:04:31.040
<v Speaker 1>data do you have within that given area, how representative

0:04:31.720 --> 0:04:35.000
<v Speaker 1>are those observation stations. If you have a single observation

0:04:35.080 --> 0:04:39.000
<v Speaker 1>station for several square miles, well that's not going to

0:04:39.040 --> 0:04:41.440
<v Speaker 1>give you very good resolution, right You're going to have

0:04:41.800 --> 0:04:44.360
<v Speaker 1>a very specific idea of what's going on at one

0:04:44.440 --> 0:04:48.360
<v Speaker 1>point within that area, but everything further out from there

0:04:48.640 --> 0:04:51.719
<v Speaker 1>it's going to be some variation of the information you've

0:04:51.760 --> 0:04:54.520
<v Speaker 1>pulled down. So if you want high resolution, you have

0:04:54.560 --> 0:04:57.760
<v Speaker 1>to have lots of observation stations throughout that same area,

0:04:57.920 --> 0:05:01.640
<v Speaker 1>and you collectively are able to determine what's happening by

0:05:01.680 --> 0:05:05.160
<v Speaker 1>looking at all of them, but obviously that adds a

0:05:05.160 --> 0:05:09.520
<v Speaker 1>lot more information to your calculations. In an ideal world,

0:05:09.920 --> 0:05:13.480
<v Speaker 1>you have all areas densely packed with observation stations, giving

0:05:13.480 --> 0:05:18.440
<v Speaker 1>you amazing consistent resolution and the processing power necessary to

0:05:18.480 --> 0:05:21.200
<v Speaker 1>take all that raw data and crunch it to produce

0:05:21.279 --> 0:05:25.320
<v Speaker 1>reliable weather forecasts at any given moment. But we just

0:05:25.520 --> 0:05:31.600
<v Speaker 1>aren't there yet. So weather models, what's the story on those? Well,

0:05:31.640 --> 0:05:33.920
<v Speaker 1>it helps to look back on the birth of meteorology

0:05:33.960 --> 0:05:37.159
<v Speaker 1>and weather forecasting in the form of numerical weather prediction.

0:05:37.480 --> 0:05:39.559
<v Speaker 1>That's really what we get down to when we start

0:05:39.600 --> 0:05:43.200
<v Speaker 1>talking about weather models. And to do this we actually

0:05:43.200 --> 0:05:45.760
<v Speaker 1>have to backtrack a little bit. I know, we talked

0:05:45.760 --> 0:05:48.719
<v Speaker 1>a lot about the various tools in the last episode

0:05:48.720 --> 0:05:50.920
<v Speaker 1>and we got pretty up to date, but we're gonna

0:05:50.920 --> 0:05:54.440
<v Speaker 1>have to go back to talk about weather models specifically. Now.

0:05:54.440 --> 0:05:57.480
<v Speaker 1>In the nineteenth century, so this is the eighteen hundreds,

0:05:57.600 --> 0:06:01.320
<v Speaker 1>physicists were beginning to suss out the law of thermodynamics.

0:06:02.279 --> 0:06:06.680
<v Speaker 1>These are the basic laws of energy that we UH

0:06:06.680 --> 0:06:11.320
<v Speaker 1>that everything is is UH has to obey, at least

0:06:11.320 --> 0:06:14.200
<v Speaker 1>everything on the macro scale has to obey. And it

0:06:14.240 --> 0:06:18.760
<v Speaker 1>was relatively easy to put hypotheses to test with modest experiments, right, Like,

0:06:18.800 --> 0:06:23.040
<v Speaker 1>you could do tests about fluid dynamics with small contained

0:06:23.279 --> 0:06:27.560
<v Speaker 1>systems and you could limit the variables and make lots

0:06:27.560 --> 0:06:32.160
<v Speaker 1>of observations. That was pretty easy, relatively speaking, But it

0:06:32.240 --> 0:06:35.039
<v Speaker 1>was much more challenging to step back, and I mean

0:06:35.160 --> 0:06:38.120
<v Speaker 1>way way back and see how those same laws applied

0:06:38.120 --> 0:06:41.760
<v Speaker 1>to something as massive as our atmosphere. If you want

0:06:41.760 --> 0:06:45.320
<v Speaker 1>to think about another way, it's one thing to look

0:06:45.400 --> 0:06:49.479
<v Speaker 1>at a maze that has rats running in it. It's

0:06:49.480 --> 0:06:52.640
<v Speaker 1>another thing to try and figure out what the maze

0:06:52.760 --> 0:06:55.680
<v Speaker 1>is like. When you are inside the maze and you

0:06:55.680 --> 0:06:58.159
<v Speaker 1>can only see a small part of it, How do

0:06:58.200 --> 0:07:01.240
<v Speaker 1>you know what the entire layout of the mazes from

0:07:01.279 --> 0:07:03.599
<v Speaker 1>that perspective? So, in other words, the perspective of the

0:07:03.680 --> 0:07:08.120
<v Speaker 1>rats we are inside the actual environment that we want

0:07:08.160 --> 0:07:11.120
<v Speaker 1>to describe. That makes it way more difficult for us

0:07:11.160 --> 0:07:17.400
<v Speaker 1>to uh isolate and weigh every single variable in the system. Well,

0:07:17.440 --> 0:07:21.680
<v Speaker 1>in nineteen o one, there was a professor named Cleveland Abbey.

0:07:21.840 --> 0:07:25.239
<v Speaker 1>He published a piece in a journal called Monthly Weather Review.

0:07:25.400 --> 0:07:28.160
<v Speaker 1>Now I was really sad to discover that this wasn't

0:07:28.160 --> 0:07:32.120
<v Speaker 1>actually a list of reviews for actual weather like Weather

0:07:32.160 --> 0:07:35.760
<v Speaker 1>Today was pretty good. I give it three stars. No

0:07:36.000 --> 0:07:38.600
<v Speaker 1>it It actually was a scholarly journal on the subject

0:07:38.640 --> 0:07:42.760
<v Speaker 1>of meteorology, and Abbey's piece had the title The Physical

0:07:42.840 --> 0:07:47.559
<v Speaker 1>Basis of Long Range Weather Forecasts. And in that piece,

0:07:47.560 --> 0:07:50.119
<v Speaker 1>Abbey pointed out that forecasts of the time were based

0:07:50.160 --> 0:07:54.400
<v Speaker 1>on experience rather than any real knowledge of how weather works,

0:07:54.600 --> 0:07:57.520
<v Speaker 1>and that the physical theories explained the development of whether

0:07:57.560 --> 0:08:01.400
<v Speaker 1>we're either superficial or non existent. So it goes back

0:08:01.400 --> 0:08:05.400
<v Speaker 1>to that example I gave earlier. Weather forecasting was based

0:08:05.440 --> 0:08:09.720
<v Speaker 1>on people's experience with weather, but not knowing how the

0:08:09.760 --> 0:08:13.240
<v Speaker 1>weather was actually working. So you might say, well, I

0:08:13.280 --> 0:08:17.000
<v Speaker 1>think that it may snow tomorrow based upon what the

0:08:17.040 --> 0:08:19.840
<v Speaker 1>conditions are right now, and the fact that I remember

0:08:19.880 --> 0:08:22.080
<v Speaker 1>a day that was like this where it snowed the

0:08:22.120 --> 0:08:27.080
<v Speaker 1>next day. But that's not a very scientific approach ultimately speaking,

0:08:27.080 --> 0:08:30.800
<v Speaker 1>and it doesn't have It is not based upon understanding

0:08:30.840 --> 0:08:35.160
<v Speaker 1>the factors that lead to things like a snowstorm, and

0:08:35.200 --> 0:08:38.280
<v Speaker 1>so Abby was arguing that in order to have real

0:08:38.440 --> 0:08:42.240
<v Speaker 1>weather forecasting prowess, we would have to gain that understanding

0:08:42.360 --> 0:08:47.040
<v Speaker 1>of the underlying factors of weather. Abby asserted that we

0:08:47.120 --> 0:08:50.959
<v Speaker 1>just had to understand the laws of mechanics and heat

0:08:51.320 --> 0:08:54.679
<v Speaker 1>of the atmosphere. Only then, he posited, could we use

0:08:54.720 --> 0:08:57.920
<v Speaker 1>the information to start making more accurate forecasts. And his

0:08:58.040 --> 0:09:00.200
<v Speaker 1>peace would go on to outline what he saw as

0:09:00.280 --> 0:09:04.280
<v Speaker 1>the necessary steps to get there, including a thorough investigation

0:09:04.360 --> 0:09:06.959
<v Speaker 1>of the behaviors of the atmosphere, and he said that

0:09:07.000 --> 0:09:11.199
<v Speaker 1>the science of meteorology is quote essentially the application of

0:09:11.280 --> 0:09:17.280
<v Speaker 1>hydrodynamics and thermodynamics in the atmosphere end quote, So he

0:09:17.400 --> 0:09:22.320
<v Speaker 1>was calling for the establishment of a new area of science,

0:09:22.760 --> 0:09:26.480
<v Speaker 1>specifically within meteorology, something that that would require people to

0:09:26.520 --> 0:09:30.120
<v Speaker 1>dedicate a lot of time to try and understand this

0:09:30.320 --> 0:09:35.400
<v Speaker 1>complex system that is our atmosphere. Then you have a

0:09:35.440 --> 0:09:42.000
<v Speaker 1>Norwegian scientist, Vilhelm Biekness. He was born in Christiania, Norway,

0:09:42.120 --> 0:09:44.560
<v Speaker 1>in eighteen sixty two, and as a young man he

0:09:44.640 --> 0:09:49.840
<v Speaker 1>worked with a notable physicist, Heinrich Hurts Hurts I mentioned

0:09:50.040 --> 0:09:53.200
<v Speaker 1>in our episodes on the history of electricity, you know

0:09:53.320 --> 0:09:58.000
<v Speaker 1>the Hurts. He went on to he being Bakness went

0:09:58.080 --> 0:10:01.800
<v Speaker 1>on to teach applied mechanic and mathematical physics at the

0:10:01.920 --> 0:10:04.839
<v Speaker 1>University of Stockholm, where he sussed out some theorems that

0:10:04.880 --> 0:10:08.760
<v Speaker 1>helped him create a synthesis of hydrodynamics and thermodynamics for

0:10:09.000 --> 0:10:13.560
<v Speaker 1>large scale atmospheric motions, the very thing that Abby was

0:10:13.640 --> 0:10:17.880
<v Speaker 1>calling for. Bierk Nous was the one to to develop

0:10:17.920 --> 0:10:23.600
<v Speaker 1>a very comprehensive model, the first really comprehensive model for that,

0:10:24.040 --> 0:10:26.720
<v Speaker 1>and this led to the development of air mass theory,

0:10:26.880 --> 0:10:30.439
<v Speaker 1>one of the principal ideas upon which we base weather forecasting.

0:10:31.480 --> 0:10:35.200
<v Speaker 1>Now in n Berk Now published a work titled on

0:10:35.280 --> 0:10:39.160
<v Speaker 1>the Dynamics of the Circular Vortex with Applications to the

0:10:39.200 --> 0:10:43.640
<v Speaker 1>atmosphere and to atmospheric vortex and wave motion. And it's

0:10:43.679 --> 0:10:47.400
<v Speaker 1>a real page turner, guys. This is a pretty dense

0:10:48.679 --> 0:10:51.920
<v Speaker 1>piece of of scholarly work. It's considered one of the

0:10:51.920 --> 0:10:55.800
<v Speaker 1>most important scholarly works in the field of meteorology, and

0:10:55.800 --> 0:10:58.160
<v Speaker 1>it was the basis of our understanding of general weather

0:10:58.200 --> 0:11:01.280
<v Speaker 1>pattern behaviors and why they take on the forms the

0:11:01.320 --> 0:11:03.760
<v Speaker 1>way they do. In other words, it was pretty much

0:11:03.800 --> 0:11:07.240
<v Speaker 1>what Professor Abbey was saying was necessary before we took

0:11:07.240 --> 0:11:11.200
<v Speaker 1>a rationally scientific approach to forecasting the weather. Now, what

0:11:11.400 --> 0:11:16.720
<v Speaker 1>Wilhelm illustrated was that the atmosphere and thus weather does

0:11:17.160 --> 0:11:22.280
<v Speaker 1>can be described in math through fluid dynamics factors like

0:11:22.360 --> 0:11:25.760
<v Speaker 1>temperature impact those behaviors, so you have to take that

0:11:25.800 --> 0:11:29.720
<v Speaker 1>into account. And as things change, there's a sort of

0:11:29.800 --> 0:11:34.760
<v Speaker 1>ripple effect. If you change one part of the the system,

0:11:34.800 --> 0:11:37.319
<v Speaker 1>that ripples out and affects the rest of the system

0:11:37.360 --> 0:11:41.120
<v Speaker 1>in different ways depending upon other factors. And nothing in

0:11:41.160 --> 0:11:44.840
<v Speaker 1>the atmosphere is remaining completely unchanged, and as each element

0:11:44.920 --> 0:11:48.360
<v Speaker 1>shifts or cools down, or heats up, or the density

0:11:48.520 --> 0:11:52.360
<v Speaker 1>changes or whatever it may be, it affects other parts.

0:11:52.400 --> 0:11:56.520
<v Speaker 1>So the math gets pretty challenging pretty fast. He further

0:11:56.559 --> 0:11:59.480
<v Speaker 1>went on to create a two step process for rational

0:11:59.559 --> 0:12:03.440
<v Speaker 1>forecast nesting of whether now. The first step was diagnostic,

0:12:03.880 --> 0:12:07.240
<v Speaker 1>which is, in other words, using observations to determine what

0:12:07.440 --> 0:12:10.120
<v Speaker 1>is the present state of the atmosphere. This is where

0:12:10.480 --> 0:12:12.760
<v Speaker 1>you take all those readings and you say what is

0:12:12.800 --> 0:12:16.240
<v Speaker 1>going on right now? That's the diagnostic step, and it's

0:12:16.320 --> 0:12:19.400
<v Speaker 1>absolutely necessary before you can do anything else. You can't

0:12:19.440 --> 0:12:22.160
<v Speaker 1>say what's going to happen next until you have an

0:12:22.200 --> 0:12:26.640
<v Speaker 1>understanding of what is happening right now. The second step

0:12:26.720 --> 0:12:30.680
<v Speaker 1>was prognostic, which meant that you would use that information

0:12:30.720 --> 0:12:34.920
<v Speaker 1>from the diagnostic step and project outwards and say, all right, well,

0:12:35.120 --> 0:12:38.120
<v Speaker 1>based upon what we know is happening right now, what

0:12:38.320 --> 0:12:41.400
<v Speaker 1>is going to happen twelve hours from now, or a

0:12:41.520 --> 0:12:44.679
<v Speaker 1>day from now or two days from now. And you

0:12:44.720 --> 0:12:47.280
<v Speaker 1>would have to use the information you had gathered in

0:12:47.320 --> 0:12:50.600
<v Speaker 1>the diagnostic step, combined with our knowledge of the laws

0:12:50.640 --> 0:12:56.520
<v Speaker 1>of motion for atmospheric masses, to predict what would happen next. Now,

0:12:56.600 --> 0:12:59.840
<v Speaker 1>if you could strip everything away and just look at

0:12:59.840 --> 0:13:02.720
<v Speaker 1>the math, you'd be looking at a collection of what

0:13:02.840 --> 0:13:06.600
<v Speaker 1>are called partial differential equations. The mathematicians out there know

0:13:06.679 --> 0:13:10.160
<v Speaker 1>exactly what I'm talking about. These are equations that deal

0:13:10.200 --> 0:13:14.640
<v Speaker 1>with rates of change with respect to continuous variables. So

0:13:14.679 --> 0:13:19.040
<v Speaker 1>you're not just talking about variables like temperature, pressure, and velocity.

0:13:19.360 --> 0:13:21.840
<v Speaker 1>You are talking about those, but you're also talking about

0:13:21.840 --> 0:13:26.640
<v Speaker 1>the rate of change of those variables. How quickly is

0:13:26.679 --> 0:13:31.320
<v Speaker 1>the temperature changing, how quickly is the pressure changing, etcetera. Now,

0:13:31.320 --> 0:13:35.200
<v Speaker 1>the way you frame and solve these equations defines your

0:13:35.600 --> 0:13:41.439
<v Speaker 1>weather model. Different weather models place different emphasis on these

0:13:41.520 --> 0:13:44.320
<v Speaker 1>variables and the rates of change. All of this boils

0:13:44.320 --> 0:13:48.760
<v Speaker 1>down to a computer program ultimately that solves these equations

0:13:48.840 --> 0:13:52.560
<v Speaker 1>as you have directed. So one model might approximate different

0:13:52.559 --> 0:13:55.960
<v Speaker 1>equations one way and another model does so in a

0:13:56.080 --> 0:13:59.240
<v Speaker 1>different way, and thus you're going to get two different forecasts.

0:13:59.280 --> 0:14:03.320
<v Speaker 1>Consulting these two different models, they might resemble one another,

0:14:03.480 --> 0:14:06.040
<v Speaker 1>but they're taking different pathways to get to their destination,

0:14:06.280 --> 0:14:10.400
<v Speaker 1>so sometimes they might be very different from one another.

0:14:10.800 --> 0:14:13.480
<v Speaker 1>And it's all because of the way you have told

0:14:13.520 --> 0:14:18.400
<v Speaker 1>the program to prioritize the various processes, which ones you know,

0:14:18.400 --> 0:14:23.320
<v Speaker 1>which factors have the most weight and under what circumstances. Now,

0:14:23.360 --> 0:14:25.880
<v Speaker 1>this doesn't necessarily mean one model is by its nature

0:14:25.960 --> 0:14:29.600
<v Speaker 1>superior to the other. Some models are for specific regions

0:14:29.600 --> 0:14:32.080
<v Speaker 1>in the world, and those regions, due to geography and

0:14:32.160 --> 0:14:35.760
<v Speaker 1>general atmospheric motions, may require more importance to be placed

0:14:35.840 --> 0:14:40.280
<v Speaker 1>on certain sets of variables rather than others. Now Berkness

0:14:40.400 --> 0:14:45.760
<v Speaker 1>identified seven variables he saw as critical for accurate weather forecasting.

0:14:46.120 --> 0:14:51.160
<v Speaker 1>That includes pressure, temperature, density, humidity, and then three different

0:14:51.200 --> 0:14:56.160
<v Speaker 1>components of velocity. He also identified seven equations, three therma

0:14:56.800 --> 0:15:00.560
<v Speaker 1>hydro dynamic equations I should say three hydro dynamic equation, emotion,

0:15:01.120 --> 0:15:05.040
<v Speaker 1>the continuity equation, the equation of state, and equations expressing

0:15:05.080 --> 0:15:08.160
<v Speaker 1>the first two laws of thermo dynamics. Now, keep in

0:15:08.200 --> 0:15:11.400
<v Speaker 1>mind that the atmosphere is three dimensional. You have to

0:15:11.480 --> 0:15:16.160
<v Speaker 1>essentially consider any region within that area a three dimensional grid.

0:15:16.800 --> 0:15:19.400
<v Speaker 1>So your grid has an x, y, and z axis,

0:15:20.080 --> 0:15:24.080
<v Speaker 1>and the events within one part of that grid can

0:15:24.120 --> 0:15:28.200
<v Speaker 1>affect other parts of it, particularly atmospheric motion. And you

0:15:28.240 --> 0:15:31.560
<v Speaker 1>need to figure out how to take partial derivatives which

0:15:32.200 --> 0:15:36.680
<v Speaker 1>computers can't really handle, and then turn them into approximate

0:15:36.760 --> 0:15:42.560
<v Speaker 1>partial derivatives that computers can handle instead. This approximation adds

0:15:42.560 --> 0:15:46.520
<v Speaker 1>in a bit of imprecision by its very nature. But

0:15:46.600 --> 0:15:51.240
<v Speaker 1>then's the brakes. And speaking of brakes, let's take a

0:15:51.320 --> 0:16:00.880
<v Speaker 1>quick one right now to thank our sponsor. So getting

0:16:00.920 --> 0:16:06.080
<v Speaker 1>back into forming weather models. There's a meteorologist named Lewis

0:16:06.200 --> 0:16:10.080
<v Speaker 1>Fry Richardson who was influenced by Berkness, and he did

0:16:10.160 --> 0:16:13.520
<v Speaker 1>his best to tackle the problem of numerical weather forecasting,

0:16:13.600 --> 0:16:16.840
<v Speaker 1>but he stated that the sheer amount of computation was

0:16:16.920 --> 0:16:19.960
<v Speaker 1>impractical for the time. This would be in the early

0:16:20.040 --> 0:16:23.200
<v Speaker 1>twentieth century, first couple of decades of the nineteen hundreds.

0:16:23.720 --> 0:16:27.800
<v Speaker 1>He did say, quote, perhaps someday in the dim future,

0:16:28.080 --> 0:16:31.360
<v Speaker 1>it will be possible to advance the computations faster than

0:16:31.400 --> 0:16:34.920
<v Speaker 1>the weather advances. But that is a dream end quote.

0:16:35.240 --> 0:16:37.960
<v Speaker 1>So he's saying, by the time I'm able to work

0:16:37.960 --> 0:16:40.720
<v Speaker 1>out the math, whatever the weather was gonna be has

0:16:40.760 --> 0:16:45.560
<v Speaker 1>already happened. I'm predicting what happened hours ago. Uh. And

0:16:45.560 --> 0:16:47.800
<v Speaker 1>that was a real problem. Was just that again, you

0:16:47.880 --> 0:16:50.720
<v Speaker 1>had these very complex equations with lots of points of

0:16:50.800 --> 0:16:53.440
<v Speaker 1>data and lots of variables that you had to solve for,

0:16:54.080 --> 0:16:56.080
<v Speaker 1>and by the time you would be done with all

0:16:56.080 --> 0:17:01.520
<v Speaker 1>the calculations, the time had passed. So he was saying,

0:17:01.520 --> 0:17:06.480
<v Speaker 1>there is a need for some sort of engine that

0:17:06.560 --> 0:17:11.720
<v Speaker 1>can do computations faster than what humans can do. So

0:17:11.760 --> 0:17:13.960
<v Speaker 1>the math was just too complex to complete without the

0:17:14.080 --> 0:17:17.720
<v Speaker 1>use of that computational engine. One person determined to help

0:17:17.720 --> 0:17:20.680
<v Speaker 1>design such an engine was John von Neumann, who was

0:17:20.720 --> 0:17:24.439
<v Speaker 1>a mathematician who made numerous contributions to the sciences, and

0:17:24.440 --> 0:17:26.639
<v Speaker 1>he realized that some of the more advanced problems in

0:17:26.720 --> 0:17:30.520
<v Speaker 1>hydrodynamics and weather forecasting would benefit from a powerful automatic

0:17:30.560 --> 0:17:34.199
<v Speaker 1>computational machine. He worked on a project at Princeton at

0:17:34.240 --> 0:17:36.960
<v Speaker 1>the Institute for Advanced Studies and it would become known

0:17:37.000 --> 0:17:42.120
<v Speaker 1>as the Electronic Computer Project. Meanwhile, over at the University

0:17:42.119 --> 0:17:46.600
<v Speaker 1>of Pennsylvania's More School of Electrical Engineering, you had J. G.

0:17:46.880 --> 0:17:50.200
<v Speaker 1>Brainerd who was heading up a project, and J. Presspur

0:17:50.280 --> 0:17:53.600
<v Speaker 1>Eckert and John W. Malchley who were working on what

0:17:53.640 --> 0:17:59.399
<v Speaker 1>was called the Electronic Numerical Integrator and Computer or NIAC

0:17:59.760 --> 0:18:03.080
<v Speaker 1>for short, and computer nerds out there, I consider myself

0:18:03.119 --> 0:18:06.040
<v Speaker 1>one of them will kind of bristle at the sound

0:18:06.040 --> 0:18:09.040
<v Speaker 1>of ENNIAC. They might prick up their ears and say, oh,

0:18:09.280 --> 0:18:11.879
<v Speaker 1>I know, I've heard of ENNIAC. ENIAC being one of

0:18:11.880 --> 0:18:16.360
<v Speaker 1>those early early computers in the dawn of the computing age.

0:18:16.720 --> 0:18:20.320
<v Speaker 1>Well brain Nerd, the man who was heading this project,

0:18:20.400 --> 0:18:23.560
<v Speaker 1>invited von Neumann over to the University of Pennsylvania to

0:18:23.640 --> 0:18:25.880
<v Speaker 1>check out ENIAC, and von Neuman would end up having

0:18:25.920 --> 0:18:29.119
<v Speaker 1>these very deep discussions with the team, and those discussions

0:18:29.160 --> 0:18:33.240
<v Speaker 1>would help inform the design of the successor to ENIAC,

0:18:33.680 --> 0:18:36.680
<v Speaker 1>and these early computers would become some of the first

0:18:36.720 --> 0:18:40.639
<v Speaker 1>capable of tackling those difficult computational problems. I was mentioning

0:18:40.640 --> 0:18:44.119
<v Speaker 1>a second ago, and that brings us to the concept

0:18:44.600 --> 0:18:48.000
<v Speaker 1>of the weather model. Now, your weather model is an

0:18:48.040 --> 0:18:51.280
<v Speaker 1>advanced computer program that runs all of these sorts of

0:18:51.320 --> 0:18:54.399
<v Speaker 1>equations and then calculates outcomes. So, in other words, it

0:18:54.520 --> 0:18:57.920
<v Speaker 1>generates your weather forecast based upon those points of data.

0:18:58.680 --> 0:19:01.120
<v Speaker 1>Many of these weather models have been written in four

0:19:01.240 --> 0:19:05.000
<v Speaker 1>chan for Tran, I should say, largely because that's how

0:19:05.040 --> 0:19:08.560
<v Speaker 1>it's been done for decades. So if you've ever chatted

0:19:08.600 --> 0:19:11.000
<v Speaker 1>with somebody and you're saying, why are we doing it

0:19:11.040 --> 0:19:13.080
<v Speaker 1>this way, and they say, it's because it's how we've

0:19:13.119 --> 0:19:15.600
<v Speaker 1>always done it, that's sort of the case with Fortran

0:19:15.840 --> 0:19:19.919
<v Speaker 1>in weather models. Uh, that's one of the reasons. But

0:19:20.440 --> 0:19:26.680
<v Speaker 1>it's also a very useful language that has evolved over time.

0:19:26.720 --> 0:19:29.680
<v Speaker 1>It's not like it was developed and then forgotten about.

0:19:29.800 --> 0:19:33.879
<v Speaker 1>It has received a lot of I hesitate to use

0:19:33.880 --> 0:19:37.679
<v Speaker 1>the word love, but development over the years. Now, this

0:19:37.760 --> 0:19:40.960
<v Speaker 1>four trend program is compiled into machine language. That's the

0:19:41.040 --> 0:19:43.920
<v Speaker 1>language that computers understand, and we'll talk more about that

0:19:44.000 --> 0:19:47.000
<v Speaker 1>in the Programming Languages episode that will be coming up soon.

0:19:47.440 --> 0:19:49.600
<v Speaker 1>So keeping the year out for those episodes, they should

0:19:49.600 --> 0:19:54.159
<v Speaker 1>be following this one shortly. The program, the weather model

0:19:54.240 --> 0:19:56.879
<v Speaker 1>takes all this information, the data fed to it from

0:19:56.960 --> 0:20:01.520
<v Speaker 1>multiple sources, all those observation stations, and all those equations

0:20:01.560 --> 0:20:04.920
<v Speaker 1>based off of fluid dynamics and thermodynamics, and steps through

0:20:05.040 --> 0:20:08.959
<v Speaker 1>in time to simulate what will happen next. So the

0:20:08.960 --> 0:20:13.399
<v Speaker 1>computer is actively trying to simulate the behavior of weather

0:20:13.440 --> 0:20:19.680
<v Speaker 1>patterns based upon our understanding of hydrodynamics, thermodynamics, and all

0:20:19.680 --> 0:20:25.120
<v Speaker 1>of these variables. So it's it's actively simulating the outcomes.

0:20:25.359 --> 0:20:29.679
<v Speaker 1>Now you're getting these simulations in the form of numeric answers.

0:20:29.720 --> 0:20:35.159
<v Speaker 1>It's not like you're looking at a graphic representation of weather.

0:20:35.240 --> 0:20:37.280
<v Speaker 1>You're not, you know, looking at your computer and you

0:20:37.320 --> 0:20:40.080
<v Speaker 1>see a massive storm is roiling across the screen. I'm

0:20:40.119 --> 0:20:42.880
<v Speaker 1>pretty sure that's how Hollywood would do it. But we're

0:20:42.880 --> 0:20:46.560
<v Speaker 1>talking more about lots of numbers, so not as sexy

0:20:46.960 --> 0:20:51.680
<v Speaker 1>as say, watching Twister on Netflix and you're saying, that's

0:20:51.720 --> 0:20:53.879
<v Speaker 1>what the way, what's the what the weather is going

0:20:53.920 --> 0:20:59.119
<v Speaker 1>to be? Uh, that's not exactly the case. Sadly, Maybe

0:20:59.119 --> 0:21:02.520
<v Speaker 1>one day we'll get there, but not not right now now.

0:21:02.560 --> 0:21:06.800
<v Speaker 1>Some simulations can project out for multiple days, and some

0:21:06.880 --> 0:21:10.560
<v Speaker 1>are more immediate. Some look at short range forecast, some

0:21:10.640 --> 0:21:13.439
<v Speaker 1>do mid range and long range as well, and the

0:21:13.480 --> 0:21:16.960
<v Speaker 1>highest amount of accuracy typically is within the next several hours.

0:21:17.400 --> 0:21:19.960
<v Speaker 1>And then, of course the further out you go from

0:21:20.040 --> 0:21:23.160
<v Speaker 1>the moment you gathered all that data and did your

0:21:23.200 --> 0:21:28.040
<v Speaker 1>diagnostic stuff, the more you are likely to diverge from

0:21:28.160 --> 0:21:32.639
<v Speaker 1>reality for your forecast, more uncertainty enters into the picture

0:21:32.760 --> 0:21:36.919
<v Speaker 1>because it's hard to predict how all of those different

0:21:37.000 --> 0:21:41.040
<v Speaker 1>variables are going to uh what what their state will

0:21:41.080 --> 0:21:43.000
<v Speaker 1>be at any given point in the future. And the

0:21:43.000 --> 0:21:46.000
<v Speaker 1>further out you go, the more uncertain you're going to be. Typically,

0:21:46.760 --> 0:21:49.280
<v Speaker 1>So let's make up a hypothetical situation to kind of

0:21:49.320 --> 0:21:53.560
<v Speaker 1>explain what I'm talking about here. Let's say I'm in

0:21:53.600 --> 0:21:57.000
<v Speaker 1>the north of wester Ross and I know winter is coming.

0:21:57.640 --> 0:22:00.760
<v Speaker 1>My weather forecast model is very much focused on atmospheric

0:22:00.800 --> 0:22:04.320
<v Speaker 1>movements from beyond the wall and less concerned with other

0:22:04.440 --> 0:22:09.320
<v Speaker 1>variables like maybe humidity or I don't know, dragons, because

0:22:09.400 --> 0:22:11.919
<v Speaker 1>humidity and dragons don't play such a large role in

0:22:11.920 --> 0:22:15.440
<v Speaker 1>the weather patterns of my region, right, I mean, I'm

0:22:15.480 --> 0:22:18.879
<v Speaker 1>one of the Starks in this hypothesis. The model I

0:22:18.920 --> 0:22:22.280
<v Speaker 1>have created is as accurate a representation of how patterns

0:22:22.320 --> 0:22:25.320
<v Speaker 1>emerge and behave in my region as I can get

0:22:25.320 --> 0:22:28.439
<v Speaker 1>my hands on. So that's what I rely upon. But

0:22:28.520 --> 0:22:32.800
<v Speaker 1>let's say you in your fancy pants King's landing house

0:22:33.240 --> 0:22:36.240
<v Speaker 1>are concerned with trade winds coming in from out over

0:22:36.280 --> 0:22:39.560
<v Speaker 1>the sea, because that's a large influencer of the weather

0:22:39.600 --> 0:22:43.440
<v Speaker 1>in your area. So your weather model takes that into

0:22:43.480 --> 0:22:46.320
<v Speaker 1>account and gives it greater weight than some of the

0:22:46.400 --> 0:22:49.159
<v Speaker 1>variables that I'm concerned with. And this is so that

0:22:49.240 --> 0:22:53.040
<v Speaker 1>you can create accurate forecasts for your area. Your model

0:22:53.080 --> 0:22:55.960
<v Speaker 1>and my model aren't equivalent. Your model would not work

0:22:55.960 --> 0:22:59.160
<v Speaker 1>as well in my region, and vice versa. And neither

0:22:59.240 --> 0:23:02.480
<v Speaker 1>model is comp inhensive, which means neither model covers all

0:23:02.520 --> 0:23:05.800
<v Speaker 1>of wester Roast. That's very much regional. Now in the

0:23:05.840 --> 0:23:11.320
<v Speaker 1>real world spoiler alert, Game of Thrones isn't real. We

0:23:11.480 --> 0:23:15.320
<v Speaker 1>sometimes find that our computer models are mostly good, but

0:23:15.480 --> 0:23:19.960
<v Speaker 1>not perfect. Some may, under certain conditions under or over

0:23:20.480 --> 0:23:23.399
<v Speaker 1>estimate the temperature for example. Now, this could happen for

0:23:23.520 --> 0:23:25.760
<v Speaker 1>lots of different reasons, such as, you might have a

0:23:25.800 --> 0:23:27.880
<v Speaker 1>region that's close to the ocean, and the ocean could

0:23:27.920 --> 0:23:31.040
<v Speaker 1>affect the temperature in ways that the model is not

0:23:31.320 --> 0:23:35.520
<v Speaker 1>quite capable of accounting for. So you might experience more

0:23:35.600 --> 0:23:38.960
<v Speaker 1>windy conditions than other areas, and the wind may affect

0:23:38.960 --> 0:23:42.720
<v Speaker 1>temperatures in ways that the model can anticipate. The wave

0:23:42.800 --> 0:23:46.880
<v Speaker 1>dynamics could affect whether in ways that the model can't anticipate,

0:23:47.960 --> 0:23:50.119
<v Speaker 1>so you still have meteorologists who are dealing with this,

0:23:50.200 --> 0:23:53.520
<v Speaker 1>and they're fudging the numbers a bit once they've been processed,

0:23:53.560 --> 0:23:58.080
<v Speaker 1>because you learn over time how well your model does

0:23:58.320 --> 0:24:02.119
<v Speaker 1>versus reality. So you can look at the results of

0:24:02.160 --> 0:24:05.600
<v Speaker 1>your model, what does the predictions say, and then you

0:24:05.640 --> 0:24:09.720
<v Speaker 1>can compare that against the actual results that you get

0:24:09.760 --> 0:24:12.080
<v Speaker 1>just by waiting around. Right, you wait around and you

0:24:12.119 --> 0:24:15.320
<v Speaker 1>see what actually happens. You compare that to the forecast

0:24:15.359 --> 0:24:17.960
<v Speaker 1>that your model gave, and you start to look and

0:24:18.000 --> 0:24:21.000
<v Speaker 1>see if there's any any adjustment that needs to be made,

0:24:21.080 --> 0:24:23.640
<v Speaker 1>or in some cases you may just say, well, this

0:24:23.680 --> 0:24:28.440
<v Speaker 1>model is frequently about two degrees warmer than what really happens,

0:24:28.520 --> 0:24:32.080
<v Speaker 1>so we're going to build in an adjustment. We will

0:24:32.119 --> 0:24:36.760
<v Speaker 1>automatically no to decrease the temperature forecast by two degrees

0:24:37.359 --> 0:24:40.000
<v Speaker 1>from this model, and that we are more likely to

0:24:40.240 --> 0:24:43.680
<v Speaker 1>hit on what the actual temperature will be. This happens

0:24:43.720 --> 0:24:46.560
<v Speaker 1>all the time with lots of computer models, not just

0:24:46.600 --> 0:24:50.879
<v Speaker 1>for temperature, but for other variables as well, and really

0:24:51.080 --> 0:24:53.320
<v Speaker 1>we should expect this to continue to happen because we

0:24:53.359 --> 0:24:57.320
<v Speaker 1>cannot have a perfect understanding of how everything is going

0:24:57.359 --> 0:25:00.919
<v Speaker 1>to be and builded into a computer, not yet, possibly

0:25:01.000 --> 0:25:05.320
<v Speaker 1>not ever. It is so complex and so dependent upon

0:25:05.359 --> 0:25:08.439
<v Speaker 1>so many different variables. But what we can do is

0:25:08.480 --> 0:25:13.480
<v Speaker 1>we can correct for those known problems. If we know

0:25:13.640 --> 0:25:15.639
<v Speaker 1>that there is an issue and it's not likely to

0:25:15.720 --> 0:25:18.200
<v Speaker 1>cause a ripple effect, which I'll talk about a little

0:25:18.200 --> 0:25:21.560
<v Speaker 1>bit later in this episode, then we can just correct

0:25:21.560 --> 0:25:23.880
<v Speaker 1>for it at the end and say, all right, let's

0:25:23.880 --> 0:25:26.240
<v Speaker 1>bump up or bump down the temperature by a couple

0:25:26.280 --> 0:25:29.359
<v Speaker 1>of degrees based upon our knowledge of how this model

0:25:29.480 --> 0:25:33.520
<v Speaker 1>performs against what really happens. It's kind of interesting because

0:25:33.520 --> 0:25:37.280
<v Speaker 1>it really nails home how computers are all about precision

0:25:37.320 --> 0:25:42.160
<v Speaker 1>and replication. They don't tend to give you vague guesses.

0:25:42.200 --> 0:25:47.080
<v Speaker 1>They can create different answers that have different probably probabilities

0:25:47.080 --> 0:25:50.760
<v Speaker 1>of being correct, and then choose whichever one is the

0:25:50.800 --> 0:25:57.280
<v Speaker 1>most likely to be correct. But they are about making

0:25:57.320 --> 0:26:03.440
<v Speaker 1>these precise uh outputs, and we as humans are the

0:26:03.480 --> 0:26:06.119
<v Speaker 1>ones who have to add extra levels of interpretation on

0:26:06.240 --> 0:26:09.200
<v Speaker 1>top of that, which means that there's still a human

0:26:09.240 --> 0:26:13.639
<v Speaker 1>being associated with this process. It's kind of what you

0:26:13.840 --> 0:26:16.440
<v Speaker 1>have to do with an old scale. If you had

0:26:16.440 --> 0:26:18.679
<v Speaker 1>an old like weight scale and it was off of

0:26:18.720 --> 0:26:22.159
<v Speaker 1>its calibration, you couldn't quite get it to reset at zero.

0:26:22.359 --> 0:26:24.240
<v Speaker 1>So let's say you notice that your scales giving a

0:26:24.320 --> 0:26:27.080
<v Speaker 1>reading that's always two pounds less than what it should be.

0:26:27.560 --> 0:26:29.560
<v Speaker 1>You know that when you weigh something, you need to

0:26:29.600 --> 0:26:32.800
<v Speaker 1>add two pounds to your scales reading whenever you weigh something.

0:26:33.119 --> 0:26:36.000
<v Speaker 1>Meteorologists will often do the same thing, and sometimes they'll

0:26:36.040 --> 0:26:39.080
<v Speaker 1>do it to just a very specific region within a

0:26:39.119 --> 0:26:42.480
<v Speaker 1>computer models area of coverage. They know that the model

0:26:42.520 --> 0:26:45.199
<v Speaker 1>has a history of under or overestimating things, and so

0:26:45.280 --> 0:26:49.199
<v Speaker 1>they just correct for it. Now, for that reason, we

0:26:49.280 --> 0:26:52.120
<v Speaker 1>still have human beings involved in meteorology and all these

0:26:52.119 --> 0:26:56.080
<v Speaker 1>different phases. Meteorologists use their training and expertise to interpret

0:26:56.119 --> 0:26:58.960
<v Speaker 1>the output from weather models, and they learned the quirks

0:26:58.960 --> 0:27:01.879
<v Speaker 1>of the models, even as new versions of those models

0:27:01.920 --> 0:27:05.120
<v Speaker 1>come out to correct for inaccuracies or to increase resolution

0:27:05.240 --> 0:27:09.120
<v Speaker 1>or frequency. So remember whether forecasting depends upon the quality

0:27:09.240 --> 0:27:12.440
<v Speaker 1>of the weather model, the accuracy of the information being

0:27:12.480 --> 0:27:15.840
<v Speaker 1>fed into the model, and the frequency with which that

0:27:15.880 --> 0:27:19.560
<v Speaker 1>information comes in, and the density of the observations within

0:27:19.600 --> 0:27:23.280
<v Speaker 1>that region. All of these things will affect the accuracy

0:27:23.400 --> 0:27:26.120
<v Speaker 1>of the ultimate weather forecast to come out of that

0:27:26.160 --> 0:27:29.320
<v Speaker 1>computer model. If you have the best model in the world,

0:27:29.720 --> 0:27:32.760
<v Speaker 1>it's still not going to give you a very accurate prediction.

0:27:33.000 --> 0:27:36.280
<v Speaker 1>If either you don't have enough observation stations so your

0:27:36.280 --> 0:27:41.400
<v Speaker 1>resolution is low, you aren't consulting your observation stations frequently enough,

0:27:41.880 --> 0:27:47.040
<v Speaker 1>so you are relying on older information, or the information

0:27:47.160 --> 0:27:50.480
<v Speaker 1>you're feeding into your model is somehow inaccurate. Let's say

0:27:50.480 --> 0:27:53.480
<v Speaker 1>that you have some sensors that aren't working properly and

0:27:53.520 --> 0:27:58.280
<v Speaker 1>are giving you, uh the wrong reading for some element here,

0:27:58.640 --> 0:28:02.439
<v Speaker 1>whether it's air press or temperature, whatever it might be. Well,

0:28:02.520 --> 0:28:05.240
<v Speaker 1>if that information gets fed into your computer model, then

0:28:05.520 --> 0:28:07.960
<v Speaker 1>you would expect that the outcome is not going to

0:28:07.960 --> 0:28:11.080
<v Speaker 1>be accurate because it wasn't accurate information going in, or,

0:28:11.359 --> 0:28:16.440
<v Speaker 1>as some people say, garbage in garbage out. Your outcomes

0:28:16.440 --> 0:28:18.520
<v Speaker 1>are only going to be as good as your data,

0:28:19.680 --> 0:28:21.240
<v Speaker 1>as well as the fact that you have to worry

0:28:21.280 --> 0:28:24.800
<v Speaker 1>about the the quality of your model itself. Now, if

0:28:24.800 --> 0:28:28.000
<v Speaker 1>this sounds like it's a ton of processing, it is.

0:28:28.400 --> 0:28:31.480
<v Speaker 1>Traditionally one of the big applications we have for supercomputers

0:28:31.680 --> 0:28:35.040
<v Speaker 1>is for weather models. So whenever you hear about supercomputers

0:28:35.080 --> 0:28:39.480
<v Speaker 1>and the massive amounts of processing power they have. Often

0:28:39.960 --> 0:28:45.560
<v Speaker 1>these computers are being put towards the task of simulating weather,

0:28:45.680 --> 0:28:48.720
<v Speaker 1>taking these weather models and trying to get more and

0:28:48.760 --> 0:28:53.440
<v Speaker 1>more accurate simulations of what is going to happen. ANIAC

0:28:53.480 --> 0:28:56.280
<v Speaker 1>itself was used to generate weather forecasts. But even though

0:28:56.400 --> 0:28:58.800
<v Speaker 1>NIAC was a big jump forward on just working out

0:28:58.800 --> 0:29:01.680
<v Speaker 1>the equations by hand, it was still limited and the

0:29:01.720 --> 0:29:05.600
<v Speaker 1>weather model wasn't much more than a barotropic equation. A

0:29:05.680 --> 0:29:09.480
<v Speaker 1>barotropic equation is a fluid dynamics problem in which density

0:29:09.520 --> 0:29:13.800
<v Speaker 1>is a function of pressure only. Even this limited interpretation

0:29:13.840 --> 0:29:16.280
<v Speaker 1>of the factors that affect weather was still a big

0:29:16.400 --> 0:29:20.280
<v Speaker 1>leap forward. However, any act success led to the development

0:29:20.320 --> 0:29:24.040
<v Speaker 1>of new models, including multi level models, and one such

0:29:24.080 --> 0:29:27.240
<v Speaker 1>model was the product of several scientists work in the

0:29:28.040 --> 0:29:31.520
<v Speaker 1>in the in the wake of a massive storm system

0:29:31.560 --> 0:29:35.200
<v Speaker 1>that took place on Thanksgiving Day in nineteen fifty. So

0:29:35.320 --> 0:29:39.280
<v Speaker 1>this big storm ended up being a great opportunity for

0:29:39.360 --> 0:29:42.000
<v Speaker 1>the scientists who were trying to make a weather model,

0:29:42.040 --> 0:29:46.360
<v Speaker 1>and the model they developed seemed to simulate actual events accurately.

0:29:46.400 --> 0:29:48.840
<v Speaker 1>They were very excited. This multi level model appeared to

0:29:48.840 --> 0:29:51.880
<v Speaker 1>be much more accurate than the barotropic model that had

0:29:51.920 --> 0:29:55.120
<v Speaker 1>been used as it turned out their model was only

0:29:55.160 --> 0:29:59.080
<v Speaker 1>really accurate for that one set of circumstances. They found

0:29:59.080 --> 0:30:03.160
<v Speaker 1>that as they ran more simulations, it was not giving

0:30:03.200 --> 0:30:08.880
<v Speaker 1>accurate forecasts, at least not in every situation. So it

0:30:08.920 --> 0:30:12.880
<v Speaker 1>turned out that that weather model was really great for

0:30:13.040 --> 0:30:16.640
<v Speaker 1>one set of circumstances, but it didn't handle other ones

0:30:17.160 --> 0:30:19.920
<v Speaker 1>nearly as well. It didn't get nearly as accurate a result,

0:30:20.440 --> 0:30:23.840
<v Speaker 1>and the barotropic model actually was superior. The older model

0:30:23.880 --> 0:30:25.880
<v Speaker 1>that had been running on any act was superior to

0:30:26.000 --> 0:30:29.640
<v Speaker 1>the multi level model, at least in some situations. So

0:30:29.760 --> 0:30:32.840
<v Speaker 1>throughout the nineteen fifties, meteorologists were mostly relying on this

0:30:32.920 --> 0:30:37.000
<v Speaker 1>older barotropic model because it was more accurate more often

0:30:37.520 --> 0:30:41.440
<v Speaker 1>than multi level models that had been proposed. Starting in

0:30:41.520 --> 0:30:44.719
<v Speaker 1>ninety eight, multi level models began to gain more acceptance

0:30:44.760 --> 0:30:47.280
<v Speaker 1>as they tuned into the right waitings for the various

0:30:47.320 --> 0:30:50.800
<v Speaker 1>variables and weather forecasting, and from that point forward we

0:30:50.840 --> 0:30:55.360
<v Speaker 1>saw more varieties of weather models arise, each with its

0:30:55.400 --> 0:30:59.960
<v Speaker 1>own pros and cons, And what followed were numerous symposes

0:31:00.360 --> 0:31:03.440
<v Speaker 1>about computational models and the machines that would be needed

0:31:03.440 --> 0:31:05.840
<v Speaker 1>to crunch the numbers in a reasonable amount of time.

0:31:05.880 --> 0:31:11.320
<v Speaker 1>And it gets super duper technical. Now today we have

0:31:11.480 --> 0:31:14.880
<v Speaker 1>many models, most of them covering specific regions. Creating a

0:31:14.960 --> 0:31:19.040
<v Speaker 1>global weather model is an enormous task, and not just

0:31:19.120 --> 0:31:22.200
<v Speaker 1>to combine our understanding of weather behavior from around the globe,

0:31:22.480 --> 0:31:25.040
<v Speaker 1>but also to find a computer capable of processing such

0:31:25.080 --> 0:31:28.040
<v Speaker 1>an enormous amount of data regularly enough to give us

0:31:28.040 --> 0:31:30.720
<v Speaker 1>an accurate weather forecast at any given time for any

0:31:30.760 --> 0:31:34.120
<v Speaker 1>given location. But here's some of the models that we

0:31:34.200 --> 0:31:36.800
<v Speaker 1>use today. One of the big ones is the European

0:31:36.880 --> 0:31:41.760
<v Speaker 1>Center for Medium Range Weather Forecasts or e c MWF.

0:31:42.320 --> 0:31:44.760
<v Speaker 1>They provide one of the more important models in the world.

0:31:45.160 --> 0:31:48.600
<v Speaker 1>The Journal of Computational Physics describes the model as quote

0:31:49.120 --> 0:31:54.240
<v Speaker 1>a spectral primitive equation model with a semi Lagrangian, semi

0:31:54.280 --> 0:31:58.400
<v Speaker 1>implicit time scheme and a comprehensive treatment of physical processes.

0:32:00.120 --> 0:32:04.080
<v Speaker 1>I'm pretty sure that means it can summon cthulhu. In addition,

0:32:04.400 --> 0:32:07.440
<v Speaker 1>this model is coupled with an ocean wave model, and

0:32:07.600 --> 0:32:11.640
<v Speaker 1>the basis is the Integrated Forecast System or i f S.

0:32:12.000 --> 0:32:15.680
<v Speaker 1>The model runs on high performance supercomputers capable of performing

0:32:15.720 --> 0:32:19.520
<v Speaker 1>several terra flops of calculations, and just a reminder, a

0:32:19.640 --> 0:32:24.240
<v Speaker 1>flop is a floating point operations per second. So generally speaking,

0:32:24.480 --> 0:32:26.640
<v Speaker 1>the number of flops the computer can perform gives you

0:32:26.640 --> 0:32:30.040
<v Speaker 1>an idea of its processing power or speed, and terra

0:32:30.120 --> 0:32:34.480
<v Speaker 1>flops means a lot. All Right, we're in the home

0:32:34.600 --> 0:32:38.960
<v Speaker 1>stretch for meteorology. But before we jump into that final section,

0:32:39.040 --> 0:32:49.400
<v Speaker 1>let's take another quick break to thank our sponsor. Alright,

0:32:49.440 --> 0:32:52.920
<v Speaker 1>I just talked about the weather model over the big

0:32:52.960 --> 0:32:55.800
<v Speaker 1>one over in Europe, and keep in mind there are

0:32:56.120 --> 0:32:59.040
<v Speaker 1>dozens of weather models, but over here in the good

0:32:59.040 --> 0:33:01.360
<v Speaker 1>old US of A, you've got a big one with

0:33:01.400 --> 0:33:05.360
<v Speaker 1>the National Centers for Environmental Prediction or in c e

0:33:05.480 --> 0:33:09.600
<v Speaker 1>P as it is known, and it has a globally

0:33:09.680 --> 0:33:13.880
<v Speaker 1>gridded set of data about the state of the Earth's atmosphere.

0:33:13.960 --> 0:33:16.520
<v Speaker 1>And there are tons of other models too. As I

0:33:16.560 --> 0:33:19.400
<v Speaker 1>was just saying, some of them are more localized than others.

0:33:19.640 --> 0:33:22.400
<v Speaker 1>Some of them are capable of much higher resolution because

0:33:22.400 --> 0:33:25.840
<v Speaker 1>they consult more observation systems with respect the area covered

0:33:25.920 --> 0:33:29.840
<v Speaker 1>by the model, and those grids are important. You want

0:33:29.960 --> 0:33:33.800
<v Speaker 1>um smaller grids, You want the the sides of each

0:33:34.440 --> 0:33:36.320
<v Speaker 1>of the grids. To keep in mind, this is three dimensional.

0:33:36.480 --> 0:33:40.680
<v Speaker 1>It's not just um land area, but elevation as well.

0:33:41.760 --> 0:33:46.120
<v Speaker 1>You want smaller grids because that increases that resolution, right,

0:33:46.720 --> 0:33:50.600
<v Speaker 1>because each grid represents an area where you understand what

0:33:50.800 --> 0:33:55.360
<v Speaker 1>is going on inside of that area. The smaller you

0:33:55.400 --> 0:33:58.040
<v Speaker 1>make the grids, the higher the resolution is. This is

0:33:58.120 --> 0:34:02.760
<v Speaker 1>again a lot like your television or computer display. If

0:34:02.800 --> 0:34:04.880
<v Speaker 1>you make a picture out of just a few pixels,

0:34:05.000 --> 0:34:08.000
<v Speaker 1>it will be blocky. It has very low resolution. Like

0:34:08.080 --> 0:34:10.960
<v Speaker 1>think about eight bit graphics back in the day. Every

0:34:11.040 --> 0:34:13.239
<v Speaker 1>all the characters on video games were made up of

0:34:13.280 --> 0:34:16.600
<v Speaker 1>these blocks. They all had very jagged edges. It was

0:34:16.640 --> 0:34:19.880
<v Speaker 1>not a high resolution. If you use more pixels to

0:34:19.960 --> 0:34:24.240
<v Speaker 1>make your photo, that improves the resolution to a point. Anyway,

0:34:24.280 --> 0:34:26.600
<v Speaker 1>there gets to a point where we can't really perceive

0:34:26.640 --> 0:34:28.919
<v Speaker 1>it anymore, but you certainly can perceive it at those

0:34:28.920 --> 0:34:32.920
<v Speaker 1>early stages. So the smaller, the smaller, and more numerous

0:34:32.960 --> 0:34:37.480
<v Speaker 1>the pixels, the higher the resolution is and the higher

0:34:37.560 --> 0:34:41.080
<v Speaker 1>quality you get of an image up to a certain point.

0:34:41.800 --> 0:34:44.600
<v Speaker 1>The same is true for weather models. So if you

0:34:44.640 --> 0:34:48.120
<v Speaker 1>have a grid with small squares, such as on the

0:34:48.239 --> 0:34:51.759
<v Speaker 1>order of a few kilometers per side, you would have

0:34:51.800 --> 0:34:54.560
<v Speaker 1>a high resolution, and those grid points can have a

0:34:54.600 --> 0:35:00.480
<v Speaker 1>single value per atmospheric variable per observation. So another words,

0:35:00.520 --> 0:35:04.960
<v Speaker 1>you get a value for temperature, a value for wind direction,

0:35:05.000 --> 0:35:09.120
<v Speaker 1>a value for wind speed, a value for atmospheric density,

0:35:09.160 --> 0:35:13.520
<v Speaker 1>et cetera. Uh, all of that tends to be consulted

0:35:13.560 --> 0:35:18.040
<v Speaker 1>about once an hour with most of these models. So

0:35:18.080 --> 0:35:21.640
<v Speaker 1>once an hour you pull all that observational data for

0:35:21.760 --> 0:35:27.480
<v Speaker 1>every square or cube if you prefer, within that grid.

0:35:28.480 --> 0:35:30.600
<v Speaker 1>So you pull all of the information for all of

0:35:30.640 --> 0:35:34.759
<v Speaker 1>the grids within that area or all the cubes within

0:35:34.800 --> 0:35:37.319
<v Speaker 1>that grid, and you crunch the numbers from all of

0:35:37.320 --> 0:35:42.960
<v Speaker 1>that to see how weather will progress from that moment forward. Now,

0:35:43.000 --> 0:35:47.040
<v Speaker 1>if one variable from one grid is way off, it

0:35:47.080 --> 0:35:50.760
<v Speaker 1>can cause bigger errors and forecasts further down the line.

0:35:50.880 --> 0:35:53.080
<v Speaker 1>That garbage in, garbage out thing I was talking about,

0:35:53.120 --> 0:35:57.320
<v Speaker 1>and this is the infamous butterfly effect. The butterfly effect

0:35:57.400 --> 0:36:00.000
<v Speaker 1>refers to a small effect that can have much larger

0:36:00.160 --> 0:36:04.080
<v Speaker 1>consequences further on in time, and you've probably heard about

0:36:04.120 --> 0:36:07.440
<v Speaker 1>the effect before. The classic example is that you have

0:36:07.480 --> 0:36:10.600
<v Speaker 1>a butterfly flapping its wings in South America and the

0:36:10.640 --> 0:36:13.400
<v Speaker 1>force from the breeze generated from the flapping ends up

0:36:13.440 --> 0:36:16.239
<v Speaker 1>contributing to a system that eventually grows in power and

0:36:16.320 --> 0:36:20.400
<v Speaker 1>ultimately culminates in a massive typhoon in Asia, for example.

0:36:21.239 --> 0:36:24.359
<v Speaker 1>Now that's just a thought experiment, obviously, but with weather

0:36:24.440 --> 0:36:27.480
<v Speaker 1>models something similar can happen. If you have a large

0:36:27.520 --> 0:36:30.440
<v Speaker 1>grid and each square in the grid is representing a

0:36:30.480 --> 0:36:34.440
<v Speaker 1>relatively small area, and one of those areas within that

0:36:34.520 --> 0:36:39.359
<v Speaker 1>grid produces data that doesn't reflect real conditions, your forecasts

0:36:39.440 --> 0:36:42.360
<v Speaker 1>will be affected by this. Now, depending upon the weight

0:36:42.480 --> 0:36:45.240
<v Speaker 1>of the variable in question, it could make the entire

0:36:45.320 --> 0:36:49.800
<v Speaker 1>forecast inaccurate after a certain amount of time. Generally speaking,

0:36:49.880 --> 0:36:52.120
<v Speaker 1>the further out you go in time, the more you

0:36:52.160 --> 0:36:56.200
<v Speaker 1>have to depend upon numerical forecast models. A short term

0:36:56.280 --> 0:36:59.680
<v Speaker 1>forecast might not require a full numerical analysis. It could

0:36:59.760 --> 0:37:02.480
<v Speaker 1>depend and more on what's going on right now and

0:37:02.520 --> 0:37:05.160
<v Speaker 1>the likelihood of how weather will change over the next

0:37:05.239 --> 0:37:08.759
<v Speaker 1>few hours, so you can refer more on experience in

0:37:08.760 --> 0:37:12.520
<v Speaker 1>those cases. Beyond that, however, you'll need some more numerical

0:37:12.560 --> 0:37:15.319
<v Speaker 1>analysis to get a better than UH to do better

0:37:15.360 --> 0:37:18.800
<v Speaker 1>than just giving a wild guess. So even so, you

0:37:18.880 --> 0:37:21.120
<v Speaker 1>might run the data through a couple of different models

0:37:21.200 --> 0:37:24.160
<v Speaker 1>to look at potential forecasts, and from that point and experience,

0:37:24.239 --> 0:37:27.920
<v Speaker 1>meteorologists might look over the data to see which predictions

0:37:27.960 --> 0:37:31.600
<v Speaker 1>appeared to be the most realistic. Sometimes computer models get

0:37:31.640 --> 0:37:35.439
<v Speaker 1>stuff wrong. They might predict an extremely unlikely outcome. Other

0:37:35.480 --> 0:37:39.680
<v Speaker 1>models might have a very different forecast. The meteorologist has

0:37:39.719 --> 0:37:42.719
<v Speaker 1>to determine which of these outcomes best represents what is

0:37:42.760 --> 0:37:46.160
<v Speaker 1>likely to actually happen, based upon how well they seem

0:37:46.200 --> 0:37:49.960
<v Speaker 1>to handle the current weather situations. So you might look

0:37:49.960 --> 0:37:51.920
<v Speaker 1>at a computer model and say, well, how is it

0:37:51.960 --> 0:37:54.839
<v Speaker 1>handling what's going on right now. If it's doing that well,

0:37:55.640 --> 0:37:58.960
<v Speaker 1>then we can at least lay some assumptions that the

0:37:59.120 --> 0:38:02.560
<v Speaker 1>any predictions coming from this computer model are going to

0:38:02.719 --> 0:38:05.960
<v Speaker 1>at least be semi accurate. If it's not handling it well,

0:38:06.000 --> 0:38:08.120
<v Speaker 1>then we may need to consult a different weather model

0:38:08.160 --> 0:38:12.600
<v Speaker 1>for this particular forecast. Now, if observation data is affected,

0:38:13.000 --> 0:38:15.360
<v Speaker 1>as in, if there are problems with sensors, then the

0:38:15.400 --> 0:38:17.520
<v Speaker 1>information you will get out of the models will not

0:38:17.719 --> 0:38:20.600
<v Speaker 1>be dependable. The high resolution can help smooth this out.

0:38:21.160 --> 0:38:25.200
<v Speaker 1>So if you're getting one sensor with erroneous data, but

0:38:25.280 --> 0:38:28.080
<v Speaker 1>you've got lots of other sensors in the area, you

0:38:28.120 --> 0:38:31.160
<v Speaker 1>could possibly smooth that out. You might say, well, this

0:38:31.239 --> 0:38:36.000
<v Speaker 1>is clearly an anomaly. If most of your observation stations

0:38:36.000 --> 0:38:40.480
<v Speaker 1>are reporting that the temperature is about seventy degrees fahrenheit,

0:38:41.120 --> 0:38:44.520
<v Speaker 1>and one of them is saying it's degrees fahrenheit. You

0:38:44.520 --> 0:38:47.680
<v Speaker 1>could say, well, this one clearly there's an anomaly. Maybe

0:38:47.719 --> 0:38:50.440
<v Speaker 1>something is going on in that area. Maybe it's close

0:38:50.520 --> 0:38:54.200
<v Speaker 1>to a fire or something not too close but fairly close.

0:38:54.239 --> 0:38:59.040
<v Speaker 1>Because pretty off the track for everything else, you can

0:38:59.160 --> 0:39:03.960
<v Speaker 1>perhaps week your model to ignore that particular sensor so

0:39:04.000 --> 0:39:07.160
<v Speaker 1>that way it doesn't affect the rest of your forecast

0:39:07.560 --> 0:39:12.080
<v Speaker 1>and throw things into disarray. But if you have just

0:39:12.239 --> 0:39:16.160
<v Speaker 1>very few observation stations, then the loss of even one

0:39:16.560 --> 0:39:20.040
<v Speaker 1>could be enough to throw your forecast off anyway, So

0:39:20.280 --> 0:39:22.880
<v Speaker 1>you may end up having your forecast thrown off either

0:39:23.000 --> 0:39:26.920
<v Speaker 1>because a sensor is giving you incorrect information or because

0:39:26.960 --> 0:39:30.440
<v Speaker 1>without that sensor you don't have enough information to build

0:39:30.600 --> 0:39:36.439
<v Speaker 1>a reliable prediction. So it's a delicate thing. Meteorologists also

0:39:36.480 --> 0:39:38.960
<v Speaker 1>have to keep up with what is actually happening at

0:39:38.960 --> 0:39:41.319
<v Speaker 1>any given time, and this seems pretty evident, but it's

0:39:41.320 --> 0:39:44.200
<v Speaker 1>important to either verify that a computer model is in

0:39:44.239 --> 0:39:48.080
<v Speaker 1>fact forecasting, whether accurately or if it's off track. And

0:39:48.120 --> 0:39:51.000
<v Speaker 1>we learn more from our mistakes than we do from successes.

0:39:51.719 --> 0:39:55.600
<v Speaker 1>Just like in that example of that first multi level model,

0:39:55.960 --> 0:39:58.360
<v Speaker 1>the scientist thought that they had really hit on something

0:39:58.480 --> 0:40:01.520
<v Speaker 1>because their models seemed to handle the conditions of that

0:40:01.560 --> 0:40:06.520
<v Speaker 1>Thanksgiving Day storm and give very realistic outcomes, But as

0:40:06.560 --> 0:40:09.720
<v Speaker 1>it turned out, it wasn't good at handling other situations.

0:40:10.960 --> 0:40:14.480
<v Speaker 1>If we succeed, we might think that what we've done

0:40:14.600 --> 0:40:16.919
<v Speaker 1>is perfect, that it's worked, but it may turn out

0:40:16.960 --> 0:40:19.720
<v Speaker 1>that that's not the case. When we fail, we realize, oh,

0:40:19.840 --> 0:40:22.400
<v Speaker 1>something is not quite right here. We need to figure

0:40:22.400 --> 0:40:24.839
<v Speaker 1>out what that is and how to correct for it.

0:40:25.200 --> 0:40:27.760
<v Speaker 1>This is true, by the way, in all areas of science,

0:40:28.040 --> 0:40:30.560
<v Speaker 1>we learn more from our failures than we do from

0:40:30.560 --> 0:40:35.319
<v Speaker 1>our successes. As computers get more powerful, the simulations can

0:40:35.360 --> 0:40:38.040
<v Speaker 1>take in more data and in theory, will generate more

0:40:38.080 --> 0:40:41.719
<v Speaker 1>accurate forecasts. The addition of some other elements, such as

0:40:41.760 --> 0:40:45.279
<v Speaker 1>deep learning algorithms that can assign probabilities to outcomes, might

0:40:45.360 --> 0:40:50.640
<v Speaker 1>also help. These probabilistic models assigned statistical probabilities to various outcomes,

0:40:50.760 --> 0:40:54.839
<v Speaker 1>letting meteorologists or even an artificially intelligent program determine which

0:40:54.880 --> 0:40:58.840
<v Speaker 1>one most likely represents what is really going to happen.

0:40:59.640 --> 0:41:02.879
<v Speaker 1>But some challenges will remain. I'd like to end this

0:41:02.920 --> 0:41:07.120
<v Speaker 1>episode by quoting from the second edition of Introduction to

0:41:07.280 --> 0:41:11.880
<v Speaker 1>Tropical Meteorology to illustrate just how dann complex this is,

0:41:12.480 --> 0:41:17.280
<v Speaker 1>and I quote from chapter nine of said textbook, Tropical

0:41:17.320 --> 0:41:21.160
<v Speaker 1>weather is difficult to forecast. Mid latitude weather is dominated

0:41:21.200 --> 0:41:24.719
<v Speaker 1>by synoptic systems moving in the westerly's, which formed the

0:41:24.760 --> 0:41:27.840
<v Speaker 1>basis for the weather analysis methods developed in the nineteenth

0:41:27.840 --> 0:41:32.680
<v Speaker 1>and twentieth centuries. In the mid latitudes, baro clinic instability

0:41:32.760 --> 0:41:37.200
<v Speaker 1>results from air masses with contrasting temperature and density. Their

0:41:37.320 --> 0:41:41.160
<v Speaker 1>energy is concentrated in extra tropical cyclones that can be

0:41:41.239 --> 0:41:45.440
<v Speaker 1>tracked fairly easily. By comparison, the tropics have a relatively

0:41:45.520 --> 0:41:50.000
<v Speaker 1>homogeneous air mass and fairly uniform distribution of surface temperature

0:41:50.000 --> 0:41:54.640
<v Speaker 1>and pressure. Therefore, local and mesoscale effects are more dominant

0:41:54.640 --> 0:41:59.920
<v Speaker 1>than synoptic influences, except for tropical cyclones. For example, service

0:42:00.000 --> 0:42:04.000
<v Speaker 1>temperature and pressure can change quickly with convection and sea breezes.

0:42:04.760 --> 0:42:09.360
<v Speaker 1>So you see, we cannot We cannot apply what works

0:42:09.400 --> 0:42:13.759
<v Speaker 1>for one area across all areas of Earth because it

0:42:13.880 --> 0:42:17.719
<v Speaker 1>just doesn't work that way. There are some areas where

0:42:17.719 --> 0:42:21.960
<v Speaker 1>things that are of a major impact on weather patterns

0:42:22.120 --> 0:42:30.200
<v Speaker 1>are almost non factors, and so until we develop very

0:42:30.280 --> 0:42:36.800
<v Speaker 1>specific particular ways of observing, measuring, and predicting weather across

0:42:36.840 --> 0:42:40.120
<v Speaker 1>all of Earth, and then synthesizing that so that we

0:42:40.160 --> 0:42:46.520
<v Speaker 1>can give global weather forecasts that can then narrow down

0:42:46.560 --> 0:42:50.040
<v Speaker 1>to the hyperlocal area, we're going to continue to have.

0:42:50.080 --> 0:42:55.160
<v Speaker 1>This uncertainty is a phenomenal area of science. It is

0:42:55.800 --> 0:43:00.240
<v Speaker 1>remarkable to see technology applied to that area of sience

0:43:00.280 --> 0:43:03.719
<v Speaker 1>in such a way that is easy to illustrate the

0:43:03.760 --> 0:43:10.359
<v Speaker 1>importance of pushing back the barriers of computational power. It's

0:43:10.440 --> 0:43:13.520
<v Speaker 1>why a lot of people look at stuff like Moore's

0:43:13.600 --> 0:43:17.280
<v Speaker 1>lawns said say, it's really important that we keep that going,

0:43:17.400 --> 0:43:19.640
<v Speaker 1>even though it's getting harder and harder to keep Moore's

0:43:19.719 --> 0:43:26.400
<v Speaker 1>law relevant, because we do have these needs for heavy

0:43:26.440 --> 0:43:34.040
<v Speaker 1>computational loads that have real effects and and and powerful

0:43:34.080 --> 0:43:37.480
<v Speaker 1>outcomes for billions of people on this planet. I mean,

0:43:38.080 --> 0:43:45.160
<v Speaker 1>accurate weather forecasts have the the potential to affect or

0:43:45.200 --> 0:43:51.920
<v Speaker 1>to save people from calamity, or to help businesses determine

0:43:52.040 --> 0:43:56.120
<v Speaker 1>when and where they're going to transport goods to get

0:43:56.160 --> 0:44:00.359
<v Speaker 1>to people more effectively, thus reducing lots of things like

0:44:00.520 --> 0:44:05.040
<v Speaker 1>environmental impact and the economic impact. You start to see

0:44:05.760 --> 0:44:10.200
<v Speaker 1>how intrinsic our weather is to everything else we do.

0:44:11.080 --> 0:44:13.920
<v Speaker 1>It's more than just small talk, and it's more than

0:44:13.960 --> 0:44:16.720
<v Speaker 1>just whether or not you need to grab your umbrella

0:44:16.800 --> 0:44:19.560
<v Speaker 1>before you leave the house. And I hope that these

0:44:19.600 --> 0:44:23.120
<v Speaker 1>episodes were interesting to you. I find meteorology to be

0:44:23.280 --> 0:44:26.680
<v Speaker 1>absolutely fascinating and I would love to learn more about it.

0:44:26.719 --> 0:44:30.319
<v Speaker 1>And I love chatting with meteorologists because even though they

0:44:30.360 --> 0:44:33.440
<v Speaker 1>can get super technical and they can really talk about

0:44:33.520 --> 0:44:37.719
<v Speaker 1>some heavy duty math that I can sometimes kind of

0:44:37.760 --> 0:44:43.799
<v Speaker 1>sort of follow. There dedication to understanding something so complex

0:44:43.960 --> 0:44:48.960
<v Speaker 1>I find inspiring. Now, our next episode will be about

0:44:49.040 --> 0:44:52.040
<v Speaker 1>the history of programming languages. It's likely going to be

0:44:52.080 --> 0:44:55.440
<v Speaker 1>a two part episode, and I'm going to study the

0:44:55.520 --> 0:44:59.360
<v Speaker 1>origin and evolution of computer languages. But if you have

0:44:59.440 --> 0:45:04.080
<v Speaker 1>suggestions for future episodes of tech Stuff, please share them

0:45:04.120 --> 0:45:06.680
<v Speaker 1>with me. You can send me an email. The address

0:45:06.840 --> 0:45:10.160
<v Speaker 1>is tech Stuff at how stuff works dot com, or

0:45:10.200 --> 0:45:12.520
<v Speaker 1>you can drop me a line on Facebook or Twitter.

0:45:12.640 --> 0:45:15.840
<v Speaker 1>The handle of both of those is tech Stuff hs W.

0:45:16.640 --> 0:45:19.279
<v Speaker 1>You can always drop in and watch me record these

0:45:19.280 --> 0:45:23.360
<v Speaker 1>episodes live that you can find at Twitch dot tv,

0:45:23.600 --> 0:45:27.920
<v Speaker 1>slash tech Stuff. I record on Wednesdays and Friday's today.

0:45:27.960 --> 0:45:30.080
<v Speaker 1>If you had joined us in the studio, you would

0:45:30.080 --> 0:45:32.360
<v Speaker 1>see that I'm in a brand new studio, or at

0:45:32.440 --> 0:45:34.279
<v Speaker 1>least a different one from the one I'm usually in,

0:45:34.920 --> 0:45:37.880
<v Speaker 1>and that Dylan has been separated from me by a

0:45:38.000 --> 0:45:42.799
<v Speaker 1>pain of soundproof glass, as nature intended. And I hope

0:45:42.840 --> 0:45:44.799
<v Speaker 1>that you guys can join me for future episodes. Just

0:45:44.840 --> 0:45:47.239
<v Speaker 1>go to twitch dot tv slash tech Stuff and you'll

0:45:47.280 --> 0:45:50.600
<v Speaker 1>find a schedule right then and there, and I'll talk

0:45:50.640 --> 0:45:59.520
<v Speaker 1>to you guys again really soon for more on this

0:45:59.680 --> 0:46:01.920
<v Speaker 1>and of sense of other topics. Is it how stuff

0:46:01.920 --> 0:46:12.320
<v Speaker 1>works dot com, wh