Not my finest run

A few tired miles around the 'hood

Today's run (street): 3.7 miles

Despite better weather, today's run didn't go all that well. I'm either run down or I pushed too hard on yesterday's run. I'm not a fan of running uphill and my legs reminded me of that today.  I was hoping that (sort of) keeping up with SIOR and TPP at the NJL park might have activated my fast twitch leg fibers. I actually think they were deactivated.

My goal every weekend is to do at least one run outside of my neighborhood. Since I did that yesterday, I figured a run around my local roads would be just fine. I started out well, although I did experience sinus pain when the wind hit me head on. Thankfully that went away once I'd warmed up. I began to feel lethargic the more I went on and I noticed that my heart rate was showing less than 75% max. Despite the fatigue, I picked up the pace until I was in the low 80% range. That was all I could manage today.

Yesterday's run was understandably challenging because I ran about 10% faster than I normal do. Plus there were some hills. Today's difficulties are a little harder to explain. I never struggled, but I did get tired. Perhaps it was getting up at 4:30 AM this morning that did me in. I'll get some rest tomorrow and try this again on Tuesday.

Feeling low and staying low

Declined to incline

Today's run (street): 4.2 miles

There are days when I know when I'm in for a good run and other days when I strongly consider other workouts. I wasn't feeling it this morning and my instinct was to explore options such as strength training, elliptical or core. Rather than decide, I took the easier path and ran. Not that the running was easy. It was not.

Yesterday's difficult run could be blamed on overdressing or overeating (or both). I had a decent night's sleep and chilly weather in the morning. Both are positive conditions for a good run. However, I lacked my usual energy and that accounted for a change in plans from my original route.

I was going to run to the top of the Bethpage bike trail at Woodbury Road and follow the path to the LIE overpass and back (red highlight on map). By the time I reached that road, I decided that I wasn't up for that long incline and elected to follow Woodbury Road to Meyers Farm and back. My run along Woodbury Road turned out to be harder than expected as the path was covered in a thick layer of leaves.

Despite lacking energy, I was able to hang in for a couple more miles. Like yesterday, I was pretty worn out by the end. Not a great week for mileage, but I did manage to get in four workouts. I'm hoping I'll rebound by next weekend.

Exhausting week and pumpkin-y run

Pumpkin: gourd and shirt category

Today's run (street): 3.5 miles

I knew I was facing a long, tough week despite the Monday holiday. It seemed to take forever to get to Friday. Besides a busy workday schedule, I had an exhausting Board of Directors dinner on Thursday night that got me home fairly late. It didn't help that I needed to get in the office extra early on Friday morning. My Friday evening was spent at a fun event called Rise of the Jack O'Lanterns but I was reaching zombie state by the time I turned in.

I managed to sleep later than my usual 6:00 AM rise time and hoped that all those hours of rest would restore my energy level. However, even after eight hours sleep I was feeling run down. Any thoughts of getting out for an early run were offset by fatigue and slight dizziness. I had two cups of strong coffee and it wasn't until I checked in with the Runsketeers to get a read on how to dress for my run that I geared up and headed outside. By then it was almost 10:30.

Conditions were fall-perfect, the temperature was in the low 50's and the sun was shining. I wore a long sleeve running shirt with compression shorts under regular running shorts. I also wore a pair of light knit running gloves that kept my hands comfortable. I followed one of my usual routes around the neighborhood and motored along at a comfortable pace. The lack of hard effort and the cool dry air kept me sweat-free throughout half the run. The air had the smell of maple and burning leaves and the pumpkins and Halloween decorations were out in force.

I haven't checked my Garmin data, but I know today's performance was unremarkable. Some of that was due to feeling less than 100%. I also know that I'm never going to get back to my old performance level if I continue to run only three to four times a week, mostly at distances between 3-4 miles.

Just a few years ago, I was typically running 6 days a week and logging between 18-22 miles. That put me in a position where I could run a 5 or 10K at a moment's notice and confidently hit my targeted pace times. Until I can figure out a way to fit in some additional weekday runs, I'll need to be satisfied with the pleasant, easy runs I'm doing these days.

Undone by a mis-selected K-cup

Dear Bro: can GMC increase the font size of its decaf label?

Today's run (street) 4.2 miles

