I was wondering what others do / consider best practice for definition of seasons within intervals.icu for comparing against previous bests / training load etc (on the /power, /fitness, /compare, /totals pages for instance).
I have tended to simply have a season per year, but am thinking perhaps that is not the best thing to do. For instance at this end of the year my power bests and training load are down compared to my bests during the Summer (Northern Hemisphere-er here!), so comparison there is of no real benefit. And come January 1st, it doesnāt really make sense to zero everything as my January efforts will be of interest compared against my recent end-of-year efforts.
Iām thinking it may be better to set up e.g Summer & Winter seasons to compare easier the type of training that I am doing. Perhaps aligned to Spring & Autumn equinoxes? Which would be season changeover at end of March & end of September. But then I may still put some good efforts in during October with the last of my Summer formā¦ so maybe would be better to have unequal length seasons, e.g November - March (5 month winter season) & April - October (7 month summer season). And that would align with clock changes for daylight savingsā¦
On a related note I do have āseason matchā functionality on the todo list i.e. comparing how you are doing now compared to the same number of days into last season.
I have been busy with a lot of data migrations and devops work but thats all coming to an end now. So I should be able to crank out features a bit quicker now.
To your seasons backlog, can I add the ability when defining a season to pick the end date? That is, I should be able to define arbitrary āseasonsā that overlap.
Did a search on āSeasonsā to try and learn how people are using this feature and couldnāt find a solution to my situationā¦so posting here.
I ride road in the Spring/Summer/Autumn and I ride track in the Autumn/Winter/Spring.
For the last 3 years I set up seasons as ā<year.> Roadā or ā<year/year> Trackā (since it overlaps 2 years).
The switchover isnāt that clean though and I end up with road data mixed in with track data in the Autumn and Spring when weather allows me to get outside while still riding road.
I considered suggesting a Season selection with a bike used filter, but Iām not sure that would help as it would not include road data in track season in my power curves/etc. Or vice versa.
Thoughts on how I should set up to keep my road data separate from my track data but keeping my Autumn/Spring season changes? Or disregard my current seasons set upā¦ideas on what might be better?
Thanks @William_Barnes that filter works great! (why did I NOT see that before?!?!)
Just tested it out and Iām able to see my power number based on my track or road bike and iāll just include the seasons I care about.
I may need to rethink my seasons strategy.
There is some training after the last āeventā so Iāll have a few weeks where Iām riding both track and road. More so in the Autumnā¦track season will start late August and road might not end until early November.
Iāll think it over.
