Measuring distance, speed and clock

  • #51
What?? Post 50? And I am still grabbing Post 17?? I'm afraid the administrator will close this thread. Hmmh...
 
Physics news on Phys.org
  • #52
Stephanus said:
Thanks harrylin for your responds. But [..] How can we even multiply coordinate time? ##kt##, and then he corrected it's not ##kt_{e}##, but it's ##k\tau_{e}##. Because he once made mistake, so I want confirmation because I'm afraid he made another mistake :smile:.
That was not a correction, as he explained (and I repeated it); and in the Lorentz transformation you also multiply coordinate time. Just plug in some numbers and you'll see. :smile:
 
  • #53
harrylin said:
That was not a correction, as he explained (and I repeated it); and in the Lorentz transformation you also multiply coordinate time. Just plug in some numbers and you'll see. :smile:
Dear harrylin, not that I want to argue with you, but how can we multiply coordinate time? As I understand it,
Coordinate time is, for example, July, 2nd 2015 18:00:00 and,
Proper time is, for example, 20 seconds.
What would be if you multiply July, 2nd 2015 18:00:00 by two? January 5,th 2031 12:00? Of course if you count start time is January 1st 1 CE 00:00. Correction it would be January 5,th 2030 12:00, because CE start at 1 not at 0 year. (or if we want the start time from the big bang 13 billion years ago, well...) Of course if you multiply July, 2nd 2015 by two FROM July 1st, 2015 than, it would be July 3rd 2015.
So, I think, just like vector and coordinate that I learned at high school (or junior high?) we can only multiply (July 2nd 2015 MINUS July 1st 2015) by two, then we can get answer. And the answer is proper time. And if we add that proper time to July 2nd, then again, we'll have coordinate time again.
And if I understand it correctly, if I treat proper time and coordinate time just like vector.
Is this right?
A. Proper Time + Proper Time -> Proper Time
B. Proper Time - Proper Time -> Proper Time
C. Proper Time * constant -> Proper Time
D. Proper Time / constant -> Proper Time
E. Coordinate Time + Proper Time -> Coordinate Time
F. Coordinate Time - Proper Time -> Coordinate Time
G. Coordinate Time + Coordinate Time -> ??
H. Coordinate Time - Coordinate Time -> Proper Time [EDIT: Coordinate Time]
I. Coordinate Time * constant -> ??
J. Coordinate Time / constant -> ??
 
Last edited:
  • #54
Stephanus said:
Dear harrylin, not that I want to argue with you, but how can we multiply coordinate time? As I understand it,
Coordinate time is, for example, July, 2nd 2015 18:00:00 and,
Proper time is, for example, 20 seconds. [..]
That understanding was wrong.
Coordinate time is the time (of a clock, or calculated) that is related to a reference frame. For example, July, 2nd 2015 18:00:00 GMT is a coordinate time of a time zone of the ECI frame. When you use it in equations, you simply count the number of days or seconds (or years) from a convenient reference time. Thus coordinate time is often handily chosen to be 0 seconds at the start time t0, and after 20 seconds we then have t1=20 s.
On the other hand, proper time is simply the "time" indicated by a clock in whatever state of motion.

See for example http://www.iep.utm.edu/proper-t/ , sections 3 (coordinate systems) and 15 (Time and Space Dilation). The Lorentz transformations compare time ("coordinate time") of two inertial reference systems in relative motion, and the proper time of a clock that is comoving with a reference system does not need to differ from the coordinate time of that reference system at that position.
 
Last edited:
  • #55
harrylin said:
That understanding was wrong.[..]
See for example http://www.iep.utm.edu/proper-t/ , sections 3 (coordinate systems) and 15 (Time and Space Dilation).[..]
Okay, okay. I click the link. Mentz114 has given me some link in Wiki, but I'm still studying Post 17, that's why I didn't click the link.
 
  • #56
https://en.wikipedia.org/wiki/Proper_time
In relativity, proper time along a timelike (or lightlike) world line is defined as the time as measured by a clock following that line.
Proper Time3.jpg

So, supposed if there is an astronout (A) wearing a red wrist watch, and he moves at 0.6c as shown in green world line.
And a rest observer (R) is staying in his room with a brown floor clock
So the proper time for (A) is shown by the red clock, because the red clock is moving with (A), if supposed (A) can see brown clock, it's not (A)'s proper time because brown clock ticks at different rate than the red clock. Is this something like that?

http://www.iep.utm.edu/proper-t/#H3The essence of the Special Theory of Relativity (STR) is that it connects three distinct quantities to each other: space, time, and proper time. ‘Time’ is also called coordinate time or real time, to distinguish it from ‘proper time’. Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes. For example, proper time for an ordinary mechanical clock is recorded by the number of rotations of the hands of the clock. [..]
[EDIT: INSERT]
This invariance principle is fundamental to classical physics, and it means that in classical physics we can define: Coordinate time = Proper time for all natural systems. [..]

However, the distinction only gained real significance in the Special Theory of Relativity, which contradicts classical physics by predicting that the rate of proper time for a system varies with its velocity, or motion through space. The relationship is very
[EDIT]

[..]the faster a system travels through space, the slower its internal processes go. At the maximum possible speed, the speed of light, c, the internal processes in a physical system would stop completely. Indeed, for light itself, the rate of proper time is zero: there is no ‘internal process’ occurring in light. It is as if light is ‘frozen’ in a specific internal state.
So, I want to ask something here,
-"The faster a system travels, the slower its internal processes go."
-"Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes"

But for the system itself, its one second is still one second right? All we know for 1 second is the tick of the second hand that moves 60 at our desk, altough as I have often heard in this forum, we are traveling near the speed of light according to LHC.
Do I get it right?
 
Last edited:
  • Like
Likes Mentz114
  • #57
Stephanus said:
View attachment 85807
So, supposed if there is an astronout (A) wearing a red wrist watch, and he moves at 0.6c as shown in green world line.
And a rest observer (R) is staying in his room with a brown floor clock
So the proper time for (A) is shown by the red clock, because the red clock is moving with (A), if supposed (A) can see brown clock, it's not (A)'s proper time because brown clock ticks at different rate than the red clock. Is this something like that?

Yes, that's the right idea.

So, I want to ask something here,
-"The faster a system travels, the slower its internal processes go."
-"Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes"

This reference seems unclear and a bit muddled to me. I'd stick with the Wiki definition. It's also worth looking at the SI definition of the second, from NIST, http://physics.nist.gov/cuu/Units/current.html. The SI second measures proper time.

The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the cesium 133 atom.

