srvanrell / ranking-table-tennis Goto Github PK

Revise Readme and package build and upload instructions.

A few ideas to be implemented in the future:

• Number of participants vs tournaments (overall and per category)
• Number of active/inactive players vs tournaments (overall and per category)

Raw rankings have initial tid metadata. Revise.

Create a single command line rtt that call the other scripts as:

• rtt preprocess
• rtt compute-ranking
• rtt publish

Consider adding tests and hooks to improve PEP8 compliance.

Addition date or TID should be included into initial ranking

Multiple run of publish commands should give the same results.

move to a config file

• spanish phrases
• hard written text
• headers

Currently configs are considered fixed during the championship and when it was required, hacks have been added to make changes during a championship. Evaluate an alternative approach to consider these kind of changes, which would allow to reuse configs from one year to the other.

Add it to setup.py for the next deployment

Configs are simple yaml files. That could be replaced for a more elegant strategy like OmegaConf.

As a visual aid, a blank line can be added in published tables where applies the category limit

Nowadays is publishing stats of future tournaments. For example, T03 is showing results for >= T04.

Due that the new site has been published, uploading data to spreadsheets is no longer required (except for tournament sheets)

Show results of unknown player with known players (and their ratings) so it is easier to define the initial rating points

It should check for differences before attempting to update

Currently, database is created locally every time scripts are executed. They could be stored as BigQuery tables, which would enable creation of published sheets much easier and less manual.