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.

Race report: 2013 Great Cow Harbor 10K

See, some people finished after me!

Today’s race (Great Cow Harbor 10K): 6.2 mile – (9:53 pace)

Another Cow Harbor race has come and gone. Just like the three that I’d run prior to today, I’m incredibly impressed by both the effort and the execution. It’s a massive undertaking, with many moving parts. Cow Harbor relies on a well organized army of dedicated volunteers at every stage, and they make it one of the greatest races in the country.

The flow of a Cow Harbor morning has a certain familiarity. First you have to find the high school (I often miss that tricky left on Old Pine lane), find a parking spot (easy at 7:00 AM) and get on a shuttle bus. The ride from there to the Laurel Ave school takes me back to junior high (do we have gym today? I hope we don’t have to run!). The walk from the bus to the school provides time to evaluate your level of energy and to gauge weather conditions.

Starting line an hour before the race

Every time I’ve run Cow Harbor, the heat and humidity have been a factor. However, before the start, it can feel chilly. I usually head into the building to maintain warmth and people watch and then go outside to get in line for the Porto’s before they stretch as far as the starting corrals. I ran into some friends this morning who were also running the race, although I didn’t see everyone I’d hoped to see.

Elite runner registration desk

I found my place in the 9000 section and made small talk with my corral-mates while we waited. After the playing of the national anthem the announcer started the first wave, that consists of elite and semi-elite runners. A minute later the 1000’s went, and eight minutes after that, my group was unleashed. I never really know how ready I am until I’m actually on my way. Those first few minutes told me that I might have some problems today.

Scudder Ave is the first main component of the course and everyone talks about the temptation to run it full tilt because it’s pretty much down hill. What I always forget is that Scudder starts out with a noticeable uphill, and today it felt difficult just getting past it. Uh, oh. If that was hard, how would I do on Bayview and James?

Once Scudder began to slope down, I felt some rhythm return to my stride. We reached Woodbine and then passed Main Street to big crowds and bagpipers. Bayview is mostly uphill, but mildly so, and I was doing okay, although I definitely wasn’t feeling my best. I was amused when a spectator yelled, “You guys look great!” and the runner behind me yelled back, “Thank you for lying!” We all knew what was in store for us in a couple of minutes.

As I rounded the corner onto James Street, I thought about whether I’d like Cow Harbor more if this hill wasn’t part of the route. In that moment, I realized that “Widow Hill” was the defining element of the race. Today it defined me as well.

I’ve prided myself in races past, on my ability to take James Street at a steady pace and make it through, sweating but unscathed. I really struggled this morning and was tempted to walk, but I never had before and I wasn’t going to today. I kind of wish that I had, because it took me another half mile before I felt my strength return. I lost at least a minute off my overall race time as I worked back to race pace.

Coming down Ocean near Eatons Neck turn

I was doing okay at three miles and was delighted to see an ex-work colleague at the point where Ocean Ave meets Eaton’s Neck Rd. I told her that I’d be coming through around 9:15 but it was closer to 9:05. She yelled, “You’re doing better than you predicted!” Sadly, no. I just got the math wrong.

The rest of the race was a puzzlement. While I wasn’t feeling my best, I was running credibly and attacking every downhill I could find to make up some time. Waterside Rd, with its long uphill slope, can hit you hard in the later miles of the race. I felt that I was maintaining my targeted cadence and speed and the split announcements made me think I was tracking for a mid-9:00 time or better.

There was no point in the race where I felt overwhelmed by the effort and I remained hopeful that I’d match or exceed last year’s time. The last big challenge of the race is Pumpernickel Hill and I found it slightly tougher (and seemingly longer) than in past years, but I got over it and put everything into the remaining distance (about .9 miles). I didn’t back off the throttle until I crossed the finish line.

When I looked at my Garmin and saw that it took me 61 minutes to get through the course, I was a bit disappointed. I couldn’t understand why I missed my target, especially after the speed, hill and base training I’d done. At the same time, I was thrilled to have completed the race and managed an average pace within the nine minute rage (if just barely).

The thing about racing is that you can do everything to support your success but it all comes down to how you feel on race day. I’ll admit that I’ve been tired this week and, in retrospect, I may have been better off not walking the hilly Bethpage trail for 80 minutes yesterday (although I enjoyed spending that time with my wife). My taper-ending five mile run on Wednesday could also have contributed. Today’s shortfall may have had to do with other factors, like not enough sleep. I really wanted to hit 58 minutes.