When you can carry out this definition precisely as written (well, you're actually allowed to ignore any/all of the quantum issues, SR is a classical theory), and actually count the number of vibration periods of some hypothetical cesium-133 atom undergoing the specified transition, you are measuring proper time.

Note that you need to specify what is called a worldline (a particular path through space-time), to measure the proper time. The "twin paradox" is an example of how two cesium atoms traveling diferent paths can start and end at the same pair of events, but experience different amounts of proper time on their journey.

It's also worth noting what proper time does not measure. Proper time has no concept of "now", it does not specify a mechanism of synchronizing clocks. Any measurement which requires clocks synchronization to be performed is not a measurement of proper time.
 
  • #58
Stephanus said:
View attachment 85807
So, supposed if there is an astronout (A) wearing a red wrist watch, and he moves at 0.6c as shown in green world line.
And a rest observer (R) is staying in his room with a brown floor clock
So the proper time for (A) is shown by the red clock, because the red clock is moving with (A), if supposed (A) can see brown clock, it's not (A)'s proper time because brown clock ticks at different rate than the red clock. Is this something like that?

That is close. The brown clock is blue's proper time. Every clock shows the time along its own worldline.

Your diagram shows the proper times of both observers.

So, I want to ask something here,
-"The faster a system travels, the slower its internal processes go."
-"Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes"

But for the system itself, its one second is still one second right? All we know for 1 second is the tick of the second hand that moves 60 at our desk, altough as I have often heard in this forum, we are traveling near the speed of light according to LHC.
Do I get it right?

Locally one second is always one second and the speed of light is always c. No one notices any relativistic effects on their own clocks or rulers.
 
  • Like
Likes Stephanus
  • #59
Dear pervect, dear PF Forum,
Thanks for you answer. I really appreciate it.
pervect said:
Yes, that's the right idea.
Finally...:olduhh:
pervect said:
Stephanus said:
-"The faster a system travels, the slower its internal processes go."
-"Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes"
This reference seems unclear and a bit muddled to me. I'd stick with the Wiki definition. [..]
The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the cesium 133 atom.
When you can carry out this definition [..]and actually count the number of vibration periods of some hypothetical cesium-133 atom undergoing the specified transition, you are measuring proper time.
So, what I mean is this.
Even if we travel fast and "The faster a system travels, the slower its internal processes go.", but 1 second for us is:
- "The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the Cs 133 atom.", or
- The movement of the second hand clock for 60 clockwise (of course)
For a rest observer watching us moving, our clock is slower, but we still doesn't feel any different compared than we are at "rest", do we. The clock in our wristwatch, the atomic clock that (supposed) we carry, everything works "normal".
pervect said:
It's also worth noting what proper time does not measure. Proper time has no concept of "now", it does not specify a mechanism of synchronizing clocks. Any measurement which requires clocks synchronization to be performed is not a measurement of proper time.
I'll contemplate this.

Thanks for the answers.
 
  • #60
Mentz114 said:
That is close.
Finally...:oldeyes:
Mentz114 said:
The brown clock is blue's proper time. Every clock shows the time along its own worldline.
As long as the clock moves along with the observer, right?
Mentz114 said:
Your diagram shows the proper times of both observers.
I want to ask something here.
Proper Time A3.jpg

Okay,... Blue and green move at the same velocity.
1. Can we say that blue and green are at the same frame of reference?
2. G2 will see Blue as B2, and B1 will see Green as G1, is this true?
3. If number 1 is true, can Blue use Green time as proper time?

Mentz114 said:
Locally one second is always one second
Of course. I completely understand that.
Thanks.
 
  • #61
Stephanus said:
Finally...:oldeyes:As long as the clock moves along with the observer, right?I want to ask something here.
View attachment 85817
Okay,... Blue and green move at the same velocity.
1. Can we say that blue and green are at the same frame of reference?
2. G2 will see Blue as B2, and B1 will see Green as G1, is this true?
3. If number 1 is true, can Blue use Green time as proper time?
Thanks.
It is not strictly true to say that something is 'in' a frame of reference. The whole world covered by the coordinates is 'in every frame'.

Green and blue are comoving, They have zero relative velocity, ##\gamma=1## and so their clocks and rulers are the same..

From your diagram we can say that if green sends a beam of light to from G1 to blue, it arrives at event B1. If blue sends a beam from B2 it arrives at event G2.

This scenario tells you more. You can see a symmetry between green and blue because the are comoving. From any frame the times on the clocks of green and blue at all the events will be the same, 0 for B2 and G1, and 6 for B1 and G2. All proper times are invariant.

gb_0.png
gb_1.png
 
  • Like
Likes Stephanus
  • #62
Dear PF Forum,
Thanks for any helps for me so far.
But I still have questions, that I need confirmation.
If we have two observer (B) Blue and (G) Green.
- They are at rest,
- Clocks are synchronized (is this related to our discussion? I don't think so, but I'll write anyway)
- Then at a preagreement time, G moves toward B at 0.6c ##\gamma = 1.25##
What is the correct way to draw the ST diagram?
ST-01.jpg


or
ST-02.jpg

Because "they" said that for the moving object the length is contracted, but then again I remember
harrylin said:
A little elaboration: suppose that at CERN in Geneva a particle is accelerated to 0.99999c in the direction of Lyon. Does that contract the distance between Geneva and Lyon?
or
ST-03.jpg

I purposedly add the wider green world line (see red circle), because "they" said that for a moving object, there is simultaneity of event. So the "distance between Geneva and Lyon is not contracted", but Green does have already moved several distance when Blue receive event G, see the wider green line.

And in Picture 4, I tried to draw light rays, but there is something that doesn't make sense.
I drew light cones for events on Green world line, namely
G-3, G-2, G-1, G0, G+1, G+2, G+3. Each one representing each second for Green. And each event on green world line corespond to Blue world line
G-3 -> B-3
G-2 -> B-2
G-1 -> B-1
G -> B
G+1 -> B+1
G+2 -> B+2
G+3 -> B+3,
But if Green moves, it seems that even if G-1, takes place before G+1, but B+1 takes place before B-1. Where did I go wrong?
ST-03a.jpg

Please see the zoomed picture 4b.

I could have quoted Sherlock Holmes dictum, "If you leave all the impossible, the remains however improbable is the correct answer", then I'll choose Pic 1. But then again, where is the length contraction in Pic 1?
Thanks for any help
 
  • #63
Stephanus said:
[..]
So, I want to ask something here,
-"The faster a system travels, the slower its internal processes go."
-"Proper time is also called clock time, or process time, and it is a measure of the amount of physical process that a system undergoes"

But for the system itself, its one second is still one second right? All we know for 1 second is the tick of the second hand that moves 60 at our desk, altough as I have often heard in this forum, we are traveling near the speed of light according to LHC.
Do I get it right?
Yes you got it right. :smile:

Note however that you have put only part of a phrase in bold, the phrase is wrong for SR:
in classical physics we can define: Coordinate time = Proper time for all natural systems.
 
Last edited:
  • Like
Likes Stephanus
  • #64
Stephanus said:
Dear PF Forum,
Thanks for any helps for me so far.
But I still have questions, that I need confirmation.
If we have two observer (B) Blue and (G) Green.
- They are at rest,
- Clocks are synchronized (is this related to our discussion? I don't think so, but I'll write anyway)
- Then at a preagreement time, G moves toward B at 0.6c ##\gamma = 1.25##
What is the correct way to draw the ST diagram?
View attachment 85827

Yes, that is the correct diagram.

After that I cannot understand what you are doing. It is alarming that you still think the objects are moving in the time direction. Have you tried the 'Animate' feature ?Length cotraction is the projection of the x'-axis in the x-axis. I'll try to do a diagram.

[Edit]
My diagrams are wrong. I cannot show length contraction on the diagram right now.
 
Last edited:
  • #65
Mentz114 said:
Yes, that is the correct diagram.
Thanks
Mentz114 said:
After that I cannot understand what you are doing. It is alarming that you still think the objects are moving in the time direction. Have you tried the 'Animate' feature ?
I do animate feature before, but not for this. Now I have. But I can't still make it sense. But your previous answer has explained enough for me. Now I know the correct diagram.
Mentz114 said:
My diagrams are wrong. I cannot show length contraction on the diagram right now.
It's okay. Take your time
 

Attachments

  • #66
Stephanus said:
ThanksI do animate feature before, but not for this. Now I have. But I can't still make it sense. But your previous answer has explained enough for me. Now I know the correct diagram.

The diagram you sent me does not agree with your scenario. Pic 1 of post#62 is correct, if green is one object.

The x-axis is like a long straight street. One can only move up the street or down the street. The time axis shows the clock-times for the clocks in the street.

You seem to be making it complicated when it is simple.

You are also jumping around again. Length contraction is taken care of by the LT. Leave it until you understand ... something.
 

Attachments

  • Image3.png
    Image3.png
    2.9 KB · Views: 405
  • #67
Mentz114 said:
The diagram you sent me does not agree with your scenario. Pic 1 of post#62 is correct, if green is one object.

The x-axis is like a long straight street. One can only move up the street or down the street. The time axis shows the clock-times for the clocks in the street.

You seem to be making it complicated when it is simple.

You are also jumping around again. Length contraction is taken care of by the LT. Leave it until you understand ... something.
Thanks Mentz, for your clarification.
Actually these are my diagrams. Those are without light rays.
ST-01 is for Pic 1, and ST-02 is for Pic 2.
 

Attachments

  • #68
Stephanus said:
Thanks Mentz, for your clarification.
Actually these are my diagrams. Those are without light rays.
ST-01 is for Pic 1, and ST-02 is for Pic 2.
There is something very wrong. When I load those diagrams they look fine. But when I boost with 'match speed' - it boosts with v instead of -v !

Also when I try to animate it is as if the worldlines do not exist - the animation is empty.

If I plot a similar diagram - it works fine. Please try loading this and try 'animate'. I'd like to know what happens. In the meantime don't believe anything the plotter is doing.
 

Attachments

  • #69
Mentz114 said:
There is something very wrong. When I load those diagrams they look fine. But when I boost with 'match speed' - it boosts with v instead of -v !

Also when I try to animate it is as if the worldlines do not exist - the animation is empty.

If I plot a similar diagram - it works fine. Please try loading this and try 'animate'. I'd like to know what happens. In the meantime don't believe anything the plotter is doing.
"Don't believe anything the plotter is doing??"" Oh, I'm so sorry Mentz114. It's not a bug.
I edited the text file!
This software is very good, but what troubles me is the resolution. So, I worked out the coordinate in Microsoft Excel and I edit the text file, and I load the text in the plotter.
For x coordinate it is 300 + x*20
For t coordinate it is 300 - t*20
Then I get the picture, then I save it to bitmap.
It's completely my fault. I'm afraid it's the resolution.
 
  • #70
harrylin said:
Yes you got it right. :smile:

Note however that you have put only part of a phrase in bold, the phrase is wrong for SR:
in classical physics we can define: Coordinate time = Proper time for all natural systems.
Again, my bad quoting habit. Next time, I'll try not to mislead the meaning of a paragraph. Thanks harrylin.
 
  • #71
Stephanus said:
"Don't believe anything the plotter is doing??"" Oh, I'm so sorry Mentz114. It's not a bug.
I edited the text file!
This software is very good, but what troubles me is the resolution. So, I worked out the coordinate in Microsoft Excel and I edit the text file, and I load the text in the plotter.
For x coordinate it is 300 + x*20
For t coordinate it is 300 - t*20
Then I get the picture, then I save it to bitmap.
It's completely my fault. I'm afraid it's the resolution.

Yes, I worked out that you hacked the file. You swapped the start and end points - but the software always rearranges them when you create the wl. The program got the velocity reversed because the endpoints were swapped after creation.

Please don't hack the saved files. You can delete a worldline if you right-click on it.

I hoped the animation would help you to see that each horizontal line is a time-slice, and the objects on slanted lines will change position in each slice.
 
  • #72
Mentz114 said:
Please don't hack the saved files. You can delete a worldline if you right-click on it.
not "hack", please. But "editing". And I think there's a bug in deleting an event. Suppose we have 5 events,
ev1, ev2, ev3, ev4 and ev5. If we delete for example ev4 then ev1 is deleted, not ev4, and if delete ev4 for the second time, ev2 is deleted. That's why I deleted the text manually.
Mentz114 said:
I hoped the animation would help you to see that each horizontal line is a time-slice, and the objects on slanted lines will change position in each slice.
I haven't observed transformation just watched. I just use it to draw wl and light ray and event. It's a very good software, it helps me very much. Thanks.
[EDIT] For now, but later, I think I have to study at least acceleration wl
 
  • #73
Stephanus said:
If we have two observer (B) Blue and (G) Green.
- They are at rest,
- Clocks are synchronized (is this related to our discussion? I don't think so, but I'll write anyway)
- Then at a preagreement time, G moves toward B at 0.6c γ=1.25\gamma = 1.25
What is the correct way to draw the ST diagram?
Picture 2 is obviously wrong. In it the green line is discontinuous. That means that green disappears from one location and reappears at another location. You are saying that turning on a rocket engine causes not only acceleration, but also teleportation.
 
  • Like
Likes Stephanus
  • #74
DaleSpam said:
Picture 2 is obviously wrong. In it the green line is discontinuous. That means that green disappears from one location and reappears at another location. You are saying that turning on a rocket engine causes not only acceleration, but also teleportation.
Teleportation :oldlaugh:, Now that's funnier than
harrylin said:
A little elaboration: suppose that at CERN in Geneva a particle is accelerated to 0.99999c in the direction of Lyon. Does that contract the distance between Geneva and Lyon?
Thanks DaleSpam, Mentz114 has already answered me. #64
 
  • #75
pervect said:
However, you can work out this formula for yourself following Bondi's apporach, simply from knowing that "k" exists. Suppose observer A is approaching observer b. At some time 1 second before they meet, A sends out a signal which B receives at a time k seconds (k<1) before they meet. B retransmits the signal, which is received by A, at a time k^2 seconds before they meet.
Example - if k=1/4, then A sends a signal 1 second before meeting, B receives this signal 1/4 = .25 seconds before they meet, and retransmits it. A receives the return signal 1/16 of a second before they meet.
From this exchange of signals, plus the knowledge that the speed of light is constant in his frame, A can compute the velocity relative to B as follows:[..]
I don't quite sure, but I think "A receives the return signal 1/16 of a second before they meet" is wrong.
I tried to work it out:
https://www.physicsforums.com/attachments/85844
Okay,...

The picture is not in scale to avoid measuring the distance to find the answer.

F1: "Suppose observer A is approaching observer b. At some time 1 second before they meet, A sends out a signal which B receives at a time k seconds (k<1) before they meet. "
At E0 A emits a signal to B 1 second before they meet. So L1 distance is VA * 1 sec

F2: "Example - if k=1/4, then A sends a signal 1 second before meeting, B receives this signal 1/4 = .25 seconds before they meet..."
So, B is receiving the signal at ##1 sec - 0.25 sec = 0.75 sec## after A sends the signal.
So L1 distance is 0.75 ls.
Combining F1 and F2, so Va is 0.75c, because it takes 1 sec for A to travel to B0.75c
So I want to work out, what is E1 distance from E0.
Supposed: E1 is A position when the light reaches B, see F2. So it takes 0.75 sec for A which travels at 0.75 c to reach E1.
So E1 is 0.5625 or ##\frac{9}{16} ls or \frac{63}{112}##

F3: "B receives this signal 1/4 = .25 seconds before they meet, and retransmits it. A receives the return signal 1/16 of a second before they meet."
So, when A is at E1, B retransmit the signal.
Supposed A meets the signal at E2. To answer that we have to calculate L3 and L4
We know that ##L2+L3+L4 = 0.75 ls = \frac{12}{16} or \frac{84}{112}##
##L2 = \frac{63}{112}##
So ##L3+L4 = \frac{21}{112}##
A travels at 0.75c and light travels at c.
So combining both,
##t = d/(v+c)##
##t = \frac{21}{112} / 1.75 = \frac{3}{28}##
I think A will not receive the signal 1/16 before they met, but at ##\frac{3}{16}-\frac{3}{28} = \frac{9}{112}## seconds.
Or perhaps my calculations are wrong?
Or my understanding is wrong?
 
  • #76
Oh, no. The attachment failed. Ok, I ask again my question.
pervect said:
However, you can work out this formula for yourself following Bondi's apporach, simply from knowing that "k" exists. Suppose observer A is approaching observer b. At some time 1 second before they meet, A sends out a signal which B receives at a time k seconds (k<1) before they meet. B retransmits the signal, which is received by A, at a time k^2 seconds before they meet.

Example - if k=1/4, then A sends a signal 1 second before meeting, B receives this signal 1/4 = .25 seconds before they meet, and retransmits it. A receives the return signal 1/16 of a second before they meet.

From this exchange of signals, plus the knowledge that the speed of light is constant in his frame, A can compute the velocity relative to B as follows:[..]
Dopper Example.jpg
This is my picture. Again, not to scale because at first we (I) didn't know what their positions, so we have to calculate every point. This picture just makes us easier to do the calculation.
Okay,...
"Example - if k=1/4, then ..."
F1: ##k = 0.25##
F2: "At some time 1 second before they meet, A sends out a signal" A sends the signal at ##E0##, ##L1 = V_A * 1 sec= V_A##, for simplicity the second ##V_A## is not a velocity, but a distance.
F3: "B receives this signal 1/4 = .25 seconds before they meet", supposed B received the signal when A is at ##E1##, so ##L3+L4 = \frac{1}{4}V_A##
F4: "B receives the signal and retransmits it. A receives the return signal 1/16 of a second before they meet." Supposed A received the signal when A is at ##E2##
------------------------------------------------------------------------------
F3: B receives the signal at ##0.25 seconds## before they meet, or ##1-0.25 = 0.75seconds## after A sends the signal.
So length ##L1 = 0.75c##
So ##V_A = 0.75c##
F3: ##L3+L4 = \frac{1}{4}V_A = \frac{3}{16}##light seconds
So A travels at 0.75c and c travels at -c. The will meet at E2
Dopper Example-2.jpg

Again, not to scale.
##L3+L4 = \frac{3}{16}##
The time it takes for A to reach E2 (or C reaches E2) is
##\frac{L3+L4}{V_A-C} = \frac{3}{16}/1.75 = \frac{3}{28} seconds##
The time for A from E2 to reach E3 is ##\frac{7}{28}-\frac{3}{28} = \frac{1}{7}## seconds.
Did I do it right?
Do I understand the problem correctly?
 
  • #78
Stephanus said:
Okay, today I learned that
'''
'''
are actually the same. And we can use the same formula to calculate them.
##k=\sqrt{\frac{1-\beta}{1+\beta}}## or ##k=\sqrt{\frac{1+\beta}{1-\beta}}##
I don't understand the diagrams.

This is a clip I made some time ago that might help to understand the Doppler effect. The moving object emits light pulses at a regular frequency and the two stationary observers detect the frequency to be different. The script is attached and you should get the same result if you do an 'animate' of this.
 

Attachments

  • #79
Mentz114 said:
I don't understand the diagrams.

This is a clip I made some time ago that might help to understand the Doppler effect. The moving object emits light pulses at a regular frequency and the two stationary observers detect the frequency to be different. The script is attached and you should get the same result if you do an 'animate' of this.
Wow, thanks Mentz114. I have had this file a month ago. At least the movie not the text file. You sent me. Of course I didn't get the text file, just the representation graph and the video. How can STPlotter make the video out of it?
Btw, what I mean about my picture is this.
I kept imagining that B sends a signal for every, say, 10 seconds. And if B moves toward A, A will receive the signal less then 10 seconds.
And the good advisors/mentors/members kept saying about sending light and blue shifted and red shifted.
What I didn't realize was, both were the same.
Sending signals for every 10 seconds is the same as, for example, sending a green light.
But in green light case, you'll send signal for every 540 pico seconds.
https://en.wikipedia.org/wiki/Color#Spectral_colors
That's what keeps holding me understanding their answers.
But thanks anyway for your responses. I'll read the previous post' again.
 
  • #80
Stephanus said:
Wow, thanks Mentz114. I have had this file a month ago. At least the movie not the text file. You sent me. Of course I didn't get the text file, just the representation graph and the video. How can STPlotter make the video out of it?
I forgot that I'd sent this earlier. The frames can be saved and a video making program used to join them into a clip.
Btw, what I mean about my picture is this.
I kept imagining that B sends a signal for every, say, 10 seconds. And if B moves toward A, A will receive the signal less then 10 seconds.
Yes and no. The receiver detects the time gap between signals. The transmission time is not important. And a detector moving away sees the gap as more than 10 secs.

And the good advisors/mentors/members kept saying about sending light and blue shifted and red shifted.
What I didn't realize was, both were the same.
Blue shifted means the frequency is increased and the wavelength is decreased. Red shifted means the reverse.
Sending signals for every 10 seconds is the same as, for example, sending a green light.
But in green light case, you'll send signal for every 540 pico seconds.
Yes. The colour we perceive depends on the frequency of the light wave hence 'red' and 'blue' shifted.
It is similar for gaps between pulses. That is how ground-based radar can detect the speed of a vehicle.
https://en.wikipedia.org/wiki/Color#Spectral_colors
That's what keeps holding me understanding their answers.
But thanks anyway for your responses. I'll read the previous post' again.

I hope it is clearer.
 
  • Like
Likes Stephanus
  • #81
Mentz114 said:
Blue shifted means the frequency is increased and the wavelength is decreased. Red shifted means the reverse.
Just like in Franhover lines? (or Frauhover, I forget the exact name)
Thanks for the respond Mentz114.
Perhaps you can understand my confusion.
At first I tought that:
1: B burst a signal every 10 seconds.
While all the answers sugest that
2: B sends colored light, for example Green. Or B sends signal very but not at 540 pico seconds as I mistakenly wrote above. 540THz is the frequency, so B actually sends signals every ##\frac{1}{540E12} = 0.0018 pico seconds##
Conclusion:
1: B burst a signal every 10 seconds (any color)
2: B burst an EM wave signal every 0.0018 pico seconds (Green light)
Conclusion: The logic is the same.
And if B moves toward A, the signal is blue shifted. Perhaps the frequency can rise to 500 THz at the orange range?. Forgive the pun.
 
  • #82
Suppose B sends a radio signal, like WWV, that has a 10 Mhz frequency, but is also amplitude modulated at 1khz. Then we can say that both the carrier frequency and the modulation frequency are red/blue shifted by the same amount due to doppler effects. This follows from the fact that at the transmitter, the ratio of the modulating frequency to the carrier frequency is 10,000:1, and the fact that this ratio is expected to be constant even if the carrier is red or blue shifted.

It doesn't really matter what the details of the modulation are. We can generalie from the above example with a sinusoidal carrier and a sinusoidal modulation signal to "bursty" modulation once every 10 seconds (.1 hz). The point is that the carrier signal and the modulating signal will both be red/blue shifted by the same amount, this is necessary for logical consistency.

[add]
It might be easier to explain this way. Suppose we send out "bursts" each of which contain 1000 carrier pulses. Then everyone will agree that there are 1000 pulses in a burst, even if they don't agree about the carrier frequency due to the doppler effect.
 
  • #83
Finally, pervect...
pervect said:
Suppose B sends a radio signal, like WWV, that has a 10 Mhz frequency, but is also amplitude modulated at 1khz. Then we can say that both the carrier frequency and the modulation frequency are red/blue shifted by the same amount due to doppler effects.
Yes, I understand.
pervect said:
This follows from the fact that at the transmitter, the ratio of the modulating frequency to the carrier frequency is 10,000:1, and the fact that this ratio is expected to be constant even if the carrier is red or blue shifted.
Yes
pervect said:
It doesn't really matter what the details of the modulation are. [..]The point is that the carrier signal and the modulating signal will both be red/blue shifted by the same amount, this is necessary for logical consistency.
Yes
pervect said:
[..]Suppose we send out "bursts" each of which contain 1000 carrier pulses. Then everyone will agree that there are 1000 pulses in a burst, even if they don't agree about the carrier frequency due to the doppler effect.
Yes

But, pervect, can I ask you about your previous post? About sending a signal where k = 1/4. I think there's something not match there. Or the mistake is mine. It is in https://www.physicsforums.com/threads/measuring-distance-speed-and-clock.821115/page-4#post-5167834
 
  • #84
Stephanus said:
Finally, pervect...
Yes, I understand.YesYesYes

But, pervect, can I ask you about your previous post? About sending a signal where k = 1/4. I think there's something not match there. Or the mistake is mine. It is in https://www.physicsforums.com/threads/measuring-distance-speed-and-clock.821115/page-4#post-5167834

Yes, there's a problem, which I'd describe as you not taking into account the fact that simultaneity is relative and the effects of time dilation. A's watch and B's watch keep different time. This means that A's watch and B's watch read different times, we have to be careful not to conflate them.

The sequence of events from A's point of view goes like this:

A sends a signal at -1 second (1 second before impact) according to A's clock. A receives a return signal at -.0625 (-1/16 a second) according to A's watch. The returned signal from B is conveniently timestamped with B's time reading. B's clock reads -.25 seconds. But A knows not to confuse the reading on B's clocks with his own readings.

A considers himself at rest in his own frame, with B moving towards him. A knows that the time it takes for the signal to reach B is equal to the time that the signal takes to return from B. Interpreting his radar results, A concludes that the round-trip time for the light/radar signal was (-1/16 - (-1)) seconds, i.e. the round trip time was 15/16 seconds, which implies that the one-way trip time was 15/32 of a second.

A computes the time in A's frame that B received the signal as the start time (-1 second) plus the one-way travel time (15/32 of a second), for a result of -17/32 seconds, i.e. -.53125 seconds

This is obviously different from the time B assigned to the same event. If A is familiar with special relativity, he expects this - he expects B's clock to be running slow, and it is - just as much slower as predicted, reading only -.25 seconds rather than -.53125 seconds.

It may help to draw a space-time diagram of this.

Now, for the velocity. A meets B at 0 seconds, and A knows that at the time B received the signal (-.53125 seconds), that B's distance was c multipled by the one-way travel time, i.e 15/32 seconds * c, c being the speed of light. Recall that the speed of light in A's frame must be constant an equal to c in A's frame on both the outgoing and ingoing trip.

So A computes B's velocity as the distance, (15/32) light seconds dived by the time it takes for A to reach B, (17/32) seconds, thus B's velocity was 15/17 of the speed of light.

It might be easier to work out a closely related problem where all the times are integers - or to use algebraic variables. Using the former approach (integers), we can imagine A sending a signal at 16 seconds before impact (by A's watch), and receving the echo at 1 second before impact (by A's watch).
 
  • Like
Likes Stephanus and Mentz114
  • #85
Thanks pervect for your answer.
pervect said:
A receives a return signal at -.0625 (-1/16 a second) according to A's watch. The returned signal from B is conveniently timestamped with B's time reading. B's clock reads -.25 seconds (add: according to B's watch).
Ahh, that makes a big different. Okay, I'll start again.
Dopper Example.jpg