Our trip provided three days of high energy fun but rest time was at a premium. Last night, it was a treat to finally sleep in my own comfortable bed and I looked forward to waking up feeling refreshed and ready for good long run. I got up a little before 6:00 AM and made a cup of coffee to start my engines. Instead of feeling rested and energized, I felt like going back to bed. I decided to relax for the time being, even though I wanted to get out early to beat the heat.

I couldn't understand why I felt so tired, but I managed to gather my gear for my run. I had been thinking about a six miler, possible at Bethpage, but I couldn't shake the feeling of fatigue. I decided to stay local and modified my targeted distance to three miles. I figured it would be better to do something, rather than not running at all.

The sun was still low in the sky when I finally took off at 8:30 AM. I kept an easy pace that I knew I could sustain. The humidity wasn't as bad as it was during yesterday's afternoon run, and I knew I could get through a short workout without much problem. I thought about the track workout I did with SIOR and TPP a few weekends ago when I logged some decent 400's. I tried to duplicate the turnover I used to make those sub-8:00 quarters, but the speed didn't come today.

Surprisingly enough, I was able to beat today's shortened goal. In fact, I covered more distance than yesterday, when I barely got through four miles. Still, I was unusually tired after I finished, and that fatigue continued after a cooling shower and lunch. I decided to have another cup of coffee, hoping that would wake me up and help me get rid of a dull headache. That's when I discovered the probable cause of my lethargy.

When I removed this morning's spent K-cup, I realized that I'd accidentally put in decaf version of Green Mountain Dark Magic. I had been operating caffeine-free all day, no small thing for me. I don't need much caffeine, but I definitely need it in the morning. One cup is all it takes to return me to the world of the normal. I quickly made a cup of leaded and, within ten minutes, I was energized and headache free.

Tomorrow I'll try to break out of my four mile range with a longer run. I'm not sure where I'll go, but you can be sure I'll be starting my day with an extra strong cup of caffeinated brew.

Angry workers and the endless trail

My view of the trail today

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

With the Marcie Mazzola 5K happening on Sunday, I needed to figure out a way to get my long run done this week. On Wednesday I logged six miles and was planning to run 10 or 11 on the weekend. I didn't want to run that much the day before a race, so I decided to cram it in today. I'm wrapping up a lot of things as I prepare for a new role on Monday, so my schedule was tight.

I decided that the bike trail was my best option, so I drove to the small lot that sits on the bike trail north of Old Country Road. I quickly started running north until I reached Washington Ave and turned around to run south. My target was 10 or 10.5 miles and I felt great. The weather was perfect and the setting serene. I must have seen thirty cottontails along the path and countless birds. Not too many people though.

I did fine through the first five miles despite the hills that came about every quarter mile. My only concern was time, because I needed to be home (and hopefully showered) before a business call that was happening mid morning. Once I'd traveled south of the Bethpage lot and down the big hill, I started to feel a little fatigued. I'd swapped the sock liners in my Virratas for gel insoles and that turned out to be a good idea. However, the softer landing probably made me work a little harder on the hills.

By the time I reached seven miles, I became concerned that my progress was not fast enough to meet my timeline. I was really feeling fatigued and the trail seemed endless. I also realized that I did bad math in terms of turnaround point and I wouldn't quite make ten miles. Oh well, it was only a 3/10th of a mile difference. The only disruption to this placid experience was when I reached Old Country Road near the end of my run.

Before I'd rounded the corner to the street, I heard loud male voices screaming at each other. It was mostly expletives. These were town or county workers who were fixing the bike trail at the point where it met Old Country Road. I was mildly concerned because I needed to run between them to get across the street and more concerned when I saw that one of the arguers was driving a huge front loader.

I think they realized the danger of interfering with a civilian, so they stopped while I passed through. Immediately after, the guy in the front loader started yelling, "I !@#$% quit!" By then I was on the trail on the opposite side heading to my car.

Even though today's distance was almost the same as last Sunday's, today's run was far tougher. I'm hoping it had to do with running almost ten miles after running 6 just two days prior. For some, that would have been a non-issue, but it was only about five weeks ago when I was struggling to complete 4 miles on this same trail.

Tomorrow I will rest and Sunday I'll race. What I'll do for training next week is still up in the air. I'll have to see what my schedule holds.

