jluttine / bayes-league Goto Github PK

Make it mobile friendly and better looking. And easier to use.

Add multiple players on create player page

• Show ranking history
• Show match history and how the results compare to the expected results

Import and export either players only or both players and matches.

Take into account the number of matches the player has played too.

For a single player: The "effect" of each match to the player's ranking could be shown by using derivatives: The derivative of the log-likelihood of the match result w.r.t. the player's ranking score tells how "strongly" the result is pushing the score to one way or another - or if it's in balance (zero derivative). The derivatives of the matches should sum to zero. The scale is arbitrary so it doesn't tell anything to the user but the relative magnitudes and the sign tell something.

For a match as a whole: Show a measure that tells how much of the probability mass has lower probability density than the actual result. 100% is the most probable result. Maybe values below something like 5% would then be interesting.

Add a possibility for simple authentication. Authenticated users can add players, matches, results etc. Other users have read-only access.

What would be a good authentication mechanism?

• Username and password? A bit heavy. Requires registration and user management.
• Token/passphrase in the URL? It's easy to lose the full-access URL.. Perhaps only registered users can create leagues and they could then have those URLs visible under their user accounts. For now, the site admin would have that access. Or, alternatively, the admin URL is created for a email address and can be recovered anytime by requesting the admin URL as an email to the address given when the league was created.
• Password protection? Easy to give to others and possible to remember. Not very safe because the passwords would most likely be very weak.
• What else?

A league can define default bonus points for winning a period. Also, each stage can override these bonus points.

For instance:

• 0 bonus points for winning a period in calibration stage
• 2 bonus points for winning a period in group stage
• 0 bonus points for winning a period in play-offs

Note: The relevant rankings must be updated when bonus points are modified.

Add a possibility to designate a match into a stage (e.g., group stage round 1, quarter-final stage, semi-final stage, etc).

For each stage, save the ranking so the ranking history can be explored based on stages. ("What was the ranking after the third round?")

Add dependencies among the stages so that a stage can have "parent" stages which means that the matches from those stages are taken into account as well. This way stages can also be independent of each other. For instance, groups A and B can be independent but the rounds within each group depend on the previous rounds:

• Group A Round 1 -> Group A Round 2 -> Group A Round 3
• Group B Round 1 -> Group B Round 2 -> Group B Round 3

Then, a group can have multiple parents so that, for instance, the playoffs can depend on the group stages:

• Group A Round 3 & Group B Round 3 -> Quarter-finals

Is it possible to guarantee that it's acyclic in the database? Perhaps add a custom validator.. But still be prepared to handle cycles without hanging indefinitely.

In the ranking page, one can see the latest overall ranking which shows all players and takes into account all matches. But there should be tabs/links for each stage as well so one can see the ranking of a stage.

Whenever a match is edited or added, all the stage ranking and its child stage rankings need to be updated.

(Or scale scores by 10 so that the magnitude is hundreds.)

If easily possible, use a smaller font for the decimals.

Make it possible to set the match datetime manually. Default can be current datetime.

Add stage deletion feature

Add a button which creates a set of matches based on the current ranking.

Provide:

• Number of players in each team
• Number of matches per player, that is, the number of rounds
• Optional: A phase/stage (e.g., calibration games, group stage games, etc)

Constraints:

• The teams and the players in the teams should be as equally good as possible
• Minimize the number of times a player plays with or against a same player
• The number matches should be the same for all players

Result:

• Matches are created

Add a button for deleting a player in the player editing page.

Add a possibility to delete matches.