pervect said:
A sends a signal at -1 second (1 second before impact) according to A's clock. A receives a return signal at -.0625 (-1/16 a second) according to A's watch. The returned signal from B is conveniently timestamped with B's time reading. B's clock reads -.25 seconds.
It takes 1 second for A to travel L1 distance. Supposed A speed is V, then ##L1 = V##, A receives the return signal at 1/16 seconds, ##L4 = \frac{1}{16}V## Light travels at ##V+\frac{1}{16}V = \frac{17}{16}V distance##
A travels at ##\frac{15}{16}V## distance. So A speed is ##V = \frac{15}{17}c## Okay,... Conform your calculation
pervect said:
[..]thus B's velocity was 15/17 of the speed of light.
Motion is relative, right. It's A who's at rest and B travels.
##\gamma = \frac{1}{\sqrt{1-V^2}} = \frac{1}{\sqrt{1-\frac{15^2}{17^2}}} = \frac{1}{\frac{8}{17}} = \frac{17}{8} = 2.125##
The signal will reach B according to A clock at ##\frac{2}{17} seconds## before impact. Because B travels at ##\frac{15}{17}c##, so, B clock according to B is
##\frac{2}{17}*\frac{17}{8} = \frac{2}{8}## Gosh, the number match!
But I still can grasp it intuitively. I'll study it again. Thanks pervect.
Now, go back to Post #17
 
  • #86
