Showing posts with label pace. Show all posts
Showing posts with label pace. Show all posts

Monday, December 29, 2014

The two dimensions of running speed

Sample combinations
Today's run (street): 3.4 miles

I was looking at the metrics of today's run on Garmin Connect and thinking about the factors that determine pace. I recently put a new battery into my foot pod so I can capture my cadence as well as time, pace, heart rate and elevation. Besides steps per minute (SPM), the foot pod also shows average stride length. After looking at new and past data, I'm seeing some correlation to pace.

When you think about it, running speed is controlled by two factors -- how far you are propelled with each step and the frequency of these steps. As an example, last year I ran the Hot Chocolate 5K averaging 178 SPM, but with an average stride length of 1.03 meters. That translated to an 8:46 pace. A month later I did the LIRCC Hangover Run averaging 172 SPM and .95 meter stride length and averaged 9:50. Fairly small differences translated into almost a minute difference in pace.

Interestingly, my data shows when I run intervals, my stride length drops to half a meter. However, average cadence jumps up to 188. That usually results in an 8:00 pace or better. I've read that, to improve performance, increasing cadence is a better approach than increasing stride length. I'm sure that's due to the danger of over striding which can put excessive pressure on the knees, tendons and ligaments.

Today both my cadence and stride length were middling and I ended up pacing in the mid 10's. That was by design as I wanted to minimize wear and tear on the muscles that may be aggravating my sciatica. Once I'm past this annoyance I'll start playing more with cadence and will try to make my way to the ideal (180 SPM). I'd like to run some intervals this week get that started, but I want to make sure I don't do more harm than good.

Friday, August 8, 2014

Doing the wave on a friendly Friday

Howdy neighbor!
Today's run (street): 4 miles
Tuesday's run (treadmill): 2.3 miles

In the scheme of things, adding a couple of miles to your weekly volume doesn't make a lot of difference. However, when you are only able to run three days a week, adding another workout day provides some psychological benefit. Or perhaps it lessens guilt. Same thing. So for the past two weeks, I've dutifully risen at 4:00 AM to up my weekly run count to four and get my mileage a little closer to where it used to be.

The rest of my week's running happens between Friday and Sunday and I kicked that off today with a 4 miler around the neighborhood. I work from home on Fridays and that saves time from my long commute. I try to get outside early so I can finish my run and start my business day at my usual time. Since I prefer early running, this works out fine. Today it worked out great.

I've written dozens of posts complaining about running the same streets of my neighborhood, day after day. I thought about that this morning as I covered a section that I've probably run more than 800 times over the past six years. But every one of those runs has differed in some aspect. There's always a story.

Getting out early provided great weather conditions with temperatures in the mid 60's and humidity at its lowest point in the day. As I ran, I noticed some people in business clothes walking out to their cars, ready to start their commute. Perhaps it was a TGIF mindset, but almost everyone waved or said good morning as I ran by. I crossed paths with a couple of runners and they gave friendly waves as well. Even people in cars waved as they passed. Lots of waving today.

That pleasantness carried over to my run. I felt good enough to push my pace and ended up averaging about 20 seconds per mile better than my current training pace. I had hopes that it would be even faster than that, but I'll take what I can get. As much as I enjoyed my friendly neighbors today, I'm looking to get away from my local roads over the weekend. The Bethpage trail would be an obvious choice but since I'm not planning to run Dirty Sock this year, I may go to Belmont Lake and run the course.

Sunday, June 15, 2014

Father's Day track workout with the 'skeeteers

After 14 laps of father's day fun
PHOTO COURTESY OF THE PETITE PACER
Today's run (track speed work): 14 x 400's = 3.5 miles

Happy Father's Day! I'm certainly a happy dad, and I've had a great day. The morning started with a track workout with my running buddies. I usually do these workouts on the local high school track so traveling to SIOR's town was a nice change. My local track runs around the football field and is very isolated, while this track is located within a neighborhood and it felt somewhat quaint.

SIOR ran from her home and I saw her running on the road as I pulled up to the track. TPP was already there, and we started our workout a little after 8:00 AM. The weather was sunny and the temperature was still in the low 60's.

