Kepler Challenge – 10 Things That I Wish I Knew

Here is a quick wee list of things that I didn’t know going into the race – and that will have an impact on how I approach the event next time around.

1. The gear check at the top of Mt. Luxmore is very efficient.I expected to be standing around waiting for ages whilst a large group of runners in front of me had their gear checked. I expected that this process would take around ten minutes, and that I would have to do various stretching exercises etc whilst I waited.The reality was very different. There were at least ten people checking gear, and they did their job very efficiently. I queued for less than a minute before my gear was checked. The queue was alongside food and drink tables, so I was able to get plenty of nourishment whilst I waited. The gear check itself was very fast. The entire gear check process, including queueing, took just over two minutes. Brilliant.
2. Food at the checkpoints is pre-cut.
   
   As silly as it may sound, I was worried about how I would eat the bananas/oranges provided at the checkpoints. I mean – do I peel the banana there and then? What if I struggle to remove the peel from my orange due to having cold fingers? What do I do with the peels once I have finished – do I just throw them on the ground?The good news here (for me at least) is that all bananas are but in half, and all oranges are but into bite-sized segments. This may seem like a small thing, but it saved so much time at each checkpoint. This in turn meant that I ate at every checkpoint, which helped me to take on board the fuel that I needed to finish the race.
3. Yes, there is snow – but the trail is groomed. The wonderful people at the Department of Conservation had been working hard in the days leading up to the event. They had cleared the snow from the track, meaning that we had only a very small amount of snow trekking to complete. Snow is a fickle thing, and there is guarantee that the trail will be this clear next time around – but I did not get wet feet, and I did not get frostbite on my toes
4. Mt. Luxmore is not very steep. Seriously. It isn’t. I could have run up the entire thing (and would have, had I not known that there was another 35km to go after reaching the top!). The hills that I ran during my training programme were considerably steeper. – they just weren’t that long. This actually presents  a problem – the vast majority of people were walking up the track, and I felt like I should have been running up the hill. In the end I compromised by running for a minute, then walking for a minute. This allowed me to make some good time without totally thrashing my legs. Which leads me to my next point….
5. Running down Mt. Luxmore thrashes your legs.
   
   I run downhill a lot. I consider myself to be a good downhill runner. But I am used to downhill stretches of  a couple of kilometres, dropping maybe 350 metres in altitude. The run down from Mt. Luxmore was a distance of 7.3km, and a drop of 1,100 metres. It felt brilliant at the time, so I was fairly hammering it downhill. I still felt good once I reached the flat too. But about 5km later, my legs crashed on me. From that point on I was reduced to a slow jog, well below my usual slow running pace. Next time I will still run down Mt. Luxmore, but I will keep the pace under control to conserve my thighs for the long run out to the finish line.
6. There aren’t a lot of toilets on the course.
   
   Fortunately, this wasn’t an issue for me on the day. But if you are a runner that needs frequent toilet breaks, keep in mind that the huts/emergency shelters etc tend to have a single toilet only. The start line was well equipped with portaloos (ten or so), so nervous runners waiting to start the race are well catered for.
7. It was cold when I started, and hot when I finished. I’m not of the exact temperature when the race started, but it was cold. I wore a hat and a pair of gloves for the first 45 minutes of the race.  I warmed-up pretty quickly going up Mt. Luxmore, was chilly again on the ridge line between Mt. Luxmore and Hanging Valley Shelter, and got pretty sweaty on the descent down to Iris Burn. By the time that I hit the long, flat run out beyond Iris Burn it had developed into a hot day. It got up to around 24 degrees in the afternoon.
8. Drinks are dispensed in cups, not from a tap.I was hoping to see big drums full of Leppin that I could quickly use to fill up my camelbak. Maybe I missed them, but all that I saw on the course were half-full cups. This was fine if you just wanted a quick drink, but was a real pain for refilling a hydration bladder. You needed to take several cups, and pour them in one at a time. Next time I will take my camelbak and a drink bottle. I will refill the drink bottle at the drink stops, and use the hydration bladder between the checkpoints.
9. I’m a runner, but I spent a lot of time walking.Going into the race (my first ultra), I was confused as to when I “should” be walking/running/whatever. I had a target time of eight hours and managed to finish twenty minutes inside that mark. I was surprised when I checked my Garmin Forerunner log after the run – I had actually spent nearly two hours of the race walking. Breaking it down further, I walked for 9.75 of the 60kms. Not all in one go of course, but little uphill sections spread throughout the course would slow me down to walking pace. Two hours of walking is much more than I anticipated doing – but I still comfortably beat my target time. I guess that the lesson here is that walking in an ultra is not a crime, and you shouldn’t feel guilty doing it.
10. Talking to those around me helped to confirm my pace.I had a target time of eight hours for the event, but as I had never done the race before I had no idea of whether I was “on track” to meet my target. The solution was all around me – other runners.  A large number of entrants had completed the event in previous years. They were all friendly, and they all were happy to have a quick chat on the course. As I was chugging up Mt. Luxmore I was concerned that I was runing whilst many others were walking. I was keeping pace with another chap that was also running – so I asked him if he had done the event before, and if so what was his previous time. He replied that he had done it twice before, and that both times he completed it in just under eight hours. This immediately reassured me that I was doing the right thing, running at around the right pace, and that if I kept a rough pace with this other runner I should be in goopd shape to meet my target time.