Stephanus said:
Thanks pervect for your answer.
Ahh, that makes a big different. Okay, I'll start again.
View attachment 86067

It takes 1 second for A to travel L1 distance. Supposed A speed is V, then ##L1 = V##, A receives the return signal at 1/16 seconds, ##L4 = \frac{1}{16}V## Light travels at ##V+\frac{1}{16}V = \frac{17}{16}V distance##
A travels at ##\frac{15}{16}V## distance. So A speed is ##V = \frac{15}{17}c## Okay,... Conform your calculation
Motion is relative, right. It's A who's at rest and B travels.
##\gamma = \frac{1}{\sqrt{1-V^2}} = \frac{1}{\sqrt{1-\frac{15^2}{17^2}}} = \frac{1}{\frac{8}{17}} = \frac{17}{8} = 2.125##
The signal will reach B according to A clock at ##\frac{2}{17} seconds## before impact. Because B travels at ##\frac{15}{17}c##, so, B clock according to B is
##\frac{2}{17}*\frac{17}{8} = \frac{2}{8}## Gosh, the number match!
But I still can grasp it intuitively. I'll study it again. Thanks pervect.
Now, go back to Post #17

Here is a diagram of the above ( nearly). Between A (blue) and B(green) we have ##\gamma=2.13##. The grid scale is (As coords) 1sec = 20 grid units.

