The FSTracker collects and processes data from strava and other platforms for the amateur runner. It offers training load tracking such as acute/chronic ratio, REDI and other state of the art methods.
In order to get started, the first step is to set up your strava API access. There are many different tutorials like this one.
The next step is to clone this repo. It is still a work in progress and it is susceptible to change in time.
Once you've set up the Strava API with the correct reading rights you should create a file strava_api/config_strava.json:
{
"client_id": "[YOUR_CLIENT_ID]",
"client_secret": "[YOUR_CLIENT_SECRET]",
"refresh_token": "[YOUR_REFRESH_TOKEN]"
}Note that the token "[YOUR_REFRESH_TOKEN]" is the token with the activity:read_allpermissions form the tutorial.
So far, the pipeline from data acquisition to front is not formalized. It is necessary to run the files strava_api/strava_reader.py, then training_loads/simple_loads.py
and then finally front/landing_front.py.
- Training load evaluation based on Strava data -> So far, ACWR and Redi have been implemented
- Data viz app using dash
- Incorporate Polar/Garmin etc...