"Eddington Number"

[jefmcg]

Anyone calculate their 2018 Eddington number**? Any spectacular numbers to share?


**I did. It was not a bumper year cyclingwise for me. I am attempting to better it this year. I hopefully will do so well before the end of January. Yup, that bad.

 

[Supersuperleeds]

My 2018 number was 68.

 

[jefmcg]

I'm liking that, despite your 2018 number being greater than my lifetime one.

 

[Supersuperleeds]

Oops, I lied, I've just double checked and it was only 67.

My Km equivalent was 100

 

[jefmcg]

Oops, I lied, I've just double checked and it was only 67.

My Km equivalent was 100

No more likes for you!

Glad you had a good year cycling. I kinda, maybe getting my mojo back.

 

[ColinJ]

Anyone calculate their 2018 Eddington number**? Any spectacular numbers to share?


**I did. It was not a bumper year cyclingwise for me. I am attempting to better it this year. I hopefully will do so well before the end of January. Yup, that bad.

I hadn't noticed that the calculator can do limited intervals. I'll track my annual totals from now on, as well as the lifetime number.

Hmm, I get an error for 2013 - "Data column(s) for axis #0 cannot be of type string". 2010-2012 are okay, and so are 2014-2018.

 

[13 rider]

Mine was 51 for 2018

 

[jefmcg]

I hadn't noticed that the calculator can do limited intervals. I'll track my annual totals from now on, as well as the lifetime number.

Hmm, I get an error for 2013 - "Data column(s) for axis #0 cannot be of type string". 2010-2012 are okay, and so are 2014-2018.

Thanks. Can you screen shot the error? I suspect it's the graph that's the problem, a screen shot might clue me in.

 

[StuAff]

True Eddington up another one to 105, 15 more to get to 106, it's now starting to get really hard

That particular hamster wheel is rather nasty, isn't it? Mine has been stuck at 101 for a while. 5 rides of 102+ to get to that, 20 to get to 103...I CBA to keep finding extra mileage on every ton, so it'll go up when it goes up, or not..

 

[ColinJ]

Thanks. Can you screen shot the error? I suspect it's the graph that's the problem, a screen shot might clue me in.

I've just realised what the problem is...

I logged rides in the first half of 2012 and then developed a DVT/PE which kept me off my bike for 8 months. Even when I started cycling again I didn't log another ride until January 2014.

When I look at the figures for 2012, there is 6 months worth of ride data to play with and the data is available again in 2014. I didn't log any rides in 2013. The software correctly gives me imperial and metric Eddington numbers of 0 for 2013 but complains bitterly when trying to plot a chart of nothing!

 

[Supersuperleeds]

That particular hamster wheel is rather nasty, isn't it? Mine has been stuck at 101 for a while. 5 rides of 102+ to get to that, 20 to get to 103...I CBA to keep finding extra mileage on every ton, so it'll go up when it goes up, or not..

I had a full on effort last year to get it up to 105 but this year I'm of the same opinion of you, I'm more interested now in getting to 200 imperial centuries then getting the Eddington up.

 

[jefmcg]

The software correctly gives me imperial and metric Eddington numbers of 0 for 2013 but complains bitterly when trying to plot a chart of nothing!

Ah, thanks for the analysis. Definitely a bug, but one - to borrow a phrase from @StuAff - I CBA fixing for now.

 

[13 rider]

Finally got to 70 this morning , 4 more for 71

 

[13 rider]

Today's ride took me to 71 ,9 more for 72

 

[Soltydog]

I'm now upto 78, 1 of 79 to move up again, so that should be soon 6 of 80miles to move again & 8 of 81 or more, so reckon that'll be the end of the year if I complete the century a month challenge 41 rides of 100 miles to move up to the magic 100, so that may be a year or two away