REVEL Mt. Charleston Race Recap

on Sunday, June 18, 2017 at 11:45 PM

So the saying about what happen in Vegas....

Late last year I was contemplating what spring race I wanted to do.  The usual standby being either Goodlife or Mississauga, leaning towards Mississauga as I hadn't done that one in a while and I'm still not too convinced that the Goodlife course is or has been properly measured.   While browsing around the Runner's world forums late last year, I got my first hint of this race in Las Vegas as supposedly a fast course. It fit in well with the training schedule and was the week before Goodlife/Mississuga. To summarize the course basically has a 5000 ft (about 1500m) elevation drop from start to finish.

Truth be told I was contemplating making another BQ attempt but was pretty sure I wouldn't be in much better shape at the end of the training cycle as I was last year so ultimately was going to expect the same result of running a BQ time, but probably not making the cutoff.  The way I looked at the 1500m elevation drop basically meant that there would 1500m that I wouldn't have to run as it was essentially given to me free.

The plan was originally to see how I did at Around the Bay and if I couldn't hold a 3:10 marathon pace for the 30k , then I would think about doing Revel Mt. Charleston.  No I didn't quite hold a 3:10 pace (barely) during ATB and it felt a bit harder than I would have liked so I started giving serious thought to the downhill race after ATB.  The problem with that was the race sold out at the end of January. However I continued on with the training targeting Mt. Charleson hoping that I would get in off the wait list. .  On a whim, I also decided to post an ad on Craigslist seeking a bib just before Around the Bay.  The transfer policy for the race is quite generous letting people transfer right up until practically race day.   I figured if someone didn't contact me by the time the taper would start, I would extend my training by one week and do Mississauga.  Luckily a few days before the taper, I was able to secure a bib. As it turns out there were a few people looking to unload their bibs on the race's facebook page the week leading up to the race (as this was after the refund period) so I think if you're quick to act and monitor their facebook page like a hawk, you can probably secure a bib quite easily even if it's sold out.

I decided to travel down on Thursday for the Saturday race.  The weather forecast was looking okay.  Just above freezing at the start (at 7000 feet) and kinda warmish 16-17C at the finish line by the time I was expecting to finish.  This was the best I could hope for because the temperatures in Vegas in the week prior to the marathon had highs in the 30's.  The wind was also co-operating coming from the north west as the race generally run in an north north easternly direction for most of the race and a southernly direction at the end. One thing I hadn't planned on but started to worry me was a collegaue was telling me about the difficult time he had when visiting his brother in Utah and that it took him a week to get acclimated to the thinner air and here I was giving myself one day to adapt. I hoped that the downhill portion would make up for the thinner air and any difficulty I had.

Picked up my bib on Friday at a smallish expo. I did need to buy some gels which I did. I also got to try a neat device called the Rapid Reboot which is compression system. You basically stick some hipwader like air bag things around your legs and it pumps air into the bags which compress your legs.  Felt like a good massage.  Would love to own one but at $1000US for the system, not cheap.

Then decided to drive the course to get an look at the elevation and to see if there were any hills.  The course profile is a bit deceiving since 5000 ft of elevation drop tends to minimize the appearance of any hills. There were a few which I took a mental note of.

Got some take out pasta to eat back at the hotel but had difficulty eating. Forced myself to eat even though I wasn't hungry.

Race started at 6:30 in the morning and buses were leaving the finish line at between 4 and 5am.  This actually was okay for me as I tried to stay on east coast time which means wake-up time was 3:30am or 6:30 east cost time so that wasn't an issue. I stayed on the strip and required about a 20 minute drive  to the bus pickup location which was in NW Vegas.  I was expecting the casino to be empty at 3:30am in the morning, but it was still quite lively.  Got a couple of strange looks dressed up in my oversized throw away clothing strolling through the casino.

Ended up on the first bus to arrive at the start line which meant first dibs at the portapotties.  It also meant an almost 1.5 hour wait until race start.  The start line is actually located at a place with a bunch of little cabins and a chalet that has a restaurant.  Last year, the chalet was closed and people had to wait outside. This year they opened it up so that people could stay warmish which was great as it meant I wouldn't have to wait out in the cold.  There was only a limited capactiy so once it filled up, they prevented people from going in so good to have been one of the first ones there.  Chatted with some people and talked hockey with a couple of people from Boston and Vegas. Kind of odd. I guess the first thing people bring up when they find out you're Canadian is hockey.

So with 30 minutes to go, left the warmth of the chalet and did one last portapotty stop.  Actually had to wait for a bit and didn't get in until with about 10 minutes to go.  Headed to the start line and just barely had enough time to drop off my gear and settle into the start area.

