Hope things go ok for you aaac. You are probably fitter than anyone on here...All the best DP.
I had an ECG and the doc thinks I am fine.
Cheeky begger said I had the heart of s healthy 80 year old.
I'm going back for another one but this time they are going to give me drugs to make my heart race. I did suggest s magazine or two instead as I am worried about failing tests post our NC victory.
No wonder it hurt a bit!! Good luck with the recovery mate, hope you can get back on the bike soon. I was going to suggest you take it easy for a bit when you do but I'm not sure you know the meaning of that!Sorry chaps but I mentioned I'd be off for a while and doctor has confirmed that I've got an onset of achilles tendon rupture... basically it's tearing away from the bone.
On the plus side it's got nothing to do with gout which thanks to the anti inflammatory pills means i can drink what i like!
If things don't go pop all being well I should be back in a month or so.
I think I may be fighting @bobinski for the best dodgy legs excuses on cyclechat!
I was 58.
I was CTO for an Internet peering company and got to a natural break point, where I felt I had to commit for another 2 to 3 years or decide to step down. I'd really enjoyed the role, but there was a lot of pressure. I was ok with that, as I'd had that for years, but I started to think that you have to go some time, and if you have the chance to go earlier then why not make the most of it, otherwise what were all the years of hard work for?
It did help that I went out on a high. All the things I committed to the Board of the company had pretty much been achieved. There was still more to do, but it was an opportunity for me to go out on a high, and a great opportunity for the guy coming in who replaced me.
Original plan was to do contract work with a friend, but one month after retiring my plans changed. The forks broke on my bike on the A23, just north of the junction with the M23, they went into the front wheel and I went over the handlebars and landed on my head. I ended up in St Georges Hospital for 3 days with a moderate brain bleed.
That sort of put everything into perspective and I had so many trips to doctors to remove stitches and dentists to repair teeth that working wasn't really an option for quite a while.
I've done a couple of jobs for old friends, but I really don't regret retiring. I ride my bike, travel a bit and now we've got a granddaughter, so life is good.
And I can spend hours wondering how Bkool's power algorithms work and why their IT and customer service is so crap!![]()
Martyn's in Rob. Tell him there's still time for him to make the team for the Nations Cup next month.admin martyn who done the DD with us last year just bought a pro 2 and requested to join the league if u could accept him
Martyn's in Rob. Tell him there's still time for him to make the team for the Nations Cup next month.
The only good bit is I have no memory of it at all.You just described my worst nightmare...front fork failure. I've had my share of flying over the handlebars (dog, car door, front brake failure) resulting in spectacular crashes but so far only small bruises.
Martyn's in Rob. Tell him there's still time for him to make the team for the Nations Cup next month.
And I can spend hours wondering how Bkool's power algorithms work
Pondered that in a post session shower many a time and could only come to the conclusion that you won't wash your hair just standing there.
I think it is pretty simple really.
To start with they used a basic algorithm similar to that on 'Bike Calculator' , put in the conditions, weight, slope wind and speed and your watts/torque/therefore resistance should be X.
This displeased folk as when the entered a slope they were confronted by a brick wall.
So they complained
BKool then introduced a bolt on inertia algorithm which was not a very clever one.
What this did was to delay the onset of resistance and/or remove the slope from the calculation for resistance but forget to tell the calculated power. By the time it decided that you were on a slope you were still doing 50kph on a 3% slope so it cleverly worked out that your power must be 3 times more that you were actually putting down and accelerated you up the next 500m before it started coming back to near reality.
Most of us then quickly perfected the 'Pro Sling' and became overnight mountain sprinters.
Well folk, including me, didn't like this.
So they complained.
I can only assume that BKool then, instead of undoing the bolt on, introduced a bolt on on the bolt on to stop the Pro Sling effect which again includes a resistance delay.
And that is where we are today, hit a short incline at speed and your over it at your entry velocity before the delay ends.
The faster you are the longer the lump you can surf (which reminds that I have already forgotten the 'surfing the blue' anomolie).
Basically the script writers are using lazy algorithms that are not properly taking into account your data point event entry conditions and data point current conditions and thier combined effect on the resistance required to simulate real life conditions.
Pondered that in a post session shower many a time and could only come to the conclusion that you won't wash your hair just standing there.
I think it is pretty simple really.
To start with they used a basic algorithm similar to that on 'Bike Calculator' , put in the conditions, weight, slope wind and speed and your watts/torque/therefore resistance should be X.
This displeased folk as when the entered a slope they were confronted by a brick wall.
So they complained
BKool then introduced a bolt on inertia algorithm which was not a very clever one.
What this did was to delay the onset of resistance and/or remove the slope from the calculation for resistance but forget to tell the calculated power. By the time it decided that you were on a slope you were still doing 50kph on a 3% slope so it cleverly worked out that your power must be 3 times more that you were actually putting down and accelerated you up the next 500m before it started coming back to near reality.
Most of us then quickly perfected the 'Pro Sling' and became overnight mountain sprinters.
Well folk, including me, didn't like this.
So they complained.
I can only assume that BKool then, instead of undoing the bolt on, introduced a bolt on on the bolt on to stop the Pro Sling effect which again includes a resistance delay.
And that is where we are today, hit a short incline at speed and your over it at your entry velocity before the delay ends.
The faster you are the longer the lump you can surf (which reminds that I have already forgotten the 'surfing the blue' anomolie).
Basically the script writers are using lazy algorithms that are not properly taking into account your data point event entry conditions and data point current conditions and thier combined effect on the resistance required to simulate real life conditions.
Short version - faster you go, easier it gets
Try telling that to Greg LeMond![]()
I think the failure was the result of baggage handlers