The light is sent 1 sec before they meet ( interval AR ) and the light returns at t=0.63 s before they meet ( interval RD).

The time on Bs clock when the light arrives can be read off as about 4.85/20 secs assuming synchronization at t=0 (A time).

This seems to agree close enough with Pervects (and your) numbers.
 

Attachments

  • std-1.png
    std-1.png
    3.2 KB · Views: 368
  • Like
Likes Stephanus
  • #87
Mentz114 said:
Here is a diagram of the above ( nearly). Between A (blue) and B(green) we have ##\gamma=2.13##. The grid scale is (As coords) 1sec = 20 grid units.

The light is sent 1 sec before they meet ( interval AR ) and the light returns at t=0.63 s before they meet ( interval RD).

The time on Bs clock when the light arrives can be read off as about 4.85/20 secs assuming synchronization at t=0 (A time).

This seems to agree close enough with Pervects (and your) numbers.
What?? You beat me by one hour
 

Attachments

  • Like
Likes Mentz114
  • #88
Stephanus said:
What?? You beat me by one hour
What do you mean ?

[edit]
I get it. Sorry.

Your diagram gives the same results but with a bit more error because it is less than half the scale of mine.

Well done. You now have the relevant times calculated by two methods. I prefer the diagram way.
 
Last edited:
  • #89