As for the plan, I decided that I was going to run this without a HR monitor nor a pace band.  I thought that 3:15 would be easily doable based on the fact that I did 2:15 (and change) for the 30k distance which predicted a 3:15 marathon, and that anything under that would be due to the downhill portion, alas my 1500m of not having to run.  While I had hoped this might mean 3:10 or better, Anything beyond what I've been able to run these past few years would have been good. 

The race started and I was beside the 3:15 bunny.  The first half mile of this race is actually uphill and is probably the steepest uphill of the race so I decided I would take the first mile easy.  The uphill portion in the first half mile is all but negated by the downhill portion for the remaining .5 miles of the first mile so I wasn't too worried about that.

1 mile: 7:40

Hit the first mile well behind pace, but wasn't too worried since the downhill portion was about to begin.

2 mile: 6:55
3 mile: 7:02

So down the mountain we go picking up speed. Now you really have to appreciate the grade of the course. Mile 2 has about 300 ft of elevation drop and mile 3 has over 200ft.  For comparison, Goodlife Toronto has about 350ft of total elevation drop also over the course of a few miles, but I was about to repeat this elevation drop for over half the course.

4 mile: 7:16

So mile 4 appears to slow down back to my regular marathon pace, cause I think there was a hill on this portion. At this point of a race, you shouldn't be hurting, but my legs were aching a bit and I felt like I was huffing and puffing more than I should.  With the course starting out with an uphill, it's hard to gauge effort and then launching immediately into 7 min/mile pace doesn't leave much time or room to recover.  I had read a lot about trashing one's quads on downhill races so I was trying to mitigate that by running efficienctly, increase cadence, not overstriding and letting gravity pull me down, but that doesn't seem to have worked as I could feel my legs were not fresh.

5 mile: 7:08

As originally laid out mile 5 was supposed to have this little loop that runs into a parking lot, but they had some difficulty with getting a permit so they had to reroute the course by eliminating this loop and then adding an out and back later in the race.  At the time, I thought this would be good because the loop had a bit of a hill to it.

6 mile: 6:57
7 mile: 7:14
8 mile: 6:48
9 mile: 7:08
10 mile: 7:15
11 mile: 7:25
13 mile: 14:47 (Missed 12 mile marker)

So continue down the hill with a couple of fast miles and a couple of slow miles. With no pace band, I had no idea how far ahead of pace I was at.  I knew I was under 3:10 marathon pace, but how much under i wasn't sure.  I was hoping to get an idea at the half mark because that's where the half marathon was supposed to start. However due to the last minute course change and the elimination of the loop in the first half, the half marathon start line did correspond to the half marathon mark of the full.  I passed the 13 mile mark at 1:33:37. add on about 45-60 seconds for the extra 0.1 mile and I was pretty happy about the time.

14 mile: 7:31
15 mile: 7:28
16 mile: 7:30
17 mile: 7:28
18 mile: 7:26
19 mile: 7:22
20 mile: 7:24

After the half marathon, I started to slow down a bit.  I think  this was because of the wind from the north west.   After mile 13, the course heads in a north eastern direction so the wind which had been providing a bit of a tailwind for most of the race became a crosswind.  Still not too much to impede your effort and it was only causing a slight slow down in pace.  It was during this time that I started to think that I was getting dehydrated. As I usually do, I carried a gatorade bottle for the race that I drank from at each mile marker, in addition to drinking at each aid station.  After the half mark, I ran into some bottle issues in that the twisty cap on my gatorade bottle wouldn't twist open.  I ended up having to resort to unscrewing the cap to drink. I was careful not to drink too much before the race which in hindsight was a mistake.  There weren't too many aid stations, only 13 for the full marathon, 6 in the first half and 7 in the back half. I had taken only one cup of fluids at each aid station by this point which was maybe only a quarter to half filled.  Usually by the 30 km mark of a marathon, I will have finished my gatorade bottle.  By the time I had reached 19 miles this time, I still had quite a bit of fluid left in my bottle. My bottle issues and the few aid stations, it was clear that I wasn't drinking enough.  With about an hour to go in the race, I decided to just chug the rest of the bottle and hope to avoid getting even more dehydrated, tossing the bottle just before the 20 mile mark. 

21 mile: 7:33
22 mile: 7:54

Miles 21 and 22 were also a bit slower because I stopped to walk at each aid station to ensure I took in multiple cups of fluids.
23 mile 8:16

