How can I accurately determine the time gained or lost by a clock?

In summary: There's still a problem. The hour hand moves 85800/11 = 79600 seconds between each meeting. This means that in total the clock gains 79600 + 85800 = 119600 seconds in one day. This is not enough time to make up for the previous day's error. Almost correct. (and in multiple choice questions almost can be good enough). However, still wrong in two ways. First, it gets there 27 seconds early, but a true 65 minutes hasn't passed yet. After a true 65 minutes the margin will be slightly larger. Also, it's every 65 minutes, not every hour, so you scaled badly. Fix those things and
  • #1
Vibhor
971
40

Homework Statement



?temp_hash=9dc10271a3c708d9148ab93d843f796b.png


Homework Equations

The Attempt at a Solution



I usually have trouble with these clock problems . In this problem I can certainly rule out option d) . I considered a simple situation in which initially the clock is at 12' o clock . After 65 minutes , the minute hand would be at 1'o clock mark wheras the hour hand would be somewhere between 1 and 2 . This means when the two hands meet the actual time elapsed should be more than 65 minutes .

Now the problem is how much time the clock has gained . Consider the hour hand . It covers 5 minute units in 60 minutes time . So, the time gained should be less than (5/60) times 86400 seconds . I am sure I am thinking incorrectly .

Please help with the problem .

Thanks .
 

Attachments

  • clock.PNG
    clock.PNG
    19.3 KB · Views: 554
Physics news on Phys.org
  • #2
Yes, it's easy to get lost in this one. I think there must be more than one way to think about it, too. My approach was to think about how many times the minute hand catches up to the hour hand in one "12 hour" period.
 
  • Like
Likes Vibhor
  • #3
Cutter Ketch said:
Yes, it's easy to get lost in this one. I think there must be more than one way to think about it, too. My approach was to think about how many times the minute hand catches up to the hour hand in one "12 hour" period.

Hello ,

Did you get one of the answers ? Could you elaborate your approach.
 
  • #4
I think the first thing should be to write an equation for the angle of rotation for each of the clock hands as a function of time (seconds or minutes). Then it seems to make sense to me to start at 1:00. At 1:00, write an equation for how much the minute hand moves relative to how much the hour hand moves until they align.

After I started writing, but before I posted this message, I read @Cutter Ketch approach. I would recommend using his approach. The math is much simpler. :)
 
  • #5
Cutter Ketch said:
My approach was to think about how many times the minute hand catches up to the hour hand in one "12 hour" period.

The minute hand catches up with hour hand 11 times i.e after every 43200/11 = 3927 seconds . 65 minutes = 3900 seconds . This means the clock gains 27 seconds per hour .Or in other words 648 seconds in a day .So the answer should be option b) .

Do you agree ?
 
  • #6
43200 is the number of seconds in 12 hours. So dividing that number by 11 gives the number of seconds in 12/11 of an hour, or 3927.2727 seconds. And (65)(60) = 3900 is the measured number of seconds (measured by a perfect clock) in 12/11 of an hour. So when you subtract those two numbers (3927.27 - 3900), the result does not give the clock error per hour. It gives the clock error per 12/11 of an hour. I hope I said that right.

Edit: Actually I think this problem is easier to work using minutes.
 
  • #7
Vibhor said:
The minute hand catches up with hour hand 11 times i.e after every 43200/11 = 3927 seconds . 65 minutes = 3900 seconds . This means the clock gains 27 seconds per hour .Or in other words 648 seconds in a day .So the answer should be option b) .

Do you agree ?

Almost correct. (and in multiple choice questions almost can be good enough). However, still wrong in two ways. First, it gets there 27 seconds early, but a true 65 minutes hasn't passed yet. After a true 65 minutes the margin will be slightly larger. Also, it's every 65 minutes, not every hour, so you scaled badly. Fix those things and your approach is correct.

I had a slightly different approach. The hands meet 11 times per 12 hours as you note. So if the hands meet in 65 minutes, then the minute hand covered 1 hour in 11 * 65 / 12 minutes. Divide that into 24 hours and that is how many hours the false clock shows in 24 true hours.
 
  • Like
Likes Vibhor
  • #8
