search

PikaTimer / pikatimer

PikaTimer: An OpenSource race timing application
GNU General Public License v3.0
37 stars 16 forks source link

Backup only read might mess up all the results #49

Open ancadogaru opened 8 months ago

ancadogaru commented 8 months ago

We encountered the following scenario. Using 2 Ultra one setup as main for the finish line and one setup as backup One athlete crosses the finish line at moment x (for example 10:30:00) and it is read only by the backup line, main had a miss.

All good. After a half of hour the athlete croses again in the neiborhoud of the finish line, this time the main ultra reads its chip. His time (10:30) captured by backup will be overriden by the main read (11:00 for example). This will lead to moving him from position 1 in the results to maybe 100...

The time read by main should be ignored if it has a difference of more than .. 10 seconds

segfaultcoredump commented 8 months ago

I'm tempted to mark this one as a documentation issue for the reasons that you cited.

The only spot I use it nowadays is at a start line. I have the runners start on the primary start line, and then cross a 2nd line a few seconds later. I mark the 2nd line as the backup and also skew it by 3 seconds or so (whatever the normal delta is between the two.

At a finish, I do not use the backup option at all. It causes too many issues.