So mile 23 was where the race kinda fell apart.  Remember that loop that they had taken out earlier on in the race? Well they had to add that distance back in, which they did around the 23 mile mark. the probelm was the back portion of the out and back was directly into a strong wind that had been at my back for most of the race.  It was horrible, probably stronger than the wind that was at Goodlife last year.  Now 8:16 doesn't seem that bad for the mile split but you have to consider that the wind portion comprised only about 150m of mile 23 where I went from running about 7:40 min/mile pace on the out portion to over 9:30 pace on the back portion into the wind. There was still another 500m of this stuff that was going to be in mile 24. Add to this was there was slight incline which slowed me down further.  I made a time check at mile 23 since I didn't have a pace band and I knew that 3.2 miles remaining is a little over 5k.  I passed 23 miles at 2:49:30 and some quick math suggested I had  25 minutes to run 3.2 miles to finish under 3:15 which means I would have to run a little under 8 min/mile and this was still with about 500 m left of running into the headwind with the uphill that I had been struggling with for the past 150m.  And remember this was only to get me to 3:15, which was my BQ time. So I made the decision at this point that though I could possible make a BQ time, getting a time that would make the BQ cutoff which I would think would have had to have been at least 2:30 under was just not going to happen.  I had planned to take a few days in the Grand Canyon and do some hiking and didn't want to beat my legs up anymore then they already were so I walked the rest of the race.

24 mile: 14:14
26 mile:  25:23
26.2 mile: 2:08

I did try to slow jog a couple of times, but shut it down realizing there was no point. I did jog the last 0.2 miles of the race and ended up finishing with a time of 3:31:12.

To say I was disappointed was an understatement. I went into the race thinking that 3:15 would have been easy and that the downhill would have added to whatever cutoff I needed. I should have drank more at each aid station or at least chugged a bottle of water right before the start.  I definitely felt that I was working harder with the thinner and dryer air.  Maybe I needed more time to acclimatize to the altitude before the race? I can definitely say that it was not as easy as I thought it would be.   Looking at the Strava autosplits which shows Grade Adjusted Pace, it reports paces of 8:30's. It did not feel like I was doing 8:30 min/mile pace.

Polar Race Stats

Mile Split Time up
on 3:15
Time up on 3:10

1 07:39.6 -00:13 -00:24
2 06:54.7 00:19 -00:04
3 07:02.4 00:43 00:09
4 07:16.4 00:53 00:07
5 07:08.2 01:12 00:14
6 06:57.4 01:41 00:32
7 07:13.8 01:53 00:33
8 06:48.3 02:32 01:00
9 07:08.2 02:50 01:07
10 07:14.6 03:02 01:08
11 07:25.6 03:03 00:57
13 14:47.3 03:09 00:40
14 07:30.6 03:05 00:25
15 07:27.6 03:04 00:12
16 07:30.3 03:00 -00:03
17 07:27.7 02:59 -00:16
18 07:26.1 02:59 -00:27
19 07:22.0 03:04 -00:34
20 07:24.3 03:06 -00:43
21 07:33.2 03:00 -01:01
22 07:53.5 02:33 -01:39
23 08:16.2 01:43 -02:40
24 14:13.6 -05:04 -09:39
26 25:22.6 -15:34 -20:31
26.2 02:07.8 -16:12 -21:12
So judging from the splits, I seemed to be doing all right up until the 22 mile with a 2:33 cutoff bank which then dropped 45 seconds in the next mile due to the wind.

Official Timing Results

On the plus side, the race gives out free hi-res race photos and videos. Mine look terrible.

As for the race, generally well put together. Very efficient, though I would have liked to see a little more fluids in the cup's at each aid station.  Though the downhill is nice, there's no shade at all for practically the whole race so if you have a nice clear sky, the sun is beating down on you as it was on that day. I should have worn sunglasses.  The wind helped cool you down so I never really felt warm, but I was definitely dehydrated after sweating way too much and not getting enough fluids.

Horrible Finish Line pic. Notice the salt stains.

So, I'm not sure where that leaves me for the BQ attempt for this year.  I've been giving some thought to maybe doing Erie again, maybe Hamilton.  This is all complicated by the fact that I got into the Berlin marathon through the lottery, though I'm not sure I want to go this year.  I would have if I had BQ'd at this race, but it's scheduled right between Erie and Hamilton.  Ideally, I would take a shot in Erie which might get me into Boston 2018, and if I don't succeed, I would have about 2 months of preparation to try again in Hamilton with their downhill course for Boston 2019. Doing Berlin in between would complicate that though I suppose I could try again in Berlin but that would be less than a month between Erie and Berlin which would be less than ideal.

