Garmin FR 35: I never saw it coming

Welcome back data

Today's run (street): 3.2 miles

This afternoon the fine folks at UPS dropped off a package at my house. I opened the box and saw that it contained a Garmin Forerunner 35 GPS watch. I really wanted the FR35 to replace my FR210 that I lost on the Bethpage trail a couple of weeks ago. Interestingly, I never ordered the watch. It wasn't until my wife told me that my friend and fellow Runsketeer KWL had sent it. I couldn't believe it, but I was very excited.

One of the reasons KWL wanted me to have the watch was to encourage me to focus again on my performance when I run. The FR35 has a lot of tracking features including an optical heart rate monitor that obviates the need for a chest strap. I prefer to run by heart rate/zone rather than pace and I'll be able to do that easily. It also works as an activity monitor. I didn't realize that until it rudely beeped at me and said "Move!" on the display.

I wish I had this watch when I went out this morning on my run. Instead, I ran with my stopwatch. That was fine, but I missed being able to track time and distance. All the same, the stopwatch did give me some useful feedback. I generally run the same route every Friday and knew exactly where I'd hit the one mile mark. Although my stopwatch was securely attached to my SPIbelt, I was able to catch a glimpse of the elapsed time. I saw that I ran the first mile 30 seconds faster than my most recent (improving) pace.

Going forward, my challenge will be choosing to push performance rather than enjoying the experience of a free form run. Today's conditions were cool and fairly dry and my running felt easy. I ran faster than I have in many months but it didn't feel hard. It felt great. I can push even harder and run even faster, but I don't know how far to go with that. I'm going to target 85% max HR tomorrow and see how that feels. If it feels okay, maybe a little speed will be worth the extra effort.

Cool weather returns but so does traffic

Today's route

Today's run (street): 3.25 miles
Sunday's run (street): 4.4 miles 

The weekend is here and I'm very glad about that. Since the school year started, my commute has gone from easy and breezy to not easy and not at all breezy. It takes me approximately twice as long to get to and from my office now than it did the last week in August. Working from home on Fridays makes the prior four day's driving more tolerable. No commuting means I can get in a run before my workday begins.

It was 54° when I got outside at 7:30 AM. The air felt cool but not uncomfortable. I wore the runner's mullet: a long sleeve shirt with shorts, that were perfect for the conditions. I'm getting used to feeling good from the start of my run after a year or so of struggling during the first few minutes. I ascribe this change to weight loss that has come mostly from consuming less sugar. My weight loss hasn't been dramatic, but it's been enough to make a difference in my running experience.

I ran my usual Friday morning loop. Due to the hour, I spent a lot of time running on the sidewalk to avoid maniac parents dropping off their children at the elementary and middle schools. The aggressive driving, speeding and ignorance of stop signs kept me off the road. Running on sidewalks is not my preference, but it's the place to be on mornings like this.

I felt I was running well and my numbers showed it. I paced 8.7% quicker than my current average and I felt like I got around my slightly modified course sooner than I expected. That said, I wasn't particularly fast compared to how I ran a couple of years ago. I'm loving this cooler weather and I'm looking forward to my weekend runs. Tomorrow morning's schedule is tight and I'm hoping to get out early enough to get in some miles before 8:00 AM. Otherwise I'll need to do a rare afternoon run.

Bethpage's hills didn't scare me today

Where bike trail meets dirt trail

Today's run (Bethpage bike trail): 4.3 miles

I'm discovering that my new approach to eating has yielded some improvement. As I mentioned yesterday, a measurable reduction in processed sugar intake and longer breaks between meals has given me more clarity and energy. Although it has been less than two weeks, I'm noticing positive changes, physically and mentally. It's too early to know if these changes are producing real results or if the improvements are more of a placebo effect. It may be a little of both.