Read Full Post »

Kepler Challenge – Completed!

Well – that was fun.

Last weekend I successfully completed my first Kepler Challenge. I had two aims for the event:

1. Finish in under eight hours.
2. Finish within the top half of the field.

I was delighted to achieve both of those aims. My finishing time was 7hrs and 42min, which put me in 119th place. That put me within the top third of the field, well above my expectations.

Here is a photo of me on the course (click to enlarge):

Here is the elevation profile from my Garmin Forerunner (click to enlarge):

Finally, here is a link to the GPS record of my run around the course. You can load it into your preferred GPS application (I strongly recommend SportTracks). This will allow you to analyse the course, see where I ran/jogged/walked/crawled, and even view the terrain via GoogleEarth. Please note that you will need to rename the file from Kepler2009.doc to Kepler2009.gpx once you have downloaded it (sorry, but I had to rename the file to a .doc before I was able to upload to this blog site).

Kepler2009

Read Full Post »

Kepler Challenge – The Big Training Run

Saturday morning saw me undertaking the biggest challenge of my training programme for the Kepler – it was time to do The Big Training Run. This run was the peak of my training regime – the longest run that I would undertake prior to the Kepler itself. It represented the ultimate test of the training effort that I had put in over the past few months – it would leave no doubt about my ability to complete the Kepler Challenge.

I was looking to run a distance of 50km. This was further than I had ever run before – effectively my first ever ultramarathon. I had also decided to build-in a significant amount of climb, so that I could test my ability not only to go a long distance, but also to do so with legs weary from grinding uphill. My course took me across the Belmont Regional Park’s Pukeariki – twice. It involved two significant climbs at either end with undulating ridge runs in between – a total of 2,000 metres of climb overall.

I treated this run as a full dress rehearsal for the Kepler. I wore the clothing that I intend to wear on the day of the Kepler. I carried a full pack, with all of the compulsory safety gear that I will be carrying on race day. I was out of bed at 4:45am, ate a full breakfast, and hit the track at 6am on the dot.

Running at such an early time is quite different to my normal routine. My long training runs normally start after 9am. I was surprised at just how different the run became due to the time factor – my time spent on the tops of the ridges was much colder than I had previously experienced. This tells me that I will most likely need to add a second layer of clothing during the ridge section of the Kepler – the wind coming off the snow will be very cold on clothes that are drenched in sweat following the climb up Mt. Luxmore.

The other surprise was how much less water I needed to take in. With the heat of the day yet to make an appearance, the first leg of my run was considerably less demanding than I was used to. This revelation has helped me to realise that I will not need to carry as much water as I was expecting to on the first few  legs of the Kepler Challenge. All good knowledge to have when faced with running up a mountain track – weight carried = effort expended!

At the halfway point I met my wonderful wife Sarah and son Ryan. The re-filled my hydration pack and feed me up on two bananas. I then turned around and headed back to where I had started. This second leg was much more difficult than the first one had been. The sun was now out and the hills were suddenly very demanding. I religiously stuck to my routine of Leppin Squeezys every 45 minutes, five gulps of Leppin Refuel drink every ten minutes, and four Jaybees jelly beans every twenty minutes. It is important to get into a good routine for hydration and feeding – if you run out of fuel on the course you are in for a long, painful day!