So afterwards, spent a couple of nights in the Grand Canyon.  I had tried to do the Vegas/Grand Canyon thing back in 2010 when I did Boston 2 Big Sur, but it was really on a compressed schedule and I didn't really get to spend any quality time in either place, something that I've always regretted. Returned this year and had a much better time, though no hiking as legs were still quite sore from the race, even with the 3 or so miles of walking at the end.

Top of the world.

Backs In Motion 10k 2017

on Sunday, May 21, 2017 at 11:52 AM

Did the Back's in Motion 10k about a month ago.  Did this race two years ago as a marathon pace test run the week before the marathon I was doing at the time as it's relatively close to home.  It seemed to work out well that year and the race also fell the week before my spring marathon this year so I thought I would try again.

Like two years ago, the training plan had a 12 mile long run. I had planned to do 6 miles before the race as warmup and then do the 6.2 miles at expected marathon pace, but I only managed to squeeze in 5 or so before the start because I started late and that only meant I had about 5-10 minutes between the end of the warmup and the start of the race.

Goal pace for this was an easy 4:30 min/km or about 7:15 min/mile which equated to a 3:10 marathon.

Tried to start off slow, but hit the first km at 4:19 and first mile marker at 6:49.  As usual, too fast.  Tried to ease off on the throttle a bit, but the second km is downhillish and so passed the second km at 4:19 also.  I should probably also mention, my HR started doing the racing thing right from the start. Just ran through it.  From that point on, I kinda hit my splits though they were a tad on the fast side. Two years ago, they messed up the turnaround which caused the course to be long. This year they had the turnaround properly marked with a volunteer dressed up as a big orange pylon with an air horn.  No chance of missing the turnaround this year.  Bumped up the pace a bit in the last two km to try and pass some people. Nice being able to pass people without actually having to redline.

At the start.

KM split
1 04:19.1
2 04:19.7
3 04:20.4
4 04:26.6
5 04:24.4
6 04:23.3
7 04:26.6
8 04:25.7
9 04:20.8
10 04:15.4

So finished overall in 43:42 which was a bit faster than the 45 minutes flat I was aiming for. 
Polar stats.

I was working a bit harder then I probably should have, but I thought that since this was after a 5 mile warmup, that 4:30 pace would have felt easier if I was fully rested.  At the time, I thought this was looking on the up and up for my marathon which was the following week.  Ended up finishing 3rd in my age group.  No chance at getting anything higher since the 2nd place guy was under 41 minutes.  Ended up with a gift certificate for a pair of diabetic compression socks.  I'm not sure if these are the same as the sports compression socks.  Will order and see, though I have three pairs of compression socks already, I hardly use them.

There didn't seem to be as much swag this year as two years ago.  They do seem to give discounted entry fees to the students (it's a chiroparactic school) so I suppose they don't bring in as much money as a normal race would.  Nevertheless, I like this race as it's a challenging course and well put together and has inside warmup and cooldown and actual washrooms. One downside is no chip time. Only gun times, even though they use chip timing.

They did have this Optogait system after that there were giving free analysis for which is a treadmill setup with a bunch of sensors that gives you feed back on your running form. Gives you measurements of a bunch of different things about your gait and any differences between your right and left legs.   I apparently have an imbalance where I run with my right leg generating more propulsive force than my left which I suppose is not unnatural since I'm right handed.  While interesting to know, not sure what I'm supposed to do to correct it, but I guess that's the point, they want you to sign up for their training to try and fix it.  Still as a numbers go, it's very interesting. 

Around the Bay 30k Race Report 2017

on Saturday, April 1, 2017 at 7:09 PM

Did Around the Bay last weekend.  I've done it a few times over the years, but it's always been part of a training run with a portion of it at marathon pace. The training plan had an 18 mile long run with 14 at marathon pace. Around this time last year, I did this same run at 7:15 min/mile pace for the marathon pace portion (not at ATB, but on a normal training run) so I thought I could try that again.  However, if I were able to hold that pace for another 4.6 miles I might qualify for the silver medal which the race gives out to those who finish in under 2:15 gun time.  I wasn't sure however this would be doable.  A 2:15 30k equates to a 3:15 marathon according to McMillan which means if I'm roughly in the same shape as last year, trying for 2:15 would be racing at my limit for the 30k distance. 