On SIOR's suggestion we alternated easy and hard quarters. Our original target was 12 laps (3 miles) but we all ended up running 14. We took off easy and I was able to hold a conversation as I ran. After one lap we dropped a gear and switched to race pace. I liked this method, using a jogging lap for recovery rather than stopping for a minute between hard laps. It kept my heart rate up and made it easier to transition to the faster paces.

SIOR and TPP burned up the track the first couple of times around and I envied their speed. I did fine, averaging somewhere within the 7:00 minute range on my fast laps. I can move along when I know that I only need to endure a hard effort for two minutes or less. TPP had a case of "Too much fun the night before-itis" and took it easier on her later laps. It was no surprise to anyone that SIOR flew through her laps. At one point I tried to catch up to her, but I didn't make much progress.

Me and SIOR finishing an easy lap
PHOTO COURTESY OF THE PETITE PACER
Per tradition, we followed our workout with a visit to Starbucks. SIOR and TPP caught up on Game of Thrones and we covered a lot of subjects. Interestingly enough, there was little mention of running. I needed to cut it short because I had some Father's Day activities. My wife and kids were going to take me to Lemonleaf Grill for lunch, but it didn't open until 1:00 PM and I'd worked up quite an appetite from all that speed work. We ended up at Quetzalcoatl in Huntington, so it was Mexican rather than Thai. But it was really good, as usual.

It's been a great Father's Day spent with friends and family. I am so glad that I got to see my Runska-buddies and do that workout with them in such beautiful weather. The day isn't finished and I'm looking forward to more family activities this evening.

Saturday, June 14, 2014

Addressing my need for more speed

My experience today
Today's run (street): 5.1 miles

I'm back into a three day running cycle and I ran in the neighborhood yesterday and today. My morning schedule was tight, so I needed to get outside early. Fortunately, it was still relatively cool and (bonus) not as humid as Friday. I had no route or distance in mind, but I did want to cover at least five miles.

Like yesterday, I started with good energy and tried to establish a faster pace from the start. It seemed a lot faster than it was. I still find it curious that putting in the same effort compared to a year ago will typically yield a 30 sec/mile slower pace. I'm not planning on doing any races before Dirty Sock, so I'm not really upset about that. Still, I'd like to gain that time back if I can.

Tomorrow the Runsketeers will get together for our first group track workout. I look forward to seeing how fast these two speedsters can run when they don't need to reserve energy. I'm not going to be able to cover as much distance tomorrow as I would on a typical Sunday, so this week's mileage total will be extra low. But track miles are quality miles. If I can figure out a way to add one more workout a week to my running schedule, I can get back to pre-commuting weekly volumes.

Tuesday, May 27, 2014

And all this time I thought I was running!

 It's official!
This past Sunday I wrote a post about my declining pace performance. I showed a graph with speeds in MPH based on GPS watch data. My Garmin often under-counts my distance, so the speeds on the graph are probably 3.2-4% slower than my actual average speed. I was a little surprised to see a comment that seemed targeted to the lowest pace on my graph. The comment said, "The official name of anything below 5.5 is 'walking.'''

This is good to know, because all this time when I was running 10-something paces for ten or more miles on the Bethpage trail, I thought I was actually running. But what about those race-walkers that reach paces in the 6:00/mile range? Very confusing. Technically, I believe it is considered running when both feet leave the ground, versus walking, where one foot always remains on the ground.

I know this commenter was just being sarcastic (if a little mean). Perhaps he/she can clear up some other questions for me, such as, "What's the official difference between rapping and singing?" In the meantime, I'm declaring anyone who calls themselves a runner to be one. And no matter what speed they actually run, it's still running.

Saturday, May 3, 2014

Liked my run and loved my park

Been there, didn't do that
Today's run (street): 4.6 miles

I'm working through my new work schedule and trying to find the time to fit in all my training runs. I caught a break on Thursday by working from home. That was good for over six miles, something that I couldn't have done if I was driving to my office that morning. I was back to the drive on Friday morning and couldn't fit in a run before that. The saving grace is that my new office is in an enormous building and I cover a lot of ground on foot during the day.

