An Eddington number is the maximum integer value X where you’ve achieved a value of at least X on at least X occasions. Sounds complicated but it isn’t really. Take my daily bike Eddington number of 131 miles. This means I’ve ridden at least 131 miles on at least 131 occasions. I started out tracking both miles and kilometres together with minutes and looking at numbers life to date and annually together with daily and weekly numbers.
This has now expanded to an ever increasing list as I’ve moved my training diary from a spreadsheet to and database and now in to a proper app. A big part of the fun has been generalising Eddington numbers since they can be calculated for any measure really.
The result is I have the following classifications within my training diary:
- Activity – eg Swim, Bike, Run, Gym etc…
- Activiy Type – eg Road, offroad, squad, openwater, turbo etc…
- Equipment – for the moment I only track which bike was used
- Period – this day, week month, year. But also rWeek (rolling week) rMonth and rYear. I then added in wtd (week to date), mtd and ytd. Finally I included for the week ones that measure starting each day of the week (to see if it made a difference what I chose as the first day of a week – it does!).
- Unit – this is things like KM, Miles, HR, Ascent, TSS etc… As I’ve generalised in my app this now includeds pretty much everything – restingHR, KG, Lbs, FatPercentage, Motivation, CTL, ATL, strain – to name just a few.
I ran this across my diary and found I generated over 10,000 life to date numbers. For each number I also calculated a “+1” value – how many of the next value do I need to advance by 1. I also calculate a maturity measure – I’m still working on this but currently it works reasonable well.
For an individual number I can now generate a full history of how the number progressed, how it matured and each annual number.
I will update the pages here to reflect the new detail and the cool graphs I can now generate: