Skip to main content

Analog Clock Trivia?

Alright... now I've seen some pretty weird stuff on the Internet... but how about this?

Picture an analog clock with an hour hand, minute hand, and second hand, ticking every second.  Have you ever wondered...
  • How often is the second hand between the hour and minute hands?
  • At what time is the clock equally divided into three parts (by the positions of the hour, minute, and second hands)?
... ya, I think about this stuff all the time. (sarcastic)

Well... in case you were wondering, I've found the answers.  The second hand is between the hour and minute hands about 32% (13832 of 43200) of the time.  There are a total of 43200 possible positions for the hour, minute, and second hands on an analog clock.  That is, 60*60*12.

And... a perfect analog clock really never is divided equally into three parts by the hands (unless you count the times when the second hand is in motion to its next position... that is, in the middle of a "tick").  However, it is closest to three equal parts at 8:22:02 (either AM or PM).  At this time, the hour hand will be about 251.0166 degrees from 12:00:00 (moving clockwise, of course).  The minute hand will be at exactly 132.2 degrees from 12:00:00, and the second hand will be at exactly 12 degrees from 12:00:00.

Good to know, right?  It was so ridiculous, that I had to post it.  My apologies for completely wasting your time.

Comments

Post a Comment

Popular posts from this blog

Wedding Prediction - October, 2013

Carla and I are planning on getting married sometime in October next year.  We need to pick a date, and that decision may  involve some science and mathematics.  :) For example, we want the weather to be nice.  To be more precise, we'd like the high temperature for the wedding day to be between 60 and 80 degrees Fahrenheit.  Obviously, we have both lived in Ohio our entire lives, and we have a pretty good idea of what the weather will be like.  We both hypothesised that October was a "hit or miss" sort of month; it could be cold, or it could be nice. But, for me, a simple hypothesis was not enough; I really wanted to know the probabilities of decent weather based on historical weather data.  Many websites on the Internet (i.e. almanac.com) charge you to review historical weather data, but Carla and I discovered a cool page on cleveland.com that provided exactly what we wanted.  I loaded the historical temperature data from 1903 to 2011 f...
2 comments
Read more

Web Browsers You Should Support

As a web developer, generally speaking, you should consider supporting the following browsers (at the time of this writing): Chrome (latest) - the browser that sets the bar for the others; you should be using it and supporting it Internet Explorer 9+ - the browser that finally caught up with the times a bit; basically, a Chrome wannabe.  I still say that IE sucks... even if it really doesn't anymore.  Yes... I'm sour about IE8 and below. Internet Explorer 8 - the old, sad browser that we sadly still have to support for a while.  CSS 3 is not well-supported here, so we use projects like CSS3 PIE or whatever.  By the way... IE8 sucks.  I can't wait until this comes off of the list. Firefox (latest) - the browser that was once awesome and has sadly suffered recently because it's slower than Chrome... but hey, lots of people still use it. Safari (latest) - Watch out for Safari as more iPhones, iPads, Macs, and more overly-priced Apple products flood the ...
Post a Comment
Read more

Computer Clocks Cause More Issues

Two nights ago, a leap second was added to system clocks running Linux, causing much-undesired havoc. On July 1st at 12:00 AM UTC, both of my Amazon EC2 instances fired an alarm indicating high CPU usage. I investigated to find that it was MySQL that was eating all of the CPU. I logged in and ran SHOW PROCESSLIST to find that no queries were running (these servers don't get hit much after business hours). I stopped MySQL, CPU utilization dropped back down to 1-3% (as normal). I restarted MySQL, and it started eating a lot of CPU again. Then, I restarted the server (shutdown -r now), and the problem went away. Both servers had the exact same problem (running Ubuntu 12.04 LTS). In my particular case, MySQL began eating CPU, even after being restarted.  It was a livelock. The only relevant item I saw in the syslog was: Jun 30 23:59:59 hostname kernel: [14152976.187987] Clock: inserting leap second 23:59:60 UTC Oh yeah... leap seconds.  Those are super impor...
Post a Comment
Read more