Zapped and tired

Zapped again

Today's run (treadmill): 45 minutes

I woke up feeling tired with a scratchy throat this morning. Morning is when my energy level peaks, but even with two cups of coffee, I felt fatigued. It was "near-end-of-vacation-pancake-day" so I had to participate. I added a cup of decaf to my coffee intake and figured the extra carbs from the pancakes would help fuel my run. If that was the case, it was a short term benefit.

My treadmill workout did not go very well. I knew I'd have trouble maintaining Friday's pace, so I started at a speed that I thought I could sustain for 40 minutes. Although the temperature has risen throughout the week, the humidity has remained low. About three minutes into the run, my hand brushed the treadmill's HRM grip. This caused a spark that wiped out the display but I didn't notice it for another minute. I reset the treadmill without knowing how far I'd actually gone.

The next ten minutes went okay, but I soon felt tired. I usually wouldn't stop a run due to fatigue, but today I made an exception. I gave myself a minute to recover before restarting the machine and dialed down the speed a half a MPH. I was able to manage through for another 30 minutes, though I don't know if it was wise to continue.

I'm hoping my strength will return so I'll be on my game tomorrow. I keep expecting a cold to come, but so far it's mostly just fatigue and an irritated throat.

Super Bowl Sunday but not a Super run

Go teams!

Today's run (treadmill): 5.1 miles

Apparently there's some big football game happening today. I'm not much of a sports fan (except for running), especially at the professional level. My youthful obsession with the Boston Red Sox and Bruins gave way to the practical realization that a favorite player's loyalty only extended to the length of his contract. In terms of my interest in today's Super Bowl, I'll go as far as to say that I'm curious to see some of the commercials.

My plan this morning was to get outside and run in my neighborhood, something that I have not done since January 15th. Conditions were okay to do that, with moderately warm temperatures outside and fairly clear streets. There was fog, but it was dissipating. I have some high visibility clothing (and pulsating LED lights) that would have ensured that I'd be easily seen.

I was tired after I'd woken up and I found it hard to motivate myself to get out and run. I knew I'd do it, but as the morning grew long, I decided to follow my wife on the treadmill after she'd completed her workout. I was determined to put in my five miles, even if it was going to happen inside.

I started my run at a brisk pace, but dialed it down at the two mile point. I wasn't fatigued, but I thought the original pace would be hard to sustain throughout the next three miles. The warmer temperatures outside translated into hot conditions inside. By mile three, it felt as hot and humid as summer. I ended up bringing my speed back up to my original pace for the last half mile. When I finally finished, I debated whether a nap would be preferable to a shower. I went with the shower.

Tomorrow is my rest day and I'm looking forward to some recovery time. I'm debating whether I'll even turn on the game later, but I am interested in the fact that it's taking place in the NY area. Either way, I'll be glad when I'm finally be able to walk through Time Square without dodging Super Bowl events. Even more, I'll be thrilled to get past the ongoing debate between New York and New Jersey on the provenance of the Super Bowl.

A little Xmas contribution to my 2013 mileage

A white-ish Christmas

Today's run (street): 3.3

It's Christmas day and even though it's a Wednesday, it really feels like a Sunday. That being the case, I was prepared to go out for a long run this morning. When my wife mentioned the combination of 20° temperatures with a wind chill making it feel like 11 degrees, I considered an indoor run. But I had counted on running outside today along the quiet, snow-dusted roads, and I decided to deal with the cold by adding extra layers.

I thought about how wearing compression pants under track pants, along with three upper layers, might slow me down. Since I wasn't planning to go out for a fast run today, a little speed restriction didn't bother me at first. I made my way through the first few roads at a jogging pace and encountered some bundled-up couples who were taking a Christmas morning walk. They greeted me happily when I went by. My present was not giving them a lecture about walking on the wrong side of the street.

The conditions made the going tough and my face was beginning to freeze. It can be very uncomfortable running with glasses in the cold, especially when the wind is hitting head-on. I own a balaclava, but it restricts my breathing and traps moisture that causes my glasses to fog up. Besides that, the tightness at the sides creates a fit issue at the temples that can tilt the lenses and distort my view. I haven't worn contact lenses in 20 years, but days like today make me miss them.