After the race, Cow Harbor puts on a great finish line festival. It’s like Woodstock for sweaty, emaciated people. I skipped all the carb snacks and flavored juice bottles and went right to the banana truck and then over to the Poland Spring truck. The band they hire to play is really good and the crowds, energy, music and harbor view reinforce that you are participating in something special.

I happily avoided the baggage check this year
I may have placed mid-pack, but I was the first one on my bus!

I ran into a few people I know who had also raced, and then headed over to the bus line. The transportation process is well managed and, without a long wait, we were on board. A woman who’d run the race for the first time today sat next to me and we talked about our favorite races on Long Island. Her son won the 2K fun run! I don’t know if her husband ran the 10K as well, but I’m guessing he did, because the whole family looked athletic. She was a really nice and funny person and it was a great way to cap off my Cow Harbor day.

My next race will be the Town of Oyster Bay Supervisor’s run in October. It’s a 5K and the first half is a steady incline while the second half is equally downhill. The challenge doesn’t match James Street, but I’ll still have to train. In the meantime, I’ll be taking a couple of days to recover from Cow Harbor. I hope my friends who ran it had good experiences today. No matter what, it’s hard not to have a good time at this race.

Tracking well through the taper

4 minutes of intensity

Today’s run (track): 3.1 miles – 1 mile warm up, 10 x 100m, 1.6 mile recovery

Nothing like 52° weather to make speed work bearable. I went to the track early this morning to run intervals, but I didn’t decide on my workout until I got there. I started with a mile warm up and followed that with 10 x 100 meter repeats. I finished with six more laps around the track, three at an easy pace and the last three somewhat faster.

Overall, it was a decent workout and I managed to run my 100 meter splits at 6:50 while maintaining a heart rate around 80% of max. I would have like to see better paces after the repeats, since my leg muscles were theoretically “activated.” Residual fatigue was the likely culprit and my overall pace for the full distance run was 8:58.

Tomorrow will be a busy day in the city for me and I’ll forgo my workout, since Mondays are my usual rest day. I’m thinking I’ll do one more easy base run, one more short fast run and then rest. I had two good race-oriented workouts this weekend with acceptable results. I’m not sure I pushed as hard as I could either day but I didn’t want to invite injury less than a week before the race.

9/11 weekday run

 

Today’s run (street): 3.1 miles

I’ve been off the blogging grid for the past two days, and most of today, because I’ve been consumed with a work project. After taking my usual Monday rest day and Tuesday as another recovery day, I was back on the street this morning. I wasn’t psyched to go out at 8:00 AM, as the news was reporting 78 degrees and a dew point of 71.

I tried to set a strong pace but, felt frustrated with my turnover. The good news was, despite the hot and humid conditions, I wasn’t tempted to tone down the effort. At around the one mile mark, I recalled that today was September 11. Except for when it fell on the weekend, this was the first time I didn’t need to commute into the city on that day. It always made me nervous to be in Penn Station on 9/11.

20 minutes into the run, I was looking forward to finishing up. Still, I kept up the effort and wondered if it would translate into a credible time. My heart rate indicated that I was holding about 80% of MAX, so even if I wasn’t moving very fast, I was trying. I ended up averaging 9:14 a mile. Given the weather, that was more than satisfactory. It was good to be back on the road, but I’m really looking forward to the fall weather.

Can you really improve your running speed?

Looping the loop

Today’s run (Business Park): 4.8 miles

I’m beginning to wonder how much one can actually do to optimize running speed. When I first started running, I was averaging 12 minute miles over the first full month. Two months later, I was breaking 10 minutes a mile. When I completed my first full year, I was averaging 9:15 per mile, with occasional dips below 9:00 on shorter distance runs.

Four years later, despite holding consistently to a six day running schedule, I’m still averaging about those same paces. The good news is that I’ve managed to keep my performance at the same level. The bad news is that it now takes a lot more effort to do that. My goal has always been to average below 9:00 a mile and I’m wondering if I’ll ever get there.

As I focus on speed, I’m realizing how difficult it will be to get to my targeted pace. After taking a break from performance to run the trails on Friday, I headed over to the local business park to run the big loop. This route provides a lot of elevation gain and loss (+/- 1,040 feet), which I thought would be helpful training for Cow Harbor.

The temperature was 59 degrees when I went out 8:00 AM, and that provided great conditions for taking on the hills. I did two laps around the park before ducking into an adjacent neighborhood for another mile. With the great weather, I was surprised to see only two other runners out this morning. One woman was circling the park counter-clockwise while I ran it the other way. She was running with traffic and we passed closely. I wonder if these people ever connect the reason why I run on the left with safety. I’m guessing they don’t.