I eventually crossed the finish line at Dry Creek. I was feeling surprisingly good – I did not hobble across the line, nor did I collapse on to the ground. To be certain, I was very tired and relieved to be able to stop running, but I also knew that I could have continued on if I had needed to. This has put me in a very positive frame of mind regarding the Kepler – I now know that I have what it takes to complete the Challenge without the need for a helicopter intervention!

My total time was (disturbingly) six hours, six minutes, and six seconds. With 2,000 metres of climb, and 50km under my belt I feel that I should be able to achieve my target time in the Kepler (I am aiming to go under eight hours).

Read Full Post »

Kepler Challenge – Getting up in the snow

Had a fantastic training run on Saturday. Armed with my new-found knowledge of the Kepler’s course, I sought-out a realistic venue for some serious training action. I made my way to Masterton, about an hour and a half from Wellington, and had a stab at the Mt. Holdsworth-Jumbo loop track.

The course itself was excellent – a bit more rugged than I expect the Kepler to be, especially nearer the top of Mt. Holdsworth. I struck snow at 900 metres (good practice as I expect snow on the Kepler as well). I carried on up Mt. Holdsworth as far as Powell Hut (1,200 metres) before deciding to turn back. The snow was deep on the ground which meant slow progress. Visibility was around 100 metres, and I was on a track which was new to me (I was running alone). The responsible/clever thing to do was to turn back, so I did a swift 180 and headed back down the mountain. Once at the bottom again I veered left and headed up the other side of the loop track, towards Jumbo hut. This helped me to build the distance of the run up to my desired 42km. By the time I had finished it was brilliant blue sunshine overhead. I had crossed multiple wire suspension bridges and seen some truly stunning native bush. A brilliant day.

All in all – this was a very successful training run. Total time for this rather demanding marathon was 4:56, which is about where I need to be if I am to achieve my target of a sub-eight hour Kepler Challenge. The terrain and climb was similar to what I am expecting on the Kepler, and I think that I am finding the right balance of running/walking the ascents. I am feeling good, and although I was fairly stuffed at the end of the run I am growing in confidence regarding my ability to actually complete the Kepler Challenge and live to tell the tale!

Here is an elevation vs. Distance from the training run (click to enlarge).

Read Full Post »

Kepler Challenge – Know Your Enemy

A big part of training for any event is trying to replicate actual race conditions. In an ideal world this means training on the event course itself – but for the Kepler Challenge this is not really an option.

Fortunately for me, the internet is a many wonderous thing – I managed to find a GPS file from a runner that has done the Challenge in a previous year. I was able to download the file and load it into the brilliant SportsTracks application for analysis.

By examining the GPS data I was, for the first time, able to see just how hard the Kepler really is. The GPS data forms a complete record of the runner’s experience on the Kepler – how long it took them to complete the run, how much of the track was uphill, how steep it was, even the pace at which they were running various parts of the track. This is all very useful information, and has proved invaluable to me both in terms of planning my training runs and measuring my progress.

The runner took seven and a half hours to complete the course. This is faster than my target time (eight hours), but close enough for me to set some goals around where I want to be on the course after certain time periods. It also answered my main question regarding the race – “if I walk up Mt. Luxmore, will I be the last person to finish the event?”.

The GPS data told me that the runner walked almost all of the ascent up Mt. Luxmore. In fact, he/she walked at several points in the race. This was a revelation to me, as I was worried that I would need to run all of the course if I was to meet my eight-hour target. Using SportsTracks I was able to see all of the points on the course where the runner slowed down to walking pace – at times they were going as slowly as 19 minutes per km.

Here is a profile map of their run – elevation versus distance (click on the thumbnail for a bigger version). It’s just one of a host of graphs that you can use to help plan your assault on the Kepler using SportsTracks.

Read Full Post »

Kepler Challenge Training – Week Six

Okay, now it is getting tough.

Week six of training and the kilometres are starting to add-up. The week consists of the following:

• Monday – 20km flat run (from Avalon to Wellington).
• Tuesday – 10.5 km hill run (from the waterfront up to the Brooklyn wind turbine, return).
• Wednesday – 20 km flat run (from Avalon to Wellington).
• Thursday – 8km flat run (around the Wellington waterfront).
• Friday – Rest.
• Saturday – 30km hill run (1,100 metres of climb, spread across Belmont regional park).
• Sunday – 6km flat run (Hutt river trail).