At around the one mile point I began to tire. I was running easy so I didn't understand it, but I definitely lacked energy. It could have been the cold or the extra weight of so many layers, but I just couldn't generate much speed. I toughed it out and ended up covering 3.3 miles. I'd planned to go longer but I was glad to finish when I did. It was nice to run without needing to share the road with cars, trucks and buses, but I was somewhat disappointed with my performance.

Mileage history (2013 projected)

My speed and stamina have taken a dip since the Hot Chocolate 5K and I wonder if I need to take a few days off to rest. I may do that tomorrow, but I need to get back to schedule after that. I'm 12 miles short of hitting 900 miles for the year, which means I'll need to cover at least that distance in the next week. Even so, I'll end up running 41 less miles in 2013 than 2012. But that would still be 100 more miles than I ran in 2011.

A run most difficult. Please explain why.

Today's run (street): 3.5 miles

Today was a tough one. I don't know why I had so much trouble getting through the run but it was a heavy-footed plod from start to finish. There is nothing I can point to that would explain my struggle. I got a good night's sleep, have no symptoms of a cold and the weather was cool and dry. Yet no matter what my mind was telling my body, my body answered, "Don't expect much."

Yesterday's route seemed short and I was surprised at the end to see the distance I'd covered. Today was opposite of that. My route was circuitous and I expected to consume most of my miles within the northern part of the neighborhood. I had a time target, but I wasn't as pressured as much as I was yesterday. I thought I was racking up the distance until I reached my turnaround point and saw that I was well short of my expected mileage. When I approached my home street, I realized that I needed to run another half mile to make my goal.

Although I ran at a sustainable pace, I felt like I was carrying an extra 30 pounds throughout the run. This wasn't the first run I've had like this, and I know that tomorrow's may be far better. I hope that's the case. One bad run is a statistical probability. Two bad runs in a row is a trend.

No rain, pain, or running strain

Today's run (street): 3.6 miles

Earlier this week the weather people on TV were talking about significant rainfall and flooding by the weekend. I was resigned to the probability of having to do my longer runs on the treadmill. While yesterday's run was wet, it wasn't anything like running in storm conditions. I expected this morning to be much worse. Happily, it was much better.

Sometime between 7:00 and 8:00 AM this morning, my energy sapping pressure headache disappeared. Between that annoyance, and the cold and rainy weather we've had, running can be more pain than gain. When I realized that the pounding from my sinuses was gone, my outlook brightened. After looking outside and seeing white, rather than gray skies, I felt even better.

Yesterday's run, while feeling low, was more symbolic than beneficial. Although my headache had cleared, I still held the expectation that today's run would be challenging. I considered not tracking my speed and distance so I wouldn't feel bad about my expected mediocre (or worse) performance, but I decided that I needed to face up to it. Besides that, I'm racing in a week and I have to focus on speed at some level.

Since you are reading this, there's a good chance you're a runner. And being a runner, you know that the first minute of a run can speak volumes about how the rest of your run might go. This morning I was surprised, in the best of ways, to find my energy level at the high end of the spectrum. I knew right away that this run would be much faster than yesterday's, and it was. The fatigue I experienced on Thursday was completely gone, replaced by the feeling that I could run all day.

I felt great all the way through but, due to my business schedule, I needed to cap the length of my run. This was quite a contrast from yesterday when, by the end, I felt like I'd just run a 10K at race pace. It was a nice way to finish out the week, especially one as tough as this. I'm looking forward to my last race training workouts this weekend before I taper down throughout next week.

Tough Thursday, restful Friday

A well timed break

Yesterday's run (street): 3.5 miles

I'm not sure if it's connected to the flu shot I received on Tuesday, but yesterday I went from feeling tired to feeling exhausted. On top of that, I developed a sore throat that grew worse as the day went on. Unfortunately, I needed to be in the city to kick off a project, and that involved a lot of talking. It wasn't an ideal situation, but I managed to get through the discussions.

Earlier in the day, I did an easy run around the neighborhood. I'd woken up lacking energy and modified my original plan to work on increasing my cadence. I got out a little earlier than usual when temperature was still pleasantly cool. The run felt great and I thought I was off to a good start for the day. By mid morning that had all changed.

