Weekly Training Plan/Log

Training Week #/i>
Activity Mon Tue Wed Thu Fri Sat Sun
Run














Elevation Feet Feet Feet Feet Feet Feet Feet Feet
Cross-Training
Garmin Connect - Profile Information for Steven_LaBranche

Tuesday, July 29, 2014

Training Stress Indicators - Heart Rate

This past weekend was my first planned Back to Back session.  16.5 miles Saturday followed by 17.0 miles on Sunday.  I've gone into longer runs with more fear and concern than this weekend.  For me, a four or five hour training run generates some anxiety (unless I have the opportunity to do it in the mountains!).  Entering the weekend with 5 hours of running felt like the normal day-to-day grind.

I was aware this would put my body into a level of stress.  So leading into it, I started tracking my heart rate more closely, even incorporating a daily Orthostatic Heart Rate (OHR) test.  Using heart rate to gauge stress is a well understood science.

"Why would such heart-rate accelerations be a warning sign for overtraining?  Bear in mind that pulse rate is controlled by the nervous system, and the nervous system is one of the first three systems to show signs of overtraining. Thus, nervous system irregularities show up as changes in heart rate, which you can monitor quite easily, without the need for expensive endocrine or immune-system tests."  - Sports Performance Bullentin (http://www.pponline.co.uk/encyc/0410.htm#)

Previously I performed this test regularly when preparing for my first marathon in 2011.  I found this two minute test to more indicative of training stress than purely tracking deviations in my morning sample low heart rate.  As an example, a two beats per minute (bpm) variance increase in my low morning heart rate could mean absolutely nothing.  Alternatively, it could also be an indicator of training stress.  Effectively, the data sample is too small to make a determination.  It was one number.  The best test I found was the two minute long OHR. Deviation over a two minute period is a sign of stress (or rest, depending on which side of the trend line I am on).  I trend both 5 days and 3 weeks.  This allows me to see if I am currently under extreme training stress/load by measuring today's OHR against both the 5 day and 3 week.  Theory calls out the 15/20 second and 90 second interval as key markers.  For me, a deviation of +5 bpm above the norm represents significant stress from yesterday's workout (or the onset of an illness).  Negative deviation represents recovery/rest.

My sample period is still too short, as I started performing the test July 23rd.  With a large enough sample size, I can look beyond the acute stress of a single day (referenced above), and spot cumulative strain when comparing the 5 day to 3 week trend.  With this, I will be more cautious with my variance.  A +5 bpm increase from my 5 day average to 3 week is extremely high - something I don't believe I want to get to.  This represents an extended period of stress, which can result in injury or illness.   Currently my variance between the 5 day and 3 week is negative, which is a good sign that general training load isn't to the point where burnout (or serious illness, ie Mono) will happen.  This is a risk with multiple weeks of intensive load.

After this weekend, I was eager to see how my OHR stacked up on Monday morning.  Unfortunately, it was a bit late as I came down with something over night Sunday (feverish).  The OHR did show the spike, as I was considerably higher almost the entire 2 minute cycle.   I was well over the +5 bpm, with several intervals hitting +11 bpm above norm.  This called for a day off - not just from running, but included any core and flexibility activity.

Biomarkers as of Monday, July 29 2014






In hindsight, the illness wasn't entirely the result of the hard workouts.  We attended three birthday parties over the weekend.  My ability to follow a regimented nutritional recovery plan was off the table. All workouts weaken the immune system - so it is vital to get the nutrients in place quickly to return the body to homeostasis. My eating habits this weekend significantly hampered my ability to do so.  To compound the problem, I was stung by a yellow jacket Sunday evening.  Normally not a problem for me, as I have no allergies.  Now knowing my state at that point, I believe the body simply was overwhelmed with fatigue and a weak immune system, which made me vulnerable.  Tipping point...f'ing yellow jacket.

The fever broke mid/late afternoon Monday.  Despite the urge to do something, I understand the importance of rest to an athlete's development.  This was, after-all, supposed to be a recovery week.  So day off, and early to bed.  Tuesday morning OHR showed marked improvement, but still noted several sample points between 5 second 7 bmp above 5 day trend (OHR Deviation Analysis, 5 Day Deviation line), so today will be another rest day.  Generally I feel back to normal. As such, I will not give up on some flexibility and core work (Wharton's AIS and Planks today).  Let's see what tomorrow shows!



Friday, July 25, 2014

Vermont 100 Pacer Duties