That’s 94.5km for the week, with approx. 1,500 metres of climb. And it only gets bigger from this point on.

*sigh*. I am finding it pretty tough. I invested in a pair of “skins” compression tights a couple of weeks ago – this after sneering at them for the past two years. But I was so achy in the legs from all of the training, I was willing to try anything. The good news is that they appear to work (I only wear them as a recovery aid – God help me if I ever decide to wear them on a run).

Compounding the issue is my (delightful, much-loved) son Ryan. He is suffering from a virus at the moment and is constantly waking during the night. Poor wee thing – he is only 20 months old, and he gets very upset when he wakes up. It is hard to be reasonable when you are waken up at 11:30pm, 12:30am, 1am, 2:15am……….and it is that much harder when you are suffering from a big run and know that you have another 20km to cover the next day. I found myself in the unenviable situation of trying to convince Ryan to go back to sleep at 2:30 in the morning, knowing that I had to hit the road on a 20km run into work at 6am that day.

Long-suffering wife pointed out that it could actually be an advantage - training in a fatigued state – but I am not sure that I follow her logic!

Read Full Post »

Xterra Belmont

Kepler Challenge training has really stepped-up this week. It started on Sunday with a cool event, one of the XTerra trail running series.

The course was in Belmont Regional Park, Lower Hutt. There were three courses on offer (short, medium, and long). All three were challenging. I opted for the long course – 19.5 km of single track, farm roads, and stream crossings. Satellite image and elevation graph below (click to enlarge):

The course was in excellent condition considering the recent rains and most people on the track had a smile on their faces. There was some serious grunt up to Belmont Trig, and the final climb up some un-even steps demanded a lot from tired legs. I’m impressed with the organisation of the XTerra events – these guys seem to listen well to feedback as each event that they host is an improvement on the previous one.

The next morning (Monday) saw me running 20km into work. Nice flat run, with a good tail-wind to help me along. My legs were surprisingly fresh but my shoulders were stiff from the previous day’s efforts. Today (Tuesday) had me running up to the Brooklyn wind turbine. A decent climb but again I took my time and the legs came through without too many complaints.

It is a good feeling to get through three tough runs in three days. I think that I have reached the point where the training is not such a struggle anymore, and I am feeling stronger than I did in those first few weeks.

Read Full Post »

Kepler Challenge – Running Gear

I’m a firm believer that in order to run the race you need the right gear. Having the right equipment for a given event means:

• Increased chance of finishing the event.
• Increased comfort during the event.
• Increased motivation during training.

The Kepler Challenge is a demanding event. As such it requires more specialised equipment than what I have used in the past. Here’s a list of the gear that I am using, both for training and for the race day itself.

Trail Shoes – North Face Rucky Chuckys

Rucky Chuckys

I wear my Rucky Chuckys on my long, hill-based trail runs. I also intend to wear them on race day. The Kepler is a trail-running ultramarathon. Whilst the Kepler track itself is very well maintained, the tracks on which I train are not. I need a shoe which gives me great grip on soft clay and mud, performs well on gravel farm tracks, and won’t hurt my feet on sealed-road sections. The Rucky Chuckys fit the bill perfectly, and as an added bonus they are specifically designed for ultramarathons. They have tremendous grip (considerably better than the Teva X1-Racer and IceBugs that I have used previously). I have heard that if the conditions are dry some Kepler competitors run in their normal road shoes. I’m going against this trend as I believe that the added grip of the Rucky Chuckys will allow me to run down Mt. Luxmore’s steep inclines with added confidence and control – thus reducing the drain on my quads.

I visited a podiatrist prior to beginning my Kepler training to get professional advice on shoe selection. I strongly recommend that anybody considering a serious training commitment do the same – his advice was very helpful.

Road Shoes – Brooks Adrenaline GTS

Adrenaline GTS

I have been running in Adrenaline GTS shoes for the past five years. I have been through five pairs of these shoes and I expect to go through several more in the years to come. They are very comfortable, offer a smooth ride, and give me all of the support that my feet need. Whenever I run on sealed roads (or on flat, dry tracks) I choose to wear my Adrenalines.

Watch – Garmin Forerunner 305

Forerunner 305

