[Cwo] CW Open Cabrillo

[Alan Maenchen]

Sounds great Don!

I agree completely:  The first priority is to get the logs .. in whatever
format we can.
During the summer we will work with the software people to do the best we
can to get it right the first time out (this year), but obviously expect the
unexpected.

BTW,  GenLog and SD both came out with their CWO contest version and both
had real problems. They are correcting now and should be ready for re-test
next week.  The more effort we put into testing up front saves delays and
time (work) later.

73, Alan  AD6E



On Sun, May 22, 2011 at 7:59 AM, Donald R Greenbaum <don at aurumtel.com>wrote:

> Guys
>
> Until we get all the logging programs set I'm not going to even start on
> the collection routines. All I need to do is give the contestants a vehicle
> to dump their files to a database.  I'm not doing any cabrillo verification
> routine. That is beyond my technical ability and we have other volunteers
> who will tackle that this summer.  I think WHATEVER The final cabrillo file
> looks like must be driven by what N1MM, writelog and wintest can provide
>
> Don
>
> By the way I just left the arena after 3 days. The interest is extremely
> high for CWO
>
> Don
>
> Sent from my iPhone
>
> On May 21, 2011, at 12:24 AM, Alan Maenchen <ad6e at arrl.net> wrote:
>
> Don, N1DG will be writing the log submission software, so he should answer
> these questions directly.
>
> Note that I threw that sample Cabrillo format together rather quickly so it
> may be that there is an error somewhere, although several of us have looked
> at it now.  Yes, you are correct: we should add back in "ex2" at the end.
> Might help too if I had chosen a real time and serial numbers more like
> 123.  Also, maybe "name1" instead of "ex1"... but all I did was to copy the
> NA Sprint format and edited out the QTH fields.
>
> My preferences .. and Don can override if he feels the need .. is:
> 1)  Fixed width fields are nice, but not necessary. Fields are separated by
> "white space".
>     That said, columnized fields that are human readable and can be easily
> edited in Notepad++ are really really nice.
> 2)  Names can be mixed-case.
>
> 73, Alan  AD6E
>
>
>
>
>
> On Fri, May 20, 2011 at 2:26 PM, < <k6rb at baymoon.com>k6rb at baymoon.com>wrote:
>
>> Alan, AD6E, is in a much better position to respond that question, Hank,
>> so I've copied him.
>>
>> Rob K6RB
>>
>> > Hi Rob,
>> >
>> > Know you're at Dayton awaiting the end of the world. When you get home
>> > could
>> > you please give Bill the info he needs.
>> >
>> > Thanks Mate!
>> >
>> > KB,
>> >
>> > Hank, W6SX
>> >
>> >
>> > On Fri, May 20, 2011 at 9:16 AM, Willard Myers < <K1GQ at me.com>
>> K1GQ at me.com> wrote:
>> >
>> >> As a contest logger software developer, I need a bit more information
>> >> than
>> >> is supplied in the FAQ, which says:
>> >>
>> >> • Log format should be Cabrillo v3.
>> >> • QSO template is similar to NA Sprint, but without the QTH columns:
>> >> ------info sent----------- -------info rcvd—————
>> >> • QSO: freq mo date time call nr ex1 call nr
>> >> • QSO: ***** ** yyyy-mm-dd nnnn ********** nnnn aaaaaaaaaa **********
>> >> nnnn
>> >> aaaaaaaaaa
>> >> • QSO: 14042 CW 2011-09-20 0000 N5TJ 1 JEFF N6TR 1 TREE
>> >>
>> >> I need to know what string is expected for the CONTEST: record.
>> >>
>> >> I’d like to know whether or not the robot will insist on fixed-width
>> >> fields
>> >> as suggested by the fourth bullet, or will accept space-separated
>> fields
>> >> as
>> >> suggested by the fifth bullet. And, will it accept mixed-case names?
>> >>
>> >> Also, note that the above specification for the QSO record is
>> >> inconsistent;
>> >> I suspect the third bullet should read:
>> >>
>> >> • QSO: freq mo date time call nr ex1 call nr ex2
>> >>
>> >> Can you forward this to the appropriate person?
>> >>
>> >>  Bill, K1GQ
>> >
>>
>>
>>
>  _______________________________________________
> Cwo mailing list
> Cwo at kkn.net
> http://www.kkn.net/mailman/listinfo/cwo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.kkn.net/pipermail/cwo/attachments/20110522/f3d4d9b2/attachment.html