This morning I targeted 4 miles around the neighborhood. I plan to run as close to 11 as I can on Sunday. Just for a change, I wrapped my run around the neighborhood, following Jericho Turnpike west to South Oyster Bay road and then onto Terrahans going east. The change of scenery was welcomed and I figured that this new route would distract me for the first two miles and make the overall run feel shorter. That sort of worked, even though I added another 2/3 mile to my distance.

I feel that I'm running exactly the same way and expending the same amount of energy that I did a year ago. Now my typical pace is now almost a minute slower. I used to be able to sustain sub-9 paces with a focused effort. These days I'm happy when I see that I've averaged mid-9's. Today I didn't even break 10:00. I'd hope that my weekly speed workouts would have moved the needle, but I've seen little payoff from it.

Later in the day, we all headed to Caleb Smith State Park in Smithtown for "I Love My Park Day." Last year we planted a tree and were looking forward to this year's tasks. However, when we arrived at noon, the event organizers were wrapping things up. Our information said that activities would go until 3:00 PM, but it was incorrect. We were disappointed, but it didn't prevent us for spending an hour hiking the trails.

If everything works out, we'll have a Runsketeer run tomorrow morning that includes a couple of guest runners (J who I met on the bike trail two weeks ago and his wife). I'm very curious to see how I hold up for 11 miles or more. Only two more Sundays before the Brooklyn half, and I need to make them count.

Tuesday, April 22, 2014

Boston is back and back to the track

Tracking Marathon friends on BAA.org
Today's run (track intervals): 
6 x 400's plus 1 mile warm up/cool down

Yesterday was a big day for running, with the 118th Boston Marathon taking place (thankfully) without incident. Both SIOR and TPP's sister ran great races, and it was fun to watch their progress using the tracker on the BAA website. How perfect that Meb Keflezighi won the men's race. I'll never look at Skechers the same way again. I was disappointed when Shalane Flanagan dropped back after leading for so long, but she scored an American course record while finishing seventh overall.

The marathon would have been great inspiration for a Monday run, but I held to my rest day to ensure I'd recover from Sunday's long distance. Speed work was on the calendar today, and since the schools are closed until tomorrow, I went over to the track to run intervals. I've done weekly speed workouts all throughout my half marathon training cycle, but I hadn't done a single set on the track until today.

The temperature was 55° when I arrived at the high school. Although I was wearing shorts, I was concerned that having two top layers would cause me to overheat. With the 6 MPH wind, it felt chilly enough to keep them both on the entire time. The high school cross country team was assembled at the southern end of the track infield and I wondered if my workout would happen alongside a crowd of much faster runners.

My HRM now takes 5 minutes to sync
It turned out that I didn't need to share the track at all. The coach was having the team run laps barefoot on the grass, first slowly, then at speed. While that was happening, I started my workout with two laps around the track at around 8:50/mile followed by 6 x 400's at 8:00/mile. I finished with a half mile cool-down that I ran at a mid-9 pace.

It was good tactical workout. I probably could have added another two quarters, but I wanted to keep it light today. I'll try to cover much more distance tomorrow. With the race on Sunday, I'm not sure what to do about my weekend long run.

Friday, April 18, 2014

Cadence increasing, visibility high

Artist's rendering using Google Maps street view
Today's run (street): 3.3 miles

I missed Tuesday's run and needed to make it up today, although the Higdon plan called for a rest day. I felt ambivalent about today's workout and whether to go easier this morning after yesterday's semi-fast run. My motivation for speed was low, so I decided to let my level of intensity play out as I ran. Once I got the door I noticed the cold, but the winds that made Wednesday's conditions feel like 24°, were no longer a factor.

My Garmin hasn't performed well lately in terms signal accuracy, making my real-time pace data suspect. I've been running by feel and heart rate which seem to provide more useful feedback. The type of workouts that I've been doing over the last five weeks have helped me increase my cadence. As a result, I'm finding it easier to hold a decent pace on shorter runs. I kept my heart rate around 85% today and ended up running my distance in the high 9's. That's exactly what I wanted to do.

