Add warning for results inconsistent with a competitor's previous times.

[mckeenicholas]

Currently, WCA Live gives a warning if a result entered is not consistent with the competitor's other times in the round, however, an average that is consistent, yet obviously incorrect (for example entering someone's Skewb times for 3x3) does not give any such warning.

Two possible solutions I propose, with potential drawbacks listed below:

Check the results being entered against a competitor's historical times in the database, and give a warning if it is not within some deviation of their previous results.

• While this is the more accurate option, it would place additional load on the WCA servers, and WCA Live having to verify every result against the db.
• This requires that a competitor has attended a competition to get a "baseline" for results.
• Competitors improving quickly, or who had a bad average at their last competitions would give unnecessary warnings.

Check if a result breaks NR/CR/WR and display a warning if so.

• Not as accurate. A result that is incorrect but does not break any record would not be flagged.

[william-herring]

Why not warn for both of these instances? I feel that this is an important change considering how many incorrect record entries there seem to be.

[jonatanklosko]

We could do more checks, but we need to find a balance. We definitely shouldn't introduce an additional back-and-forth to the server for this. Verifying against current regional records is definitely useful, I believe cubecomps used to do that.

[william-herring]

Thanks for your reply. I don’t think that checking for inconsistencies in competitor results is that important, as most results are double checked after initial entry. However, verifying against records would certainly be a useful change. We don’t necessarily have to make requests to the server every time we need to do this. One solution would be to simply load all current records into browser storage or a cookie when a user first signs in to enter times. Certainly something worth considering.

…

On 23 Oct 2022, at 5:26 am, Jonatan Kłosko ***@***.***> wrote: We could do more checks, but we need to find a balance. We definitely shouldn't introduce an additional back-and-forth to the server for this. Verifying against current regional records is definitely useful, I believe cubecomps used to do that. — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUOUU6RIQTV6JQ5WGQ6EV3WEQWV7ANCNFSM53ZZXWPA>. You are receiving this because you commented.