etc.
Sender: owner-cq-contest@contesting.com
Precedence: bulk
X-List-Info: http://www.contesting.com/cq-contest-faq.html
X-Sponsor: W4AN, KM3T, N5KO & AD1C
> Now with log checking software, who is going to be the
> first to write it into their contesting software programs
> n6tr, k8cc or k1ea?
Well - truth be known, there are already many shared code segments
between some of the log checking software used and TR Log.
I supposed this puts me in a good position to implement new features
to improve both your log accuracy and your score. The new version
of TR Log to be introduced at Dayton has some interesting new
features:
WORK YOUR FRIENDS = TRUE
This feature takes all the work out of getting your friend's callsigns
into you log. Just make up an ASCII file with their callsigns and name
it FRIENDS.DAT. The program will automatically insert a QSO with one
of these callsigns during a long gap in your log without QSOs. Make sure
you properly use the BREAK TIME command so it won't insert a QSO during
a break. However, if you do this by mistake, you can still use the
RUBBER CLOCK command in POST to fix the times up.
NO UNIQUES = TRUE
This feature is used along with the TRMASTER.DTA file to identify
probable uniques during the contest. These are probably callsigns
you miscopied and ignored the program's suggestion for correct
callsigns. During your off time, the Z80 OP is activated and QSOs
are made with your unique callsigns to ten other stations - thus
making sure they will not be "unique" during the log checking process.
RANDOMIZE SENT QSO NUMBER = TRUE
This feature works with the # character in your exchange string.
Whenever working a station that has a QSO number > 90 percent of
your QSO number, a random QSO number will be sent instead of the
"correct" QSO number. The default is to have the number 100 QSOs
higher than your current QSO number in order to maximize the psych
out effect. Also, the QSO will be removed from their log during
the checking process.
LEVERAGE LAST'S YEAR LOG = TRUE
When TRUE, for every five QSOs you make, an additional QSO will be
logged using a random QSO from last year's log. This has been shown
to increase most scores by 20 percent. Since it is possible you
will work one of the added stations later on in the contest, it is
suggested you also enable the NO DUPES command when using this feature.
NO DUPES = TRUE
If a dupe works you - don't worry - the program will automatically change
the callsign to another active station with a similar callsign. This is
done so that the callsign is different enough that the log checking
software won't be sure it is a busted call - but close enough that you
can defend the QSO in a court of law.
We expect that these new features will put TR Log users in a class
by themselves in the upcoming contests.
73 Tree N6TR
tree@contesting.com
--
CQ-Contest on WWW: http://www.contesting.com/_cq-contest/
Administrative requests: cq-contest-REQUEST@contesting.com
|