djong1 / gp3s

gps-speedsurfing and more
6 stars 1 forks source link

Script to Rebuild in 2022 Dunkerbeck Speed Challenge “The Summer Edition” (748) #18

Closed jhdebruin closed 1 year ago

jhdebruin commented 1 year ago

Based on the very handy python script from @logiqx this entries have to be rebuild in the event 748, @djong1 could you please make a small script for this ? All other events have been rebuild manually already :)

44 / 439 users need a rebuild in 2022 Dunkerbeck Speed Challenge “The Summer Edition” (748): Kai Kaufmann (16746) - speed_250, speed_500, speed_100, speed_10sec, speed_mile, speed_avg Christopher Tyack (22404) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Tor Kjell Grytnes (22817) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Konstantinos Palogos (23998) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Jorgen Dyblie (23206) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Torbjörn Hellström (23334) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Kristian Grytnes (23632) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Will Trossell (2911) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Sven Hulst (23299) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Pavlos Kapsianis (24816) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Jorrit Bonnema (22388) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Markus Lindman (5423) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_avg Marco Düwell (26365) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Ingolf van Oostveen (3874) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Bert Bodde (20514) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Alwin Visker (15697) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Mandy van de Hoef (23463) - speed_250, speed_2sec, speed_100, speed_10sec, speed_avg Ove Jansson (4642) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Alberto Marugan (25183) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_avg Chris Platt (25193) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg René Bijmolt (21711) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Jüri Kaldoja (4497) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Fons van den Hove (24311) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Phil Noden (2708) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Olsson Orjan (18230) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Frank Heinen (82) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Tore Hvideberg (25617) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Nicole Skodda (6348) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Lianne Hofstee (26179) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Hans Prins (5376) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Magnus Bengtsson (2046) - speed_250, speed_500, speed_hour, speed_100, speed_10sec, speed_avg Anders Bjorkqvist (2558) - speed_mile, speed_hour, speed_avg Dylan de Jong (53) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Arne Noer (24403) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Edwin Buruma (23550) - speed_250, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Peter L Rasmussen (26059) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Robert Baas (19409) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Thomas Moldenhauer (24163) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Hans Kreisel (2042) - speed_250, speed_500, speed_hour, speed_100, speed_10sec, speed_mile, speed_avg Regis Lesieur (22394) - speed_250, speed_500, speed_hour, speed_2sec, speed_100, speed_10sec, speed_avg Deyan Gospodinov (26011) - speed_250, speed_500, speed_2sec, speed_100, speed_10sec, speed_mile, speed_avg Hannes Rieger (24349) - speed_250, speed_2sec, speed_100, speed_10sec, speed_mile Saar Schuling (25189) - speed_mile, speed_hour Mateusz Kasprzak (25524) - speed_hour

Logiqx commented 1 year ago

Prettier report now hosted on GitHub - https://logiqx.github.io/gp3s-query/events/748.html

djong1 commented 1 year ago

@Logiqx please advise. You have created a great script to discover mismatches however I do need some additional help to understand what is wrong in the ranking:

Eventranking:

image

Rider session:

image

Rider sessions:

image
Logiqx commented 1 year ago

@djong1 - After re-running my reports the problem has now disappeared as the rankings have been updated.

I received the session details from the API around 5 hours ago but the rankings (main website and API) only updated within the past hour.

Either the rankings updated automatically or maybe @jhdebruin did a manual fix in response to my comment on #17.

jhdebruin commented 1 year ago

sorry for the disturbance, i actually did a manual rebuild for this one less than an hour ago 🙃 but was disturbed and forgot to comment this

Logiqx commented 1 year ago

@jhdebruin Thanks for clarifying. Good to have an explanation as opposed to it being a mystery!

Something worth bearing in mind with my script is that immediatley after a session has been posted (but prior to the rankings being updated) , my script has the potential to report a discrepency, if I just happen to run it at that time.

I might enhance the script to ignore newly discovered sessions (up to 1 hour after first discovery) to avoid this scenario.

djong1 commented 1 year ago

@Logiqx Jan hendrik confirmed that he did not rebuild the Dunki event, however I see the same thing:

image image
Logiqx commented 1 year ago

@djong1 That session is not associated with the Dunkerbeck event.

image

I've now improved the message to say "These rankings do not have a session associated with the event.".

djong1 commented 1 year ago

To give you a bit more insight: we are currently in the transition from 1 to 1 relations between session and event to 1 to many. To give users the opportunity to attach the session to multiple events. We do this first for the events rankings and for events that run on global or country level. We do that in coexistence to slowly transition (in a controlled manner) towards this new model. In the end: the event name will be removed from the session detail page, once a user is subscribed to an event his session will be automatically added to the event, the event selection will be removed from the add session page when posting.

This change will also affect the api in the end. We use a newer api version already for the web front end and when fully transitioned we will enable this one also for external use. We need some internal api operations during the coexistence phase.

So my concern is that with this change we do not introduce new problems and make sure that old bugs are removed before transitioning. So your help is very valuable. Your data sparked also an idea to change the architecture a bit to overcome these issues by design. But first things first.

Logiqx commented 1 year ago

To give you a bit more insight: we are currently in the transition from 1 to 1 relations between session and event to 1 to many ... Your data sparked also an idea to change the architecture a bit to overcome these issues by design. But first things first.

Cool. Thanks for the insight.

jhdebruin commented 1 year ago

@Logiqx I've done a rebuild of the Dunkerbeck Event, if all is ok we can close this issue...

Logiqx commented 1 year ago

@jhdebruin Very close with the DSC.

2 user rebuilds outstanding.

image

jhdebruin commented 1 year ago

This specific action is closed, new open issues will be collected in #15