I stayed overnight in Hamilton at the same place I've stayed the previous two years. Have that down to a science now,  breakfast, consisting of oatmeal with brown sugar, bagel with PB and jam and a waffle with syrup and a little bit of water to wash it down. Left hotel room 10 minutes before start, jogged to the start line for a brief warmup, stood around for a few minutes and then the race starts.

 Gear consisted of shorts and long sleeve T over a short sleeve T which was about perfect for the conditions, just above freezing, windy but no rain.

I had initially planned to start with the 2:15  pacer and scoped out at the expo that there were actually two pace bunnies this year.  One of the guys was the same guy who ran the 3:15 marathon last year at Goodlife and who had started out too fast, the other guy seemed to have good pacing performances in the past with nice even splits, so I was going to run with him and use the group to block the wind at the start which was coming from the NE.  However, once in the corrals on race morning, the guy I had intended to follow had dropped down to pacing 2:25 which meant that I only had one option for pacers which was the fast start guy.

Having thought about it some more, I decided not to try to stick with pacer because I was pretty sure he was going to go out too fast, add to this that he was actually at the back of the first corral which means he also had to make up the gun-chip difference. I thought trying to chase after the silver medal wouldn't be worth it.  Medals don't mean too much to me.  I have shoeboxes of medals in my closet that I haven't looked at since the day I got them. I thought I could still chase 2:15 for a chip time but I wouldn't try for the gun time because the forecasts were predicting wind and I thought it would be better to start off a ways back so I would have people to block the wind for me. 

Some general comments. I decided not to run the race with a pace band. I normally always have a pace band, but I thought the math would be easy to do on the run if needed (4:30/km, 9:00/2km). The markers seemed all over the place at times. Pretty sure the 10k marker and timing mat was misplaced because everybodies 10k split time seems slow and everyones 10k-15k split time seems fast.  The first 15k of the race is into the headwind at times and I tried my best to tuck in behind people where I could.  I wasn't too concerned with split times or pace but just tried to run a good effort level and found that keeping my HR around 170 seems to work. Didn't have any HR issues early.

The 2:15 pace bunny was behind me for the first mile so maybe he was going to be okay, but then he took off and I let him go. Looking through his Strava race, half of his miles in the first half were sub 7 min/miles with a couple of sub 6:45's in there (a 2:15 30k is 7:15 pace) Glad I didn't try to stick with him. Approaching the 15k mark, I could see the clock was around 1:07:30, in fact checking the split times after I hit the half mark at EXACTLY 1:07:30 (gun time) (1:07:11 chip) which was putting me on track for a 2:15 guntime finish.  This actually surprised me as it means I had made up the chip gun differential and the first half had the head wind.  I started giving thought that maybe I could still chase after the silver medal. The next little bit would have a tail wind where I could bank some time which I could give back up when I got to the "hill".  Easier said then done, because the rolling hills on the next 5k, even with the tail wind, didn't allow me to bank any time whatsoever.  Crossing over the 20k mat, I was about  5 seconds over where I needed to be for the silver medal, but with the hilly part still to come, wasn't too sure that I was going to be able to ramp up the pace. This was compounded by my HR spiking just after the 23k mark.  At this point, I had run 14 miles at marathon pace and was contemplating slowing down/stopping  to try to get the HR to reset. I ended up just continuing to run and not bothering with split times anymore.

Down the hills and then up to "heartbreak" which was not pleasant, but thankfully this hill is relatively short and over with quickly.  I think I did one time check within the last 5 km which I think was at the 28km mark because I remember thinking at the time that 2:15 chip time probably wasn't realistic, but that I would comfortably finish before 2:16 (The split had me 40 seconds over 2:15 chip).  However looking back in hindsight, the 28k marker was severely misplaced as it seems like I was a lot closer than I thought. If I had checked at the 27k mark, I would have seen that I was right on the bubble. In the end I finished in 2:15:10 chiptime. Gun time was 2:15:30 which means I missed the silver medal by 30 seconds. Could I have found an additional  10 seconds over 30k? yeah probably.   Could I have found 30 seconds? Maybe. Pretty happy with the effort level though.

Splits are as follows. Polar data is here.