I got out to Bethpage this morning and parked at Runsketeer HQ off of Haypath. I usually run north to Washington Ave., but today I decided to go south toward Bethpage State Park. Like yesterday, I felt great from the start to the end of my run and I truly believe it has to do with reducing refined sugar and minimizing insulin response. While this change is exciting, my performance hasn't improved.

Great run despite 88% humidity

Today's pace was fairly typical compared to what I'd normally run for four miles. The difference is that maintaining that pace is now far easier. I normally grit my teeth to get through my runs and focus on the end result: finishing. There was none of that today, even though I took on some challenging hills between Haypath Road and my turnaround point on Picnic Polo Road.

So what about performance? If I continue to feel the way I did on my last two runs, I can start focusing on speed. That's something that I haven't done in a long time. Either way, I'm enjoying, rather than enduring the experience in way I haven't in quite a few years.

How Dr. Phil (not that one) is helping my running

I'm sweet enough already

Today's run (street): 4.25 miles
Yesterday's workout (Treadmill and elliptical): 40 minutes
Tuesday's run (street): 3.5 miles

Roses are red, violets are blue, sugar is sweet and so bad for you. I recently read Christopher McDougal's newest book, "Natural Born Heros" that at one point focused on Dr. Phil Maffetone whose methods have helped many elite athletes increase performance. The key takeaway for me is that most assumptions about fueling athletes are incorrect.

Two examples of this both relate to hydration. One, that runners are at much higher risk of dying from water intoxication than from dehydration. The point being that humans are made to endure long periods without water and that's why we are successful hunters. The other example is that hydration drinks like Gatorade, that contain large amounts of sugar, provide little benefit compared to the damage they do. High sugar drinks will spike both glucose levels and insulin response and can contribute to disease, inflammation, depression and increased body fat.

A lot has been written about how processed foods, especially those with refined sugar, are quickly stored in the body and become very difficult to burn. I started thinking about my own diet, which is pretty good compared to many, but it's higher in sugar and simple carbs than it should be. I decided to address this in a logical way that doesn't require a big change. I believe this has already yielded benefits.

I currently eat a vegetable-rich diet and that won't change. I get protein from high quality sources (mostly chicken, turkey, nuts or tofu) and that won't change either. But I am reducing the amount of refined carbs I ingest (far fewer) and sugars of any type that have anything more than a low (value of 10 or less) glycemic load.  An important aspect of these changes is that I am increasing the amount of time I wait between any meal and any snack that follows it. This is to prevent insulin spikes that promote the conversion of glucose to stored fat.

It's been about 10 days since I made these changes and I believe there's something to it. I haven't sacrificed much except cutting a few hundred sugar-heavy calories from my daily intake. I've lost a couple of pounds and my energy level is noticeably higher, while my crankiness level is lower (Mrs. ER debates this but I know better). Work pressure is high right now, but I'm feeling far less stress than I usually would.

That's all well and good, but here's the best part. Today I had my best run of the year. It wasn't my fastest, and it certainly wasn't effortless, but not once did I wish for the run to end. I felt like I did back in 2011, when my running was at its peak. I took a few opportunities to throw in speed during the run and snapped back without feeling overtaxed when I resumed my natural pace. I felt great in both mind and body.

Will I feel the same tomorrow when I run? I hope so, but I know that every run is different and I've had bad runs follow good ones. I may not achieve today's level of energy and spirit, but I think these practical changes have yielded real results. It's hard to believe such a simple change could provide so much improvement. It will be interesting to see if I feel this way in a couple of weeks.

Kenyans are faster than my commute

These cars were new when I started my commute

Today's run (street): 3.4 miles

If you took every car on Long Island and laid them end to end, it would stretch all the way to my exit off the Long Island Expressway. That is the reality of my daily commute home. 35 miles in 150 minutes is an average of 14 MPH. An elite runner could run home faster. This is the reason I like Fridays, because working from home saves me one day of all that aggravation.

