The gameplan, round 2

Well, the LOST finale has started, but I don't want to watch commercials, so I'm killing time for a few minutes before starting it off the DVR, and so I thought it was probably time to get my training goals for round 2 set down. Lucky you, my special handful of readers :-)

Anyhow, this week was designated as an easy week, and it turned out to be much easier than initially planned. I followed through with running a mile time-trial on Tuesday on the course that has more inclines to it, as I mentioned in a previous post, and came up with a 6:35 that I was very pleased with. My intent was then to run a two-mile trial on Friday night, and then go 4-5 miles today. However, I wound up doing some fasting this weekend, and I figured serious exercise isn't probably the best idea when you're not eating much, so I put those plans on hold.

Anyhow, this coming week will bring the resumption of training. I have previously mentioned the major tweaks to my approach this time out, and there's another one or two I will mention in the details here.

Speed Intervals
Starting objective: 4 intervals, all run in 1:25 or less
Final objective: 7 intervals, all run in 1:25 or less

This is one of my minor tweaks. The training plan itself calls to start at 3 and go to 6 intervals by the end of the schedule. I could do that, with a goal to get much faster this time out. However, I'm already intervaling at or just above the pace I've read I need to look at if I want to get to my long term goal, so it's more important to be able to add intervals rather than speed them up. I don't need more top-end speed, I need more ability to sustain it. I'd like to be able to get to 8 intervals by the end of the 3rd cycle, so I'm planning on going from 4 to 7 with a slight time drop this time, and then just look to go from 5 to 8 with a similar time in the 3rd cycle. You'll note, as opposed to last time, I'm not looking to drop my times over the course of training - I discovered last time that's just not that realistic. I'm adding an interval at least once every two weeks, so that's all I can really ask - trying to go faster at the same time isn't helpful.

Midweek 2/3 mile runs
Starting objective: 2 miles at 8:20/mile pace
Ending objective: 3 miles at 8:10/mile pace

Again, I could do these faster if I wanted, but it would wind up creating problems with my more important workouts, mainly the tempo runs. I proved that point to myself last cycle, when about week 5 I was feeling really good and wound up going 8:05 pace over 3 miles, which was a good 25 seconds better than I was supposed to run - it led to a couple of subpar workouts in a row until I took some extra rest. 8:20 is about what I was able to do very comfortably at the end of the last training cycle, and I'm really not looking to go much faster with these.

Tempo runs
Starting objective: 30 minutes total, 15 minutes fast (7:25/mile pace)
Finishing objective: 40 minutes total, 20 minutes fast (7:15/mile pace)

At first glance, if you saw my first cycle objectives, it looks like I'm taking a step back. I met my goals and was tempoing at/under 7:10/mile by the end of the first cycle. However, there are a couple mitigating factors here - mainly the change of venue. I'm moving from my half-mile loop, which is pretty flat and may be a bit short, to my mile loop, which has more hills to it, and is definitely at least the length I'm counting it as. Also, I think I was previously tempoing too fast. Given my mile time of 6:35 on the same course, 7:25 is an appropriate tempo pace. We'll see how it goes. Regardless, the change of terrain should make these runs much more indicative of what I would be able to do comfortably on a moderate 5k course.

Long runs
Starting objective: 5 miles, 8:45/mile pace
Finishing objective: 7 miles, 8:30/mile pace

Nothing too fancy here - my last long run of cycle 1 was 7 miles at an 8:37 pace. If I can take these runs a bit faster comfortably, I will, but I'm not looking for crazy improvement here, because pushing these runs will, again, negatively impact my speed/stamina workouts.

So, there's the plan. There is a minor catch this time around. My training plan runs 8 weeks, including the taper week before the race, but the next race I'm officially training for is 12 weeks ago. My plan will be to taper mid-plan for the race in Shippensburg on 6/26, give myself another relatively easy week the week after, and then resume by repeating the last week I had done on the schedule. That will eat up 3 of my 4 extra weeks, so I'll still have a week to play with, and how that gets used will depend on how the rest of the cycle goes.