KM Time Split Time relative to 2:15
1 0:04:30.6 04:30.6 00:00.6
2 0:09:17.5 04:46.9 00:17.5
3 04:23.0
4 0:18:03.6 04:23.0 00:03.6
5 04:24.6
6 0:26:52.7 04:24.6 -00:07.3
7 0:31:20.5 04:27.8 -00:09.5
8 0:36:03.3 04:42.8 00:03.3
9 0:40:27.7 04:24.4 -00:02.3
10 0:45:55.6 05:27.9 00:55.6
11 0:49:18.0 03:22.4 -00:12.0
12 0:53:48.7 04:30.7 -00:11.3
13 0:58:19.2 04:30.5 -00:10.8
14 1:02:46.5 04:27.3 -00:13.5
15 1:07:11.6 04:25.1 -00:18.4
16 04:33.8
17 1:16:19.3 04:33.8 -00:10.7
18 1:20:41.5 04:22.2 -00:18.5
19 1:25:07.8 04:26.3 -00:22.2
20 1:29:35.3 04:27.5 -00:24.7
21 1:33:56.3 04:21.0 -00:33.7
22 1:38:38.6 04:42.3 -00:21.4
23 1:43:13.3 04:34.7 -00:16.7
24 1:47:49.1 04:35.8 -00:10.9
25 1:52:37.0 04:47.9 00:07.0
26 1:57:01.2 04:24.2 00:01.2
27 2:01:30.6 04:29.4 00:00.6
28 2:06:39.7 05:09.1 00:39.7
29 2:10:52.7 04:13.0 00:22.7
30 2:15:10.0 04:17.3 00:10.0

So the race went pretty well. I'm still not sure that I could sustain this pace over the course of a marathon as it's been 9 years since I've been able to do that and fitness wise. I don't feel that much better in terms of fitness than I was last year where 3:10 was a pipedream but who knows, maybe the taper can increase my pace by a few second per km which might put me in the ball park. I don't necessarily need to run a 3:10 marathon, but just close enough to clear the BQ cutoff under 3:15.  What that cutoff is though is a bit of a crapshoot so the more time the better.

Scotiabank Waterfront Half Recap 2016

on Saturday, October 22, 2016 at 8:49 PM

Paced the 1:45 half at Scotiabank again this year.  With no marathon training to rely on, I needed to maintain some level of fitness over the summer, which totally went into the crapper during the film festival.  Normally when I have a pacing gig, I like to do an LT workout  at a pace where the equivalent race time says I should be able to do an equivalent time at the pacing distance.  So about 3 weeks ago, I did an 3 mile LT run at a pace that says that for a 3 mile time trial, I should be able to do a 1:42 half.  I extended that to a 4 mile LT run the following week which also said 1:42 half.  Still not quite convinced, two weekends ago, I did 15 miles which included 13 miles at about 7:45 pace (1:45 is 8:00 min/miles) so I was pretty confident that 1:45 would be doable.

Normally going into the last week of an important race, I am extra careful about not getting sick or injuring myself, which I completely ignored this final week and with my luck, I started to come down with something on Tuesday and a had a full blown cold on Wednesday/Thursday. Immediately, went on the Cold-F/X (not sure this works, but hey I was desperate) and Vitamin C and it seemed to have settled down by Sunday.  Still not completely recovered however, but at least I could breath through my nose.

I found that in the past, I tend to overcompensate when something goes wrong and I realize now that my drinking too much at my race back in May led to me not hydrating enough going into this race. I didn't quite drink enough on Saturday and was probably a bit dehydrated going into the race. I had left home somewhat late and arrived at about 8:00 for the 8:45 race start.  Parked at the Eaton's Centre but made the mistake of trying to cross Bay to city hall by walking south, not realizing that they weren't letting people cross Bay because the 5k race had started at 8:00am.  So after backtracking a bit, it was probably around 8:15 and so had to find bag check, take my pre-race gel and headed into corrals at about 8:30.  Didn't even get a chance for a bathroom break, but didn't need to as it would turn out.

Some general comments for future reference. As is typically, I started the race too fast even though I had made a conscious attempt to be slow.  The Polar GPS pace (left arm) was way off for the first km, but the Garmin (right) seems about right so maybe next time I will just let the Garmin dictate the pace at the start.  I made an immediate correction during the 2nd km and was basically on pace by the 2 km mark. It was very humid, including a light drizzle of rain at the start. Rain stopped after a few kms, but the ground was slick and a bit slippery.  Coming down Bathurst, I heard someone behind me take a nasty spill. Normally on this part of the route, I run down the centre of the street between the two sets of streetcar tracks.  I've done this in the past to avoid the camber of the road and get an optimum GPS signal, but I think this might be dangerous because as people crowd around, there's a risk of people stepping on the train tracks on either side of me and falling which might have happened this time.  Last year, an elite runner broke her leg on the streetcar tracks so in hindsight, probably best to stay on one side of the road. 

Generally on pace for most of the race, picking up time on the downhills (3-8km). The slow down at 7km is due to the train overpass at Bathurst-Front.  I think the slowdown at 12km was an aid station issue since both GPS's show I slowed down to slower than 9 min/mile pace for a short period of time. It might also partially be a tangent issue since this part is a bit curvy. Slowdown at 19km is due to the Lakeshore overpass at Spadina.