I've decided to forgo my run this morning. This is starting to become a habit, with the last couple of Friday runs being substituted for walks at Bethpage with my wife. We both have busy schedules today, so there will be no opportunity to get there today. I'm hoping that getting some additional rest today will get me back to full strength. I need to increase my hill training as I prepare for my upcoming 5K.

Controlled conditions can't control humidity

Yesterday's run (treadmill): 3.1 miles 

One syllable sums up yesterday's run - ugh. I've been focused on a project this week, and days of intense viewing on my laptop created fatigue that was exacerbated by yesterday's brutal humidity. By the time I was ready to run, it was too hot and humid to be outside. I figured I'd do better in the controlled conditions of my workout room. That wasn't quite true.

I set the CAC to 76 degrees, cranked up the floor fan to high and turned on the puny treadmill fan. My plan to start fast was a miscalculation. After a mile run at 6.7 MPH, my heart rate was approaching 90% of Max. I dialed back my speed and, even at 6 MPH, I was sitting at 80% Max. I slowed down even further, until things came more into line. I eventually worked my speed back through the last mile, but by the time I reached my targeted distance, I felt exhausted.

I was glad to get my workout done, but with the relentless humidity, I may have pushed too hard. I felt worn out the rest of the day. Conditions are less humid today, but I'm going to run easy to prevent a recurrence of that fatigue. I'll do my last race training over the weekend and will then start my taper and rest during the week. I hope I still have some speed left in my legs.

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.

Business exhaustion + run exhaustion = redemption

Wheel of redemption

Today's run (treadmill): 3.1 miles

I thought that leaving my job might profoundly change my life. Actually, it has, but not exactly in the way that I expected. I'd imagined myself taking leisurely runs on the trail each morning, followed by a variety of activities that I've put off for years. Despite those expectations, my running schedule hasn't really changed. Highly anticipated activities, like returning to playing my classical guitar, have been put on hold. I may not be getting up at 3:30 AM anymore, but I'm working harder than ever.

Much of my attention has been diverted to a consulting practice that I recently started. Creating a business requires many steps, ranging from setting up legal and business resources, to selling services to clients. So far it's been energizing, but all the meetings, calls and proposals can wear you out. That became evident this morning when some work I was doing distracted me past my scheduled run time. After forcing myself to stop, I realized staring at web code for hours had given me a pounding headache. Instead of a run I felt like I needed a nap.

We were up late last night, but I'd found it impossible to sleep past 6:00 AM. I'd planned to go to Stillwell for a trail run. Soon enough, I started self-negotiating to shorter distances on local roads. The wind was blowing hard outside, further eroding my motivation to do my run. I started thinking about forgoing my workout altogether.

In the meantime, my wife who was similarly tired from our late night, had completed her workout and taken a shower. She said it made her feel better, although she felt her run was harder than usual. Inspired by her, I made my way to the guestroom to face the treadmill. I made no pretense that I'd make it a speedy run. This workout was far more about maintaining commitment than improving fitness and conditioning.

I started by running a pace that was 15% slower than usual, and stuck with it until the display showed one mile. From there, I began to increase the treadmill speed every couple of minutes. By the time I'd reached two miles, it was feeling like five. The experience of watching the readout slowly tick toward three miles was torturous, especially since I'd increased my speed to a relatively brisk pace by then.

Considering the short duration, I haven't had many runs that felt as hard. I was thrilled to kick down the speed after 3.1 miles for cool-down. Although I was wiped out, I was also energized, and my headache was gone. This workout felt like redemption and I was very pleased that I didn't skip my workout. On the downside, I realized that I'd failed to transfer my Fitbit to my running shorts so I didn't capture all those steps and distance. I may have lost all that data but I gained back some self esteem. 

Correlating my sleep time and run fatigue

Frozen Fitbit

Today's run (street): 4.8 miles

Yesterday afternoon I checked my activity progress on the Fitbit only to discover that the readings hadn't changed since morning. The numbers displayed at 5:00 PM were almost the same as they were at 9:30 AM. I took some steps to see if they would record but the numbers didn't change. I connected the Fitbit to my laptop using the USB charging cable and that seemed to jolt it back to life.

I was happy that the device was working again, but disappointed that I wouldn't get "credit" for the steps, miles and flights of stairs that didn't get captured yesterday. I'll watch the display a little more closely, now that I've had that experience. It was working fine this morning and I took it along during my run.

