Sorta the electromechanical equivalent of
If that’s the case, and the on-air hosts know that they’re on a 15-second delay, the chime should ring 15 seconds early. With the delay, they’ll ring at the correct time.
I had something similar happen a couple years ago. I was at the Kennedy Space Center watching a rocket launch. They had TVs set up showing the NASA coverage of the launch. One of the docents told us that the TV was delayed by 9 seconds. We started our 10-second countdown when the TV was at 19.
I’ve always kinda wondered how the delay on live broadcasts worked in practice. There must be someone listening to the hosts for any objectionable words, who can then quickly switch to the delayed signal to bleep out the offending word. That seems to create a loophole. If someone swears twice, 15 seconds apart, the monitor will miss the second one because he was busy bleeping the first one.
Here they tell the story of a vengeful ex-girlfriend who called the time phone number in New York.
The story was of an office romance with a married boss and his secretary. He dumped her just before he left with his family to go back to the States for a couple of weeks. She made the call from his office.
I first heard this in the 80s, when international calls were insanely expensive. It was told as an obvious joke so I think that urban legend has been going around for a long time.
Yes, the '80s would be about right. Funny how these stories made the rounds before internet virality. You heard it in Tokyo? I heard it in Berlin. And international calls were indeed insanely expensive back then.
I do! I wish my iPhone and iMac displayed seconds on all time displays including photos. Actually, I wish fractional seconds were displayed on photos, because they can be taken much less than a second apart. Time is a great way to identify and sort theem.
I used to do scientific research on big machines. Sometimes I’d have multiple data loggers on them, because I had so many channels or because the machines were so long that running small analog signals through long enough wires would introduce noise. In these cases, subsecond timing was important when comparing measurements (such as how fast a pressure change propagated along the length of the machine). For these situations I wrote a program that could get subsecond accuracy setting the data loggers (DataTaker DT800) through their RS232 port. Then I’d also log digital transitions to use as internal comparison timestamps through postprocessing.
I like GPS time. I’ve toyed with buying a Stratum 2 receiver for my home network, but until I do, I’m using NTP. On my iPhone I have a couple of apps that read NTP servers; one emits clicking sounds and displays 100 points in a circle to mark tens of milliseconds, and the other reads multiple servers and displays an intercomparison.
I have two six-digit NTP wall clocks. I set my camera clocks from them, and sometimes go as far as taking photos of the seconds transitions to estimate photo timestamp accuracy. I’ve also photographed the wall clocks with the iPhone app to compare.
Agreed. But there’s a certain subtle qualifier needed. NIST makes available a current time through radio transmissions, but that’s a tentative time. The final determination of accurate time is done retroactively by comparison of multiple sources later. IIRC it’s something like a month later, though I could have this delay wrong. You can record the time of an event to the highest resolution you can, and weeks later you can adjust it to improve its accuracy.
This is profoundly messed up.
As I mentioned above, I could walk to the broadcast facility for WWV. I offered that I could simply head over there and ask them what the time is.
But you’re saying I have to ask them what the time was?
And if I do that, how will I reference when I’m talking about? This sounds needlessly epistemological, metrological, circular, confusing, and anxiety-provoking.
I’m getting a sundial. QED
You will to have gotten a sundial
Paid for next Tuesday I hope.
Be sure to get one that compensates for atmospheric refraction.
I’m sorry. I may have mist something, because I haven’t the foggiest notion what that meant.
Interestingly, my phone (Android) time display is a few fractions of a second faster than the time on the NIST website.
Atmospheric refraction causes the sun to appear to be slightly higher than its true position (the position at which it would be observed if there were no atmosphere). The effect is largest when the sun is low in the sky. A naively constructed sundial will therefore be slightly wrong in the early morning and late evening. Since the discussion in this thread is about precision time measurement, I was making a small joke about one effect that contributes to the inaccuracy of sundials.
And I was making an even smaller joke about two possible factors that can cause atmospheric refraction
Perhaps you two should sit down and reflect a bit on what you’ve done before throwing shade on one another’s gnomon.
TIL. I look forward to the day I win Trivial Pursuit with that tidbit.
I bought one from a local guy who created a unique design for one! It is customized for my house location, so if I ever move out the sundial stays with the house.
Daniel Wenger’s sundial
➜ The Wenger Sundial ■
Daniel lives about an hour away, in Santa Cruz. I found him through NASS, the North American Sundial Society. It does not, however, provide the precise seconds. I’ll have to file a complaint, LOL.
I always thought it was part of some archipelago, somewhere
I’m looking into how to acquire a second home on DiscWorld.
Not sure about the visa requirements etc?
The sun there is a proper sun that behaves in accordance with Narrativium…?
You could ask them what UTC(NIST) is. The actual UTC is calculated later. That is to say, a record of the differences between UTC(NIST) and UTC is calculated and published later. If you recorded UTC(NIST), you can correct it to UTC. This might be important for, say, stellar occultation data.
" The concept of a virtual time scale can be difficult to grasp, but perhaps becomes easier when you consider that none of the clocks in the UTC ensemble reside at the BIPM and thus the BIPM doesn’t measure any physical clock signals. Instead, the BIPM calculates UTC from measurement data that is sent to them by the more than 80 laboratories mentioned earlier.
[…]
Once a month, after all clock measurements have been collected and after all calculations are complete, the BIPM publishes the results in an on-line document known as Circular T. This document lists the time difference between UTC and each of the local time scales that are subsets of UTC, such as UTC(NIST). In Circular T parlance, the local time scales are known as UTC(k), where k is a variable that designates the name of the local time scale’s laboratory, and where values for UTC – UTC(k), are reported at 5-day intervals. The publication of these values is extremely important for ensuring that UTC is indeed “coordinated” around the world, because it verifies the accuracy of each UTC(k) time scale with respect to UTC.
[…]
To make data available more frequently than once per month, the BIPM also publishes an unofficial time scale called Rapid UTC, or UTCr. Rapid UTC is published once per week, with values of UTCr – UTC(k) reported at 1-day intervals. Currently (November 2020), NIST and more than 60 other laboratories participate in UTCr.
Although the values computed by UTC and UTCr are not known until after the fact, UTC(NIST) is continuously adjusted using forward prediction techniques that anticipate where UTC will be when the Circular T is published. As a result, UTC(NIST) is an excellent approximation of UTC that has the advantage of producing physical signals in real time, and that typically differs from UTC by less than three billionths of a second (3 ns).
[…]
[https://www.nist.gov/pml/time-and-frequency-division/time-realization/utcnist-time-scale-0/introduction-utcnist]
By the way, if you walk over there to ask them, and you care about getting the most exact version, stand close to whomever you ask. At a typical conversational distance of three feet, the time for light to travel from them to you is about equal to the discrepancy between UTC(NIST) and UTC.
No one is going to take the bait on that one?