I do not understand why this is such a hard concept to grasp. Page 102 Oct
QST: Morse contest starts at 2100 UTC and ends 0300 UTC. Now if you don't
know how to setup your computer for that then that is a whole different set
of problems, but the starting and stopping times of the contest are very,
very, clear. UTC is UTC there is no DST involved.
Good Luck
73
MAL
N7MAL
BULLHEAD CITY, AZ
http://www.n7mal.com
----- Original Message -----
From: Aldewey@aol.com
To: KI9A@aol.com ; cq-contest@contesting.com
Sent: Monday, September 24, 2007 0:03
Subject: Re: [CQ-Contest] CWSS and daylight savings time
In a message dated 9/23/2007 6:17:13 P.M. Central Standard Time,
KI9A@aol.com writes:
We start an hour later than normal, the way I see it. Am I right?
2100Z during DST is 4 PM local ( central )
2100Z after DST is 3 PM local ( central )
73-Chuck KI9A
The way I understand it, we will start at the same time (3 PM in the
midwest) but then ending time will be one hour earlier on the wall clock
(i.e 8 PM
in the midwest).
My concern is that there are some logging programs out there that may be
set
up to look at the local time in your computer and then work with an offset
to get it to GMT to display in your log. If that's the case, it would seem
like at some time during the weekend (2 AM?) the time would jump back one
hour
and some Qs would be recorded with duplicate times. Also, I'm not sure
what
effect this will have on time off / time on calculation.
By the way, I think I did install the patch earlier this year for the new
DST change but, as I recall, it did not work correctly. I still had to get
up
the next day and manually change the clock.
Maybe this is all transparent and the major logging programs have this all
figured out. I don't recall ever operating a contest on a weekend when the
time changed. I guess I just don't want a surprise in the middle of the
contest.
73,
Al, K0AD
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|