When I first heard that there were some companies coming out with power meters for running, I couldn’t wait. I love to be able to objectively quantify my workouts. Knowing how this works for cycling, being able to add this to running would be a bonus. Then I thought about it a bit and realized it would probably be best to hold out a bit. The technology was new and Still evolving. Also, none of the training watches or software would pick it up anyway without some hacking involved.
I had played around a little bit with running power by using my Cyclops PowerCal Heart Rate Monitor which was kind of interesting. The problem was I had to run with my Garmin in biking mode all the time. Not something I really wanted to do since I would miss out on the other running-specific data. Then Garmin came out with the HRM-Runs’ running analytics which I thought was better data than just having power.
The Stryd Running Power Meter
The Stryd unit seemed to be the one that was getting the most attention and it had gone through a few iterations of its product already. It started out as a little widget that you clip on your shorts, then it turned into a heart rate strap and now it is a little foot pod. It finally seemed like they were stabilized a bit, so I decided to “pull-the-trigger” and order one. It took a few months to arrive.
I am glad I waited because the HR strap looks like it sticks out a bit and would look very strange bulging out of your shirt. One advantage of the HR strap one was that it measured power in 3 planes, vertical, horizontal and lateral, whereas the footpod only measures the first two. I don’t think this is a big deal for me since I think I am a pretty efficient runner thanks to my Chirunning practice.
I have had the Stryd footpod now for a few months now and feel I have some initial impressions of it. I say few months because I had to send it back to be replaced already since the tab where it clips to its back clip broke off. It doesn’t seem like there is much really to grab onto there. While it still held in place on my laces, I was a little leery it was going to fall off sometime. The folks at Stryd quickly replaced the unit and got me back and running again. Pun intended.
Collecting the Data
I started reading Jim Vance’s “Running with Power” book while I was training with the unit. I had already read Vance’s previous book “Triathlon 2.0” which I really liked, but I felt the Running with Power book was not quite as good. Most of it was just a re-hashing of the other books’ concepts on Power for cycling. While there were a few new metrics, namely Efficiency Index or EI, that are different from cycling, I feel this book is a little premature at this point since the technology is still being figured out. Hopefully the “Running with Power 2.0” will be better.
One of the recommendations in Vance’s book was to just start running with the power meter and start collecting data. For the next couple of months, I just ran with it and checked in on the numbers post-mortem of my runs.
After finally collecting several months of data I decided it was now time to analyze it. Well despite the fact that Jim Vance’s book stressed how essential the Efficiency Index (EI) metric was, none of the training sites, except for SportTracks even implemented it! Not even Training Peaks or Stryd! This is even though they published blog posts(here and here are just a couple examples) about Vances’ book and the metric itself. WTH? Also, SportTracks implemented only for individual activities so there was no way to track this metric over time.
Analyzing the Data
So what is a data geek to do? Start tracking it myself I guess. I started by downloading my workout summary data from Training Peaks and then crunching the numbers in my favorite analysis tool, Qlikview. Below is the running results for the current training season in regard to Efficiency Index(EI). The formula is V(M/min)/rPwr(watts).
Efficiency Index EI by Month
Efficiency Index Components by Month
As you can see in the first graph, my EI has dropped a bit from December to February and then pretty much leveled out from there. Is that good or bad? Pretty hard to tell without looking at the components of it. Personally, I think EI, by itself, is pretty meaningless.
February was pretty much a wash month for me. I was pretty sick for a solid 2 weeks of it and spent the next couple weeks getting back to normal again. Looking at my average velocity for each month it has been increasing steadily, which I would say is good. My power numbers have also gone up too. April increased significantly due to having a 4-mile and a half-marathon race in there. So if both the components are increasing, then I am getting faster and stronger I guess. This leaves EI pretty much staying the same. See what I mean by EI being meaningless by itself now?
One other variable is that my weight has dropped a bit during the training months. I was surprised that this didn’t affect EI at all. I would think I would have gotten faster while using fewer watts and am not seeing that happening here either.
Looking my average heart rate versus the increase in speed and watts does show that hasn’t changed too much. This would indicate that despite those increases in output, my aerobic “engine” doesn’t appear to be increasing. So I guess I am getting more efficient.
Another running power metric has recently come onto the scene called Runner Effectiveness. This is outlined in a recent post by Steve Palladino on the Training Peaks Blog. This metric, while similar to Vance’s EI metric, uses Watts/kg in the denominator instead which brings the athletes weight into the mix. It also uses Meters/second for velocity in the numerator as opposed to Meters/minute in the EI metric.
Running Effectiveness = (m/s) / (w/kg)
Palladino shows how this metric can be calculated in Training Peaks’ WKO4 client software program as well. I actually have a copy of this program haven’t had a chance to really delve into it yet. Perhaps the EI metric can also be calculated here too.
For now, I calculated this one too in my Qlikview app. As you can see below it pretty much shows a similar trend, just not quite as drastic as EI above.
Running with power is still new territory and there is still some data gathering and analysis that needs to be done to get anything valuable out of it. One thing that is valuable now is that it is a good way to quantify your individual workouts for calculating TSS. Is it necessary though? I don’t think so. It is a lot of money for something that is just a “nice to have”. I think training with pace, heart rate and time is still just as good and will save you a couple hundred dollars. If you have one of the watches that track the new running dynamics metrics, I think that they are more worthwhile for those looking to improve their efficiency. High cadence, minimal ground contact time and vertical oscillation will help you track that.
Yesterday, I ran the St. Luke’s Half Marathon in Allentown, PA for the 4th time. Last year I had gotten a new personal best time of 1:45:10 since the first time I ran the race back in 2010 with a time of 1:46:41. 6 years older and over a minute faster.
This year my plan was to start out a little slower so that I had a little more energy for the last half of the race. The second half of the race runs through the Lehigh Parkway which has some crushed stone paths and this short, steep little hills that seem to suck the life out of my legs.
I also planned to down a caffeinated gel around the halfway aid station so I had a little extra energy too. Last year I didn’t eat anything and I thought that may have left me a little depleted at the end.
The race started out well. I was running in the 7:45-7:55/mi pace and was feeling quite comfortable. Heading into the Parkway I kept my cadence steady and slowed a bit on the uphills to try to save my legs a bit. The hills still took their toll on my quads but I managed to keep a little quicker pace than last year.
At around mile 9, I looked at my Garmin virtual race partner and it showed I was about a minute ahead of last year. Hold steady now! Next thing I hear someone say the 1:45 pace group was coming up behind me. WTH?
The pace group passed me on one of the final little inclines and it kind of took some wind out of my sails. I never looked back at my Garmin to see if I really was over 1:45 because I thought it would depress me more. Now I wish I would have.
So I crossed the finish line in 1:45:20. I didn’t realize until I got home, but I had finished 10 seconds slower than last year. It is a bit frustrating to think that a little extra effort and I could have beaten last years time. Well, one thing is for sure I am pretty consistent I guess. Next up, Ironman Boulder!
Last season I had to bail out on the St. Luke’s Half Marathon on the morning of due to a nasty stomach bug. I was looking forward to putting that behind me and getting another result here under my belt.
To make things a little more interesting, I also challenged a friend from work, who we’ll call “Stéphane” to protect his anonymity, to this race. Stéphane is a much younger, lighter and naturally faster runner than I am, but I hoped that the longer distance may help level the playing field a bit. Also, the added competition may help motivate me to a new personal best time.
This race had given me my current standing half marathon PR back in 2010 with a time of 1:46:47 at a 8:06min/mi pace. I was also about 20 lbs lighter(165lbs) and 6 years younger(41) back then. Could I really beat this 6-year-old PR carrying another 20lbs and being over a half a decade older? I felt like I could, but who knows.
The weather turned out to be perfect running weather. Sunny, clear and in the mid-50’s. I made it to the starting line without issue and with plenty of time. Stéphane and I chatted a bit as the 5k-ers took off. We were lined up pretty close to the front, so not to get caught up in the herd. I had got caught up in this the first time I did this race and suffered 2 of my slowest miles until I got past this group.
The gun went off and we were on our way. Stéphane was off and quickly out of site into the leading pack. I stayed back and tried to settle into a somewhat comfortable pace without getting caught up in the start of the race over-eagerness. I looked down at my Garmin and saw my pace was in the low 7 min/mi. Whoa…nelly!
My first mile was a 7:15 which is more like my 5k pace. I toned it down a bit and settled into around 7:30min/mi pace. While this seemed a bit fast for me, it was feeling right. I pretty much maintained this pace for the first half of the race, which runs along Martin Luther King Blvd and is mostly flat.
As I approached the first turnaround near South 4th St., I saw my coach, Todd Wiley, flying by very close to the leaders of the race. He would end up finishing 6th overall!
I soon saw Stéphane, heading back as I went by the Parkettes Gymnastics gym. He was about a quarter mile ahead of me, but still not out of reach if he had issues later on. But could I keep up this pace and catch him.
I hit the 10k split timer just past the 15th street bridge which read 46:57! This would be a 10k PR time for me??? WTH?!
I made the left turn over the steep little bridge into the Lehigh Parkway. As I hit the gravel path things started to slow down a bit. Was the loose gravel stealing my energy or was it the steep incline of the bridge and the little hill that followed taking the wind out of my sails? My legs were starting to rebel a bit.
As I reached the next two steep hills before the red covered bridge turnaround my pace was slowing to a 8:30 min/mi pace. I could feel the fatigue really starting to hurt now. I was starting to question whether I could sustain the personal best time I had started with.
I tried to hit most every water stop and get at least a mouthful of water in at each without stopping. I know that I don’t need much hydration a race of this duration. Getting a swig every 15 mins or so is good for me. I stuffed down an Amrita Bar right before the start and had another one broken up into pieces in my Spibelt if I needed more. The problem is getting the bar out of the Spibelt seemed like it would take more time to get out than it would be worth, so I pressed on.
After a couple slower miles in the parkway, I was able to pick things up a little during the 11th mile. Miles 12 and 13 were a little slow again as my legs were really hurting. I knew there was no catching up with Stéphane unless he was having a really bad day. The thought that that may be a possibility kept me pushing on.
I finally made the last turn down along Cedar Beach and up into J. Birney Crum Stadium. I was so glad to be almost done. My Garmin was reading 1:44 and some change so I was pretty sure I had a new PR, but not sure where my speed co-worker was.
As I crossed the line, I grabbed my medal and saw Stéphane standing there already finished. Ahhh! I got so caught up in trying to catch him that my PR seemed to be of no significance to me. I was also a bit disappointed that I slowed as the race went on. A sign that I probably went out too fast.
Ok, I just PR’d my Half-Marathon time by over 2 freakin’ minutes??!!! What the hell is wrong with me? It wasn’t until a little later when I met up with my coach who asked how I did. My initial reaction was that of disappointment but then followed up with I PR’d by over two minutes. He was like what? He was then like “that’s awesome!” I thought huh, yeah what am I disappointed about? I guess sometimes you can’t see the forest for the trees.
Last week I was talking about it with my strength coach, Fernando, and explaining how I was able to PR that race being 6 years older and 20 lbs heavier. Fernando said you are “older and faster” and I added “and fatter too”. Hence the title Older, Fatter, and Faster! Pretty funny.
I have actually dropped about 15 lbs so far since the beginning of this season and am on track to lose at least another 15 by Ironman Mont-Tremblant in August. Getting down another 15 lbs will only serve to make me that much faster. I have PR’d both races I have done this season, so I am off to a good start and the sky is the limit here.
Next up is the French Creek Olympic Distance Triathlon in late May. This will be a good indicator of where my triathlon fitness lies by putting together all the disciplines. I am anticipating some improvement in the swim with some of the changes in technique I have made that have improved my times in the pool. Running off the bike will be interesting to see if I can sustain my improved pace with some bike legs. 2016 is proving to be off to a good start to a hopeful season.
Six weeks ago I had this compulsive idea to sign up for the Blues Cruise 50k Ultra Trail run. I found out about the race through a friend who had done it a few years ago and it has always been floating around in my mind. I really didn’t have any real intentions to do another race after finishing the Steelman Olympic Tri in August. I always wanted to try doing an ultra-running event and something finally jarred me to sign up for this one. I had already fallen pretty deeply into off-season mode at this point and had already gained about 13 lbs, so getting into greater-than-marathon shape would be a bit of a stretch. I changed my goal to basically building up some longer than marathon endurance and not really focus on speed. Instead, I would just enjoy the being out on the trail for the day.
My weekly training for the race consisted of more difficult hour trail run, a bit slower less technical run, then one longer LSD run on Saturday, followed by another hour run the Sunday to shake out the previous days run. Rest days would be sprinkled in between. The long Saturday runs started out at 2.5 hours and worked up to around 4.5 hours before tapering a week out from the event. I have to say I really enjoyed getting off the road and into the woods for my training runs. I am fortunate to have a ski area a couple miles from my home that has some pretty technical mountain biking trails that make for serious trail running. Along with a few face plants and turned ankles. Trail running will quickly teach you to lift your feet.
I also had a week of vacation in Asheville, NC thrown in there which was a help. If you are not familiar with Asheville, it is a very outdoorsy and active place. There are vast amount excellent mountain biking trails in the Bent Creek Experimental Forest just outside of the city which make for fabulous trail running. So I was able to log some good miles down there trail running and mountain biking. We had planned this trip before I signed up for the race, but it could not have worked out better. I would also recommend picking up Trish Browns’ book “Asheville Trail Running: Taking Bent Creek and the Mountains-to-sea Stride” which is a great resource for the trails down there.
On Sunday, October 4th I headed down to Blue Marsh Lake near Reading, PA for my first trail ultramarathon. I hadn’t overly advertised that I was doing this event since I didn’t have any great expectations about my performance. I just wanted to complete it in whatever time it took. It is the off-season and this was to just be something fun and different to do. I heard that the ultra running scene is a bit more laid back and fun compared to the typical road running scene where people are obsessed with times and pace. That sounded a bit more my style and I was looking forward to it. Also, the thought of running in the woods all day sounded like a lot of fun. Wow…running just for the fun of it? What a concept?!
When I arrived at the lake, I followed another car into the Dry Brooks Day Use area where the race start was located. I followed him down to a parking lot where people were setting up some tables and tents. I was surprised to see that we were the first runners there. This was really odd given I was only an hour earlier than the start of the race. I thought “Wow…this really is laid back!” After I made a trip to the port-O-john, the guy from the other car asked if I was running in the race. I said “Yes.” He said, “I don’t think this is for the race.” Just after the words left his mouth a lady below yelled “Are you guys here for the race?” She then followed up with “it is down below closer to the lake.” Doh! So we drove around the other parking lots and finally found the one with the race start on the other side of the hill. There was a race sign down the road with an arrow on it, but it was past the point where we had made a left turn. Not a great placement.
Despite being a little later now, there still was not a large amount of racers in the parking lot. I headed over to the bib pickup table to get my race number(#295) and some swag. We got a really nice, soft long-sleeved tech shirt and a running hat plus some race flyers and RoadId coupons in the bag. We would also get a long sleeve 3/4-zip pullover for finishing the event. A pretty good deal considering it was only a $70 race. I have done tri’s costing double that and got much less.
It was a relatively cool & cloudy morning ranging in the low 50’s(F) which was perfect for a run. We had recently gotten a ton of rain in the last week, so I had no idea how muddy the trails were going to be. Fortunately, it stopped the day before and was holding off for the day. The forecast actually showed a high of 60 and partly cloudy with a bit of wind. I hung out in the car and just chilled while more people rolled into the venue. I told my wife Denise not to come because I didn’t want her to have to sit around there for what would probably be about 6 hours or so and it was silly to drive two cars there. I told her I would post updates on my Instagram and also turn on the Live Tracking feature on my Garmin 920xt so she could watch my progress in real time. That is if it worked this time and I had cell coverage.
At 8:10 I started getting ready. I was carrying my running Camelbak which was stocked with a few Amrita Bars and some Osmos Hydration mix packets which I was trying out. I also had a drop bag that I would pickup at the 18-mile aid station. I packed a PB&J, some rice chips, Skratch hydration mix and a fresh pair of socks. I had purchased a pair of CEP compression socks a couple days before the race, which I got more for the protection from the elements than the compression. I packed the other pair of socks in case I didn’t like the high compression socks.
And We’re Off…
I headed over to the race start, dropped off my drop-bag along the way, and lined up at the back of the start line. I snapped a quick selfie to let my wife know it was starting. It wasn’t long before they were calling out the last few seconds countdown to the start and then we were off.
The herd of around 400 runners gently ambled up the road and then broke off onto the trail. We then were down on “all fours” as we maneuvered under a gate that kept motor vehicles off the trail. It was starting to feel more like a steeplechase run than an ultra. I quickly regretted lining up so far back in the pack as I got stuck in a long line of slower runners as we made our way through the singletrack trails. I kept trying to spot some passing area ahead while still maintaining some view of the immediate trail coming underfoot. In hindsight, getting behind some slower runners may have been a good thing since it kept me from going out too fast.
Trail running is a whole different animal compared to road running. Not only do you have to pay attention to the typical personal things while running but you also have roots, rocks and hills to deal with. Not to mention other runners in front of you, which only gives you a split second to make decisions or else you are doing a face plant in the dirt. If you are not focused and in-the-moment while trail running, you will be done pretty quickly. And not in a good way. In addition, you most likely have a few pounds of water strapped to you and anything else you need to carry along. The aid stations are usually a bit more spread out due to the inaccessibility to the trails.
The First 10 Miles
The first 10 miles were pretty easy. The terrain was fairly flat and once I got past the slower folks I was able to pick up my pace a bit. My mile splits decreased down to a 10min/mi pace by my 10th mile. I did get slowed down by a bee sting on the back of my right calf and I turned my ankle about 3 times. I thought my new socks had a tag or pin poking in the leg, but I eventually realized I had been stung. The socks did a good job of protecting me from the weeds hanging over the trail, but they don’t do much against bees.
I also have a bad left ankle that frequently rolls on my for no apparent reason. This usually happens on flat terrain too, so I can never blame it on something when it happens and I just have to look stupid. Well, it didn’t fail to happen 3 times on the flattest part of the race. The last one really hurt too and I wasn’t sure if I would recover from it. Of course, it happened when I was in the middle of a long line of runners and everyone was asking if I was ok. It did eventually shake out and I continued on.
I took in extra water at each aid station along with some pieces of boiled potatoes with salt on them. In between aid stops I would nibble on an Amrita Bar that I neatly stashed into the little pocket on my Camelbak strap. I would slurp some water from the hydration pack routinely as I ran along. I was eager to drain it to get some weight off my hips, but I guess that would require taking a pee which I only did once.
Things Start to Get More Difficult
So much for the easy stuff. At mile 10 I finally encountered the much-anticipated hill known by mountain bikers as “The Judge.” On Strava it is known as the Stump Ln Climb. I have ridden it, or should I say walked my bike up it before, so I knew what I was in for. It averages a 14% grade of 3/10’s of a mile but has sections that are almost up to 30% grade. Going down the other side was no treat either. It was a little more of a switchback trail which helped level out the steepness.
Things started to get a bit tougher from the “The Judge” on. We climbed about 1000 feet in elevation gain over the next 6 miles, where we only about 800 in the first 10 miles. My pace started to creep back into the 11-12 min/mile range. My plan was to walk fast up the hills, bomb the downhills and steady on the flats. I started getting some tightness in my hip flexors which was fighting for my attention. I tried to ignore it and figured it would go away eventually or just be replaced by something else that hurt more.
I hit the mile 18 aid station and they retrieved my drop bag for me. I was really that hungry for my PB&J but could feel some hydration setting in. I was starting to accumulate some salt which was quite visible on my black Amrita tech shirt. I poured a Skratch Labs Lemon-Lime Matcha pack into my hydration bladder and topped it off with some water. I crushed my bag of rice chips and funneled it down my throat. I also snagged some more potatoes which taste so good during an endurance event. The mile 18 aid station is the one with the ladies in the German Lederhosen outfits, so I was in no rush to leave.
Eventually, I left mile 18 aid station and pushed on. After mile 20, things started really tightening up and hurt a bit. The 1300 additional feet of climbing we did over the next 10 miles surely didn’t help at all. I was also starting to cramp up in my inner thigh/groin area which I thought was odd for running. This would be more expected playing hockey or something with a skating motion, but not running. I finally had to give in and stop to stretch it out. I watched a handful of people that I had passed earlier trot by me. One guy who I had been running with most of the day went by and held his hands up saying “what’s going on?” That was a bit heart-breaking.
In Familiar Territory
I finally reached the dam spillway that feeds the Tulpehocken Creek which is familiar territory. I knew I was only a couple miles from the finish at that point and I was relieved. I also realized that the sun had come out and it was a particularly nice day. The nice breeze kept the temperature in the perfect running temperature zone. We spilled out onto the road that leads into the parking lot for the dam but it was mostly uphill. Everyone in front of me was walking and I succumbed to the peer pressure and joined them. The pavement just hurt. My feet hurt with every step. I could have really used a pair of Hoka’s right now. I was now looking forward to getting back on the trail again. Never happy!
We came to a sign that marked the entry back to the trail and made a sharp left which led to another steep climb up a grassy hill. Ugh! I started to run again as I reached the top of the hill. It was a good thing too. As I made my way around the hill I saw a trucker hat with the Wyoming bucking horse symbol on it. My foggy mind even recognized that hat! Under it emerged my wife Denise who decided to surprise me by driving out and meeting me on the trail. It was the push I needed to get me through the last mile or two. We ran together back to the parking lot that she parked at and then I continued on.
As I crossed the driveway a few equestrians were coming up the drive as well. One tried to shortcut me to the trail but I managed to beat them to it. I pushed on and back into a more wooded section again. The equestrians caught up to me again and were running up my back. I decided to let them pass since it seemed like they were going faster than I. They were not very friendly when they passed me and they slowed down again after they passed me. I was coming right up the back of them and it was looking as if I would have to pass them. At the last minute, they sped up and then I never had to deal with them again.
We crossed another driveway and Denise was standing there snapping a couple more pictures as I slowly ambled by. I knew this was the drive that I rode in on the morning to get to the race start so I knew I was almost there. We ran along a farm field and I saw a couple guys standing along the trail with finishers shirts on cheering us on. We made a quick left after that and then I recognized the start/finsh line area. I passed one other guy before the finish who looked like he was struggling a bit.
I finally reached the grassy area before the finish line and there quite a few people there cheering the finishers on. Right before I got to the finish line, a little girl came running across in front of me(see her in pic below) oblivious that I was coming. I had to slow down and grab her by the shoulder so she didn’t run into me. Everyone got a laugh out of it though. I crossed the line in 6:29:25, which was a tad bit slower than I had hoped, but I can’t ask for much since I only started training for it 6 weeks before. I was happy just to have completed the distance and was able to enjoy the day. I am hoping my legs will keep that endurance in their muscle memory so the next time I do an Ironman Marathon it will seem short.
Given this was my first “ultra” distance running event, one of the first questions I thought to myself and my wife asked was “Will you do another one?” I think probably will. I already started searching on UltraSignup.com. I don’t know if I will do the same race or even the same distance, but I have to say I really enjoyed it. I like being off-road and in the woods and I like the more laid back culture of the people that participate in these events. I would like to do something in a place that is a bit more rugged and deeper forest. I would probably want to try a little longer distance such as a 40 or 50 miler. Even a 100k may not be out of the question.
Ahhh the old love-hate relationship with tapering continues. While greatly anticipated, this break in training and the general feeling of malaise that comes along with it I did not. I guess you can’t have everything.
The Ironman Lawn…
I was finally able to get my lawn looking somewhat manicured with some extra time on my hands now. I had been cutting the front mostly so that it at least looked well kept from the street. The back was another story. I had cut a few sections so the dog could go do his thing, but most of it had grown so high it was going to seed. When my dog ventured into that territory I would see him occasionally jump high into the air as of the long strands brush up against his belly. Kind of entertaining.
Training-wise things were actually going pretty well. The somewhat shortened workouts had high intensity and I felt good while I was doing them. I had one of my best tempo run workouts of the season on Wednesday with a solid 7:50 pace in Zone 3.
FTP Test Gone Bad…
I had a 3 hour bike planned for Saturday, but I decided to break it up into a 1 hour FTP test on the trainer followed by a two hour easy ride on the road. I wanted to get an accurate assessment of FTP before my race. I felt it was also a good time between resting a bit and race to do it. I was hoping for a little improvement over last year(253 watts), but what I got at the end was nothing like I could have expected.
Obviously a bug in the TrainerRoad iPad app. Despite this issue I was able to calculate my FTP to be around 248 watts based on this test. A little depressing that I lost 5 watts, but really 5 watts isn’t that big a deal really. Perhaps it will help me to chill a bit on the bike. The main reason I wanted to do the FTP test was so I could plug in accurate number on Best Bike Split and get an idea of my race plan for the bike leg. It looks like it will be just a smidge slower than my bike leg last year at Lake Placid. You can check it out here if you are interested…
Bon Voyagey Bike…
On Sunday I had to take my bike down to Keswick Cycle in Glenside to drop it off for the TriBike Transport pickup on Tuesday. I finished up some last minute maintenance, did a final cleaning and removed the pedals. I also ordered the additional gear bag option too, so I loaded a duffle bag with my wetsuit, aero helmet, spare tubs and some tools. The TBT website said only pack aero helmet if in a hard case, so I put it in a cardboard box with some extra packaging materials too. Hopefull that should be ok. I filled out a couple forms at the shop and handed my bike over to the guy at the shop. Bon Voyagey! See you in Coeur d’Alene!
I stopped at a nearby Chipotle for lunch before heading to Whole Foods in Plymouth Meeting for our monthly stock-up on organic, frozen fruit. WF was rather crowded, so I was happy to get out of there.
I still needed to do a 1-2 hour run when I got home. It was brutally hot & humid and I was really not into it, so I decided to just run on the treadmill. I tried to load up this FitTrip app on my iPad which shows point-of-view(POV) trail running videos coordinated to your heart rate. Well it didn’t work so well. Downloading the videos took forever and then when they finished it would pop up a message saying it failed! WTF! I eventually got one to download successfully and then it would not connect to my HRM using the ANT+ dongle. Ugh!
I finally gave up and just watched some similar videos on YouTube which worked fine. I had unfortunately wasted a bunch of time trying to get that working. I ended with only about a 7 mile easy run, but I figured that was good enough.
Geekin’ Out on Training
Training volume this week was basically chopped in half. Still managed to miss one of my 3 strength training workouts though. No sense is cramming now right?!
A few red marks on the old HRV training guide this week. Body is recovering a bit so this is expected. Hopefully next week things will pick up a bit.
The PMC chart shows the plan for the taper. The pink line dropping is the fatigue withering away with the form(yellow) increasing. Fitness(CTL in blue) declines a little bit, but it will be worth it.
The HRV timeline took a bit of a nose dive during this first week of taper. It make sense since I felt a little crappy. Things ended on a high note on Monday AM so it looks like recovery/taper is working. Hope that continues until race day.
That’s all for this week. Next week things should get easier and hopefull start feeling great again.