Find out what went wrong

[TomNaessens]

We should skim through the logs to find the cause of the issue of the missing rounds yesterday and what we can do to fix it (more gyrids, adapt lap-detection algorithm, ...).

[TomNaessens]

So, what went wrong?

…

On 9 Mar 2018 13:26, "Isaura Claeys" ***@***.***> wrote: Closed #164 <#164>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#164 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA32urnzfkK-jwurZqvYhZRlMpymzt-1ks5tcnTvgaJpZM4INv1k> .

[becousae]

Too much wifi hotspots interfering with our bluetooth chips

[TomNaessens]

And what will be done to prevent this from happening again in the future?

…

On 9 Mar 2018 13:30, "benji" ***@***.***> wrote: Too much wifi hotspots interfering with our bluetooth chips — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#164 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA32uoDf1rUi3_WRCJaNLJeogEgrbs2wks5tcnXXgaJpZM4INv1k> .

[becousae]

Don't go to the watersportbaan again

[TomNaessens]

Are there any monitoring tools that notify you when a round is out of the ordinary to catch these faults? Some easy statistacs could go a long way I think 2018-03-09 14:29 GMT+01:00 benji <[email protected]>:

…

Don't go to the watersportbaan again — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#164 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA32ukDEGW3tKB8bRuxE9bBP9L4Hx3Yrks5tcoPMgaJpZM4INv1k> .