Today's run was unremarkable, except at one point when I was running down a long road near my house. I spotted my wife's car heading in my direction. She and the kids were going out to do errands and when they passed me, the windows were down and they were cheering for "The Emerging Runner." They saw me from a distance because I was wearing a bright orange running shirt. High visibility isn't just for safety!

Saturday, April 5, 2014

High winds and slow paces

 
Today's run (street): 3.1 miles

There was a point in this morning's run when I told myself, after calculating my final pace, to remember how windy it was today. I know from many track workouts how wind can restrict speed. I once ran 400's where my pace varied by over 15 seconds depending on which direction I was running. Today's run, in terms of perceived effort (PE), felt much harder than Thursday's, but I ended up running 10 secs per mile slower.

The purpose of today's run to was to maintain my targeted half marathon pace over the prescribed three mile workout. That's exactly what happened on Thursday's 3 miler, but I barely broke a 10 minute pace today. During the few times on this run, when the wind was at my back, I felt like I was moving. That made me feel good about my form. I'd like to be running the easy 3-milers at around a 9:20 pace, but I'm not there yet.

The Runsketeers are doing a long run tomorrow morning. For me it's seven miles, TPP is doing 11 and SIOR is doing 16. We're trying to coordinate our rendezvous so we can all run together. Between our different paces, start times and meeting points, it's an interesting math problem. The route we chose will be hilly (I'm told). Seven miles of that should help me make progress on my endurance, but I'm expecting to be sore by the end.

Tuesday, March 25, 2014

Daft repeats: longer faster better stronger

Today's workout (treadmill repeats): 2 miles 
6 x 400m plus .5 mile warm/cool

Week 3 of half marathon training started better than week 2 finished off. After my second consecutive Sunday long run fail (only in the sense of performance, personally I had a great time) the evidence is pointing to cold induced breathing issues. Every run that I've done, either at temperatures above 40° or indoors, since my Brooklyn half training kickoff, has resulted in a decent performance. The two times I ran in high 20's/low 30's weather, I struggled mightily. Cold weather, J'accuse!

Or it could be the hills. Either way, the fact that I'm running decently more often than not is keeping me hopeful. Spring is here so chances are that one of these upcoming Sundays will provide better weather. That may help me turn the corner on my weekend base runs.

Today was speed day. It was 22° outside this morning, so I opted to do my workout indoors. Hal Higdon's program prescribed a 3.5 mile run, but I decided that I know a little more about this stuff than he does. But seriously, I've modified the Higdon training program to start my week with speed on Tuesdays and a base run on Wednesdays. Hal puts speed work into the Wednesday slot and allocates only Sundays to long runs. I felt I needed a little more base than that, an opinion echoed by some knowledgeable runners.

Hal's speed workout is 6 x 400's at 5K pace (8:24) and that's what I did this morning. In between repeats, I did 240 meter recovery jogs (.15 miles), which I may cut down to .12 miles next time. I also did a half mile warm up and cool down. I normally would have run another mile at my usual training pace to make a full three, but today I decided that 1.5 miles of speed stood on its own.

Tomorrow should be a 4.8 mile base/recovery run. The "feels like" temperature is predicted to be 19° when I plan to go out in the morning, so I'll have to decide whether to endure this cold and its effects, or suffer the tedium of a longish treadmill run. We're getting snow overnight, so that may help the decision.

Monday, March 10, 2014

Treadmill 220's, surprisingly fun

220m intervals with 70 second recovery jog
Today's run (treadmill intervals): 3.2 miles (16 x 220m, 1 mile warm up/cool down)

Although you wouldn't know it by looking at my Garmin data from my weekend runs, I have turned my attention back to performance running. It isn't without irony that, despite my now-clear neighborhood streets, I did my first speed workout this year on the treadmill. My preference would have been to do this on the track, but I was reluctant to risk being hauled off by security for trespassing at the high school.

I normally take Mondays as my rest days but I really needed to focus on my readiness. If the weather holds, I'll be racing on Saturday with the Runsketeers. I didn't intend to take as much time as I ended up needing for today's workout, but it was good that I did. My plan was to start with a half mile warm up at about 9:30 a mile and then run 12 x 100m before finishing with a mile cool down. I discovered that running intervals on a treadmill can be difficult. This is because the machine lacks the hard start/stop precision of the track. I had to account for the time it took the treadmill to get up to full speed each time.