A better way (I think)

So, as you might know, this Sunday is the finale of ABC's LOST, one of the more anticipated events in recent TV history. The show has been quite popular and has kept it's fans guessing for the better part of the last 6 years, and they will all be watching as the answers (well, at least most of them, I'm sure there will be some mystery left) are revealed. And I will join them, though my journey has been a bit different.

You see, prior to the first of this year, I had never seen a single episode of LOST. I really am not one to be drawn to new TV shows by the previews, so I rarely catch a new show from the very beginning, and by the time I'd heard enough good things about LOST to be intrigued by it, it was several episodes in, and I knew it was the kind of show that I'd want to see from the beginning. Catching up on a show was not as easy back in 2004 as it is today, with the prevalence of things like iTunes, video on-demand service, networks posting back episodes on their website, etc, so I figured some day, at least after the first season DVDs came out, I'd give the show a try and catch up if I liked it. Some day turned out to be earlier this year, and it wasn't by some serious compulsion - I got a Blu-ray player for Christmas, had my Netflix account ready to go, and was looking for some adds to the queue. LOST was one of the more intriguing options to come to mind, so I added the first season and was ready to see if I liked it. After the first disc or so in the first season, I was into the show and decided that I would continue.

This immediately presented me with a bit of a deadline. I knew the season that was upcoming was to be the last for the show. As popular and talked about as LOST was, I also knew that, were I not caught up and able to watch the finale when it aired, there was no way I was going to be go any length of time without hearing some major spoilers - so I had to caught up by the finale. I added seasons 2-5 to my queue and got to work. When the beginning of February rolled around, I set my DVR to record all of this season's episodes so they would be ready for me when I needed them. I initially wound up going almost too fast, and in March and April had to "ration" my watching, because I decided I couldn't go from being able to watch a new episode pretty much on demand to getting caught early in the final season and having to wait week to week. It worked out pretty well, and tonight I just watched last week's episode and last night's episode, so I'm all caught up and ready for the finale.

Inadvertantly, I may have stumbled onto a vastly superior way to watch TV - or at least serial dramas. I see a number of very positive aspects of going this way:

1. No fear of "failure" - Like I said, I don't often get in on the ground floor of shows very often, so this isn't something I've run into too often, but very often serial dramas don't grab enough of an audience and get dumped before they can wrap up their storylines - which really sucks for the loyal fans the show did have. My most recent similar experience to this has been with Friday Night Lights, which started out on NBC, was very nearly axed after its first season, and then was moved so that its first run epsiodes would air exclusively on DirecTV, before re-runing on NBC. It's made it through 4 seasons now (the last two have been shortened), but the 4th season was the first one that ended with any certainty about whether the show was coming back (the last renewal was for seasons 4 + 5, with 5 widely expected to be the last), and yet season finales constantly left plenty of unresolved questions. Heroes also just got axed after 4 seasons having left a lot open in its season (now series) finale, but that show has been consistently going in the tank for the last couple seasons and I wasn't likely to come back anyhow. Regardless, going the "wait and catch-up" route eliminates this concern - you can start watching knowing the plots will be brought to conclusion, or you can at least make an educated decision to watch a show that got the early axe, knowing what you'll be getting into.

2. No waiting - Watching a show as it unfolds always necessitates waiting at least a week between episodes, and in the case of serial dramas, you're usually signing up for months between seasons with some sort of cliffhanger to be resolved. The shorter seasons LOST has run from 4-6 have resulted in almost 9 months between season finale and season premiere, and for shows that run through a full traditional season, these days you're almost invariably looking at some form of hiatus at multiple times to keep the episodes lined up with sweeps and the like. The longest I went between LOST episodes was a week (driven by blizzard related mail delays and a disc that was broken on delivery), and it just so happened that occurred between the 2nd season finale and 3rd season premiere, so I was still months ahead of everyone else on that wait. This also feeds into...

3. No commercials - There are no commercials on Blu-rays, and I can skip them on the DVR'd episodes. Nothing more needs to be said.

4. Ease of recall - Most shows aren't as involved as LOST, but in general, serial dramas are building on something, which makes it helpful if you remember what happened in previous episodes and seasons. I could be wrong, but I'm assuming it's much easier to remember what happened in Season 1 if you watched it a few months ago as opposed to several years ago.

5. Muting of a potential final letdown - Let's face it, a number of these kind of shows have had finales that were quite disappointing. I feel like such a letdown would be much less brutal if you've only been watching for a few months before getting to them as opposed to 5+ years.

Now, there are also some potential pitfalls with this method, the primary one being the obvious issue of spoilers. By catching up before the finale, I've eliminated the possibility the "big" spoiler, but as popular as LOST is, it was inevitable that I was going to pick up somethings, some of which I had picked up before I even started watching. It got particularly difficult once season 6 started up, but overall, I didn't have anything major spoiled. And of course, there's the fact that if everyone tried to employ this method, there would never be a serial drama made again, because they wouldn't get ratings. This is also an easier method for me, because I don't watch a ton of non-sports TV to begin with, so I have time to devote to such an effort, in short bursts.

Regardless of all of that, I've really enjoyed watching LOST in this manner, and will likely try do something similar in the future. I'm probably not patient enough to take this approach with every show that piques my curiosity :-)