I again recorded my sleep pattern overnight and saw that I'd slept a total of six hours. The good news was that I "only" woke up six times instead of twelve. The Fitbit site assigned me a sleep efficiency rating of 96%, far better than the first time I tracked my sleep cycle.

Perhaps it was a lack of sleep time that factored into the fatigue I felt during today's run. I'd averaged 40 more minutes of actual sleeping time prior to last night. After yesterday's rest day, I expected to feel slightly more energized than normal, but a few minutes into the run I knew something was missing. I set the best pace that I could, determined to cover my distance target of 4 miles.

When I run, I often think about racing and how I'd feel if I was in a race in that moment. I'll often tell myself that I could manage more speed, if needed. Depending on the distance, I can usually muster enough energy to pick up my speed and sustain a better pace. Today I hoped I had enough in the tank to get me through the route I'd planned.

I was determined to get in a full workout and, after making a few loops through my immediate neighborhood, I crossed into neighborhood #2. I had this dual sensation of feeling tired yet ready to cover my distance. There were a few points where I could have cut the run short, but I didn't. In fact I ended up running almost a mile longer than I expected. I was plenty tired by the time I got home and a little puzzled that my heart rate didn't reflect the perceived effort I was experiencing.

Tomorrow I may keep it short, as I'm close to reaching my weekly mileage goal. If my energy returns I may even do some speed work. I'll try to extend my sleep time 40 more minutes and get back to average. I think that contributed greatly to my tiring experience this morning.

Caleb Smith trails: bad conditions for both run and runner

Hazards abound on the Caleb Smith trails

Yesterday's workout (Caleb Smith State Park): 3.4 miles (run), 1 mile (hike)

It was a busy Saturday for us, and I didn't get a chance to post about yesterday's activity until this morning. Yesterday afternoon we headed over to Caleb Smith State Park where my wife and kids participated a candle making workshop while I hit the trails. Hurricane Sandy had done a lot of damage to the park, but they'd just re-opened the yellow trail. The blue, green and red trails still remain closed.

Prior to leaving for Caleb Smith, we'd stopped for lunch at Moe's. That was a mistake on my part. Lunch was fine, but I didn't give myself enough time for proper digestion. I thought I felt fine when we arrived, but soon after I'd started toward the trail I could tell that's the going would be tough. I pressed on hoping that I'd begin to feel better as time went on.

After a mile I couldn't ignore the discomfort. It wasn't a stomach issue, but I felt lethargic and my legs felt heavy and unresponsive. I decided to walk it off and covered a half mile before resuming my run. The trail was in poor condition, with branches strewn along the path by the storm and thick mud from the morning rain. The parts of the trail that were covered by leaves were the most run-able.

I felt marginally better after a half mile hike and resumed my run for the next mile. I had looked forward  to this trail time, but I wasn't enjoying it much. The trail markings were a little inconsistent and I found myself on the closed paths once or twice. In most cases I could keep going until I reconnected to the yellow trail but once or twice I had to double back.

At one point I thought I saw another runner through the trees, but couldn't really see much, except that it clearly wasn't a squirrel or a fox. I thought it was odd that someone would run off-trail, especially with the current conditions. During my next loop around, I detected the same movement and saw that the "runner" was actually a deer. I noticed two or three others soon after. They kept their distance but didn't run away when our paths came together at a clearing.

I ended up running over 3 miles, though not continuously. I was happy to be finished and vowed not to repeat my mistake of having a big lunch prior to an effort of that scale. After my run, I spoke for a while with a ranger whose team maintained the park. He told me it would be some months before the cleanup was completed. There's a lot of tree damage that they can't get to with heavy equipment so it comes down to a two man crew that uses old fashioned methods to precision cut and remove damaged trees.

I'm planning to do a neighborhood run later this morning and really hope that yesterday's running difficulties don't carry forward to today. I'd rather have yesterday's lunch to blame than to be dealing with a bigger issue related to being ill.

Incomplete recovery is better than none

Yesterday's troubles continued through the night, and I got to bed early in hopes on sleeping off my pounding headache. I woke up in the middle of the night feeling no better, so I took some pseudoephedrine and Advil and went back to bed. When I got up, my headache was far less noticeable and the heavy fatigue I'd carried most of Wednesday was gone. Still, I knew better than to try a run. I learned something from yesterday.