Developed a side stitch on right side about half way through. Probably due to lack of hydration. It was really starting to bother me late into the race to the point that I was having difficulty carrying the sign. I normally hold up the sign for the whole race, but was having difficulty doing so because of the cramping. I tried to just carry it by my side for a short while, but realized there was no point carrying it like this if no one was going to see it, so I decided to toss it at an aid station near the 18 km mark.  I still had the time goal on the bunny ears and was wearing a sign on my back so that would have to do. It was a struggle towards the end.  I tried to do the breath on the side opposite the side stitch thing to lessen the pain, but this required a 1-1 breathing pattern and a slow down in cadence which caused me to run less efficiently, which means I had to expend more effort to do so.

During the last km, I usually try to be  encouraging to people running up Bay, but I was in my own little world of hell trying to maintain the proper pace with my abdomen begging for me to slow down. Checked my watch at the 200m and 100m to go mark and saw that I was pretty close to my goal time so no room for error. In the past, I'm up by at least 15 seconds so I can take the last little bit easy. Not this year. Ended up finishing at 1:44:56.

Splits are as follows

KM Cumulative Time Split Goal Time Time Under
1 0:04:53 04:53 0:04:59 -00:06
2 0:09:58 05:05 0:09:57 00:01
3 0:14:57 04:59 0:14:56 00:01
4 0:19:51 04:54 0:19:54 -00:03
5 0:24:43 04:51 0:24:53 -00:10
6 0:29:26 04:43 0:29:51 -00:26
7 0:34:32 05:06 0:34:50 -00:18
8 0:39:28 04:56 0:39:49 -00:20
9 0:44:27 04:59 0:44:47 -00:20
10 0:49:26 04:59 0:49:46 -00:20
11 0:54:23 04:57 0:54:44 -00:21
12 0:59:30 05:07 0:59:43 -00:13
13 1:04:31 05:02 1:04:42 -00:10
14 1:09:28 04:56 1:09:40 -00:12
15 1:14:27 05:00 1:14:39 -00:11
16 1:19:27 04:59 1:19:37 -00:11
17 1:24:27 05:00 1:24:36 -00:09
18 1:29:27 05:00 1:29:34 -00:08
19 1:34:32 05:05 1:34:33 -00:01
20 1:39:29 04:57 1:39:32 -00:03
21.1 1:44:56 05:27 1:45:00 -00:04

Polar Route and Stats

HR did spike at 16km but had turned off HR display so didn't know.  My HR was also much higher prior to this hovering in the upper 170's.  I think this was a remnant of the cold and it being quite humid and relatively warm (was 19C at start). I did the 15 mile run the weekend before in the upper 160's.  

Generally, pretty good split times and even pace.  In previous years, they only had a 10km intermediate timing mat, whereas this year they added timing mats at the 5km and 15 km mark which allows me to track who actually ran the race with me. I imported the finish line results into Excel and calculated gun time splits for everyone and then sorted by gun time finish. Using the advanced filtering feature, I can generate a list of people who finished within 30 seconds of my gun time who also were within 30 seconds of me at each of the 5, 10 and 15k mats. In total there were 26 people who fit this criteria.

Engineering degree comes in handy...
 There were also 37 more people who were within 30s of me at the 5, 10 and 15k marks who finished outside of the 30 second finish window, 6 of whom finished more than 30 seconds ahead. 

So all in all, quite happy with the pacing performance this year, even despite the side stitch. Still need to work on that first km though... 

Oh Well..

on Sunday, October 16, 2016 at 8:19 PM

So I didn't get into Boston.  The cutoff was 2:09 which means I wasn't even close.  I needed to run 3:12:51.  Looking back at my BQ run in May, it didn't matter that the last 7 km was into a brutal headwind, I was already behind by the 35km mark. Relying on the BQ estimates that other people were calculating proved to be a bad choice.  The method they used was somewhat accurate last year, but not remotely accurate this year.

This has had me rethinking the Boston qualifying attempts.  The past 2 years I've just tried to squeak in by using the previous years cutoff as a guide.  This hasn't worked and the issue is that everyone is now aiming to beat their BQ time by 5 minutes to ensure that they can register for the first week.  While it would be easy to say that I should just train for 3:10, the part of me that thinks back to how hard it was 8 years ago to run a 3:10:23 on higher weekly mileage and I start to question whether it's even doable now.  But of course, I don't actually have to run a 3:10 as I just need to clear enough time to make the cutoff so a slip to 3:12 during a 3:10 attempt might be okay.  This is a lot better than initially aiming for 3:12 which doesn't leave a lot of room for error.