Some course corrections

So, if you read the comments in my race report, you might have noticed that my initial disappointment in my performance in my first ever 5k had begun to fade as the day continued on, and that trend continued. Not to say that I'm totally pleased today, but I'm content with it for a number of reasons.

1. Prior to Saturday, I had never competed in an actual race of over 1/4 mile (I think), so just finishing was an accomplishment I became more pleased with as I reflected.
2. A significant part of my struggles were caused by poor initial pacing. Proper pacing is probably one of the hardest things to do in a 5k, and so it was probably somewhat unrealistic for me to expect to get it right in my first race.
3. My goal time of 22:30 was based on my perception of what my optimum performance should be over 5k, and upon further reflection, there was no reason I should have expected optimum performance given the course, which had 2 short but quite steep inclines, and featured full a mile of running directly into a stiff headwind. (Yes, said wind was at my back for most of the last mile, but trust me, it doesn't even out...) The winning time in last year's race was 17:51, and although they haven't posted the official results for this year's race yet, I was told by my cheering section that the first runner came across the line in well over 18 this year. These are not blazing fast 5k times, and for a race of this size (I would say approximately 300 people) to be won by them would definitely indicate that this is not a particularly fast course. In retrospect, a time of 2300-23:30 was probably what I would have been looking at with proper pacing.

So, overall, I'm in much better place with my feelings about the run. Further, I was quite encouraged by my fitness level today when I did a mile time trial in what I am going to call my personal best, of 6:35. I say I'm going to call it my best, because technically I ran a faster mile shortly before I started officially training for Saturday's rest, in 6:25. However, I ran that mile as 2 circuits of my half-mile loop, which I am now convinced is slightly shorter than a half mile. I ran today's mile on my mile loop, which is definitely a mile and if anything is slightly longer. The mile loop is also rather undulating with a couple of steady climbs, while the half mile loop is pretty flat, so even if they are the same length, I'm convinced my 6:35 time on the mile loop is a much better running performance. I'll have to get to a track at some point, because I'm convinced I could probably start to attack the 6 minute mile barrier on a flat run.

So, all of that said, upon reflection, I'm looking at the following changes to my training and race plans. Originally, I only intended to do 3 races this year, to allow time for a full training cycle in between each one. I'm now convinced I need to run a few more races to get experience, even if I'm not "fully" trained for the extra ones. So, my current plan is to next run the Travis Henry Memorial 5k in my hometown of Shippensburg on 6/26 as an "experience" race, and then the Run for Reading 5k in Mechanicsburg on 8/14 as my next race I'm formally training for. After that, I will be looking for a 5k in the mid-September time frame, while training for the Falcon Fun Run at Messiah's Homecoming on 10/16. I've also decided I'll want to stay in training through to December before taking the coldest part of the winter a bit easier, so I'll probably be looking for a race or two in the November/December time frame.

Because the 8/14 date for the Run for Reading is out a couple weeks beyond my 8 week training schedule, I may actually take the week before the 6/26 run and taper for it, but we'll see how things go. I, of course, reserve the right to change my schedule due to injury, other setback, or my whim:)

I'll be setting some training goals later this week, but I have decided to make two key changes to my training approach this time around. First of all, to help myself with being able to feel proper pace, I'm going to work to discipline myself not to check my watch at intervals smaller than half a mile on my tempo and long runs. Secondly, I am going to move my tempo runs (my longest speed workouts) from the half-mile loop to the mile loop. There are two reasons for this - the first being the distance issue I mentioned earlier - I think running the half-mile loop this time around gave me a slightly unrealistic picture of my pace, by moving to the mile loop, if anything, I'll think I'm going a bit slower than I really am, and I prefer that going into a race. Secondly, the mile loop, while not containing any severe hills, comes much closer to replicating what I could expect on a typical 5k course in terms of inclines than the flater half-mile loop.

So, at this point, I'm really feeling re-energized and ready to start prepping for the next race. Of course, that's not to say I'm not enjoying having a more relaxed schedule this week :-)

Armed Forces Day 5k - Race Report

Well, after some spotty weather all week, we were blessed with a beautiful day for the race. It was about 60 degrees and sunny, with a nice breeze moving at race time (8 am).

That, unfortunately, was the main highlight of the day, as I made the mistake I absolutely swore I couldn't make and went out too fast. My plan of attack was to be even mile splits, or even negative splits (getting fast over the course of the race), but assuming the rough mile markers I got from the online course maps (there was nothing official out on the course), I blew that possibility out of the water by running the first mile in about 6:50-6:55, which is a good 20 seconds below the 7:10-7:15 pace I was looking to have over the course of the race, and it absolutely cost me in the last half of the race.

Adding to the difficulties was that I had not totally had a good understanding of the course. We started on City Island and did almost a full lap of the island before heading across the Walnut Street walking bridge. At this point, we did a little turn and headed along the river. Looking at the map, I was thinking we were just staying up at the level of the bridge, but we actually dropped down to the lower level via a fairly steep hill. Not a big problem at that point, but it meant that we were going to have to go back up that hill right before the finish, and it also meant there was a similar hill to navigate at the turnaround point about 2 miles into the race. It also put us right down next to the river, into quite a wind tunnel that was blowing into our faces on the way out.

Between the wind in the face and having gone out too fast, my planning of having something in reserve for the last mile just didn't come together, and I was really just trying to hang on. The hill back up onto the bridge pretty much did me in, and the final run back across the bridge was far from triumphant. I did manage a final push to the finish to get in around 24:30, which was a solid 2 minutes below my goal, and I'm pretty that way too fast first mile cost me pretty much all of that time. Granted, 24:30 for a 5k is nothing to be ashamed of in the grand scheme of things, it's still under an 8 minute mile pace, and while the official results are yet to come, I know I finished ahead of significantly more people than I finished behind. That being said, I know I could have done a lot better - by the end of my training cycle I was able to run 3 miles at an 8:10-8:15/mile pace and feel very comfortable throughout, so going well under an 8 minute pace in 5k race shouldn't have been much of a problem - had I done a better job of pacing myself early in the race.

So, that will be a point of emphasis for my next round of training - being able to have a better feel for my pace. The difference between training and a race is that I know my training courses, I have checkpoints all along the way, so if I'm off pace, I know about it within a quarter mile and can make the adjustment. Today, all I had was a rough idea of where each mile was, and so until I got my first reliable time check, I was already in trouble. So, I will probably try to find some less familiar paths to run this time around, and also discipline myself to not look at my watch as much while I'm on my regular paths. I do not think my 22:30 goal was unrealistic for my level of conditioning, despite the fact that I fell 2 minutes short of it - I think the time was more reflective of my lack of experience than anything else.

So, what's up next? I plan to have a slightly easier week this week, perhaps just a couple days where I do some time-trailing at some shorter distances (1 and 2 miles) and then a 4-5 mile run over the weekend, and then I'll reset my training plan with new goals for this time around. At this point, I'm eyeing a couple options for races in late July/early August to be the next one that I'm "officially" training for. There's also a 5k in my hometown on 6/26 that I'm eyeing more seriously after today. It will be squarely in the middle of my training cycle, so I would be looking at it more for getting some more experience at running the distance than for a real barometer of progress - though I would probably be hoping for at least some sort of a PR given my time today.

So, all in all, I was disappointed today, but not disheartened, and very motivated to continue training and learning so that I can improve. I finished, and for the first one, I guess that has to be the primary goal :)