Last night it took 2 1/2 hours to get from my office to my house. I had every intention of doing a post-work elliptical session, but my night was getting short and I decided to forgo it. Today I had no excuses. I was pleased to see the below 70° temperature and feel the cool dry air when I stepped outside this morning. I felt good from the start and that continued throughout the run.

It's getting close to fall, my favorite running season, and I'm wondering if I'm finally turning the corner on my lethargic performance. Little by little, I've increased my effort on my runs and have started to see incremental improvements to my pace. Today I focused on increasing cadence and a more dynamic leg motion.

The end result was a substantial improvement in my pace compared to a few weeks ago. As impressive as that sounds, I'm still over a minute per mile slower than I was last year. On the other hand, today's pace was half a minute faster than last Sunday. This type of progress is very encouraging. If it continues, I might get fast enough to out run the Expressway traffic.

Happy on the Bethpage trail

Trail appreciation day

Today's run (Bethpage trail): 5.4 miles

The best part of today's run came during the last half mile. I'd spent the previous five moving at my usual pace (slow) but opened up the throttle on the last stretch of the path. I ended up with a final split in the range of my old normal pace. That contrasted with the rest of my data and really highlighted how much my performance has dropped off over the past few years.

I wanted to break out of my typical 3 to 4 mile rut and I knew the best way to do that was to run the Bethpage bike trail. There was partial sun breaking through the clouds and the humidity didn't seem too bad. But humidity can be deceiving and, a few miles in, I began to regret leaving my water bottle in my car. Garmin data says humidity was 83%. On the other hand, there was a steady breeze coming from the west that acted like a cooling fan, especially when I was heading south.

Rather than go north as usual, I decided to run south to Bethpage State Park, turn around there and head north to Old Country Road. I figured that would get me my targeted five and then some. Soon after I'd started, I saw a couple of people running ahead of me at about the same pace that I was running. Well the guy was running my pace and the woman was running faster and looping back periodically to run with him. It reminded me of running with TPP and SIOR!

I eventually caught up to them, but they kept going south while I turned around. I was feeling good and took the time to look around and appreciate how fortunate I am to have this beautiful trail ten minutes from my home. The abundant trees and well maintained paths make it a happy place. I noticed that they've put in water coolers near the end of the first section of the northern path. Very civilized. I wish I'd drank from it when I had the chance.

For some reason, I expected that my run north would feel short because I'd covered 2.75 miles by the time I'd looped back to where I'd started. It wasn't a slog covering the remaining distance, but it seemed to take longer to cover slightly less distance. As it turned out, I went much faster during the second half. That was probably due to my more urgent pace towards the end.

The fact that I could hold a much faster pace for a fairly long stretch reinforced that my speed issue isn't physical. I've definitely fallen into the habit of running comfortably rather than with a performance goal. My absence from racing explains that to some degree. I'm not sure that I want to start folding in faster paces in all my runs, but with cooler weather coming, it might be a nice thing to try.

Finally, I want to give a shout out to SIOR who finished in the top 8% of the Suffolk County Half Marathon this morning. It makes me proud to be a Runsketeer. Even if I'm the slowest one.

Early run on an early Father's Day

Obligatory selfie at the business park

Today's run (street): 4.2 miles

Although Father's Day is officially on Sunday, we always celebrate it on Saturday. That gives my family an entire day to spoil me without the specter of the workweek starting the next day. On top of that, my son is still studying for Regents and finals that he'll finish on Tuesday so Sunday will be a big review day. So today is Father's Day (observed).

We had lots to do before lunch and I thought I would miss out on a chance to run in the morning. Like yesterday, I got out early and managed to get my miles in by 7:30. I'm planning to run with my buddies tomorrow morning and I'm targeting about 6 miles for that. I decided to cover less distance on today's run to ensure that I stayed on schedule.

I got my GPS signal and went directly over to the business park to run a few loops. Although the elevation loss and gain is the same in either direction, I prefer to run this route clockwise. That allows me to get most of the gain out of the way in the first third of the loop. I did two full and one partial circle before turning back for home.

