- Nov 28, 2004
- 1,513
- 0
- 0
For what it's worth, the speed of light isn't all that fast from the perspective of modern hardware - between two clock ticks of a 3ghz CPU, light only travels about 4 inches. Put differently, if you were to watch the clock ticking in your CPU, by the time you can observe a given clock tick, the CPU is already a few cycles ahead!Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
Originally posted by: CTho9305
For what it's worth, the speed of light isn't all that fast from the perspective of modern hardware - between two clock ticks of a 3ghz CPU, light only travels about 4 inches. Put differently, if you were to watch the clock ticking in your CPU, by the time you can observe a given clock tick, the CPU is already a few cycles ahead!Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
Originally posted by: hypn0tik
Originally posted by: CTho9305
For what it's worth, the speed of light isn't all that fast from the perspective of modern hardware - between two clock ticks of a 3ghz CPU, light only travels about 4 inches. Put differently, if you were to watch the clock ticking in your CPU, by the time you can observe a given clock tick, the CPU is already a few cycles ahead!Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
You're comparing speed with frequency?
Also, your formula doesn't make sense.
c = 3e8 [m/s]
f = 3e9 [Hz]
L = Lambda = wavelength [m]
We know that c = fL -> c/f = L.
So, what you did was you first found the wavelength of light at 3Ghz and then multiplied it by 1s, giving you dimensions of [m*s] for your final answer. This isn't quite right.
I think what you wanted to do was the following.
T = Time taken to complete 1 cycle = 1/f = 3.33e-10
Distance covered in that time = 3e8[m/s]*3.333e-10= c/f = L = 0.1[m]
Hence, at 3 GHz in 1 clock cycle, light would have traveled 0.1m or approx. 4 in. Although numerically the answers are identical (since you picked 1s), your method was slightly off.
Originally posted by: CTho9305
Originally posted by: hypn0tik
Originally posted by: CTho9305
For what it's worth, the speed of light isn't all that fast from the perspective of modern hardware - between two clock ticks of a 3ghz CPU, light only travels about 4 inches. Put differently, if you were to watch the clock ticking in your CPU, by the time you can observe a given clock tick, the CPU is already a few cycles ahead!Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
You're comparing speed with frequency?
No. I was pointing out that light takes its sweet time to travel a few feet, relative to the time periods all of our PCs are based on. The OP seemed to be looking at the claim intuitively and thinking "light is really fast - it must be very hard to measure its speed over a short distance like a few feet"; I was pointing out that we have lots of technology that operats on timescales short enough that a few feet is far.
Also, your formula doesn't make sense.
c = 3e8 [m/s]
f = 3e9 [Hz]
L = Lambda = wavelength [m]
We know that c = fL -> c/f = L.
So, what you did was you first found the wavelength of light at 3Ghz and then multiplied it by 1s, giving you dimensions of [m*s] for your final answer. This isn't quite right.
I wanted to find out how fast light goes in 1/3rd of a nanosecond. I took c and divided it by unitless 3 billion (so I still actually got a result in m/s). This was a shortcut; to keep the units in line, I should have divided it by 3 billion seconds^-1. Since I didn't feel like figuring out how to convey that to Google quickly, I just multiplied by a second (which is mathematically identical - I stuck seconds^+1 in the numerator instead of seconds^-1 in the denominator). You'll also note that Google, which tracks units, says I got a distance as a result and not a distance*velocity (m*s) as you are saying (I'm not sure where you're getting that).
I think what you wanted to do was the following.
T = Time taken to complete 1 cycle = 1/f = 3.33e-10
Distance covered in that time = 3e8[m/s]*3.333e-10= c/f = L = 0.1[m]
Hence, at 3 GHz in 1 clock cycle, light would have traveled 0.1m or approx. 4 in. Although numerically the answers are identical (since you picked 1s), your method was slightly off.
Wavelength is mostly irrelevant. Any light will travel ~4in per clock cycle. You're right that the wavelength of the "light' your CPU clock would emit is about 4 inches, but while obviously lambda = distance/c = [other permutations of c, freq, distance], it's not of any relevance here.
This looks like the paper. I can't download it from home, but the abstract seems to fit.Originally posted by: Super Nade
Any links to the original published article? I checked Europhysics Letters, Optics letters and PROLA. Found nothing.
Originally posted by: Farmer
silverpig:
I guess that's a keen example, esp. if you take all the 'human' factors, like being on Earth (which places people at motion WRT each other, an in an accelerating frame), and having people do things.
If you just say there are just a bunch of lights floating in deep space, at rest WRT to eachother, seperated by some small distance, and are programmed to do what you said, I would say that example works. I mean, I wouldn't say, it carries no information, I would just say everything that carries information (i.e., light, and anything else) never needs to travel faster than c to do what you described.
Originally posted by: silverpig
Let's give them all atomic clocks, and tell them all that Santa will turn his light on at 12:45:00 exactly, and we'll tell the second guy to turn on his light at exactly 1 100-trillionth of a second later. We'll arrange for the nth person down the line to turn on his flashlight n 100-trillionths of a second after Santa does.
Now to someone observing, the lights will light up in a wave traveling faster than c, however because the turn on times were all pre-determined, they don't carry any information with them.
Thanks for the clarification on the first rule of physics.
Suppose you have a line of lights at rest WRT to eachother, they all light up at the same time; that could be interpreted as a wave traveling at infinite speed.
Originally posted by: hypn0tik
Originally posted by: CTho9305
For what it's worth, the speed of light isn't all that fast from the perspective of modern hardware - between two clock ticks of a 3ghz CPU, light only travels about 4 inches. Put differently, if you were to watch the clock ticking in your CPU, by the time you can observe a given clock tick, the CPU is already a few cycles ahead!Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
You're comparing speed with frequency?
Also, your formula doesn't make sense.
c = 3e8 [m/s]
f = 3e9 [Hz]
L = Lambda = wavelength [m]
We know that c = fL -> c/f = L.
So, what you did was you first found the wavelength of light at 3Ghz and then multiplied it by 1s, giving you dimensions of [m*s] for your final answer. This isn't quite right.
I think what you wanted to do was the following.
T = Time taken to complete 1 cycle = 1/f = 3.33e-10
Distance covered in that time = 3e8[m/s]*3.333e-10= c/f = L = 0.1[m]
Hence, at 3 GHz in 1 clock cycle, light would have traveled 0.1m or approx. 4 in. Although numerically the answers are identical (since you picked 1s), your method was slightly off.
Originally posted by: Capitalizt
LINK
Thoughts?
Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
Originally posted by: Capitalizt
LINK
Thoughts?
Personally I think it's BS. Light travels at 186,000 miles per second, and they are measuring how fast it travels 3 FEET. It's gotta be a measurement error.