Another side of me says hey I can wait a few years and my BQ time increases to 3:25, but I thought it would be neat to aim to run Boston at least once in each age category which means I would need to do it within the next 2 years before I age-up into the next category.

I haven't really tried to train for a 3:10 marathon in a long while so I guess I'll have to see how it goes, if it even goes at all.  It's easy for me to say now what I intend to do over the winter, but you know what they say about the best laid plans of mice and men...

Registering for Boston

on Monday, September 12, 2016 at 7:07 PM

Boston registration started today, but with the new rolling registration system and me having less than a 5 minute buffer, I won't be able to register until next Monday.  I booked my hotel for Boston last week as I'm pretty confident I will be able to get in.  There have been a bunch of different people(here, here and here) who have been data crunching the results list of various races over the past year and they are predicting a minimal cutoff because there are a lot fewer qualifiers compared to this time last year. Most of the drop off was due to the warm conditions in Boston this year, but also a lot of other races this past summer have had crappy conditions so the pool of potential qualifiers have dropped significantly.  Actually, the whole idea is a pretty interesting data mining project.  If they had this registration system back when I was in grad school, I probably would have taken the task to do the analysis as it's fairly rich dataset that would have been easy to work with.  

Looking at peoples times is one thing, but the one wildcard in this was the number of places that Boston was going to offer next year.  All of the above analysis assume that the number of entries next year would be the same as last year which was 30,000.  Obviously, if the number dropped, with fewer place available, the competition gets more heated and the analysis would go out the window.  I was holding out on committing to Boston until I knew the number of places for next year, which they announced last week at 30,000 so that was good and the hotel was booked.

I also applied to the lottery for Tokyo and London for next year which take place in February and the week after Boston, respectively.  With my luck, after striking out over the past few years, the one year I don't want to get in will probably result in me getting into both of them!  I'll cross that bridge when I get to it though it'll be a nice problem to have. 

Run For Hutington Disease 10k Recap

on Friday, July 1, 2016 at 7:18 AM

I did a 10k race last Sunday, but I didn't actually end up racing it.  After doing a marathon, I usually like to do a few shorter races to test where the fitness is.  I had originally planned on doing the Run for Lions event which is on the Saturday that I had done last year, but I slept in.  I also had a weird twinge in my ankle on Friday.  I had switched shoes recently and I think it ended up stressing my ankles so the extra day of rest would hopefully be beneficial.  The race takes place at Sunnybrook park, and starts at the same place as the Korean Peace Marathon and Spring Into Action races that I've done before, but the route was different.  While the other two races are a 5km out and back course.  This race consisted of a 2.5 km out and back course that we would have to do twice.  While this might seem a bit boring, I actually don't mind this route as it eliminates a big hill that is present when you do the 5km out and back course.

I arrived Sunday morning and it was a bit warm and I don't like racing in warm weather.  While I had hopes of setting a PR, I quickly realized that this was going to be unlikely. I did the warm-up HR spike thing which I did get to go and reset, but as soon as I started, the HR took off right away hitting 190 in less than a minute.  I ended up running to the first water station which is just after the 2.5 km turnaround and then decided that with the HR spiking that I would shut it down.  I then proceeded to walk hoping to get the HR to reset.  I thought it did a couple of times, but as soon as I started running again, the HR would take off. In the end, I spent the next 4.5km or so trying to get the heart rate to reset. Was finally able to get the HR to come down shortly before the 7km mark for good and then proceeded to run out the rest of the race at a moderate effort.

Polar Stats and Route

So here's crazy HR.

HR at start is well over 190 and over 200 by the time I shut it down at the first turnaround, whereas at the end, the HR is at around 180 even though the pace is roughly the same.   You can also see me doing the run/walk thing in between.  Normally, when I walk, the HR is just over 100, but when it spikes it hovers at around 140 or so.  You can see when it spontaneously resets at just over 40 minutes when the HR drops suddenly and that's when I start running again to finish the race.  

Finish time was 58 minutes or so, which I guess isn't so bad when you consider that I walked for a good chunk of this. It was nice to actually enjoy the route and take in the scenery. It would have been better if I didn't have to pay a $50 entry fee to do so, but I got a tech shirt out of it and the money goes to a good cause so I suppose it's okay.

I'm finally getting the HR thing looked at again so hopefully I"ll have more information to better decide if its okay for me to actually just run through these HR episodes.