As a result, I decided to run 220m repeats instead of 100's. I'm not confident of the accuracy of the speed displayed on the treadmill, but I set it 25% faster than what I usually run on the machine. I averaged 67 seconds for the 220's (about an 8:10 pace), after factoring in the starting lag.

I started and ended today's session with regular running. I bumped up the speed on the cool down to take advantage of the fact that 6.5 MPH feels a lot easier after pushing close to 8 MPH for twenty minutes. I was surprised that my heart rate averaged only 81% of max overall. Perhaps 67 seconds isn't enough time to go up from 64% (heart rate during recovery cycle). I'm sure that if I was doing 400's at that pace I'd be in the red zone by the end of each repeat.

Treadmill intervals were more fun than I expected and I hope this was a good way of reactivating my speed. I may do another speed session on Wednesday before my mini taper. Running fast is fun. I wish I could remember that more often.

Saturday, January 18, 2014

Graupel and snow, the track and the treadmill

Waiting for the skies to clear
Today's run (track & treadmill): 1.5 miles - track, 2.5 miles progressive speed run

My goal was clear this morning. Go out before the rain and do speed work at the high school track. Before I did that, I decided to finish up a small business project so I wouldn't have to think about it over the weekend. While I was pleased with the progress I'd made, the time had slipped and I was scrambling to get out of the house.

I noticed a few scattered drops on my windshield during my short drive to the track. I'd left under sunny skies, but five minutes later conditions had changed to cloudy and gray. Even so, I felt that the slight drizzle would pass and I set out on my first warm-up lap. There were a few walkers on the track and a guy I recognized running in the opposite direction. He seemed to recognize me as well and we exchanged hellos the first time he came around. I felt really good and ready for the intervals I had planned for later in the workout.

During the New Year's Hangover run, Runsketeer teammate TPP had showed me a technique for lengthening my stride while keeping a proper center. She demonstrated that form with an impressive burst of speed and I've tried to duplicate it for short periods during every outdoor run since then. I used the technique today and marveled at the effect. It is a far more potent method for rapid acceleration than what I've previously relied upon. I looked forward to using that on my repeats.

I'd planned to run six laps at around a 9:00 pace and then run a series of 100's and 200's followed by some cool down laps.  Once I was into my fifth lap, I started hearing what sounded like BB's hitting the ground. Later I heard on News 12 that this is called graupel, or small hail. I figured that if this was happening, I didn't need to worry much about rain. Wrong.

By my sixth lap the graupel had given way to wetter stuff and, when I ended the lap, I headed to my car to wait out the rain. My late start had put some time pressure on me and I knew I couldn't wait too long. Once I could see that this rain was not letting up, I decided to cut my losses and head home.

I changed out of my wet shoes and put on short sleeves to continue my workout on the treadmill. My new speed plan was to start fast and go faster. Since the treadmill's idea of speed is different than mine, I focused on perceived effort (PE). I'd just run my track warm up at a low 9:00 pace, so I was familiar with how that felt. The initial setting of 6.5 MPH felt much more challenging than the 6.6 MPH that I'd just run at the track.

I incremented my speed every quarter mile until I was running an 8:20 pace that felt like sub-8:00. I really should calibrate my foot pod and measure my true speed on the treadmill. Once my heart rate went over 90% Max, I held that speed for a quarter mile. I then began incrementally backing down my speed until I completed my run.

Second workout: view from the treadmill
The second workout of the day was pretty intense and I was pleased that I could maintain a high PE over a couple of miles. That was my goal today, as I prepare for February's trail relay. My wife had walked into the room during my treadmill run and opened up the shade to reveal heavy snowfall. I guess I made the right decision to come home. Tomorrow might be a good day to try some speed on the trails, though with this rain and snow it could get muddy. It was nice to be outside today but, surprisingly, my best running happened indoors.

Sunday, January 12, 2014

Oh pavement, how I've missed you

Nice to run again on terra firma
Today's run (street): 4.85 miles

