Ten zeros are zero.

Right? Ones and zeros, the binary code.

A one by three matrix of all zeros.

So we have to add two zeros here.

let me write this this is four zeros.

If you cut two zeros, it's much better.

You can see that these zeros line up.

And even though there are zeros in between, those zeros are part of our measurement, because they are in between non zero digits.

You can not divide by zeros. You take the limit.

Lined up the decimal points, include the zeros on top.

This is going to be times 6 with two zeros

This is a computer program made of zeros and ones.

We want to have a bunch of zeros after the 873

That is equal to 3 and then you have 1,2,3 zeros.

So let me put a 873 over here with 2 zeros

So that would literally be 291 times 3 with 2 zeros

You just want to include all the non zero digits and everything in between. and and trailing zeros trailing zeros if a decimal point is involved.

So twenty times forty is equal to just eight with two zeros.

So we essentially, so let's think about how many zeros we have

If two repeating minus two repeating that's just a bunch of zeros.

If we do a 1746, and then add two zeros to it

These are your ones, but you've got a few zeros thrown in.

And four hundred times eighty is equal to three two and three zeros.

Sometimes people say, hey look, you could just count the number of zeros.

Now instead of ones and zeros, let's use your fingers one, two, three.

You can just see there's a nine and a string of zeros here.

So you say, okay, 873 and I'm going to have 1,2,3,4 zeros behind it

This first erases the floppy by writing zeros and then it creates the file system.

He says, How many zeros in a trillion? I've got to calculate that right away.

If its all zeros then A star resorts back to the search algorithm already implemented.

I initialize this with zeros, and I set the same size as my vector p.

But I have to multiply times 3 with 1,2,3,4 zeros to get this number 8.73 million

The odds against it, of course, are so great that if you set out writing zeros at the time of the origin of the universe, you still would not have written enough zeros to this day.

And then we have 800 times s, so that's plus 800 s, and then 800 times 20, so that is 8 times 2 is 16, and we have one, two, three zeros, one, two, three, zeros.

Now that we're dealing with something that's in the hundreds we're going to put two zeros there.

We actually want leading zeros in here and we want hours, minutes, and seconds separated by colons.

After hitting Run, I have the original path over here zeros all the way to 4, 4 .

So we follow the same path, we don't update because they're all zeros all along this path.

Twenty times thirty you might not know is two times three and you have two zeros there.

Now I add the zeros, just because this zero and this five need to be subtracted from something.

If I run it with a heuristic function of all zeros I get back my original search algorithm.

Unfortunately, if we leave it out, the result will just be zeros, which is not what you want.

Since it's a six hundred, we put two zeros here, and we just treat it like a six.

When you're seeing these pictures, it's all ones and zeros, and when you're talking on your telephone, your cell phone, and it's going over the network, your voice is all being turned into ones and zeros and magically whizzed around.

So you don't want to count leading zeros before the first non zero digit, I guess we could say.