I completed my first ever ultra pacing duties. It was exhilarating. The only person with a deeper high, would be my runner. Sean successfully completed his first 100 mile effort, breaking his target goal of 24 hours by nearly 90 minutes. Going through this has confirmed many of the pacing theories I had researched.  I knew the value of a pacer, having only survived Zion 100 with a pacer and well prepared crew.  I wanted to prove that same value to Sean.  A good pacer can save a race and reduce the pain for the runner.  Success brings great joy for both pacer and runner.  Failure, while isn't considered an option, lingers in everybody's mind. In my young ultra career, I haven't experienced a DNF, and don't know what that translates to emotionally. Let's try and keep it that way. 

Pretty House Aid Station (21m). Sean with Colleen
Sean's crew was fabulous.  They proved to be a valuable motivational tool late in the run.  The crew, made up of his mom, three cousins (who flew in from California for this), and his girlfriend, were all novices.  Not only with how to crew, but the ultra as a whole. They caught on quickly though. I helped guide them with initial instructions on to best support him, and sent them on their way to deal with it solo early in the race. After the start, I didn't see the crew until mile 70.  At Camp 10 Bear (69.6mile) Aid Station, the crew showed up with smiles, and gave me a thumbs up stating they followed my directions and felt Sean was doing well. For those that have never crewed, the most basic task is to stay positive (smiles, encouragement) and do whatever the runner asks.  This team had that task down pat. I asked the crew to be a little more proactive, and take the water/food bag (Nathan's, Camelback, etc) and water bottles from the Sean.  Maintaining continuous dialogue with the him is required. Often, through the later stages of the race, a runner is mostly motivated to see their crew.  They want to know how long till the crew, as opposed to the end of the race. Seeing familiar faces and hearing voices of friends and family is a significant motivator. Sean's crew flourished. They showed no signs fatigue, despite the nearly 20+ hours lack of rest. Given they only saw Sean for maybe a total of 20 minutes between start and finish, demonstrates their dedication and support.  A+ CREW!

Not only did the crew help Sean, but they helped me.  As the crew could attest, I was extremely nervous about falling short for Sean. Yeah I knew I could run 30 miles. But my fear lingered about my ankle giving out, or that I just couldn't have the endurance to pull him through. I had coordinated a backup plan with one of the other Shenipsit Striders to come in should I tap out. Dave was such a trooper, staying with the crew all night just in case I bailed. 

The first few miles after mile 70 is mostly uphill which gave us plenty of opportunity to walk and talk.       Sean made it clear the downhills had done a number on his quads. This is nothing unusual, in fact this is quite common within the ultra marathon community. Sean had prepped for the downhills, but it was obvious not quite enough.   We also worked out some logistics.  Typically this is addressed before the race- but due to our familiarity with each other's personalities,  we left it for discussion during the run. For a novice pacer I'd suggest at least discussing who should lead, does the runner want the pacer to engage in conversation, should the pacer continue to talk even if the runner is silent (think comforting background music).  Upon meeting up with the runner, pacers need to do a systems check of the runner. What are the pain points? How are they mentally?  Any symptoms of dehydration didn or hyponatremia?  Sean was feeling good mentally. Physically his quads were fatigued, which he noted slowed his pace significantly over the last few miles before Camp 10 Bear. This became obvious to me as I watched his gait down hills, he was sitting back like a runner with shredded legs. I decided to try and mix things up.  During a nice single track downhill section, I asked him to open up his stride, much like he did during our training runs together. I reinforced that this was not going to be permanent effort, but let's just try it a few times on a couple down hills. On the flats it was return to norm. Back to his version of the ultra shuffle. I did not want to push too long, this late in the race, and risk a complete meltdown with less than 30 miles to go. We continued to walk up hills, which took little bit of training for me. I tend to walk faster than Sean, and most runners in fact. So I slowed my stride down on the uphill, and continued to put the emphasis on him moving quickly with the downhills. For those that are not familiar with the Vermont 100, this course has a very large percentage of dirt road. This is extremely demoralising. It it is as if you are running on pavement for most of a hundred mile run. This is not a dig on the race, it is what the course presents to you as a challenge. During these sections the long dirt road running, I made no effort to push him.  Whether it was flat, uphill, or even downhill.   

Timing of pacer antics., motivational speeches, and/or general distractions is important as well. Surprising my runner with impromptu comments, questions, sounds, movement, etc were all done with the intention of diverting the mind's attention away from itself.  On the lengthy dirt road, my job became one of distraction and encouragement. I never attempted to push the pace when we were off of single track trail. During one long section of road, Sean had taken a turn towards the mental abyss. I knew he was either there, or on his way to dungeons. I remember a juggling with the dilemma. Do I try and distract him now, or delay until he has hit the bottom of the pit? My fear was if he was on the downward spiral, anything I say or do would have no effect, as the downward momentum is in place already. I elected to wait for a lengthy period of silence.  Then I made my move.  I am throwing him the rope.  After a few minutes, under a sliver of a quarter moon and our headlamps, I spread my arms out and performed a 'fly by' in front of him.  Complete with sound effects.  With a smile, and a bit of a chuckle, I received the response I was after.  "Oh Steve, this is why I brought you along".  Good.  He grabbed the rope.  We are working him out of the pit.  

I've known Sean for nearly a year.  We've run probably a dozen times, accumulating 40+ hours of trail running time.  Through these long runs together, we've learned a lot about each other.  I do know Sean isn't averse to having a conversation during a long run.  Some runners prefer silence.  Sean and I aren't that type.  As his pacer, I needed to find the subject 'du jour' that will spark a two way conversation.  If Sean is talking, he isn't thinking about the pain.  So, throughout the early parts of the run, I'd throw out different topics to see what stuck.  Eventually, I found the golden nugget.  Anything trail running: Rob Krar's racing schedule, 2014 Western States 100, HardRock 100, etc.   Throughout the run, when Sean appeared to need a distraction, I'd bring up a related topic.  Most times he responded and we would chat for a mile or two. Sometimes I was met with utter silence.  In those instances, he let me know to keep talking as he was listening.  THAT....I....CAN...DO!

Sean hit his lowest point around mile 97.  The 'ultra shuffle' was significantly slower than anything we had done previously.  My casual walk was only slightly faster.  He openly stated that his knee was bothering him, 'more than just soreness, it may be something bad'.  Shortly there after, he complained of dizziness.  DEAR GOD, DON'T DO THIS TO US NOW!  At this point, any thought I had of a strong finish was quickly thrown overboard.  This was the only time that I worried we wouldn't finish.  3 miles to go, we are in jeopardy.  My ship was sinking, I needed to find a way to get him across the finish line at any cost.  PERIOD.  I encouraged him to walk more.  The effort vs gain just wasn't there while he vainly attempted a 'run'.  I was no longer trying to distract him.  At this stage, I am seeking ways to drag his ass to the line.  

Around mile 98 the course had been modified.  We were warned during pre-race, to watch for the saw horse.  The land owner had enough of whatever runners had done in years' past.  Fortunately, the neighboring property was opened up to the runners.  Unfortunately, the recently cut trail (maybe a month old?) hadn't had enough foot traffic to really make it a trail. Sure, it was cleared of trees, shrubs, and other general ground forestation, but the surface wasn't stable.  Lots of undulations. This is where weak ankles meet there next rollover. Footing wasn't solid.  To compound our problem, beyond the body beating, was one of the biggest ascents we had to deal with since mile 70.  At 2AM, all that was visible beyond 10 feet, were the green glow sticks. Upon seeing each glow stick off in the distance rise higher than the previous, we realized the size of this next ascent was significant.  It was a bit demoralizing.  My heart sank even further as we hiked the ascent and I peaked behind us. I could see a pair of headlamps rapidly approaching us.  While Sean wasn't concerned about competition with other runners, I wanted to catch every pair of withered legs ahead of us.  This set of headlamps potentially represented only the second runner to pass us during my 30 mile pacing duties.  Given Sean's condition, I succummbed to the notion that we lost a place.  As we started to crest the lengthy hill, Sean said , "Let's go".  Initially I thought it was the runner behind us, as they had closed to within 20 yards and I could hear the conversation clearly. It only took a moment to realize, IT WAS MY RUNNER.  Maybe we have some juice left.  We ran a short bit to an open field, which presented us with a very long and gradual descent.  I tried a technique I used earlier to get him to move quickly on the downhills.  "Open up the stride Sean, stop sitting".  We were moving now, almost with a purpose.  He had a second wind with maybe a mile and half to go.  After turning out of the open field, we both looked back and saw four headlamps.  SHIT, TWO RUNNERS!  Most important to me however, was that Sean looked back.  SEAN IS RACING!  He let me lead, and I pushed. It is the one thing both of us agree that I bring to the table - I have the speed. Sean stuck.  I pushed harder.  Sean stuck.  We ran up, down, flat - - nearly all out.  I was talking the entire way.  Trying to keep Sean in the zone "Focus on your breathing", "short easy steps on this up hill", "open up the stride here".  We had another opportunity, with about 1/2 mile to go, to look back. The lights were gone.  I expected Sean to ask to pull back on the pace and relax to the finish. However, the antelope wanted some more space from the lions, so we pushed all the way to the finish line at 2:37AM.  Greeted by spectators, friends, and family.  100 miles. Under 24hrs. There, Sean got what he wanted most, a hug from Colleen. My task completed. Done. Hell of an experience.

100 Miler Finisher's Buckle
Sean with RD
I AM DOING THIS AGAIN







Friday, July 18, 2014

My First Pacing Duties

I am super excited about helping my friend, Sean Greaney, complete his first 100 mile ultra marathon this weekend at the Vermont 100.  He has put a lot of time on his feet in preparation for this event, and I've parted about all the knowledge I have - given my 'oh so expert' level (1 x 100 miler done in my career).  He sounds ready, as he is well tapered and has a good mix of excitement (racing engine light on) and trepidation (all systems being checked and rechecked, adrenaline up).

Being a pacer doesn't come with zero level of anxiety.  I am nervous.  "Will I be able to perform my role well enough?"  "What will I need to do to get him across the finish?"  One of the challenges of a 100 miler is the vast issues that can arise.  I am performing an old military approach by "what if'ing" this to death. Extra Gu, Stingers, Water, Salt tabs, blister protection, wipes, batteries, etc. Picture a marathoner picking up a pacer with 1 mile to go, and the pacer has a backpack full of gear for their runner. Mule.  That is me.  (note, 'muling' isn't allowed at VT100.  All my gear is for his 'safety').

My portion of the run is 'only' 30 miles. It will tax me, but nothing that I need to overly plan for.  This week's training schedule initially caused me to squirm a bit.  Point 1 - this is a training cycle week, and not geared to resting;  Counterpoint 2 - pacer's job is to do everything possible to get their runner across the finish.   Given my racing isn't until late fall, sacrificing a few days in July to ensure I am fresh for this isn't such a big deal. My target of 73 miles will drop into the mid 60s.  Not like my training program will fall apart or anything.  One thing I've learned is being flexible is the key to proper balance. I feel very good about taking a bit more time off and lowering the mileage.  I am very comfortable I will meet him under the moonlight ready to successfully perform my role as pacer.

Here is a good write-up about the pacer's experience.  While quite hilarious, it does part very valuable lessons to a noob.

http://footfeathers.blogspot.com/2012/06/how-to-be-ultra-pacer.html

Monday, July 14, 2014

Week # 6 More than a Summary...

Recovery week.  By all accounts, I was recovered very early in the week.  Typically if I feel good by the middle of a recovery week, I use the weekend as a ramp up into the next training cycle.  I have yet to find any impact to doing so.  Whether I ramp up, or continue to use the weekend as part of the entire recovery cycle, the next week I always feel fresh.  If I need the weekend to help recovery, I always come out primed come Monday.

Ainsleigh on a short trail in Bozrah
Of the 38 miles for the week, nearly half came in on the weekend.  Though it was a mild one from a mileage perspective (18 in total).  This week I have started to use my heart rate monitor, targeting zone 2 (118 - 131) for all my runs starting Thursday.  My pace has slowed, but not to a crawl.  The biggest change that I need to perfect is my pace variability.  Depending on the slope, I either need to run harder or slower to stay in the zone.  Mini-fartlek, without exerting.  I have found that the runs are not as taxing on me.  Starting to think about putting back to back 10-12 mile runs together is less daunting.

Something for any of you medically trained folks.  I have always known that my effort at the start of my runs is higher for approximately a mile (note: this happens whenever I do not conduct a full warm-up.  Typically I stretch and run).  There is a point where my effort suddenly drops, which can correspond to a faster pace.  This week, I've been monitoring the HR at the start to see what is going on.  Interestingly enough, I've found the transition point at the 5 - 6 minute point.  At this point, my HR will drop 30 - 50 bpm and my pace can quicken an additional 30 seconds per mile with no effect.

For the week:

  • 2 strength / core days (Medicine Ball and Pedestal Routine*)
  • 2 days of Sand Routine (Ankle Strength)
  • 4 days Wharton's Active Isolated Stretching Routine (1-9)
  • 1 day of Runners' Yoga (Hips and Hamstrings)

Miles: 38 Miles
ToF: 5hrs 52min
Elevation: 1,686 ft (44 ft/mile)

* = 15 minute Pedestal Routine (Kansas State University Coaches Johnson and Smith):

  • 10 reps for each leg of Prone, Elbow-Stand, Single Leg Raise
  • 10 reps for each leg of Supine, Elbow-Stand, Single Leg Raise
  • 10 reps for each leg of Prone, Hand-Stand, Single Leg Raise
  • 10 reps for each leg of Supine, Hand-Stand, Single Leg Raise
  • 10 reps for each leg of Lateral, Elbow-Stand, Single Leg Raise
  • 10 reps for each leg of Lateral, Hand-Stand, Single Leg Raise 
  • 10 reps for each leg of Prone, Flexed-Knee, Single Leg Raise
  • 10 reps for each leg of Supine, Flexed-Knee, Single Leg Raise
  • 20 reps of Crunch, low reach
  • 20 reps, low reach, with Twist

Tuesday, July 8, 2014

Feeling Great!

Today was fan-ferking-tastic! 

Something (special) is going on.  My recovery time has drastically reduced.  I don't know if the body has adapted to this level of stress, if my training approach is allowing for quicker recovery, or is it the change in diet.  I believe it is a combination of all of them.  The diet is significant, closely resembling a Vegetarian's meal plan.   My wife and I are spending significant amount of time figuring out how to get the right nutrients, down to the macro and micro level.  This is beyond when to get carbs and protein.  Many athletes profess to the magic of an effective diet (and sleep) to improve performance by reducing recovery time.  The effort has paid off for me with slow weight loss (10 lbs in 10 weeks).   We continue to investigate other diet options.  Currently much of our attention is learning about Metabolic Efficiency Training - which is a philosophy on how to transition your body from a predominant carb energy source to fat burning.  We all, even the Kenyan athletes, have enough fat to support them through multiples of marathons.   I'll write more on my diet selection later.

Back to feeling great.  Sunday was a long 4hr trail training run.  Typical coastal course....flat, with nice ocean breeze.  I didn't make this any harder than necessary. I increased the run to 4:11, simply to hashtag a marathon distance for the day's run.  Over the last two weeks, I had bagged two 4 hr and one 3 hr training run - culminating in 135 miles over that period.   I had never run that many super long runs like this.  While my approach in the second week (60 miles) allowed for significant recovery from my 75 mile supercompensation week, I was due an easy week.  This week's target is 35 miles.  Given my inability to walk up and down stairs Sunday afternoon (along with a 2 hr nap), it signalled relief was an absolute must.   I felt loose enough to run Monday, so I hit the high school track (ran on turf inside of lane 1) for an easy barefoot 3 miles. Much to my surprise, there was almost no residual effect from Sunday.  Tuesday (today) was another barefoot 3 miles flat track run.  I added the Wharton's Active Isolated Stretch routine, new sand routine (Kansas State Coaches Smith and Johnson cover this foot and ankle strengthening routine
in their DVD), and medicine ball circuit.  I wore the HR monitor to ensure I stayed in the correct zone (110 bpm).   I felt very good today - no signs of fatigue.  Moving forward, I hope to incorporate strength exercises at least two/three times a week.  Given my history of ankle sprains, the sand routine will be a permanent fixture for the next month (three or four times a week).  I closed out the day with my standard set of running form drills (fast feet, high knees, and kick backs).  

Summary of non-running activity:

Wharton's AIS
  • Single Leg Pelvic Tilt
  • Double Leg Pelvic Tilt
  • Bent Leg Hamstrings
  • Straight Leg Hamstrings
  • Hip Adductors
  • Hip Abductors
  • Quadriceps

Tools of the Trade: Long Jump Pit (Sand Routine), 3kg Medicine Ball, and Ribbon (Wharton's AIS)
Sand Routine
  • Toe Walk
  • Heel Walk
  • Feet Out (Duck) Walk
  • Feet In Walk
  • Roll Ankle In Walk
  • Roll Ankle Out Walk
  • Foot Crawl (...this one is a challenge, expect significant foot and toe fatigue)

Medicine Ball Circuit (1 set each, 10 reps per side)
  • Wall throws (chest, side/hip, overhead)
  • Wood Chops
  • Standing Leg Lift and extension (hold ball out, chest level)
  • Reverse Lunge with Twist (needs work, lacking balance - aka weak core)
  • Single Leg Deadlift (highlighted my poor balance, proprioceptive issues)
  • Push up with Ball Exchange
  • Single Leg V-Up