Motivation was low this morning, even though weather conditions had greatly improved since yesterday. With temperatures in the low 40's and not a cloud in the sky, I should have been excited about the prospect of running outside for the first time in eleven days. My wife was on the treadmill and I thought for a moment how easy it would be to just throw on some shorts and hop on after she'd finished. But I was not going to let myself succumb to Treadmill Stockholm Syndrome, prompted by six straight runs on the machine.

According to weather reports, the relatively mild temperatures we saw this morning were countered by 20-25 MPH winds. That brought the wind chill into the low 30's. In deference to that, I wore a long sleeved shirt with a short sleeve layer on top and a pair of lightweight track pants. I also wore an over-the-ears hat that provided good protection when the wind hit at certain angles.

I mapped my route in my head, thinking it would get me to at least 4.5 miles, which was my target. Some people have told me they have trouble transitioning from treadmill to road after numerous indoor workouts. I didn't have any such problems today. In fact, my stride felt far better on the road than it had on the treadmill.

Early on, I saw a guy running towards me on the same side of the street and I was tempted to give him the, "it's safer to run against traffic" suggestion. I'd seen him running in the neighborhood for years, and figured that he's probably set in his ways. The last time I suggested the safer choice to a runner, she yelled back that she's been running that way for many years, that the neighborhood is very safe for runners and basically I should mind my own business. So for the most part, that's what I do now.

I didn't burn up the road in terms of speed but I did throw in some surges. TPP had suggested a technique for opening up my stride by launching off my trailing foot while keeping my legs under me. It seemed to translate into a faster pace. I focused on running that way over the last mile and saw a 40 second per mile improvement.

I could have easily gone the additional .15 and made it a full 5 miles but I decided to end the run when I reached my street. I felt good and my heart rate averaged 83% of max overall, finishing up at around 87%. That was almost exactly what I'd been averaging on my prior runs on the treadmill. I have a work-intensive day planned for tomorrow so I doubt I'll run. Mondays are usually my rest days, so no guilt. It was nice to be back on the road today. I definitely missed it. I will start adding a little more speed this week as I prepare for the GLIRC 2x3 trail relay in Bethpage on February 15th.

Saturday, November 30, 2013

Short & sweet threshold run

Today's run (Threshold): 3 miles

This year's racing experience has been a mystery. After a decent start in February, my performance has really tailed off. I'm not sure if it has to do with my change to a less structured schedule this year or less intensity in terms of training. Whatever the reason, I haven't been satisfied with my results. November has always been my best month for achieving personal bests, but that's not been the case this year.

The Hot Chocolate 5K happens next week and I've hoped that the two 10K's I've done in November have put me in racing form. I debated whether to go to the track today to run intervals or do a threshold run. I decided a run in the neighborhood would more closely duplicate race conditions.

It was another cold morning with mid-20's temperatures. I was chilly at the start, because I wore fewer layers. If I was going for speed, I didn't want anything inhibiting my progress. I took off fast up the road, looking to get into high gear quickly. The street has a slight incline that gives way to an equally slight downward slope. I knew I was moving faster than I do on a normal training run and my Garmin shows I covered my first mile in 8:25.

I didn't have a set distance for this threshold run. It was more about running a short (but not too short) loop with some urgency. I lost some speed on the second mile, but came back fairly strongly by the end of the run. I wasn't paying attention to my distance, but after I'd stopped I saw that I'd covered three miles at 8:46. Not too bad considering my HR only averaged 85% of max.

A year ago I might have done that run 25 seconds per mile faster, but I won't complain about today's performance. I slightly regret not monitoring my Garmin and completing the full 5K distance. I doubt the numbers would have been much different. If I can hold my pace below 9:00 next Saturday, I'll consider it a successful effort. I'm hoping I'll do better than that and certainly no worse.

Wednesday, October 30, 2013

Lies, damn lies and Garmins

Look how fast I didn't run!
Today's run (street): 3.4 miles

