Your point being? I mean other than needlessly babbling about minor details that nobody disputed and that don't change anything or add anything to the conversation.Baffalo wrote:Computers run on internal clocks operating in the gigahertz range, with each pulse of the crystal causing the operations to cycle to the next operation called upon. Most computers do this independently of clocks that we care about, because the clock itself simply pulses. For the clocks we care about, most computers have a second clock that pulses and cycles registers, building up in a register until a pre-set number is reached and then it trips a register to cycle to the next second. The reason this is the case is that the second clock is actually a hardware accessory that gets called upon to deliver a number that is then added to the 1.1.1970 you mentioned Skgoa.
This isn't perfect, because these clocks sometimes skip. Most internet connected computers link up with a standardized clock, and if you pay enough attention, you'll notice your wrist-watch sometimes drifts compared to your computer. For most purposes, it's not worth noticing, but for precise scientific measurement, if you're off by enough, tiny deviations become large problems.
SF timekeeping systems
Moderator: NecronLord
Re: SF timekeeping systems
http://www.politicalcompass.org/test
Economic Left/Right: -7.12
Social Libertarian/Authoritarian: -7.74
This is pre-WWII. You can sort of tell from the sketch style, from thee way it refers to Japan (Japan in the 1950s was still rebuilding from WWII), the spelling of Tokyo, lots of details. Nothing obvious... except that the upper right hand corner of the page reads "November 1931." --- Simon_Jester
Economic Left/Right: -7.12
Social Libertarian/Authoritarian: -7.74
This is pre-WWII. You can sort of tell from the sketch style, from thee way it refers to Japan (Japan in the 1950s was still rebuilding from WWII), the spelling of Tokyo, lots of details. Nothing obvious... except that the upper right hand corner of the page reads "November 1931." --- Simon_Jester
Re: SF timekeeping systems
If we're talking about a universal, standard time for seconds (the basic unit of timekeeping), then you must be able to configure it correctly. Unless you're going to send a nuclear clock on every ship, you must be able to configure clocks to adjust for relativistic effects. If you place a gravatic sensor next to the ship's onboard computer, you can make sure the ship accurately measures time, and thus you don't wind up sending a report to Earth saying you defeated an enemy combatant 4 months before the report even arrives on Earth, or get a report dated 6 months ago.Skgoa wrote:Your point being? I mean other than needlessly babbling about minor details that nobody disputed and that don't change anything or add anything to the conversation.
"I subsist on 3 things: Sugar, Caffeine, and Hatred." -Baffalo late at night and hungry
"Why are you worried about the water pressure? You're near the ocean, you've got plenty of water!" -Architect to our team
"Why are you worried about the water pressure? You're near the ocean, you've got plenty of water!" -Architect to our team
Re: SF timekeeping systems
Only if you count things like more trade opportunities, far easier unit math/conversion, interplanetary probes not crashing and having a sane system as no benefit whatsoeverPeZook wrote:It's much easier to set up a new clock and calendar before your society is established. It's the same reason why the US isn't keen to adopt the metric system: what they have works, and changing everything would be just too much of a hassle and give no benefit whatsoever.
Speaking of time, all these systems, IMHO, are needlessly complicated and ignore one basic thing - humans. We're not going to work 17 hour shifts, stay up 20 hours at a time, or anything like that... So why just not keep 24 hour calendar, 365.25 days, then? Ok, number of days in year can be adjusted for easier computation, but with outdoor and indoor lights, we can keep 24 days, and instead make schedule flexible. Say, if planet has 30 hour days, we can divide each 'human' 24 day into 3 blocks, 8 hour sleep, 8 hour work, and 8 hour free time, using free time as padding to maximize sunlight usage. One day humans would go to work immediately after waking up, then have free time, other would go after 4 hours, work, then have 4 hours more. With tendency of work day to become shorter, future 6 hour shifts would be even easier to manage, plus, having 24 hours makes it trivial to divide day into 3-4 human-manageable shifts for continuous work in industries that need it.