What
When getting activities to build a classification model, the API does not return older activities. This leads to an less accurate model if there are few recent activities. Note equipper code doesn't appear to set any time frame on the request, so this might be happening on Strava's side. Equipper should get older activities when there are fewer than 10 usable recent activities build a good model.
How
Try setting an explicit year-old 'after' date to see if Strava will return older activities then. Results should still be sorted so that the newest are returned first.
What
When getting activities to build a classification model, the API does not return older activities. This leads to an less accurate model if there are few recent activities. Note equipper code doesn't appear to set any time frame on the request, so this might be happening on Strava's side. Equipper should get older activities when there are fewer than 10 usable recent activities build a good model.
How
Try setting an explicit year-old 'after' date to see if Strava will return older activities then. Results should still be sorted so that the newest are returned first.