As I mentioned in yesterday's post, I'm still struggling to generate speed. The perceived effort I'm putting in feels higher than the numbers I'm producing. Today's weather was as good as I could ask -- 70°, moderate wind and relatively low humidity, so I would have expected a little better performance.

We had a nice lunch in Huntington this afternoon and more Father's Day things will happen tonight. I'm looking forward to seeing the Runsketeers in the morning, although I may be seeing them through sheets of rain.

The good and the bad of weight loss

Today's run (street): 3.3 miles

Weight and running are often linked together. Many people run either to lose weight or to keep their weight at an optimum level. Some serious runners starve themselves to the point of emaciation because the less weight you carry, the less work is required to hold a pace. I took up running in 2008 when my weight slipped into the unacceptable range. By improving my diet, reducing portion sizes and running almost daily, it only took a few months to reach my target.

Over the past six years I've held my weight steady. Except for a period in 2010 when I lost a lot of weight due to pneumonia, I've stayed close to my original target. But over the last year I've put on a few pounds. Not enough to require me to go up another pant size, but enough for me to re-assess my diet.

I plan to reset and drop back down to my ideal weight. My question is how low do I go? From a running perspective, I would probably see better performance if my weight were 3-5% lower than my current target. I can get there, but I'll pay a price. When my weight drops below normal, the first fat to go is in my face. I end up looking wan and drawn. So much for my maintaining my boyish good looks.

For now, I'll work on getting back to normal and decide whether to go lower when I get there. The Runsketeers will be doing mile time trials next weekend, so I'll see if I can make some weight reduction progress over the next eight days. I may be naive to think it could make that much of a difference, but you don't see too many elite runners who resemble Homer Simpson.

I'm sending good thoughts and wishing for good weather for SIOR and TPP at tomorrow's 10 mile Run to the Brewery. You guys will rock it.

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.

Race report: 2014 Jingle All the Way 5K

Post-race coffee club (L to R: ER, TPP, SIOR)

Today's run (Jingle All the Way 5K): 3.1 miles - Time: 28:20 (9:08 pace)

After many months of resisting the call of competition, I returned to racing at the Jingle All the Way 5K in Seaford today. Joining me on this chilly morning were fellow Runsketeers SIOR and TPP, both of whom finished first in their age groups. The early results showed TPP at #1 and SIOR in the top three, but later she was bumped up to first as well. I'm sure there was no bribery involved in that decision. Well, pretty sure.

I didn't podium, but I had my best race performance in a year, finishing 5th in my division. This meant something to me, because my performance has suffered since January and I'd lost confidence in my ability to attain a credible pace (even on a 5K). There's still room for improvement compared to past years, but I did beat my expected time by over a minute.

I arrived at Cedar Creek Park in Seaford around 8:00 AM and missed the registration area as I drove through the park. I ended up parking about a quarter mile away because I saw a group of people, some of them running, and figured that was it. That turned out to be a soccer game, but I was quickly redirected by some kind spectators and made my way to check-in.

