Before: when running the scripts after doing a new data pull, unify_data.py will crash until new teams have been added to teamname_mapping.csv. These are now added manually, which can mean a team renaming can be missed (especially if they are small unknown teams).
Also, in this setup, if one roster is signed by a new sponsor, and a new roster pops up under the old name, this new roster will also be assigned the new sponsor name.
After this is implemented, the following would happen:
new team names are detected and automatically added to the teamname_mapping.csv - to be checked as part of the merge (but without a crash)
in case of a new team name, the roster is compared against existing rosters to see if it might be a team renaming
rosters for existing teams are also compared to make sure changes are checked
For this, two new csvs are added:
rosters.csv, in which for each teamname the most recently found roster and all old rosters are collected
player_mapping.csv, which can allow remapping of playernames that are different for Valve, ESL and/or HLTV
Improvement: detect new teams or updated rosters.
Before: when running the scripts after doing a new data pull,
unify_data.pywill crash until new teams have been added toteamname_mapping.csv. These are now added manually, which can mean a team renaming can be missed (especially if they are small unknown teams). Also, in this setup, if one roster is signed by a new sponsor, and a new roster pops up under the old name, this new roster will also be assigned the new sponsor name.After this is implemented, the following would happen:
For this, two new csvs are added:
rosters.csv, in which for each teamname the most recently found roster and all old rosters are collectedplayer_mapping.csv, which can allow remapping of playernames that are different for Valve, ESL and/or HLTV