Mentz114 said:
What do you mean ?

[edit]
I get it. Sorry.

Your diagram gives the same results but with a bit more error because it is less than half the scale of mine.

Well done. You now have the relevant times calculated by two methods. I prefer the diagram way.
Well, if you know me. I calculate the speed ##\frac{15}{17}##
The easiest way to do it is to put some point at 15 at the x-Axis and 17 at the t-axis. Calculate all those by spread sheet. I have the formula now, for world line, light and event. Open load project at STPlotter, see if I made a "bug". What is holding me, is the coordinate for light differs than world line. X in light is T in world line and vice versa. Depends on the speed 1 or -1. So does the coordinate for event is t,x not x,t as in wordline. That's why I didn't calculate it from 20 units as you do. This is my data:
Code:
[B]
Name  X          T        X          T
W0    0.0000 -3000.0000   0.0000  3000.0000; A world line
W1 1500.0000     0.0000   0.0000  1700.0000; B world line
E1    0.0000     0.0000          
E2 1500.0000     0.0000             
E3  796.8750   796.8750               
E4    0.0000  1593.7500               
E5    0.0000  1700.0000              
L0    0.0000     0.0000 796.8750  796.8750
L1  796.8750   796.8750   0.0000 1593.7500[/B]
Scale it down by 200, convert it to screen coordinates.
Code:
Name    X             T                 X           T
W0    300.000000    600.000000        300.000000    0.000000
W1    450.000000    300.000000        300.000000  130.000000
E1    300.000000    300.000000            
E2    300.000000    450.000000            
E3    220.312500    379.687500            
E4    140.625000    300.000000            
E5    130.000000    300.000000            
L0    300.000000    300.000000        379.687500    220.312500
L1    220.312500    379.687500        300.000000    140.625000
Add the necessary code for STPlotter and save it to ST-01.txt. Actually I like the combination of both. Calculate the numbers on spread sheet, convert it to world line, light or event code and save it to text file and load it to STPlotter.
 
  • #90
Stephanus said:
Well, if you know me. I calculate the speed ##\frac{15}{17}##
The easiest way to do it is to put some point at 15 at the x-Axis and 17 at the t-axis. Calculate all those by spread sheet. I have the formula now, for world line, light and event. Open load project at STPlotter, see if I made a "bug". What is holding me, is the coordinate for light differs than world line. X in light is T in world line and vice versa.

Add the necessary code for STPlotter and save it to ST-01.txt. Actually I like the combination of both. Calculate the numbers on spread sheet, convert it to world line, light or event code and save it to text file and load it to STPlotter.


That is interesting but it shouldn't be necessary. I can use the mouse interface to draw any worldlines in a few seconds.
 
  • #91
Mentz114 said:
That is interesting but it shouldn't be necessary. I can use the mouse interface to draw any worldlines in a few seconds.
Yep, that's right. I'm sorry, if you still remember what I've done. I'm still cartesianing ST diagram.
Consider this.
ST-03.jpg

This graph clearly shows that Green moves at 0.6c
Green distance is 900 units. I like 900 when c is 0.6
##\gamma = 1.25##, and ##\frac{900}{1.25} = 720##
So, where will the light that comes from E2 will cross Green world line?
E2 is 300 seconds.
Y = X + 300
Y = (X - 900)*3/5,

Sorry, :smile:
F1: ##X = t - 300## Light ray from E2
F2: ##X = vt + 900##, Green world line
Eliminates F1 by F2, you'll have...
##0 = t(1-v)-1200; t = 750; x = 450##, then I put those numbers in spread sheet. I have the formula to convert world line, light ray and event to screen coordinate.
W,W0, 0, 300, 400, 300, 150, 8388608
W,W1, -0.6, 390, 300, 300, 150, 32768
W,W2, 0, 390, 350, 390, 300, 32768
E,E2, 270, 300, 0
E,E3, 225, 345, 0
E,E1, 300, 390, 0
E,E4, 150, 300, 0
L,L0, 0, 270, 300,0, 0, !none, 345, 225, 1
and load it to STPlotter. This is much simpler for me.
The world line color is in RGB mode,
R*1 + G * 100h + B * 10000h
 

Attachments

  • #92
Stephanus said:
Yep, that's right. I'm sorry, if you still remember what I've done. I'm still cartesianing ST diagram.
Consider this.
View attachment 86082
This graph clearly shows that Green moves at 0.6c
Green distance is 900 units. I like 900 when c is 0.6
##\gamma = 1.25##, and ##\frac{900}{1.25} = 720##
So, where will the light that comes from E2 will cross Green world line?
E2 is 300 seconds.
Y = X + 300
Y = (X - 900)*3/5,