I have been using my Forerunner for the past two years and can honestly say that of all of the gear I use it has had the most dramatic effect on my running. To be able to accurately measure all aspects of a training run – how far, how fast, how hard I worked, how high I climbed – it has been a huge boost to my motivation and to my ability to stick to a training programme. It is also my dearest friend towards the end of any long or difficult runs. Being able to see exactly how far there is to go until the finish line is very important psychologically. By the same token, knowing that you only have another 50 metres of climb before you reach the top of that huge hill makes a world of difference when you feel tired. Finally, being able to track and measure my progress by viewing the GPS recorded history of my running is tremendously satisfying.

The Forerunner is also a heart-rate monitor. Running with a monitor allows me to stay within a given heart-rate zone. This in turn helps ensure that I avoid over-training. The use of the monitor is essential to being able to follow my training programme correctly.

Simple rule for me – if I am going for a run, regardless of length, I take my Forerunner with me.

Running Bag – Modified Kathmandu Nucleon 15L

Nucleon 15L

Bags are often a last-minute consideration for runners, but this is a big mistake. Finding a bag that works for you, both in terms of comfort and convenience, is crucial to a successful run. I do all of my long training runs wearing the bag that I will use on the Kepler. This way I get used to wearing the bag in race conditions, and I notice all of the little annoying things that magnify on race day into virtual torture devices.

For example, my Nucleon is an excellent fit, and very comfortable to wear on short runs. But I noticed that when I wear it for more than a couple of hours, and when I am sweating a lot, it started to rub against my shoulders and the middle of my back. By the end of a three hour run I was rubbed raw, and I had a serious problem. By identifying this early on during my training, I was able to make some adjustments and improvements to the bag. I now have sections of polar fleece sewn onto areas of the bag so that the rubbing effect is mitigated. I know which areas of my shoulders and chest need to have lubricant applied to them to reduce chaffing.

Other small modifications that can improve comfort/preserve sanity include trimming the ends from your bag’s straps. I adjust the straps to get a good fit (with all of my gear inside the bag), trial the fit for a couple of long runs, then cut the excess strap material and melt the end with a match (to prevent fraying). This approach prevents the Chinese water torture effect of overlong bag straps whacking the side of the bag as you run.

It is not only comfort that can be improved by adjusting the bag during training. I have made several modifications which improve its usability, making it more convenient for me during long runs. The bag has several external pockets which are designed to take food/energy bars etc. But I found that they were too snug for my Leppin Squeezy bottles, requiring too much effort to remove the bottle when I get tired. So I added two neoprene pockets to the top of the shoulder straps. These are the perfect size for my Leppin, and double as a convenient place to keep my iPod during training runs. This also means that I can use the external pockets for other items which I previously needed to keep inside the bag.

I also found that my hydration bladder would sag when the liquid volume fell into the bottom third of its capacity. This would have the irritating effect of cutting-off the flow of the liquid, which resulted in me having to reach around to the back of the bag and press the bladder upright so that I could take a drink. We added a small hook at the top of the bag’s hydration pocket, and suspended the bladder from it. This keeps the bladder fully extended no matter how little liquid is in it – problem solved.

Read Full Post »

Kepler Challenge – Training Programme

Putting together a training programme for the Kepler Challenge was a bit of a journey into the unknown for me. Over the past six months I have trained successfully for two marathons. But these were quite straight-forward to plan for – I had a set distance (one which I had completed several times before) and were on normal terrain.

The Kepler is a different beast. The distance is 20km further than I have ever run before. The terrain includes running over a 1,500 metre mountain. Most worryingly, the average time for finishers in the 2008 event is just on eight hours…….that is more than double the maximum time that I expect to be on a marathon course.

I struggled for a long time with how to address these new challenges. I am used to long training runs in the hills, and I am lucky in that I have regional parks with excellent running trails within walking distance of my house. So adding in long hill runs was a no-brainer. I figured that the longer runs would just be an extension of the routes that I was already running. But how to deal with the possibility of being on the Kepler course for eight hours…..now that was a challenge! I decided to do a little bit of research. I found blogs from past competitors (here and here). I read through the (very useful) sample training guides on the Kepler Challenge website. Eventually, a training programme that looked as though it would work for began to emerge.

My programme is based on 16 weeks (including the event week). You can download my full training programme (in MS Word format) here.  It follows a weekly pattern of:

Monday – flat run at marathon pace (i.e. within my aerobic heart rate).
Tuesday – hill run at fast pace
Wednesday – flat run at marathon pace
Thursday – flat run at marathon pace
Friday – rest day
Saturday – long hill run at marathon pace (I allow myself to exceed my aerobic heart rate on hills)
Sunday – flat run at easy pace