I was in meetings all day on Tuesday and didn't get a chance to do a run. I did cover a lot of ground on foot, so that should count for something. Along the way I noticed many marathon tourists (after all these years I can easily spot them) enjoying the sights prior to running the race on Sunday. A couple of my meetings were held near Time Square, where sports demonstrations publicizing the Sochi Olympics were going on. It was a mob scene, but fun to watch.

I had no city meetings today, so I resumed my run schedule this morning. I've been running with my foot pod so that I can capture my cadence, but I still use the Garmin's GPS to measure my mileage. Due to that, I haven't bothered to calibrate the foot pod for distance. When I fire up the Garmin, it detects the foot pod and asks whether I'm running indoors. If I say yes, it will turn off the GPS radio and use the foot pod for measurement instead.

Today I went through the routine and when it looked like the signal had locked in, I was on my way. I hadn't gone half a mile before the Garmin chirped saying I'd reached my first mile. I figured that the GPS signal must not have actually acquired before I started and the watch was working off the (uncalibrated) foot pod. I didn't care much, because I always Gmap my run to get exact distance.

The watch did switch to GPS mode shortly after that, and my remaining splits were in line with my normal pacing. While I would have liked to meet the performance that the Garmin recorded for today's run, I must admit to a far less impressive pace in the mid-9:00 range. So the Garmin lied, but I'll forgive it. If I could run five minute first miles for real, I might actually break an 8:00 pace on my training runs.

Thursday, October 17, 2013

Making my last taper count

A serious threat to pant-kind
Today's run (street): 3.1 miles

As much as I love running, business needs to come first. For that reason, I was unable to get in my workout yesterday. I was in the city all day for meetings so the opportunity for a run didn't surface. I'm temporarily boycotting my Fitbit because the holding clip has deteriorated to the point where I fear it will rip my pants when I wear it. Without it, I don't know how much distance I covered yesterday on foot, but I'm estimating it was between 4 and 5 miles.

Today I had no excuses. Without a commute into the city, I had enough time for one final run before Saturday's 5K. Although I've heard that I need to do weekly speed work in order to avoid embarrassing myself on race day, I think I've prepared well for the race. I decided that a good hard run over three miles would be a nice way to end my taper.

I took off at a brisk pace and tried to maintain that turnover throughout the entire run. The difference between this type of workout and a race centers on two factors: the influence of other runners and the psychology of competing in a timed event. Without those two things, my expectation was to see a very good, but not spectacular performance today.

That's exactly how it came out. I'd kept my heart rate around 85% max and covered the distance in a little over 28 minutes. For me, that was exactly on the mark. I could have pushed harder and dropped my pace into the 8:00 range, but I didn't see any reason to do that. 9:06 was a decent average under the circumstances. I'm making no predictions for Saturday. A lot of it will come down to how I feel on race day morning.

Tuesday, October 1, 2013

A good run today, but what have I done?

Maybe I should have thought this out
Today's run (street): 3.3 miles

Despite having my Garmin GPS, heart rate monitor and foot pod on my run today, I felt like a purist. That's because I chose not to use the metronome app. Instead, I tried to meet my targeted cadence only by feel. Like the old joke about hitting yourself in the head with a hammer because it feels so good when you stop, today's run felt extra peaceful without all that beeping.

This change seemed to pay off, as I hit 87 SPM just by focusing on a brisk cadence. I felt some awkwardness in my gait for the first 20 minutes of the run, but still achieved a mid-9:00 pace in the process. I'll take that for now. I think I understand how much harder I'll need to push to get more improvement.

Things have gotten busier in terms of work and I spent much of the day on my laptop. I did take a break before lunch and got a flu shot a the local pharmacy. Although the CDC claims that flu shots don't make you ill, last year I felt very run down a couple of days after getting mine. I really hope that was just a coincidence. But if I have any bad workouts later in the week, I'll know what to blame.

Thursday, September 26, 2013

Metronome running: Calls and Cadence

Runnis Interruptus
Today's run (street): 3.4 miles

Using a metronome may have actually helped my cadence this morning. Once I start using my foot pod (good suggestion FS) I will know for sure. It was a weird run, punctuated by a ringing cellphone that I would normally ignore. Today I had two good reason to stop. First, the call was business related and important. Second, the ringing phone shut the metronome app off. Grrr.

