[RTTY] Problem with WAE log upload robot - OM2015TITANIC

[Tom Osborne]

Hi Tim

I think the bigger problem is why the heck does someone use a call like 
this in a contest?

With a call that long, there is bound to be a lot of busted calls as one 
small hit in a call that long has to happen a lot especially in bad 
conditions like we have been having here.  If they send their call 2 or 
3 times, it just takes too long and a lot of time is wasted.

I think if they get dinged, it is their own fault.  73
Tom W7WHY

On 11/18/2015 9:22 AM, Tim Shoppa wrote:
> I had to delete several WAE QTC's (similar to example here of
> OM2015TITANIC) because they overflowed the Cabrillo, causing outright
> rejection of the entire log by the robot.
>
> Unfortunately, the other guy will get dinged for these deletions too.
>
> I would prefer it if the log robots accepted such logs without QSO editing,
> maybe with some diagnostic complaints about individual lines but still
> "accepted". The way it is now, I had to tweak and/or delete lines in my WAE
> log to get it accepted by the robot, and that doesn't seem right.
>
> I think many of the checks the log robots do are useful. For example they
> often re-iterate and have me confirm entry category details on the web
> form, and these checks have been very useful to me.
>
> But especially in light of many contest rules such as CQ WW Rule IX.9,
> which ban all post-contest log QSO corrections, I do not want to have to
> tweak my QSO details, and especially do not want to delete valid exchanges
> denying the other guy credit, after the contest to have my log accepted by
> the robot.
>
> Tim N3QE