I made it back home in time to make an early obligation. When I mapped my run, I saw that I’d averaged 9:27 a mile. Despite my focus on speed, my performance is still lagging on longer runs. Tomorrow, I’m planning on doing a fairly long tempo run, followed by hill repeats. Only one more weekend after this to train for Cow Harbor before I taper. I’m doing the best I can to prepare, but there may not be much more performance to gain.

Just me and the road, and the cars, and the buses

My worst nightmare

Today’s run (street): 3.3 miles

After three consecutive indoor workouts, I was finally able to get outside today, and it was beautiful. The sun was bright and the temperature was cool. While I waited for the Garmin to acquire a signal, I noticed a breeze that actually made it feel cold in the shade. I knew once I got started that any feelings of being cold would disappear, but it was nice to start out that way. 

Due to a scheduled call, I had to get my run done in a certain amount of time. I could have gone out earlier, but we live close to both an elementary and a middle school and I didn’t wish to compete with all the buses. By the time I hit the streets, a few buses still remained, but car traffic had picked up. You can’t win, but you can run on the sidewalk. I ended up yelling at a guy who rolled through a stop sign as I approached the intersection. To his credit, he sheepishly said “sorry.”

I continued my focus on speed and moved along, although I was having some trouble with my form. I didn’t feel like I was getting good turnover and I was concerned that I’d end up with a disappointing time. Still, I knew that I was making the effort. Most of the time, that will yield a satisfying result.

I ended up averaging 9:05, which surprised me in a good way, because I expected I’d be about 15 seconds slower per mile. My speed described a bell shaped curve, with the first and last half miles being the fastest. So far my training strategy is working, but I still haven’t put fast and long into the same run.

I really should have thought this through

Accidental self portrait after the run
I was trying to get this shot of the new gates and info kiosk

Today’s run (Bethpage State Park): 7.4 miles

As I made my way along today’s Bethpage route, I came up with various titles for this post. At the two mile mark, it was something like, “Great base run at Bethpage.” By the time I’d reached my turnaround point it was, “Oh the humidity!” By the time I reached the end of my run, the above title popped into my head.

Today was a base building run to help prepare me for Cow Harbor. With all the focus I’ve been putting on speed, I didn’t want to neglect the fact that the Cow Harbor course is 6.2 miles and hilly. I thought that Bethpage’s bike trail would be a great place to duplicate those properties. Cow Harbor’s race day weather can be oppressively hot and humid, so today I hit the trifecta for simulating conditions.

I didn’t plan a particular distance this morning, although I knew I’d run at least six miles. Once I arrived at the park, I decided to run a mile on the north trail before changing directions so I could do the bulk of my distance on the older, somewhat more challenging section. I had little trouble getting through this first part. It was cloudy and 73 degrees, so despite the 89% humidity, it didn’t seem so bad.

My new-found speed allowed me to pass numerous runners. This was gratifying since I’m often passed by club runners who populate this trail on weekends. My pace for the first couple of miles was on par with what I’ve been running lately, and I felt encouraged. By the time I reached mile three, I started to feel the effort, especially as I took on a couple of tough hills that come before the Plainview Road roundabout.

Despite growing evidence that my smooth base run was about to get rougher, I tried to maintain a brisk pace. The trail between miles three and four trends slightly down, so I was able to keep going without a lot of extra effort. By the time I passed four miles, it became clear that my glycogen level was depleted. I did my best to hold on while my body figured out what to do next.

Between a lack of fuel and the overwhelming humidity, I was hurting. Why, after seeing the weather report showing close to 100% humidity today, did I forget to bring a water bottle? My pace had slowed 90 seconds per mile compared to the start, and I switched to a more mechanical stride in an effort to just keep going. I nearly bonked at mile six, but instead slowed my pace even more. I needed to prepare for the dreaded hills that make up most of the last mile leading to the trail head.

By the time I reached the biggest and longest hill, I was moving slowly. But I was moving. I even passed a woman on a bike who was struggling to get up the hill. About 4/5ths of the way to the top, my energy began to return and I stepped up my pace enough to put me back into target range. I was thrilled to run the final section of trail leading to the lot. Stopping never felt so good.

It was a very tough workout and I’m still feeling the effects seven hours later (although I did participate this afternoon in our family’s annual obstacle race – a summer tradition). I don’t know if today’s experience was due to fitness gaps or if it was more about the weather. Last weekend I ran almost the same distance and performed much better, so it probably had more to do with conditions than conditioning. Next time I’ll think about going out so fast on a base run and I’ll definitely remember to bring along water.