Headaches of this type are really debilitating and, when they finally leave, the world feels so much better. But even with that improvement, I wasn't out of the woods. I felt well enough to go into the office but some slight dizziness and a mild headache remained. Sudafed saved the day, but it wasn't a complete victory. Another dose this morning brought further improvement.

I'm not sure what's behind these headaches but the only way to get rid of them seems to be a combination of sleep, NSAIDs, and pseudoephedrine. Missing a day's workout, like I did today, would normally bother me because it will make it harder to reach my weekly goal of 20 miles. But an article from Tuesday's WSJ.com sent to me by FS, says that (for older endurance athletes) it's better to keep weekly mileage below that number. Older endurance athletes that run 7:30 paces or faster that is. So I guess I'm good with my 20.

Debating "You'll never regret a run"

Today's run (treadmill): 25 minutes

I often quote the line, "You'll never regret a run" to make the point that the effort to exercise is always worth it despite how you might feel. Just this morning my wife said the same thing to me about her workout. Ironically enough, I may have found the exception to the rule today, having completed a treadmill run and suffering the consequences of that decision.

It's hard to differentiate between feeling tired because you've just woken up and feeling fatigued for other reasons. This morning I went through my routine of preparing for the treadmill (30° outside temps made that an easy decision). Though I felt groggy, I expected that feeling to pass once I got going. That happened, but soon after I'd cooled down I was ready to return to bed for more sleep.

Since my schedule is tight on weekday mornings, I had to ignore the dizziness and feeling of weakness. I left for the train, hoping that I could get a decent seat and take a nap. The LIRR is running less trains due to Sandy-related issues and the cars get very crowded, but I managed to secure a good spot and slept for 20 minutes.

I'd hoped that would solve the problem but my fatigue continues. Despite some strong coffee and analgesics I'm still hurting. I don't know if running on the treadmill was best thing for me this morning. Had I not done that, I could have taken an extra 30 minutes to rest and avoided the physical impact of running. If I skipped my run, I'm wondering whether I'd be feeling any better. Or would I feel worse due to the guilt of missing a workout? I'm taking solace in the thought that while I may regret today's run, I would definitely have regretted skipping it.

Base restoration, Day 1

Today's run (street): 6.4 miles

It's been weeks since I've done a run greater than five miles, so I planned for a longer run today. By the end of April (prior to the half), I was at my training peak, averaging over 22 miles a week. Right now I feel like I'm in a bit of a valley in terms of my training and performance. This is due mostly to running lower mileage weeks over the last month. I recognize that I need to refocus on my base training.

Today's route was a departure from my usual neighborhood course. After a counter-clockwise loop around the northern roads, I headed toward the local business park to run the main loop with its hilly section. On the way out, I turned into neighborhood #3 and ran a loop around those roads, finishing with a mile and a half back in my neighborhood.

I've felt slightly tired and "under the weather" since last weekend. That continued this morning, although it didn't affect my stamina. I ran about 20 seconds per mile slower than I'd planned, but I still covered my distance in a credible time.

I'm planning to rest as much as I can over the weekend in hopes of restoring my energy level. I'd like to cover another six miles tomorrow to get me to 20 miles this week. Either way, I'm happy to have run over six miles today. a good base is hard to build, and easy to lose.

Half listening to my body

Today's run (street): 4.2 miles

So much for focusing on speed, at least for today. Despite getting almost eight hours of sleep last night, I woke up with little energy. I considered listening to my body and skipping my workout, but I thought that was too extreme. As a compromise, I decided to forgo my original plan to do tempo run to start my training for the June 3rd NHP 8K. This run would have to be short and easy. 

Things started out fine and I had no expectations about my performance. I kept my pace moderate and, with the cool temperature and sunny skies, I should have enjoyed the run. I planned to keep it under 45 minutes so, by mile three, I was ready to turn toward home. It was surprisingly hard to cover that final mile. I finished feeling more tired than I should, for a four mile run.

I'm hoping that I recover sufficiently by tomorrow so I can go out for more miles. I don't regret my decision to run, but I'm glad I kept it short.