Sorry, :smile:
F1: ##X = t - 300## Light ray from E2
F2: ##X = vt + 900##, Green world line
Eliminates F1 by F2, you'll have...
##0 = t(1-v)-1200; t = 750; x = 450##, then I put those numbers in spread sheet. I have the formula to convert world line, light ray and event to screen coordinate.
W,W0, 0, 300, 400, 300, 150, 8388608
W,W1, -0.6, 390, 300, 300, 150, 32768
W,W2, 0, 390, 350, 390, 300, 32768
E,E2, 270, 300, 0
E,E3, 225, 345, 0
E,E1, 300, 390, 0
E,E4, 150, 300, 0
L,L0, 0, 270, 300,0, 0, !none, 345, 225, 1
and load it to STPlotter. This is much simpler for me.
The world line color is in RGB mode,
R*1 + G * 100h + B * 10000h

That is weird.

If I want to draw a similar diagram

1. click on 'Draw worldline'
2. Put cursor on the start point
3. Hold down left mouse button and move to end point. I can see ##\gamma## and ##\beta## in the status bar.
4. Release cursor.

Repeat for B.

To draw the light pulse path
1. select 'Draw light ray'
2. Put cursor on start point
3. Hold down left button and move to end point.
4. Release button.

There was no need to calculate the intersection of the light and WL B. The plotter forces the correct point.

So what do you use the plotter for ? Can you read off the lengths of intervals for instance ?
 
  • Like
Likes Stephanus
  • #93
Mentz114 said:
Can you read off the lengths of intervals for instance ?
But, I can't. I wouldn't know the precise distance. And if I save the project to text file, the number just isn't rounded.
And I have one problem. I like 0.6c, because gamma is round. And I like 900, because 900/1.25 is 720, and if I want to draw an event which is at 60 interval, than 900/60 is 15 round and 720/60 is 12 round and 15/12 is gamma, again round.
Again for 1-V or 1.6, so 720/1.6 is 45 and 900/1.6 is 56.25, hmmhh, still round nicely. At least not some number like 1.333333333
And I'm having trouble to draw the precise coordinate at 900, the plotter only draw in 20 units pixel for its square.
For -0.6c, supposed if I draw a wordline at (15,0) to (0,25), the plotter can't draw beyond (0,15).
I like 15 because 15/gamma is 12. The world line is supposed to cross (12,0) if I "match speed" it.
So I calculate all the numbers, based on 900 units. Then divide them by 100 scale so it can be uploaded to ST plotter limit: 20 squares, and convert it to text. Have to do it in spread sheet to speed up calculations.
Mentz114 said:
So what do you use the plotter for ?
After I calculate all the numbers, than I load project them to the plotter and I upload it in the forum, if I have a question regarding SR, so I can explain my problem clearly. Too bad the plotter does not have line for simultaneity of event. Only world line (<450) and light ray (450 or -450). But it's still a very, very good software. :cool:
 
Last edited:
  • #94
Sorry, I have to cartesian ST diagram, because I have known cartesian since junior high school. I only knew Hendrik Lorentz 3 months ago :smile:. I have to do cartesia it over and over until I can lorentz them intuitively.
 
  • #95
Stephanus said:
Sorry, I have to cartesian ST diagram, because I have known cartesian since junior high school. I only knew Hendrik Lorentz 3 months ago :smile:. I have to do cartesia it over and over until I can lorentz them intuitively.
You don't have to apologise for calculating the intersection of two lines.

Stephanus said:
But, I can't. I wouldn't know the precise distance. And if I save the project to text file, the number just isn't rounded.
And I have one problem. I like 0.6c, because gamma is round. And I like 900, because 900/1.25 is 720, and if I want to draw an event which is at 60 interval, than 900/60 is 15 round and 720/60 is 12 round and 15/12 is gamma, again round.
Again for 1-V or 1.6, so 720/1.6 is 45 and 900/1.6 is 56.25, hmmhh, still round nicely. At least not some number like 1.333333333
And I'm having trouble to draw the precise coordinate at 900, the plotter only draw in 20 units pixel for its square.
For -0.6c, supposed if I draw a wordline at (15,0) to (0,25), the plotter can't draw beyond (0,15).
I like 15 because 15/gamma is 12. The world line is supposed to cross (12,0) if I "match speed" it.
So I calculate all the numbers, based on 900 units. Then divide them by 100 scale so it can be uploaded to ST plotter limit: 20 squares, and convert it to text. Have to do it in spread sheet to speed up calculations.
After I calculate all the numbers, than I load project them to the plotter and I upload it in the forum, if I have a question regarding SR, so I can explain my problem clearly. Too bad the plotter does not have line for simultaneity of event. Only world line (<450) and light ray (450 or -450). But it's still a very, very good software. :cool:

I don't understand this but it shows you have no idea what the plotter is for. Why do you say that it is 'good software' when it won't do the stuff you mention above ?

You find ways to wriggle out of anything that might be relativistic.

Look at this diagram. Can you say what the time is on Greens clock at the event when the first light pulse intersects with the green WL ?
 

Attachments

  • std-1.png
    std-1.png
    3.2 KB · Views: 351
  • #96
Mentz114 said:
You don't have to apologise for calculating the intersection of two lines.
Because you once said something like "Don't say cartesianing ST diagram, this is nonsense." :smile:
Mentz114 said:
Look at this diagram. Can you say what the time is on Greens clock at the event when the first light pulse intersects with the green WL ?
What?? Where did you get this picture? Upload ST-03.txt and you'll see. Open "Original Source for ST-03.txt" in notepad. Don't open it in ST plotter. This is my original number. You'll see that I use 1500 and 1700 coordinate to match ##v = \frac{15}{17}c## I haven't upload it yet at PF Forum. I still have a question regarding pervect post. But your post came before I get the chance to finish my question.
Okay where it intersect Green Line? At (9.5,9.5) [(796.875, 796.875) according to my numbers].
But I have to count each square carefuly. I tought it was 10.5, not 9.5. Second calculation gives 9.5.
It's still a good software. If I "match speed" it, it will show the Lorentz transformation for one. And it helps me much than drawing ST diagram in Microsoft Excel or in Microsoft Paint.
ST-03 Match Speed.jpg
 

Attachments

  • #97
pervect said:
It may help to draw a space-time diagram of this.
ST-03.jpg

pervect said:
The sequence of events from A's point of view goes like this:

A sends a signal at -1 second (1 second before impact) according to A's clock -> E1
A receives a return signal at -.0625 (-1/16 a second) according to A's watch -> E4
The returned signal from B is conveniently timestamped with B's time reading. B's clock reads -.25 seconds -> E3
pervect said:
But A knows not to confuse the reading on B's clocks with his own readings.
PRECISELY! There's not ASSURANCE that their clock are synchronized first. Is this true?
They can only rely that each other is using an accurate atomic clock. Is this true?
And there's NO WAY for B to know WHEN they will meet. So we can rely to -0.25 number. -0.25 seconds is just an arbitrary number, is this true?
Of course at E4 A WILL KNOW when they will meet, is this true?