As the programme advances, my distances increase. The Monday and Wednesday flat runs build-up to 20km distances, at which point the Tuesday hill run becomes a normal flat run. The main focus of each week is the Saturday long run, which eventually builds-up to a 50km run. The idea is to make each week’s distance increase small and gradual. This will (hopefully) allow my body to adjust to the increased strain without introducing the risk of over-training and injury.

To give you an idea of the climb involved in my hill runs, here are a couple of typical examples in elevation form:

Short Tuesday hill run –

Wind Turbine Run

Long Saturday hill run –

Belmont Long Run

There is still a large question mark in my mind regarding time on the course. My long hill runs (30km) take me just on three hours to complete. I expect to be an average finisher in the Kepler i.e. to complete the distance in just under eight hours. I am not sure as to how I should be approaching my training runs from this perspective. Should I build some walking time into my long runs? This seems counter-productive. Should I be making a conscious effort to run slower? This also seems to go against everything that I have done previously in training. Should I simply increase the distance of my long runs, taking them over the marathon mark? I already have five very long runs in the programme, and I find the thought of adding more quite intimidating.

I guess that I will find out how things go over the next couple of months. I always have the option of altering my training programme as I go. I hate running just to fill time – I am the sort of runner that likes to go from point A to point B at a good, sustained pace. There must be a sensible compromise that I can adopt, but I have yet to see it.

Read Full Post »

Kepler Challenge 2009

About three months ago I saw an ad for an upcoming trail running event called the Kepler Challenge. It is one of those races that I see advertised each year, and each time previously I would think to myself “Wow, that would be cool, but it is for elite athletes and endurance freaks”. The Kepler (as the advertising repeats ad nauseam) is regarded as the jewel in New Zealand’s mountain running crown. It is a 60km mountain run, one which sees competitors starting off by literally running over a 1,500 metre mountain, then when they arrive at the other side they get to run a full-length marathon over undulating trails. Make no mistake – this event was in the “dream about it, but never do it” category for me.

This year, however, something was different. For the first time in my life I actually entertained the idea of entering the event myself. I began to question my reasons for not having a go – what was I scared of? Why couldn’t I do it? Was it really so difficult that a “normal” person couldn’t finish it?

I have been running relatively seriously for the past three years. I should define what I mean by “relatively seriously”, as I know that one person’s training run is another person’s challenge-of-a-lifetime. I am a slow but determined runner. I have always enjoyed running, but I have never been competitive. For many years my running programme consisted of “get outside and run 2-3 times a week”. I ran my first marathon in 2005 in 4hrs 15m (which I was more than happy with). Since then I have run four more marathons, and I have reduced my best time over the distance to 3hr 25m. I typically run around the Lower Hutt/Wellington area, with a mix of flat running and hills during the week and a longer, hill-based run on the weekend. I enter running events because I enjoy the challenge that they offer, not because I expect to win them – as a general rule, if I finish in the top-half of any event I am pretty happy.

Over the past five years I’ve done several events that seemed intimidating when I first entered them. Crazyman, Porirua Grand Traverse , Motatapu Marathon, Tussock Traverse…..all of these events were daunting when I first attempted them, but I found them all to be quite achievable given grit, determination, the right gear, and (most importantly) the right training programme. Every year my events have become that little bit more ambitious. My ‘normal’ training runs have become more adventurous, and my confidence has grown accordingly.

So, I guess that on reflection my interest in entering the Kepler is the natural progression of the past few years. That doesn’t make the challenge any less daunting in my eyes – I have never run a distance greater than a marathon. The term ultramarathon has an intimidation factor that I cannot deny. And the Kepler is a mountain ultramarathon. The step-up from a standard marathon to an event like the Kepler Challenge seems like a big one – but then isn’t that why the event is called a Challenge? Not so long ago the thought of running a normal marathon seemed like an impossible dream to me…..now I consider it to be perfectly achievable. Given the success and personal satisfaction that I have experienced in marathon running, wouldn’t the Kepler Challenge present me with the biggest reward of my running life?

All of my self-doubts are now (to some extent) irrelevant. I have entered the Kepler Challenge, I am training for the Kepler Challenge, and in December of this year I will be running in the Kepler Challenge.

Read Full Post »