Thanks Ward, for the education in New Math. DUMB LID me (self assigned but accurate). I assumed that 60+ minutes was 60+ minutes. I hadn't read the rules, assumed that a "somewhat standard" 30 minute
There's no "new math" involved here. It's simply that the Cabrillo standard only specifies QSO times down to a 1 minute resolution. Look at any of you Cabrillo logs and you will see that. In addition
The trick to contest MATH on the Clock is that the Contest clock doesn't have a second hand. Rex K7QQ Thanks Ward, for the education in New Math. DUMB LID me (self assigned but accurate). I assumed t
Yeah, but why would a neophyte, dolt, lid like me think that two contacts, an hour apart in a log, would NOT beconsidered as being one hour apart? If I subtract 22 hours and 60 seconds from 22 hours
My personal belief is that much of the grief that contesters have with the rules is a desire by some to 'game the rules' - rather than understand the 'spirit of the rules.' The time off in contests i
"Game the rules". Really!?!?!?!? Any reasonable person would assume that after more than 60 minutes have passed, he could make the next contact. Now, of course, we know that the robot isn't too smart
Why do think you have to wait 61 minutes? If you log the last one at x0.59.59 you wait one hour + one second if you log the next one at x2.00.00 and won 59 seconds of operating time the hour before.
I see you understood and if you did not log one in the last minute those 60+1 minutes will not bother you anyway. 73 Peter And if you log the last one at x0.59.00, you must still wait until x2.00.00.
Hans Of course they have to game (rubber) the clock for a few seconds on each end or they lose the 60 min . Or they could just sit for that extra 15 sec then the time will come out correct. Quack "Ga
Rex, I guess my point is this...... Most people consider the passage of an hour as measured by a clock to be "the same minute one hour later", and I think most contesters (without this discussion) wo
/"However we have learned here that the robot doesn't tell time like ordinary folks..."/ Yeah butt... :-) [Theoretically] what if the robot HAS been programmed to allow 12:00 to 1:00 timestamps to qu
It has nothing to do with "the robot". if the mechanics are of interest, this is a consequence of how logs are (and must be) checked when there are no seconds in the time. The robot only checks to be
Or, Cabrillo should be amended to allow for seconds. No, I didn't just say that:) -- Doug Smith W9WI Pleasant View, TN EM66 _______________________________________________ CQ-Contest mailing list CQ-
/"Should this be publicized more clearly?"/ All joking aside, I think the examples you provided are clear enough. To avoid the unwelcome surprises, it would call for your examples to be published whe
However we have learned here that the robot doesn't tell time like ordinary folks, so to be safe we must wait for 61 minutes of elapsed clock time before the next contact. I'm not saying that's good
Calculating the off time taken is a very simple thing to add to a contest logging program. I am surprised most programs don't include it. Tor N4OGW _______________________________________________ CQ-
What I would like to see is that option, or even another one is, say it's a 30 hour contest window, max 24 hour of operating, it posts the time you would have to stop at when you hit the 24 hour poin