Great progress, suddenly

Surprising results

Today’s run (street): 3.4 miles

I think my training program is working. I’ve been encouraged by the improving paces I’m seeing after taking a more performance-oriented approach to my training runs. Overall, my average pace has dropped about 5% since I started training for Cow Harbor. The trend line was getting me closer to 9:00 per mile, but I hadn’t yet reached that goal. That is, until this morning, when I blew right past it.

I wasted no time getting out today, hitting the road about 7:00 AM under very cloudy skies. Going out fast is becoming easier now, although I still suffer through the first few minutes while I hit my aerobic stride. The visual I keep in mind these days is putting my foot on the gas with no letup. Just like in a race, I know that to run faster, I have to think about running fast. Complacency only leads to slow results.

Like yesterday, I used my heart rate as a guide and saw that I was pretty much where I wanted to be. I considered breaking out of my 3 to 3.5 distance range that I typically follow on weekdays. I decided that while I’m developing my speed technique, I’ll take a careful approach to adding weekday distance.

When I reached the last few streets that lead me back home, I decided to step it up even more. No reason to reserve more energy than what was necessary to get me to my driveway. After reviewing the metrics, I saw that I’d covered the last half mile at 5K pace. After mapping the run, I calculated that I’d paced 8:50 overall for the run. That was the fastest training run (excluding speed sessions) I’ve done since early February.

I was both surprised and pleased to have cracked the 9:00 threshold and encouraged that I surpassed my target. Tomorrow may be a good time to start working in a little more mileage while I try to hold the gains. I’m not expecting to repeat today’s performance, but hey, you never know.

Alarming morning affects my run

Rude awakening

Today’s run (street): 3.2 miles

This morning’s fun started early. It was 2:39 AM to be exact. That was when we were woken up by an incessant beeping. It turned out that our alarm system was signaling that the backup battery was low. Apparently our street had lost power some time earlier. After a bleary-eyed call to LIPA’s outrage line (that was a typo but I’m leaving it in), we went back to sleep, only to be awoken around 5:00 AM when the power came back and reactivated the alarm.

We had overnight guests down the hall and thankfully they slept through the craziness. Since I was up early, I decided to go out for my run sooner than I normally would. The skies were overcast, but there didn’t appear to be any rainclouds in sight. I went out fairly fast (at least it felt that way) and hoped I could carry that urgency through my full distance.

My effort seemed moderately high and I tried to maintain a steady cadence. A check of my heart rate around mile 2 showed that I was 8 BPM below where I wanted to be. I hoped that was due to improved conditioning, but it was probably a case of perceived effort not matching actual effort. In the end I completed the run both pleased and disappointed. Pleased, because my time was better than average, but disappointed because I was still 15 seconds per mile slower than my last weekday run.

I’m aiming to improve on that tomorrow. Perhaps the disrupted sleep affected my performance. Yes, let’s go with that.

Fast track to performance gains

Flow of the workout

Today’s workout (track): 1 mile tempo, 12 x 100M, 1.25 mile cool-down = 3.1 miles

This morning I headed out early to the local track to run intervals and tempos. I took the Virratas out for their first run, and thought they responded well to fast pacing. My plan was to run one mile at 5K race pace, which I’d follow with intervals and a cool-down run.

The track had a few walkers and a couple of runners when I arrived. I got started quickly on my tempo warm up and found a pace that felt hard, but sustainable. I locked into that pace for four laps, guided by perceived effort. Along the way, I passed everyone including the other two runners on track. After last Sunday’s low point of the race, when I was being passed left and right around mile five, it felt good to be the one who was doing the passing. I averaged 8:18 for the mile.

Next, I ran a set of 100 meter repeats, averaging 6:40 per mile. I was surprised when I later looked at heart rate data and saw that I’d averaged between 74-80% of MAX. Knowing that, I can probably get my pace down to 6:25, while still staying under 90% MAX. However, I’ll probably keep it to 8 x 100’s for that session.

I finished the workout with a 1.25 mile cool down, run at a moderate (9:21) pace. In total, it wasn’t a lot of distance, but the intensity made up for that. I’m planning a long run tomorrow, either on the Bethpage path, or another route that will facilitate a 6+ mile distance better than my neighborhood roads. My performance has improved greatly for runs between 3-3.5 miles. It will be interesting to see how my pacing holds up, when I double that length tomorrow.