I dropped off my toy (the event is sponsored by the John Theissen Children's Foundation), got my number and found SIOR. She and I headed back to my car so I could store my jacket and affix my bib number. Unfortunately, the package contained no pins, so I ended up back at registration to get some. Along the way, we ran into TPP who was doing a warm-up jog and the reunited Runsketeers all headed toward the start.

This race is fairly small, with only 222 people participating, but they did a nice job, including placing wood burning stoves where you could toast marshmallows (and keep warm in the 30° temps). The downside of that was the possibility of smoke inhalation. After they played the national anthem, we were ushered toward the road for the start. I got a fairly forward position because there was no timing pad at the starting line and I wanted my net and gun time to be as close as possible.

That position probably helped me overall today, because I kept up with many people for the first mile, which turned out to be my fastest. The course itself is not that interesting. It's a lollipop-shaped route with a turnaround at the bottom of the "stick." Heading toward the turnaround, I first spotted SIOR among the leaders. Not long after that I saw TPP and soon rounded the bend to start my way back to the top.

My biggest concern about this race was being able to hold a brisk pace for the duration. Even though it's not a long distance, I've done very little to prepare for prolonged running intensity. Last weekend I played a bit with speed, but suffered some glute, hamstring or sciatica pain afterward. I decided to push harder than I normally would on a training run and see how it turned out. The course was relatively flat, but there were some elevated sections, including one that had us running directly into the wind.

Once I got to the circular part of the route I knew I had only about a mile to go. I maintained my speed, but didn't overdo it. Had I looked at the Garmin, I may have upped the effort enough to make up the 25 seconds I needed to average in the 8 minute range. As I got closer to the finish, I saw TPP's boyfriend JC who was on his bike, cheering us on. JC shouted some words of encouragement as I passed by and I soon entered the finish chute where I saw TPP and SIOR watching and cheering me in.

JC left to do a two hour bike ride (he's a hardcore triathlete) and SIOR and TPP located a Starbucks for our traditional post-run coffee break. SIOR was taking her daughter and her friends into NYC for an important birthday (13) so she needed to leave first. TPP and I hung out and caught up for a while before we headed off to start the non-race portion of our day.

I'm very pleased with today's result and proud of my buddies who led their age groups. I checked to see what I needed to pace to have podium-ed today and saw that there was a lot of distance between my finish time and the third place runner. I'm going to have a low mileage week but that's okay. I wanted to give my "injury" time to heal. I did feel soreness during the race, but it was minor.

Tomorrow I'll do some easy miles. The weather is supposed to be warmer and I'm looking forward to a nice recovery run. I'm not sure if I'll race again before January, but at least I'm back in the game.

Jingle on the way

Today's run (street): 3.8 miles

There are sure a lot of Christmas themed 5Ks on Long Island. I ran the Ho Ho Holiday race a couple of years ago and last December I ran the Hot Chocolate 5K with SIOR. There's also the Jingle Bell run, Stuff the Sleigh, the Toy Trot and the Holiday Fun Run. It's been months since I've raced and I'm feeling ready to return to the starting line. I'm excited to be running the Jingle All The Way 5K with my buddies on December 13.

I used to avoid 5Ks because it took a lot of time and effort to do something that goes by in less than 30 minutes. 10Ks were my favorite distance because they're short enough to require tactical speed, yet long enough to require a smart pacing strategy. However, after many month's hiatus from racing and little performance focused running, a 5K seems like a good way to restart competition.

This morning I woke up with a pain under my arch and I wondered if I'd bruised a tendon during yesterday's rough trail run. I'm always concerned that I'll develop plantar fasciitis, which is the fourth most common running injury. I debated whether I should take a rest day to help my foot recover. After having some coffee and walking around the house, the pain diminished and I decided to go out for a few miles to see how it held up.

It was very cold this morning, so I went with the Opedix Knee-Tecs once again for warmth. My objective was a 3-4 mile tempo run. I planned to start easy and increase speed after a couple of miles. If my foot pain returned, I figured I would keep to the original pace or shut down the run. After 15 minutes without pain, I stepped it up and maintained a faster pace until the end.

I ended up improving my second half pace by a full minute over the first. It still wasn't to the level of performance I'm hoping to attain on the 13th, but it's going in the right direction. I'll see if I can maintain a higher intensity in my runs leading up to the race date. There's nothing like having a race on the calendar to motivate you to try a little harder.

Perceived effort was not enough

 

Today's run (street): 4.6 miles

Yesterday's run in Old Westbury provided a great hill workout. Today I thought I'd keep it simple and keep my running to my local roads. It wasn't as cold as Saturday, but it was still pretty chilly. I wore the Opedix again, along with three top layers. It wasn't until I took my first steps off the driveway that I knew my legs had recovered well. I had high hopes for a performance improvement and I sure gave it a try.

After we finished preparing for our runs this morning, my wife said, "Okay, let's get our runs on!" We were both ready to get going - she to the treadmill and me to the street. I was psyched knowing that I would be dealing with less distance and lower elevation today. My plan was a four mile run with negative splits.

The temperature was 35° and there wasn't much wind. I was comfortable in my gear and I felt good from the start. I'd left my HRM home and though I had my Garmin, I decided to run by feel instead. The first mile went by quickly and I was convinced that I was beating Friday's moderately brisk pace. I avoided looking at the readout on my watch because I didn't want to be discouraged, or overly encouraged, by what I saw.

I'd started around 7:30 AM and there were few cars or people around, although I kept crossing paths with two other runners. I felt like I was moving a lot faster than yesterday and was hoping to finish with a big surprise in terms of time and pace. I was surprised, but not in a good way, Running by feel did not generate the speed I'd hoped for. I did achieve negative splits, but my pace was 30 seconds off of Friday's.

On the positive side, I put in almost 20 miles this week, had some good workouts and got to run and hang with my friends. I'll take that over performance anytime.

Cool, energizing, hot and humid

Saturday's run - negative splits

Today's run (street): 3.9 miles
Yesterday's run (street): 5.5 miles

This weekend has turned out to be busier than I expected and all my hopes for running with friends has gone by the wayside. I did manage to eke out ten miles between yesterday and today, but only by wedging those runs between other activities.

Yesterday's run was great. It was a little warmer than Friday, but still cool, dry and energizing. I did a tempo run, keeping my pace moderate for the first 20 minutes before increasing my speed throughout the rest of the run. I ended up running negative splits, with the last mile equaling my 2012 training pace.

This morning was so humid that I almost skipped my run in favor of an indoor elliptical workout. At least I could do that with my big fan cranked up to hurricane setting. TPP, SIOR and I tried to coordinate a run the day before, but I couldn't allocate the time to do anything but a short local run. As it turned out, that was probably for the best, since weather conditions were draining.

I knew from the start that I'd be in for a tough time this morning. All the moisture in the air inhibited oxygen flow and I adjusted my speed to maintain a good aerobic balance. I had no breathing issues but the sodden air did not help my energy level. I'm sure I'll cringe when I see the Garmin data from today's workout. My cadence was probably 5 SPM slower than on Saturday.

Tomorrow is the last day of summer vacation for the kids and we have a lot planned. I may squeak in a few miles or do a short elliptical session in the morning. Depending on the weather later in the day, I may end up doing my workout in the pool.

Persaid at Stillwell and six miles on the road

 

Today's run (street): 6.1 miles

Last night we went out late to Stillwell Woods to watch the Persaid meteor shower. Unlike last year, when it was too cloudy to see much of anything at Sunken Meadow, the skies were clear on Saturday. Stillwell is a lot closer to our house, and its relatively light-free location would normally provide an optimal viewing experience. As luck would have it, the "super moon" lit up the southern sky last night, making it difficult to see any stars. However, facing north, we were able to view some exciting celestial fireworks.

My wife and son saw one that looked like this

SOURCE: NASA

Staying up late to watch shooting stars is fun, but getting up early the next morning to run is far less enjoyable. I downed my coffee, ingested a small amount of carbs, and took off before I could fully realize what I was doing. I didn't suffer from heavy legs or feel particularly tired as I ran, but a short night's sleep undercut my interest in pushing my pace.

Along the way, I thought about next weekend's Dirty Sock run and my decision not to participate this year. My interest in competing is still low and I was glad not to be preparing for that race. I know I could run it for fun and not worry about my time, but that doesn't work for me. If I'm going to take it easy, I'll do an easy run on my own. Besides that, my narcissistic side doesn't want a slow time added to my Athlinks racing stats.

I'd considered driving over to Bethpage this morning, but instead chose to stay local. My route wound all around the neighborhood and I kept my speed moderate. About four miles in, the run began to feel easier and I stepped it up to take advantage of my increased energy. The last two miles were easier than the prior miles and I was happy to get through my sixth feeling energized.

It's not the first time that I've ended up having a good run (or a good race) after less than a full night's sleep. I read recently that you don't really pay for sleep debt the next day, it's more often the day after. That's good because I'm resting tomorrow. If I can get a good night's sleep tonight, I should rebound well. There's supposed to be more of the Persaid shower this evening, but I don't think I'll be staying up for it. If you are able to do it, I recommend the experience.

Humid, hot and foggy, but still a great run

Today's run (street): 4.4

Today was crazy busy, but my saving grace was working from my home office. At least I saved a lot of commuting time. I got in my run (my first since last Sunday) and though I went out early, I was already behind schedule by the time I got back home. I should add at least one more run during the week to maintain my targeted level of fitness, but for now I need to keep the schedule I have.

The weather hasn't been good for running lately. This morning it was 67°, humid and foggy. Rain seemed imminent, so I decided to try my new running raincoat. The jacket isn't vented and I knew I might regret wearing it, since I knew it would trap heat. Still, I was curious to experience running with it.

Surprisingly enough, I stayed fairly cool for the first couple of miles. Better still, I felt strong from the start and maintained great form throughout the entire distance. I ran faster than I expected and probably would have improved on that had I left the jacket at home. The lack of ventilation had trapped sweat and my running shirt was completely soaked by the time I finished.

Perhaps it's the rest time I'm getting by not running Tuesday through Sunday each week that helped me today. I'm time-pressed again tomorrow, and I'm not sure how I'll be able to get in my miles. One way or another, I'll get out there. When I do, I hope to see a continuation of today's good performance.

The history of my running speed

Directional declines

Today's run (street): 3.6 miles

I decided to do some data mining on Garmin Connect to compare my historical averages with my current performance. In order to keep the information consistent, I only used data captured from one source, my Garmin 210 that I bought in 2010. I know I've lost a lot of speed over the past year and my interest was in seeing whether my recent history is an aberration, or if it merely reflects a long term decline.

Charting the trends reveals a changing relationship between race speed and overall speed. My average pace has followed a linear decline, but my race paces have dropped measurably since 2012. Up to 2012, I generally paced 7.5% better in races compared to my overall average. After 2012, that gap has closed and is now almost equal to my training run times.

As I often say when working with business data, these findings are only directional. The Garmin data, acquired by GPS, has a variable margin of error. I tried to correct for that as much as I could, but the numbers do have some skew. I only selected runs I'd tagged as "street running" to filter out slower trail paces and faster track paces. It's also important to note that the 2014 data is only through May 25, not a full year.

In terms of these findings, I'm not happy to see declines, but at least the drop-off has not been as sharp as I'd suspected. I did today's run as a tempo, taking it easy through the majority of the distance and picking up the pace more at the end. The last mile was a minute faster than the prior few, and I finished feeling great. I wish I could tap into that speed more often, but based on my recent race performances, it's a little more complicated than just trying a little harder.

Running in the right direction

A subtly better run 

Today's run (street): 4.4 miles

This morning's run was 25% longer than yesterday's and 1% faster. In other words, better. What the numbers don't show is how I felt during and after the run, and that's real reason why I was pleased with today's workout.

Friday's run was the first one I'd done since the Brooklyn Half and, after five days rest, I'd hoped for a good rebound. What I actually got was a rough 3.4 miles featuring a cranky stride and more fatigue than the distance should have produced. Rather than benefiting from an (almost) full week's recovery, I felt as if I had over-trained. I don't know if it was related to the run (or a fairly intense week at the office), but I was tired for the remainder of the day.

This morning was sunnier than Friday and a little breezier. I didn't get out as early as I'd planned because I got caught up watching an episode of Lillyhammer with my son. Worth the wait. Once I got outside, I was ready to run. There was no delay with the GPS this time, 20 seconds and I was good to go. The air smelled of cut grass and something that might have been mesquite. I took off in a direction that bypassed the landscaping crew trucks that were parked up and down the road.

I had targeted four miles for my run today without any particular route in mind. I encountered some runners and walkers along the way and I observed a number of people packing up their SUV's for what I guessed were Memorial Day getaways. I felt relaxed and tried to open up my stride as the run progressed. Overall, I slightly improved on yesterday's pace.

I may go out for a little more distance tomorrow, depending on how our schedule goes. While I didn't see a dramatic improvement in performance over yesterday's, I certainly had a more encouraging experience. I finished the run feeling strong and had no after-effects like I did when I finished Brooklyn. After feeling a little down about running this week, my motivation is on the rise.

First run after Brooklyn

 

Today's run (street): 3.4 miles

It's only been six days since I ran the Brooklyn Half, but it seems like a long time ago. I'm sure that's due to a five day hiatus from running and the fact that my business focus is taking up most of my attention these days. I planned to take more than my usual three days off from running after Brooklyn and it wasn't until this morning that I finally got out on the road again. I'd hoped that all the rest I've had this week would result in an energizing run. Not quite, but it wasn't all that bad.

It was a gloomy morning and I'll admit to being less than motivated to do this workout. I had a lot of business items that I could manage from home today, so I replaced some of the time I'd be driving to the office with a short run. The skies were growing darker, so I got out early to try to beat the rain.

It took almost ten minutes for my Garmin to acquire its signal through the low cloud cover. I grew increasingly anxious as the progress bar on the watch moved slowly to the right. It repeatedly went 9/10ths of the way before dropping back toward the middle. I'd almost gave up on timing the run when it finally showed ready.

Once I got moving, I began to think about the run itself. Three miles was my target, give or take a few tenths. It seemed inconceivable that I'd participated in a 13 mile race less than a week ago. I wasn't feeling a long run, but I figured I could easily handle three miles today. The temperature was a mild 58°, yet I felt a slight chill with my short sleeve shirt and running shorts when I stepped outside.

With only one workout done in the past week (40 minutes on treadmill, not running), I was dealing with tight muscles. My stride felt cumbersome and mechanical. My form evened out after I'd fully warmed up and my cadence began to feel more natural. Even though it was a short run, my performance was marginal. I didn't try to push today as this run was primarily about getting back to routine.

I have hopes of putting in a couple of longer runs over the long weekend and, if possible, try to get in a trail run. My motivation remains fairly low right now, but that can probably be corrected with a couple of good runs.

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.

Performance is down, but excuses remain high

Ready or not, here it comes

Today's run (treadmill): 25 minutes

My running has slid back into the questionable range. I had a tough time running a very slow 5K on Sunday. That may have been due to over-training last week, shoelace malfunctions or something less obvious. This week was the start of my new job and, after taking my usual Monday rest day, I skipped Tuesday as well. This morning was a return to 4:00 AM running and it didn't go particularly well.

After 20 years of commuting on the Long Island Railroad into NYC, I had a break over the last year. I didn't miss riding the the train and I still don't. But instead of the train, I'm now driving 75 miles a day to and from my new office. Driving is not fun and I've decided to head out around 6:00 AM to minimize the amount of traffic delays on the LIE, Route 95, etc. Consequently, the window for early running before my commute is short. And unlike train commuting when I could take a seat and sleep, I need to be 100% alert when on the road.

I happened to have an all day meeting in the city today, so I got on the treadmill at 4:00 and ran for 25 minutes. It was one of the toughest workouts I've had in a while, and I'm wondering why. Since I'm making plenty of excuses about my sub-par 5K performance, I'll make more by saying that two days of driving on highly trafficked roads, plus full days in the office, have exhausted me. I'm hoping it's just that. Brooklyn will happen soon and my running confidence has taken a big tumble since last week.