We're correcting clocks to make them
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
Maciej Wozniak <maluwozniak@gmail.com> wrote:
We're correcting clocks to make them
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
That is a beginning, but you stil lack some understanding.
FYI, and for the innocent kiddies who shouldn't be misled,
there are two kinds of clocks.
1) Clocks that are allowed to run free, as they go,
and are as stable as their operators can make them.
There are hundreds of them in standards labs worldwide.
None of them agree precisely with any of the others.
TAI is determined by averaging the readings of those master clocks,
and UTC is derived from TAI by adding leap seconds.
BIPM and IERS take care of that.
TAI is what it is, as is UTC,
an average, not the reading of any particular clock.
TAI is nothing but a table of corrections to be applied
to the readings of each of those clocks, to obtain TAI.
It is retrospective only.
For each one of those clocks BIPM will say:
you are so many nanoseconds ahead/behind TAI,
and you are drifting with so many nanosecond/day.
The operators of master clocks can thereby estimate
what corrections they should apply to an instantaneous reading
of each clock to know what it says in terms of TAI/UTC.
TAI, being an average of hundreds of independent master clocks,
is an order of magnitude more accurate than each clock separately.
For comparison, if you have a watch, and you know that it is 10 seconds behind, and that it advances by 0.2 seconds/day, you can convert its
reading a month hence into correct time.
That is how those sea captains of yore navigated,
using three chronometers, with known corrections applied to each.
2) Clocks that are steered.
Using the tricks of the trade you can make a clock advance or retard.
This ability can be used to force a steered clock to read UTC,
by applying and extrapolating the corrections supplied by BIPM.
Standards laboratories will also have steered clocks,
for pratical purposes, such as giving time signals,
synchronising network time, operating power networks, etc.
Steered clocks will show UTC, as well as their operators can make it.
All of this is just practical metrology, no mythological gurus involved.
And again FYI: the GPS system as a whole is steered to UTC.
(so all clocks in all sats)
The one second pulses that you can obtain from a GPS receiver
will indicate UTP, if you count them.
And a great many others have steered clocks too,
taking their time from GPS receivers.
You probably have one, if you have a smartphone.
This is how it works, whether you like it or not,
Maciej Wozniak <maluw...@gmail.com> wrote:
We're correcting clocks to make themThat is a beginning, but you stil lack some understanding.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
FYI, and for the innocent kiddies who shouldn't be misled,
there are two kinds of clocks.
On 4/29/2023 5:36 PM, J. J. Lodder wrote:
Maciej Wozniak <maluw...@gmail.com> wrote:
We're correcting clocks to make them
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
That is a beginning, but you stil lack some understanding.
FYI, and for the innocent kiddies who shouldn't be misled,
there are two kinds of clocks.
1) Clocks that are allowed to run free, as they go,
and are as stable as their operators can make them.
There are hundreds of them in standards labs worldwide.
None of them agree precisely with any of the others.
TAI is determined by averaging the readings of those master clocks,
and UTC is derived from TAI by adding leap seconds.
BIPM and IERS take care of that.
TAI is what it is, as is UTC,
an average, not the reading of any particular clock.
TAI is nothing but a table of corrections to be applied
to the readings of each of those clocks, to obtain TAI.
It is retrospective only.
For each one of those clocks BIPM will say:
you are so many nanoseconds ahead/behind TAI,
and you are drifting with so many nanosecond/day.
The operators of master clocks can thereby estimate
what corrections they should apply to an instantaneous reading
of each clock to know what it says in terms of TAI/UTC.
TAI, being an average of hundreds of independent master clocks,
is an order of magnitude more accurate than each clock separately.
For comparison, if you have a watch, and you know that it is 10 seconds behind, and that it advances by 0.2 seconds/day, you can convert its reading a month hence into correct time.
That is how those sea captains of yore navigated,
using three chronometers, with known corrections applied to each.
2) Clocks that are steered.
Using the tricks of the trade you can make a clock advance or retard.
This ability can be used to force a steered clock to read UTC,
by applying and extrapolating the corrections supplied by BIPM.
Standards laboratories will also have steered clocks,
for pratical purposes, such as giving time signals,
synchronising network time, operating power networks, etc.
Steered clocks will show UTC, as well as their operators can make it.
All of this is just practical metrology, no mythological gurus involved.
And again FYI: the GPS system as a whole is steered to UTC.
(so all clocks in all sats)
The one second pulses that you can obtain from a GPS receiver
will indicate UTP, if you count them.
And a great many others have steered clocks too,
taking their time from GPS receivers.
You probably have one, if you have a smartphone.
This is how it works, whether you like it or not,Internally GPS system "ticks" GPS time which is a constant fixed offset
from TAI time. However GPS satellites broadcast things like the current offset from GPS time to UTC, when the next leap second will happen (if
that has been determined) and some other info. Consumer grade GPS
devices will combine these to come up with the current UTC, and from
there into their local time according to timezone and whether summer
time is active. 99.9% of users are more interested in their local legal
time than GPS time, TAI time or even UTC time.
On Saturday, 29 April 2023 at 23:36:35 UTC+2, J. J. Lodder wrote:
Maciej Wozniak <maluw...@gmail.com> wrote:
We're correcting clocks to make themThat is a beginning, but you stil lack some understanding.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
FYI, and for the innocent kiddies who shouldn't be misled,
there are two kinds of clocks.
For those innocent kiddies - there are 2 kind
od clocks, indeed. Some are real and indicate
t'=t while others are gedanken and confirming
some religious delusions of a bunch of
insane halfbrains.
Maciej Wozniak <maluw...@gmail.com> wrote:
On Sunday, 30 April 2023 at 01:46:02 UTC+2, Volney wrote:
On 4/29/2023 5:36 PM, J. J. Lodder wrote:
Maciej Wozniak <maluw...@gmail.com> wrote:
We're correcting clocks to make them
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
That is a beginning, but you stil lack some understanding.
FYI, and for the innocent kiddies who shouldn't be misled,
there are two kinds of clocks.
1) Clocks that are allowed to run free, as they go,
and are as stable as their operators can make them.
There are hundreds of them in standards labs worldwide.
None of them agree precisely with any of the others.
TAI is determined by averaging the readings of those master clocks,
and UTC is derived from TAI by adding leap seconds.
BIPM and IERS take care of that.
TAI is what it is, as is UTC,
an average, not the reading of any particular clock.
TAI is nothing but a table of corrections to be applied
to the readings of each of those clocks, to obtain TAI.
It is retrospective only.
For each one of those clocks BIPM will say:
you are so many nanoseconds ahead/behind TAI,
and you are drifting with so many nanosecond/day.
The operators of master clocks can thereby estimate
what corrections they should apply to an instantaneous reading
of each clock to know what it says in terms of TAI/UTC.
TAI, being an average of hundreds of independent master clocks,
is an order of magnitude more accurate than each clock separately.
For comparison, if you have a watch, and you know that it is 10 seconds behind, and that it advances by 0.2 seconds/day, you can convert its reading a month hence into correct time.
That is how those sea captains of yore navigated,
using three chronometers, with known corrections applied to each.
2) Clocks that are steered.
Using the tricks of the trade you can make a clock advance or retard. This ability can be used to force a steered clock to read UTC,
by applying and extrapolating the corrections supplied by BIPM.
Standards laboratories will also have steered clocks,
for pratical purposes, such as giving time signals,
synchronising network time, operating power networks, etc.
Steered clocks will show UTC, as well as their operators can make it.
All of this is just practical metrology, no mythological gurus involved.
And again FYI: the GPS system as a whole is steered to UTC.
(so all clocks in all sats)
The one second pulses that you can obtain from a GPS receiver
will indicate UTP, if you count them.
And a great many others have steered clocks too,
taking their time from GPS receivers.
You probably have one, if you have a smartphone.
This is how it works, whether you like it or not,Internally GPS system "ticks" GPS time which is a constant fixed offset from TAI time. However GPS satellites broadcast things like the current offset from GPS time to UTC, when the next leap second will happen (if that has been determined) and some other info. Consumer grade GPS
devices will combine these to come up with the current UTC, and from there into their local time according to timezone and whether summer
time is active. 99.9% of users are more interested in their local legal time than GPS time, TAI time or even UTC time.
And they're completely ignoring delusionalI never understood where you got this delusion of yours from.
"proper time" of your idiot guru.
Each atomic clock does tick at its own 'proper time',
and that is just what 'proper time' means, in the context of relativity,
It would seem that you never had two clocks of your own.
If you ever had you would know that each clock
has t' equals t with respect to itself, and only with respect to itself.
It is for professionals to make sense of the observed differences,
We're correcting clocks to make them
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
On Thursday, May 4, 2023 at 11:19:46 AM UTC+5, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
say why.There are no relativistic corrections. AccordingI was following a course on Coursera and the professor mentioned that clocks could be synchronized and stay synchronized if they were synchronized together and moved slowly apart. The professor did not pursue this method of synchronization, but did not
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
Let me put the question to ChatGPT.other.
########
Question:
How slowly would atomic clocks have to be moved apart a distance of 1 light year to continue to by synchronized withing their limits of accuracy?
Answer:
To answer this question, we need to consider the effects of time dilation due to relative motion as predicted by Einstein's theory of relativity. According to this theory, time appears to pass more slowly for objects that are moving relative to each
In the case of atomic clocks, their timekeeping accuracy is based on the frequency of atomic transitions, which is affected by the local gravitational field and the relative motion of the clock. Specifically, the frequency of the clock will be affectedby the relative motion of the clock with respect to an observer in a different frame of reference. This effect is known as the relativistic Doppler shift.
For two atomic clocks separated by a distance of 1 light-year (which is approximately 9.46 x 10^15 meters), moving apart at a constant velocity, the difference in their relative velocities will cause their timekeeping to become increasinglydesynchronized due to the relativistic Doppler shift. The amount of time dilation depends on the relative velocity between the clocks and the observer.
Assuming a constant relative velocity of 0.1c (where c is the speed of light), and the clocks have the accuracy of the most accurate atomic clock, an optical lattice clock, which can achieve an accuracy of one second in 30 billion years, the clockswould be desynchronized by approximately one nanosecond per day. Therefore, to keep the clocks synchronized within their limits of accuracy, they would need to be moved apart at a velocity much lower than 0.1c or alternatively, adjusted for the
#######in kmh
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
There are no relativistic corrections. According
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
On Thursday, May 4, 2023 at 11:19:46 AM UTC+5, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
There are no relativistic corrections. AccordingI was following a course on Coursera and the professor mentioned that clocks could be synchronized and stay synchronized if they were synchronized together and moved slowly apart.
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
On Thursday, 4 May 2023 at 12:58:17 UTC+2, gehan.am...@gmail.com wrote:
On Thursday, May 4, 2023 at 11:19:46 AM UTC+5, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
Gedanken, gedanken, gedanken and gedanken.There are no relativistic corrections. AccordingI was following a course on Coursera and the professor mentioned that clocks could be synchronized and stay synchronized if they were synchronized together and moved slowly apart.
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
Time dilation is some lack of synchronization.
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
poor halfbrain.
Or, even better,
shut up.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,A systematic error matching almost perfectly SR prediction,
what kind of miracle is that?
Or, even better,You're not in a position where you could ask anyone to shut up Maciej.
shut up.
Gedanken, gedanken, gedanken and gedanken.
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",Nope, you couldn't build GR from LET.
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
poor halfbrain.
Or, even better,You're not in a position where you could ask anyone to shut up Maciej.
shut up.
Fine,
poor halfbrain,
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,Make sure pressure and temperature are the same, it's
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
On Thursday, 4 May 2023 at 15:18:14 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:Make sure pressure and temperature are the same, it's
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
Isn't it? What precision do you offer,
And do you think it will be enough? For something
like "aging"?
poor halfbrain.
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
that can be checked in experiment because measured values
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
poor halfbrain.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:18:14 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:Make sure pressure and temperature are the same, it's
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau >>>>>>>> that can be checked in experiment because measured values
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution.
https://en.wikipedia.org/wiki/Observational_error
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
Isn't it? What precision do you offer,For "aging" of muons it is actually enough.
And do you think it will be enough? For something
like "aging"?
On Thursday, 4 May 2023 at 15:31:33 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:18:14 UTC+2, Python wrote:For "aging" of muons it is actually enough.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:Make sure pressure and temperature are the same, it's
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:https://en.wikipedia.org/wiki/Observational_error
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau >>>>>>>>>> that can be checked in experiment because measured values
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
will all verify dt = gamma*dtau +/- epsilon
Classical clock errors would follow a Gaussian distribution. >>>>>>>>>
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
Isn't it? What precision do you offer,
And do you think it will be enough? For something
like "aging"?
Python, your muons don't
"experience" the same environment temperature
or pressure.
poor halfbrain
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:31:33 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:18:14 UTC+2, Python wrote:For "aging" of muons it is actually enough.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:Make sure pressure and temperature are the same, it's
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote:A systematic error matching almost perfectly SR prediction,
Maciej Wozniak wrote:https://en.wikipedia.org/wiki/Observational_error
...
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau >>>>>>>>>> that can be checked in experiment because measured values >>>>>>>>>> will all verify dt = gamma*dtau +/- epsilon
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
Classical clock errors would follow a Gaussian distribution. >>>>>>>>>
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
what kind of miracle is that?
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
Isn't it? What precision do you offer,
And do you think it will be enough? For something
like "aging"?
Python, your muons don'tDid you really check? Clearly you didn't.
"experience" the same environment temperature
or pressure.
And even if your argument made sense (it does'nt)
On Thursday, 4 May 2023 at 15:41:52 UTC+2, Python wrote:
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:31:33 UTC+2, Python wrote:Did you really check? Clearly you didn't.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:18:14 UTC+2, Python wrote:For "aging" of muons it is actually enough.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 15:02:28 UTC+2, Python wrote:Make sure pressure and temperature are the same, it's
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:45:21 UTC+2, Python wrote:Nope, you couldn't build GR from LET.
Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 14:30:47 UTC+2, Python wrote: >>>>>>>>>>>> Maciej Wozniak wrote:A systematic error matching almost perfectly SR prediction, >>>>>>>>>> what kind of miracle is that?
...https://en.wikipedia.org/wiki/Observational_error
Gedanken, gedanken, gedanken and gedanken.SR prediction follows a simple distribution : dt = gamma*dtau >>>>>>>>>>>> that can be checked in experiment because measured values >>>>>>>>>>>> will all verify dt = gamma*dtau +/- epsilon
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
Classical clock errors would follow a Gaussian distribution. >>>>>>>>>>>
As usual - wrong.
Some of them, called "random" would.
Other , called "systematic" wouldn't.
Try again,
Your moronic religion is calling it "Lorentz's ether",
Read your question again, poor halfbrain. Was GR
or SR there?
try again (and fool yourself
again). What is the difference between your time
dilation and classical clock error?
Another one is that an error on clocks measurements wouldn't
match the effect on other physical processes that depend
on duration : cooking an egg, aging, food decay, etc.
Neither your time dilation does,
Cooking an egg is pressure dependent, food decay
or aging - temperature and so on.
Try again. And fool yourself again. As you don't want
to shut up and stop pretending you know something...
not that difficult.
Isn't it? What precision do you offer,
And do you think it will be enough? For something
like "aging"?
Python, your muons don't
"experience" the same environment temperature
or pressure.
And even if your argument made sense (it does'nt)
Ok, enough kicking the sorry
ass of an idiot troll.
You will die as idiot (if not more) than you are now.
On Thursday, 4 May 2023 at 12:58:17 UTC+2, gehan.am...@gmail.com wrote:
On Thursday, May 4, 2023 at 11:19:46 AM UTC+5, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
Gedanken, gedanken, gedanken and gedanken.There are no relativistic corrections. AccordingI was following a course on Coursera and the professor mentioned that clocks could be synchronized and stay synchronized if they were synchronized together and moved slowly apart.
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
On Thursday, May 4, 2023 at 4:45:41 AM UTC-7, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 12:58:17 UTC+2, gehan.am...@gmail.com wrote:
On Thursday, May 4, 2023 at 11:19:46 AM UTC+5, Maciej Wozniak wrote:
On Thursday, 4 May 2023 at 05:44:19 UTC+2, gehan.am...@gmail.com wrote:
On Friday, April 28, 2023 at 12:15:53 PM UTC+5, Maciej Wozniak wrote:If we assume postulates of relativity - we
We're correcting clocks to make themRelativistic corrections depend on the relative velocity between the clocks.
indicating t'=t - because we're assuming
that clocks should indicate t'=t.
No other possibility, no word gymnastic
can change that.
assume [atomic] clocks are proper. Correct.
Whatever.
If we're assuming clocks should be synchronized
(i.e. indicating t'=t) - our model can't be relativistic.
Our assumptions are violating relativistic
assumptions.
Different speeds in space give different rates...Gedanken, gedanken, gedanken and gedanken.There are no relativistic corrections. AccordingI was following a course on Coursera and the professor mentioned that clocks could be synchronized and stay synchronized if they were synchronized together and moved slowly apart.
to The Shit the clocks SHOULD desynchronize.
Yes, it is insane. It was always insane.
Doesn't really matter, however.
Time dilation is some lack of synchronization.
And 100% classical clock error is the same:
lack of synchronization.
What is the difference? Can you tell any?
It would seem that you never had two clocks of your own.
If you ever had you would know that each clock
has t' equals t with respect to itself, and only with respect to itself.
It will have t' not equals t with respect to any other clock.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 27:04:48 |
Calls: | 6,707 |
Calls today: | 1 |
Files: | 12,239 |
Messages: | 5,352,688 |