I don't know why I felt better working in hours. Your approach can quickly produce the right answer. You need the ratio false clock per true clock. You have that the false clock showed 3927 when only 3900 had truly passed. Take the ratio and multiply by 24 hours. (But don't use the rounded value of 3927. Keep all the digits)
 
  • Like
Likes Vibhor
  • #9
Another approach -

Hour hand meets minutes hand after every 65 minutes . This means actual time elapsed when the two hands meet for the 11th time is 65 × 22 × 60 = 85800 seconds . But time elapsed as per the clock is 86400 seconds .

The difference between the two is 600 seconds i.e option C) :rolleyes: .

Do you agree/disagree with this line of reasoning ?
 
  • #10
Vibhor said:
Another approach -

Hour hand meets minutes hand after every 65 minutes . This means actual time elapsed when the two hands meet for the 11th time is 65 × 22 × 60 = 85800 seconds . But time elapsed as per the clock is 86400 seconds .

The difference between the two is 600 seconds i.e option C) :rolleyes: .

Do you agree/disagree with this line of reasoning ?

Everything except "option c". As I hinted, your last try although slightly flawed got the right multiple choice answer. Here as in the previous case you've lost track of which is true and which is false. 600 seconds is how far ahead the false clock is when IT says 24 hours have passed. However it is fast, so 24 hours haven't actually passed yet. By the time 24 hours have truly passed it will be even a little further ahead.

To get exactly how far ahead, you need the ratio of false time / true time for any interval you know. Multiply that by 24 true hours and you get how far ahead false time is after 24 true hours.
 
  • Like
Likes Vibhor
  • #11
Cutter Ketch said:
600 seconds is how far ahead the false clock is when IT says 24 hours have passed. However it is fast, so 24 hours haven't actually passed yet. By the time 24 hours have truly passed it will be even a little further ahead.
I guess this is perhaps the exact reasoning problem setter had in his mind :smile: . This also looks to be the fastest way to arrive at the answer .

Impressive analysis Cutter Ketch !

As I said in OP I mess up big time in clock problems .
 
  • #12
TomHart said:
43200 is the number of seconds in 12 hours. So dividing that number by 11 gives the number of seconds in 12/11 of an hour, or 3927.2727 seconds. And (65)(60) = 3900 is the measured number of seconds (measured by a perfect clock) in 12/11 of an hour. So when you subtract those two numbers (3927.27 - 3900), the result does not give the clock error per hour. It gives the clock error per 12/11 of an hour. I hope I said that right.

Edit: Actually I think this problem is easier to work using minutes.

I have not been able to understand your line of reasoning . Sorry .

Is it similar to Cutter Ketch's reasoning ?
 
  • #13
Vibhor said:
I guess this is perhaps the exact reasoning problem setter had in his mind :smile: . This also looks to be the fastest way to arrive at the answer .

Impressive analysis Cutter Ketch !

As I said in OP I mess up big time in clock problems .

Well, maybe it's just me, but I thought this was tricky and easy to get turned around. I certainly screwed up a few times.
 
  • #14
Vibhor said:
I have not been able to understand your line of reasoning . Sorry .

Is it similar to Cutter Ketch's reasoning ?
As I read post #10 by @Cutter Ketch I realized I had made the same mistake - that I had not calculated how far off the clock was in one day; I had calculated how far off the clock was in what the errant clock reported to be one day - which actually was only 23 hours and 50 minutes. That is why I came up with the wrong answer of 600 seconds. The clock reported that 24 hours had elapsed, when in reality, only 23 hours and 50 minutes had elapsed. So as Cutter pointed out, in the additional 10 minutes, more error is added to the 600 seconds.
The ratio of reported time to actual time is 1440/1430.
So for an actual time of 1440 minutes, the reported time would be (1440)(1440/1430) = 1450.07 minutes.
 
  • Like
Likes Vibhor
  • #15
@haruspex , would you like to add/point out something in this discussion .
 
  • #16
Vibhor said:
@haruspex , would you like to add/point out something in this discussion .
The least head-hurting way might be to figure out how slow the fast clock thinks the ideal clock is, then invert.
According to the fast clock, in 24 hours its hands meet up 22 times, so the ideal clock measures 65*22 minutes.
According to the fast clock, in 24 * 24*60/(65*22) hours the ideal clock measures 65*22 * 24*60/(65*22) minutes = 24 hours.
According to the fast clock, in 24 hours and 10.07 minutes the ideal clock measures 24 hours.
 
  • Like