I used the Metronome Beats app today because it has better features than the one I tried yesterday. Most importantly, it punches out beats loud and clear, unlike Metronome Mobile's softer sound. I set it for two clicks per beat, which is easier than trying to coordinate two footfalls to a single beat. Focusing on the sound made my first mile go by quickly and the odd beeping noise produced double takes from neighbors as I passed by.

The phone call caused an interruption and I was honest about being in the middle of a run. That was no problem and I think the endorphins helped keep me calm during an intense conversation. Soon I was back to the run and I realized that it would be easier to time my arm-swing to the rhythm, rather than try to keep my footfalls synchronized.  Do your arms move at the same rate as your cadence? That would be interesting to know.

I moved really well and everything was fine, until the app quit about half a mile from home. I considered stopping and restarting the metronome, but I'd already stopped once on the run. I tried to "think" the beat that I'd been following and that may have worked. Today's pace was 9:22 and it felt fairly easy. I'd set the metronome one SPM faster than yesterday and that yielded a 2.4% improvement in pace. That assumes a lot, but it was progress and that came from somewhere.

Wednesday, September 25, 2013

Running cadence, there's an app for that

Metronome apps
Today's run (street): 3.4 miles

Yesterday I wrote that I wanted to increase my run cadence, but wasn't sure how to approach it. I got a comment from fellow running blogger, The Petite Pacer, who suggested I try a metronome phone app. That was a great idea and I downloaded a couple of free ones, Metronome Beats and Mobile Metronome. After researching how to use a metronome for cadence, I was good to go.

I decided to use Mobile Metronome first, and set the BPM at 85, which is undoubtedly higher than my current SPM. Back when I used a foot pod, my cadence typically averaged 80 SPM on the road and 83 SPM on the treadmill. I wanted to set an aspirational cadence, rather than start with the ideal of 90/180 SPM. I was curious whether I'd be able to sync my steps with the metronome's rhythm.

I always run with my phone and I keep it in a SPIbelt on my waist. Even after setting both the phone and application volumes to their maximum, the sound of the beat was faint. Under normal conditions I could hear it, but the occasional sounds of helicopters, lawnmowers and passing school buses would drown it out. The challenge of matching stride with beat was a little tough. I decided to let it happen naturally by focusing on the beeps.

I'm not sure that I achieved my targeted cadence today, since I have no way to capture the metric. I felt like I was on top of the beat, but it's hard to really know. My overall pace, a pedestrian 9:37, doesn't indicate fast turnover. Tomorrow I'm going to try the Beats app that provides the option of beat pairs that could help me sync both steps. The app also offers more ways to shape the sound, so I'm hoping it will be easier to hear, even with lots of background noise.

Wednesday, September 18, 2013

Last run before the Cow

Today's run (street): 5 miles

Training is over and now it's time to rest. Everyone has their own way of finishing a taper and mine is to put two full days between my last workout and race day. Some people I know don't even take a rest day before a 5K. I learned my lesson a few years ago that running close to race day doesn't yield a benefit. But pushing too much will definitely hurt you.

Today's run was an easy semi-base run done a minute slower than targeted race pace. I had a deadline to meet in the morning and didn't get outside until after 10:00, so I had more warming sun than usual. At that pace, it didn't matter. Aside from running face first into an overhanging branch that looked like it should have easily given way, it was a pleasurable experience. I felt a little guilty for not pushing my speed, but there was no upside to doing that.

I didn't use GPS to track my performance because I didn't want to be conscious of my pace while I ran. I didn't Gmap the route until an hour later and was hard pressed to remember all the streets I covered on my route. I did finally figure it out, and it was interesting to see the distance. I checked my time and saw that I'd met my targeted pace to the exact second.

I got a note that Cow Harbor online registration ends tonight and the site shows that over 5,000 people have already signed up. Participation is capped at 5,600 runners. Between now and 8:30 AM on Saturday, I'll be thinking about this race and its unique challenges, along with the experience of being joined by thousands of runners and tens of thousands of spectators in Northport. I look forward to seeing my friends and I can't wait to cross that finish line once again.
 

blogger templates | Webtalks