A considers himself at rest in his own frame, with B moving towards him.
- Yes
A knows that the time it takes for the signal to reach B is equal to the time that the signal takes to return from B.
- Yes
Interpreting his radar results, A concludes that the round-trip time for the light/radar signal was (-1/16 - (-1)) seconds, i.e. the round trip time was 15/16 seconds, which implies that the one-way trip time was 15/32 of a second.
-Yes

A computes the time in A's frame that B received the signal as the start time (-1 second) plus the one-way travel time (15/32 of a second), for a result of -17/32 seconds, i.e. -.53125 seconds
This is obviously different from the time B assigned to the same event. If A is familiar with special relativity, he expects this - he expects B's clock to be running slow, and it is - just as much slower as predicted, reading only -.25 seconds rather than -.53125 seconds.

- But A just can't divide -0.53125 to ##\frac{8}{17}## before E5, is this true?

Now, for the velocity.
A meets B at 0 seconds -> E5, and A knows that at the time B received the signal (-.53125 seconds), that B's distance was c multipled by the one-way travel time, i.e 15/32 seconds * c, c being the speed of light. Recall that the speed of light in A's frame must be constant an equal to c in A's frame on both the outgoing and ingoing trip.

- Yes

So A computes B's velocity as the distance, (15/32) light seconds dived by the time it takes for A to reach B, (17/32) seconds, thus B's velocity was 15/17 of the speed of light.
- But A can deduce B velocity at E4, according to Doppler, right? A doesn't have to WAIT until E5 to determine B velocity. Is this true?

pervect said:
It might be easier to work out a closely related problem where all the times are integers - or to use algebraic variables. Using the former approach (integers), we can imagine A sending a signal at 16 seconds before impact (by A's watch), and receving the echo at 1 second before impact (by A's watch).
Now you tell me, after all the calculations above. :oldeyes:
 
  • #98
Dear PF forum,
Before I ask further, can someone explain to me about time dilation?
ST-03(2).jpg

This problem is similar to Post - #84
Rather than starting at -1 second where we already know when Blue (B) and Green (G) will meet, I started the clock at 0, so we won't know at first when they will meet. "Nature can't be fooled."
Green (G) moves at 0.6c; ##V = -0.6; \gamma = 1.25##
The distance before Green starts to move is 900 ls
From Blue (B) frame,
E1: -900
E3: 900
E4: 1500
From Green (G) frame
E2: 0
E4: 1200, again if E2 is 0
Clocks are NOT synchronized, is this important?
Okay,...

E1: B:-900
B sends a signal to G, containing B clock's: B:-900
E2: G:0
G receives the signal from B, reads the data B:-900, G sends the signal to B, containing G's clock, G:0
Is it relevant for G to compare B:-900 with G's clock? I think no, because their clocks are not synchronized. G can only write (B:-900;G:0) in G's notebook.
G knows that B is moving toward G their distance is receding by 0.6c because of Doppler effect, is this true?

E3: B:900
B receives the signal from G, reads the data G:0,
Is it relevant for B to compare G:0 with B's clock? Again, I think not. B will write G:0; B:900 in B's notebook
B knows that G is moving toward B their distance is receding by 0.6c.


E4:B:1500; G:1200
B and G meet:
B reads his notebook
E3: When B is 900s, G is 0
E4: When B is 1500s, G is 1200
##\Delta t_b = 600; \Delta t_g = 1200## What is this? G's clock runs faster then B's?

G reads his notebook
E2: When B is -900s, G is 0
E4: When B is 1500s, G is 1200
##\Delta t_b = 2400; \Delta t_g = 1200## B's clock runs faster than G's.

The situation from E3 and E2 is symmetrical both for B and G. ##\frac{1}{2}##

But from G frame, it's B who moves, right? Motion is relative, and the clock for moving object runs SLOWER, not faster?
Is this how B should reconcile?
At E3, B receives the bounce signal that B has sent at -900 (E1),
##\frac{\Delta t}{2} = \frac{1800}{2} = 900##, so B knows that actually G received the signal 900 seconds ago E3. So the distance where G received the signal is 900 ls away when B clock reads ##900-900=0##.
At E4, when they meet. B see G clock is 1200, and comparing to his notebook E3: G Clocks -> 0. B clocks read 1500 at E5
So ##\Delta t_g = 1200##, while ##\Delta t_b = 1500##. So this is actually G proper time where B receives G signal at E3. Is this true?
This clocks conform gamma factor. ##\frac{1500}{1200}=\gamma = 1.25##

How B should reconcile? I can't find the solution here.
The situation should be symmetrical, right?
Thanks for any help.
 
  • #99
For post #98, in blue's frame we can write:

##(E4 - E3) = k^2 (E4-E1)##

where k is the doppler shift factor, ##\sqrt{\frac{1 - \beta}{1+\beta}} = \sqrt{.4 / 1.6} = 0.5## in this example, since ##\beta = v/c = .6##.

Here E1, E3, and E4 are time coordinates along the blue worldline, which are the reading of the blue clock at the specified events. It might be clearer to write timeof.E4.in.blue.frame instead of just E4, but that's too much work, so I just wrote down E4 , etc, and explained.

Note that E4-E1 is just the proper time along the blue worldline until it meets the green worldline. If we don't know when the two worldline's meet, we calculate that first (calculate E4), then use the above formula.So it's really not that much different, we use the same basic idea.

Similarly, we can write that (E4-E2), measured along the GREEN worldline, is equal to k*(E4-E1), measured along the blue worldline.

We can write down a few other things, too:

In the blue frame, ##E2 = (E1 + E3)/2##, which is zero in your example. We also know that the distance from blue to green in the blue frame at time E2 is given by the relationship 2*distance = (E3-E1)

That's pretty much all we need to solve the problem, as far as I know. I'm not quite sure what you're puzzled about.

The logical justification for the above formulae is just the fact that the relative velocity between blue and green is constant, implying that the doppler shift is constant, and that fact that for every transmitted signal, there is a unique time of reception, a 1:1 mapping.
 
  • Like
Likes Stephanus
  • #100
Post #99
pervect said:
Similarly, we can write that =>(E4-E2)<=, measured along the GREEN worldline, is equal to =>k*(E4-E1)<=, measured along the blue worldline.
Post #17
pervect said:
Basically, if you have two observers, one of which is moving relative to the other, who synchronize their clocks such that they both read zero when they are colocated, you can write a very simple relationship between the proper time of emission for one observer, and the proper time of reception for the other:

##t_{r} = k t_{e}##

where ##t_r## is the time of reception, and ##t_e## is time time of transmission. If you insist on synchronizing your clocks differently , then you'd need to rewrite this equation as

=>##(t_r - c_r) = k \, (t_e - c_e)##<= and set the values of ##c_r## and ##c_e## such that the receiving clock reads ##c_r## when the transmitting clock reads ##c_e## at the moment when the two clocks are colocated.
Ah, I got it!
 
Back
Top