Likes Vibhor and Buffu
  • #17
From post#7
Cutter Ketch said:
First, it gets there 27 seconds early, but a true 65 minutes hasn't passed yet. After a true 65 minutes the margin will be slightly larger.

Would you like to review this ? I think true 65 minutes have passed .

##\frac{27.2727}{(65 × 60)} × 86400 = 604.2 sec##
 
Last edited:
  • #18
Vibhor said:
From post#7Would you like to review this ? I think true 65 minutes have passed .

##\frac{27.2727}{(65 × 60)} × 86400 = 604.2 sec##

That's it!
 
  • Like
Likes Vibhor
  • #19
OK.

But you said in post#7 that when the clock was ahead by 27 seconds , true 65 minutes haven't passed :rolleyes: .

I think true 65 minutes had passed .The previous post showed how 65 minutes gives correct answer .
 
  • #20
Here's what I got:
When the clock is ahead by 27 seconds, the true time is 64 minutes and 21 seconds.
When the clock is ahead by 27.272727272 seconds, the true time is 65 minutes and 0 seconds.
 
  • Like
Likes Vibhor
  • #21
Vibhor said:
OK.

But you said in post#7 that when the clock was ahead by 27 seconds , true 65 minutes haven't passed :rolleyes: .

I think true 65 minutes had passed .The previous post showed how 65 minutes gives correct answer .

Ah. Yes. I apologize. I was wrong to say you were wrong in two ways after that post. You were after all only wrong in one way. You said the false clock shows 3927 (.2727 etc) when the true time is 3900 seconds. That is correct. You then said that that means the false clock gains 27 seconds per hour. That is wrong. As you just showed it gains 27 seconds per 65 minutes not per hour. That is why you got 648 s instead of 604.
 
  • Like
Likes Vibhor
  • #22
Ok :smile:

Thanks a lot Cutter Ketch , Tom , haruspex for your guidance .
 
  • Like
Likes TomHart
  • #23
Vibhor said:
OK.

But you said in post#7 that when the clock was ahead by 27 seconds , true 65 minutes haven't passed :rolleyes: .

I think true 65 minutes had passed .The previous post showed how 65 minutes gives correct answer .

Ah, yes. I apologize. I was wrong to say you were wrong in two ways. You were correct to say the false clock shows 3927.2727 seconds have passed when really only 3900 have passed. Your only error was taking from that that the false clock gains 27 seconds per hour. It actually gains 27 seconds per 65 minutes, and that's why you got 648 instead of 604
 
  • #24
Why I said the same thing twice: I swear I looked and my post didn't show. Now all the sudden after repeating myself they both appear. oh well.
 
  • #25
Cutter Ketch said:
Why I said the same thing twice: I swear I looked and my post didn't show. Now all the sudden after repeating myself they both appear. oh well.
Happened to me many times. :(
 

FAQ: How can I accurately determine the time gained or lost by a clock?

How does Daylight Saving Time affect time lost or gained by clock?

Daylight Saving Time is a practice of setting the clock forward by one hour during the summer months in order to have more daylight in the evenings. This results in one hour being lost in the spring and one hour being gained in the fall.

What causes time to be lost or gained by clock?

The main cause of time being lost or gained by clock is the implementation of Daylight Saving Time or other time zone changes. Natural phenomena such as leap years and the Earth's rotation can also contribute to slight variations in time.

How does time zone affect time lost or gained by clock?

Time zones are based on the Earth's rotation and divide the world into different regions with their own designated times. Changes in time zones, such as when traveling to a different country, can result in time being lost or gained by clock.

Can time really be gained or lost by clock?

Technically, time cannot be gained or lost. It is a constant and universal measurement. However, due to human-made adjustments and variations in timekeeping, the clock may appear to have lost or gained time.

How can I adjust for time lost or gained by clock?

If you notice that your clock has lost or gained time, you can manually adjust it by setting it forward or backward accordingly. Most modern devices also have automatic time setting features that can adjust for time changes, such as Daylight Saving Time.

Similar threads

Back
Top