Wolstonbury Hill is just that: one of the impressive hills in the South Downs to the left of the main A23 road as you approach Brighton. I remember this very well from last year. That event was my first run after a long recovery from injury and I thought I was going to die! It was very hot and the hill was mighty steep. I hoped to be rather fitter this time, but although the bright sun and very warm morning was welcome after such a lot of rain and cold weather recently it felt a lot like last year.
The approach to the hill, and the position of the start were very different this year. (If you click on the thumbnail, you will see my run plotted on a Google Earth image – read about how I made this below). We had to walk about 15 minutes, fairly gently uphill, to reach the start, but not much of a wait when I got there.
I could see the first control almost as soon as I started – the only trouble was it was about 50 metres above me! I managed a reasonably sprightly slog up to it, then had to keep heading up to the flat top of the hill for the next control. I felt in control and quite good, but was already breathing hard. Something was not quite right at 3: I quickly reached the end of the thicket where it was shown, and found what I was sure was the right depression, but no control, I found it fairly nearby in a depression with a big clump of bramble but lost time. I was rather vague round to 4, then fell into the groove for a while, with a level run across then round the earthworks at the top of the hill and a very long downhill run to 6 and 7, broken only when I stopped for a moment to help someone and to climb a stile.
Things went fairly smoothly really after that, except that I was becoming hotter and hotter, with sweat stinging my eyes and blurring my vision. I just could not go any faster no matter how hard I tried. I am not sure that I did the right thing from 10 to 11. I decided to go more or less straight through an area of forest which was marked as “with fallen trees” rather than follow paths around. I liked the shade but the slope was quite steep, there was nowhere I could run and there were quite a few trunks to climb or go round. I confused two paths at 13 and was in the wrong area for a few minutes then was very confident with navigation over the last few controls, but simply had nothing left to take advantage of that – I was hot and just could not go any faster than a jog no matter how I tried. I was back in an hour – quite a few of the “usual suspects” were a little faster, but I was not far behind. I ended up 22nd: a little better than recent events and almost 15 minutes faster than the last time I was here.
This event was the debut of my new toy. I recently bought a Garmin Forerunner 305 which is a wrist-worn gps and heart monitor. While you are running it captures your position and heart rate every second – you can then use software to plot your course on a map or Google Earth as well as analyse your performance. It comes with some software that keeps a running log and draws nice graphs, as well as allowing you to create and use training workouts. That is really why I bought it. The couch to 5K (see article below) plan is working very well for me but I only have a few weeks to go. It has made me realise that I have to have the discipline of a “tight” training programme in order to go further and faster without becoming injured. There are further plans that you can load into the Forerunner which should allow me to go beyond the programme’s immediate goal which is being able to run 5K without stopping three times a week.
I am sure I will not analyse in this depth very often but for the first time I had to go to town. First is the map plot of the route I took today. I plotted this on Google Earth using Sport Tracks – great free software that works with the Forerunner. I set the Google Earth view obliquely to give some sense of the hill and added the purple blobs for the controls. Apart from anything else, it shows that the course today was a really good use of the terrain – there was simply never any “dead running” – every control was a different physical and mental challenge.
I then looked at my pace over the ground.
(Click on thumbnails to see full size graphs)
At first, this plot was rather confusing with the pace yo-yoing up and down so much, then I realised that the Forerunner was being very accurate – it was able to detect even when I stopped to punch controls or climb stiles! I produced this graph with the Garmin “Training Centre” software that comes with the Forerunner, then added the notes using “Snagit”. The overall pace is not too impressive, but there were a few points where I was actually running, and it proves that I was never quite walking, except where I was struggling with navigation!
Given the nature of today’s terrain, I had to plot the elevation. There is some exaggeration on the graph, but it really was pretty steep in places! Generally, I have found that the elevation data is less accurate than position and heart rate but the plot does give a good picture of the land today.
Finally, I plotted my heart rate. Officially the maximum rate for someone my age is 171, and I topped 180 today! It certainly felt like it. What was interesting was that running downhill meant only a slight drop in heart rate, but struggling up a steep slope is pretty much guaranteed to max it out very quickly. My heart rate only really dropped when I was struggling with navigation and stopped or slowing looking around. In the software, you can overlay these plots – though that quickly becomes confusing. Heart-rate does look very closely linked to the steepness of the slope (up and down) and to pace, but there is often a lag – for example, my heart rate kept going up after I stopped at the finish, before dropping pretty quickly.