Well, it's official

Today, I officially registered for the Armed Forces Day 5k in Harrisburg on Saturday, May 15th, so I suppose it is on...

Training has gone very well to date, although I am skipping my long run this weekend because I've listened to my body. I did my longest tempo run ever on Friday evening around sundown, had a long day yesterday, and just was not feeling totally right when I got up this morning. I might have taken a go at it, except for the unseasonable warmth and accompanying humidity. The bottom line is that my endurance is well built up at this point, this is the only run I've missed in the first 6 weeks so it doesn't seem likely to really mess me up, and overtraining could lead to a major setback.

Anyhow, with 2 weeks to go, and only one week of full training (the last week is an easy week to taper down and be properly rested for the race), it's time to really start thinking about goals.

Assuming the courses I train on are pretty close to the lengths I believe they are, I've been tempo running at about a 7:15-7:20 minute/mile pace, with my longest period at tempo pace being 20 minutes (I covered about 2.75 miles in that stretch). Maintaining that pace for a 5k would lead to something in the vicinity of a 22:30 for. Now, the idea of tempo running is that it's supposed to be below race pace, so in theory I should expect to run faster than that pace in the race. However, I'm going to temper my expectations for a few reasons.
#1 - I think, since I don't have a race history to know my race pace that I'm probably tempo running closer to my limit than I should be.
#2 - I'm not yet fast enough to cover 5k during my tempo runs, so I'll have some extra distance to cover once I get best the longest I've run at such a pace before.
#3 - If anything, I think the course I use for my tempo runs is a bit shorter than I count it as.
#4 - This is my first race - I'm a bit concerned the adrenaline might mess with my pacing discipline.

Of course, there are a couple things that work in my favor:
#1 - My tempo runs are often the 3rd of 3 straight daily runs, and almost always at least the 2nd of two in a row, and they always occur towards the end of the day, so I'm not necessarily on the freshest of legs. On raceday, I'll be running first thing in the morning with a couple days of rest behind me.
#2 - When I tempo run, I start out with 8 to 10 minutes of running at a long run pace, so I'm actually 28-30 minutes into a run when I finish the faster portion. In the race, I'll be starting with completely fresh legs.

All of that put together, with this being my first race, I'm taking a pretty conservative approach and looking for a time around 22:30, though I think I might be capable of better. My plan, for the time being, is to be relatively conservative over the first two miles or so, with the hope of having plenty in the tank for a very good final mile. If I make a mistake with pacing in this race, I want to do so in favor of having something left at the end, as opposed to bonking and having to struggle to the finish. One very nice aspect of the course for the race for a novice like myself is that it is very flat overall.

Another positive development regarding the race occurred today, as some friends, who were just coming off of a half-marathon yesterday, got the bug and decided to run the race with me. I think it'll make for much more fun day having a group for support at the starting line and to celebrate with afterwards, and potentially some company on the run itself depending on how they pace.