I have not read the article yet however I am in favor with ending the
contest earlier. On the east coast Sweepstakes ends at 10:00pm. This is
way too late to have dinner with the XYL afterwards and leaves little time
to disconnect the station get things in order for the upcoming work week.
Perhaps it was set up this way because more darkness may help the east
coast score since we cannot really run on the higher bands but we still
cannot compete with the western states. Starting at 1800z and ending at
0000z like other contests would be fine with me.
John KK9A
From: "Ken Widelitz" <kwidelitz@gmail.com>
Date: Tue, 13 Mar 2018 15:48:18 -0700
Al suggests moving the start time up 4 hours. This makes a lot of sense to
me. More daylight hours so guys with a tribander will make more contacts.
Also, perhaps more importantly, East Coast SSers won't have to stay up late
Sunday night suffering the doldrums and more will probably operate later on
Sunday.
Bill suggests shortening the contest to 18 hours. I like that idea but would
suggest shortening it to 20 hours. Bill also suggests a forced off time in
the middle which doesn't appeal to me personally. His last suggestion is to
allow duplicate QSOs on 10 and 160 meters. I don't like that at all as it
makes guys without good 160m antennas uncompetitive. As to 10 meters in down
sunspot cycle years, it will only help where there is the occasional
spotlight propagation and give an unfair advantage there.
Moving up the start time and decreasing overall operating time should have a
positive effect on this contest. Of course, getting the NCCC, PVRC and YCCC
to have a yearly major focus on winning the overall gavel is what will help
the most. A few years ago when they did that there were no doldrums Sunday.
Let the flames begin, and apologies in advance to our international list
members who don't give a hoot about SS.
73, Ken, K6LA / VY2TT
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|