VA2UP
User
Platinum Boarder
| Posts: 1008 |   |
Karma: 6
|
Re:BARTG SPRINT 75 - 2011/10/17 21:44
Le mystère est maintenant résolu.
La réponse que j'ai eu de John est que leur logiciel de correction pourrait faire une certaine confusion avec le Cabrillo en zigzag comme Louis l'a bel et bien mentionné. Voici en pratique ce que John dit:
Hi Fabi,
The problems are the same in the Sprint75 and the HF RTTY contests, with the same stations.
It's not a bug in our software. It's the lousy N1MM that you are all using!
Cabrillo logs depend on having all the right data at the right place on each line of the log. Your software doesn't do this correctly. After the received callsign it leaves a couple of spaces then writes the serial number received. It should write the callsign, move across the line and put the serial number in the right position. So if you get a 3 or 4 character callsign the checking software thinks that the serial number is part of the callsign received. K0BX comes out as K0BX 005 and that's a bad call.
I have attached your corrected log ... if you compare it in a text editor with the original you will see what I mean. Also attached is your UBN file. There is a similar problem with the HF contest logs where the character positions are incorrect.
Veuillez pardonner John pour l'insulte à N1MM ha ha il n'est pas mechant, seulement getting a bit grumpy ha ha I love the guy!!
Alors ceci dit j'ai naturellement interpelé le groupe N1MM et expliqué le problème. Le fix est des plus simples. Voici ce que Bill w6wrt nous dit:
Change your font to either Courier New or FixedSys.
Et si vous aimez la lecture voici ce que Ed W0YK nous dit:
Neither ARRL nor CQ contest managers nor their robots nor log checking
software require columns to be lined up in a Cabrillo log. The delimiter
between fields, e.g., frequency, mode, date, time, call, each exchange
element, etc., is simply "white space" or the presence of one or more Space
characters.
However, since many log formats in submitted logs are incorrect and must be
edited by the log checkers before log checking can begin, having the columns
lined up is immensely helpful. If columns are not lined up, then we usually
have to do so manually in order find problems and easily correct them with a
column editor. For example, if '599' is missing from all QSO lines, it is
trivial to add it to a 3000 QSO log with a column editor. But, if the
columns zigzag, then adding '599' to each QSO line is horrible punishment
for a volunteer. ;>
That said, I see very few logs, less than 0.1%, where the columns are not
perfectly aligned. Certainly, all the Cabrillo files emanating from N1MM
Logger that I've seen are perfectly lined up.
As a couple other replies have indicated, the columns might not seem to be
lined up if you are using a proportional font. Change to a fixed-space font
and I bet you'll find the alignment to be fine.
Note that the official Cabrillo specification shows the precise character
position for each element in the QSO line. There is a lot of space for
calls because some can be rather long. Thus, for most normal 4-6 character
calls, there is a lot of white space between them and the next element,
usually '599'. I 'd guess that most software authors follow this spec. In
practice, though, I'm not aware of any contest or log checking software that
pays attention to the precise character position. The elements are parsed
based on the Space character (one or more) as the delimiter.
Finally, regardless of what a particular logger outputs as a "Cabrillo
file", the file is a simple text file that can be edited with any text
editor that doesn't add any funny control characters or other artifacts to
the text. Most common editor meet this requirement. For contest logs, a
particularly useful text editor is Crimson Editor, a freeware editor that
can be toggled into and out of column mode by Alt-C while one is editing.
Depending on the editing operation, column mode makes sense (example above)
or regular line mode makes sense, e.g., editing multiple lines in the
header.
Alors j'espère que tout cela vous sera utile et les problèmes de Cabrillo dissipés.
Maintenant les VE2 ont repris leur place réspective dans le résultat final du Sprint 75 et comme je l'aurais souhaité je félicite Claude pour une superbe performance!!
On peut revoir sous un autre oeil maintenant @:
http://www.bartg.org.uk/documents/Contests/sprint75/Sprint75%20April%202011%
20results.pdf
73, Fabi
|
Forum
. Félicitations Claude pour ton superbe score et Fabi pour ton bel effort hihi!!!