[TRLog] TR-Log
Joe Taylor
joe@puppsr1.princeton.edu
Sun, 05 Dec 1999 20:36:18 -0500
Tree --
I noticed when preparing my log for submission after the CW SS
that the Cabrillo file produced by running POST on the log does
not conform exactly to the format posted on the Web and printed
in November QST. So I made my own conversion program to line
things up in the right columns. Somewhat later, I noted that
messages on the TRLog Reflector suggest that it is not that
critical to have it exactly right.
On the other hand, when I used POST (the one that came with
TR v 6.45) to convert my multi-op K2PT ARRL-160 log to Cabrillo,
I got much bigger surprises. The first few QSOs look like this:
QSO: 1800 CW 1999-12-04 2201 K2PT W4MYA 599 599 Va
QSO: 1800 CW 1999-12-04 2202 K2PT KB1EGB 599 599 Nh
QSO: 1800 CW 1999-12-04 2202 K2PT WF2W 599 599 WNy
QSO: 1800 CW 1999-12-04 2203 K2PT K8OQL 599 599 Wv
QSO: 1800 CW 1999-12-04 2204 K2PT WK2G 599 599 SNj
QSO: 1800 CW 1999-12-04 2205 K2PT AA1K 599 599 De
QSO: 1800 CW 1999-12-04 2206 K2PT K2UG 599 599 ENy
QSO: 1800 CW 1999-12-04 2207 K2PT K1ZM 599 599 Em
QSO: 1800 CW 1999-12-04 2208 K2PT N1RR 599 599 Em
QSO: 1800 CW 1999-12-04 2210 K2PT N4AR 599 599 Ky
Not only are many things in the wrong column numbers, but the
signal report part of the "exchange sent" comes after the other
guy's call, and the section part of our "exchange sent" does not
appear at all.
I made another fix-up program to make the file conform with the
Cabrillo specification, e.g.:
QSO: 1800 CW 1999-12-04 2201 K2PT 599 SNJ W4MYA 599 Va
QSO: 1800 CW 1999-12-04 2202 K2PT 599 SNJ KB1EGB 599 Nh
QSO: 1800 CW 1999-12-04 2202 K2PT 599 SNJ WF2W 599 WNy
QSO: 1800 CW 1999-12-04 2203 K2PT 599 SNJ K8OQL 599 Wv
QSO: 1800 CW 1999-12-04 2204 K2PT 599 SNJ WK2G 599 SNj
QSO: 1800 CW 1999-12-04 2205 K2PT 599 SNJ AA1K 599 De
QSO: 1800 CW 1999-12-04 2206 K2PT 599 SNJ K2UG 599 ENy
QSO: 1800 CW 1999-12-04 2207 K2PT 599 SNJ K1ZM 599 Em
QSO: 1800 CW 1999-12-04 2208 K2PT 599 SNJ N1RR 599 Em
QSO: 1800 CW 1999-12-04 2210 K2PT 599 SNJ N4AR 599 Ky
Is all this necessary? Are you planning to fix POST, or have you already
done so?
My brother (K2PT) and I really like TR-Log -- with the exception
of this minor nuisance, it did a great job for us in the 160m contest.
-- 73 de Joe, K1JT
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html