I’ve been quiet on the running blog because I’ve been pretty quiet on the running in life. After the three weeks' rest post-VCM, I was getting in 5-6 miles a few times a week, but not being as rigorous or religious about it as I am during training. I continued to suffer the muscle soreness in my lower abdomen/groin, so it was probably just as well that I wasn’t trying to run hard, or run a lot. But I still ran, as it wasn't so bad as to prevent it. Just always there in the background.
Then, Sunday, July 10. Around 4 a.m., I woke up and turned onto my side, nothing unusual, but it felt like I kept going once turned; falling, around and around, the room tilting and spinning wildly out of control. This severe vertigo hung around all day, so that I couldn’t walk without help, and every motion of my head caused the room to tilt and slant and I’d find myself listing or flat on the couch or bed again. Even simply lying with my eyes closed; I could still feel myself whirling -- it was better to keep my eyes open. It was awful; coupled with nausea from the dizziness, it was a pretty bad day. (And very disappointing, as well; it was a nice day out – not TOO hot, not TOO humid, and we had planned a 50-mile bike ride south of the canal, where it's flatter.) Monday was marginally better; I could creep around the house if I had a wall to lean on, or something to grab as I went by, but there was no way I was going to be able to go to work if I couldn’t walk without support. I spent another not TOO hot, not TOO humid day not getting to run in the morning, and instead laying and sitting around the house, reading (I enjoyed that, at least) and being bummed when B got home and went out for an after-work mountain bike ride without me.
Fortunately, I already had a doctor’s appointment scheduled for that week (to talk about the muscular pain) so I brought up this sudden-onset dizziness while I was there. The doctor diagnosed Benign Paroxysmal Positional Vertigo (BPPV) and gave me a list of movements to do with my head (Epley maneuvers) to try to help correct it. Though not disappearing, the vertigo diminished enough over the week so that by Friday I could drive myself again and didn’t need to hold onto or be next to a wall while walking just in case. While it has improved slightly day to day, I still cannot move my head too quickly, or right myself too quickly if I have bent over to pick something up, etc. Any quick, turning/sweeping motion with my head elicits a brief (fortunately not debilitating) spell, just a quick second or three of disorientation, a weird feeling (mostly in my eyes) that things are not steady. I have been doing the maneuvers (and feeling pretty icky during them, as they spur a flash of more intense vertigo), but it isn’t improving as quickly as I’d like. It will “get better with time”, the doctor said; well, my idea of “time” has consistently proved to be much shorter than a physician’s, so I get impatient quickly. BPPV is uncomfortable, even when it is not intense anymore, so I wish it would just stop.
A week after the vertigo started, when I felt I could walk reliably without an attack of disorientation, I thought I would try to run again. Whenever a week goes by and I can't run for whatever reason, I start to get antsy, though this time, a forced week off could've been good for the muscle soreness situation, right? (More about that in a moment.) Early last Saturday, it was already quite warm, but better to get it done early than suffer heat indices near 100 later. I got all ready, really looking forward to a few miles after having been stuck inside sitting around for a week, and walked to the end of the driveway to the sidewalk. I turned to run up the street.
I didn’t even get past my yard. Immediately, with those first three or four steps, the world felt too loose1 – bouncing too much, scenery going by too crazily. I didn’t feel like I was going to fall over, but it sure seemed like everything was sliding around too much, my head just not right. I stopped after a few strides, hesitantly, then tried again a few strides.
Nope.
Later, I wondered if I ran on the treadmill, would it feel better? There would still be the up-and-down bouncing, but no scenery passing my peripheral vision; it might not be so disorienting. So, Sunday afternoon (while B went out on that long bike ride south of the canal -- I did not yet trust my head enough to ride a bike) I gave it a shot. It was also quite hot out on Sunday, so from that perspective, it wasn’t too bad to have to run on the treadmill. (I haven’t been my treadmill for many weeks, so that felt a little weird itself.) Well, it didn’t feel normal by any stretch, but if I kept my gaze focused at a fixed point on the wall in front of the treadmill, and occasionally touched the crossbar with my fingers to keep myself oriented, it wasn’t too bad. It didn’t feel like the world was as loose around me, it didn’t feel like things were skewing as much. I started out very slow and worked my way up to 8:45 pace, covering five miles.
When I got done, I felt uneasily iffy. Not dizzy, not like I was going to fall over, but my eyes didn’t feel like they had a good, firm grasp on what I was looking around at. My head didn't feel quite right -- a faint disorientation, walking to the kitchen and up the stairs to shower. It didn’t last, but it was uncomfortable. It put me off trying again on Monday. And now it is Wednesday and I still haven’t tried again. I keep hoping that after doing the maneuvers at night, and another day going by, I’ll wake up and feel better, and I mean noticeably better, not this very tiny incrementally better that’s been going on for the last week. So far, I haven’t had that breakthrough.
---
While at the doctor last week, after talking about the vertigo which was more pressing at the moment, I explained the muscle soreness, how long I’ve been having it, how it has changed and concentrated itself, and when and where it bothers me. After having me push my legs against her resistance a few ways, she concluded it is likely an issue with the psoas muscles (both sides) and prescribed physical therapy. I was relieved she didn’t mention the words "tear" or "torn" or "surgery". She mentioned there was an outside chance it could be some kind of arthritis or fracture, and to rule that out, she ordered an x-ray of my hips. I had that taken last Friday, haven’t seen the results of it.
This morning, I went to my first session of PT. It is not my first time having physical therapy; in 2008, I saw a PT for a foot injury, and then again in 2009/2010, for a sprained PCL and patellar tendon pain after the mountain bike crash in Moab. I am going to the same clinic as I did in those instances, but the therapist I worked with those times is no longer there, so I am working with someone else – he’s not officially “new” to me though. We did meet, back in 2008, and once or twice he worked with me in 2009/2010 when my regular PT was out -- but it’s been a lot of years and a lot of patients for him in between, so I didn’t expect he would remember me (he did not seem to), though I remembered him. I described the issues – where/when/what, etc. and he came to the same conclusion as my GP did: the iliopsoas is all fired up.
We went through a list of specific stretches to improve hip flexor flexibility and then a list of strengthening exercises as well, to go through on my own twice a day. He said I can continue to run, just to avoid hilly routes and to be easy on the pace.
Done and done. I like trail running, but it won't disappoint me too much to stay away from the park for a while to avoid how hilly it is there. I’d like to race this fall, but it’s not necessary, so if it takes several months of easy running and stretching/strengthening to cool down this issue, I’ll do it with no regrets of missing this half marathon or that ten-miler. I was so glad he didn't tell me to be a couch potato (or, actually, a standing potato, as lengthy periods of sitting doesn't help this issue) for a couple months. Now, if this vertigo will just give up its hold on my head, I can go back to running those nice easy flat miles – preferably outside and not on the treadmill. Weather and circumstances permitting, I’ll give it another shot tomorrow morning. I miss seeing the sun rise over the neighborhood trees while I'm looping around the reservoir.
-----------------------------------------------------------
1The best way I can describe what this was like is this (I realize that most of you may not be able to relate, but): the scanning electron microscope I use at work, an old Hitachi S4000, needs to have apertures aligned properly to give the best images. While aligning them, if the aperture is out of whack, the image on the screen bounces from side to side, and sometimes in a slightly circular way as well, the focus going in and out; the worse the alignment, the wilder and stronger this motion is. I imagine a bobblehead’s vision to be similar. That’s kind of what the world around me seemed to do when I tried to run outside; bounce and slide and turn, bobblehead-like.
Wednesday, July 20, 2016
Thursday, June 30, 2016
Ten observations: running at dawn in late June
1) A startled cardinal alighting indignantly the street, flicking his tail in reproach as I walk down the driveway to start
2) A leopard slug creeping inevitably across the sidewalk, plenty large enough to be spotted and dodged, leaving a trail that will shine later in the sun
3) The red foxy-fox rustled out of the marsh, the tip of its luxurious tail a white spark as it hurries away, wary of my approach; it pauses to look back at me before disappearing in a heartbeat
4) A band of pink circling just above the horizon line, separating two shades of blue sky on these clear, cool-ish, and dry mornings
5) Distraught mallards frantically flapping into the water, every time I loop past them; their harried quacking and honking follows my back
6) This spring's goslings are now indistinguishable from the rest of the gaggle making a mess of the path, faithfully ignoring me unlike the volatile crew which colonized Paper Mill Park
7) Deer picking daintily in the grassy spaces below the rim of the lake, unaware (uncaring?) that they are actually in the middle of a residential plain
8) A woman doing intervals, igniting a competitive flare and necessitating a reminder to my legs that they are not out there to run fast today
9) Darkness under the trees on the connector trail, requiring a delicate touch so as not to wind up meeting the roots with my face, which I wipe repeatedly as I pass through web after invisible web
10) A rumble, then a roar, as the early freight train trundles through the heart of Newark below, its blaring siren an alarm clock for anyone living along its route
2) A leopard slug creeping inevitably across the sidewalk, plenty large enough to be spotted and dodged, leaving a trail that will shine later in the sun
3) The red foxy-fox rustled out of the marsh, the tip of its luxurious tail a white spark as it hurries away, wary of my approach; it pauses to look back at me before disappearing in a heartbeat
4) A band of pink circling just above the horizon line, separating two shades of blue sky on these clear, cool-ish, and dry mornings
5) Distraught mallards frantically flapping into the water, every time I loop past them; their harried quacking and honking follows my back
6) This spring's goslings are now indistinguishable from the rest of the gaggle making a mess of the path, faithfully ignoring me unlike the volatile crew which colonized Paper Mill Park
7) Deer picking daintily in the grassy spaces below the rim of the lake, unaware (uncaring?) that they are actually in the middle of a residential plain
8) A woman doing intervals, igniting a competitive flare and necessitating a reminder to my legs that they are not out there to run fast today
9) Darkness under the trees on the connector trail, requiring a delicate touch so as not to wind up meeting the roots with my face, which I wipe repeatedly as I pass through web after invisible web
10) A rumble, then a roar, as the early freight train trundles through the heart of Newark below, its blaring siren an alarm clock for anyone living along its route
Wednesday, June 22, 2016
Planning ahead for 2016
Because I'm playing optimistic about my recovery and what running I'm going to get to do this year, I've been looking at races to put on the calendar for the fall. I'm not going to do a full marathon (I am holding firm on that decision), but I see no reason not to run a half or two, or a ten-miler or two, or a 15K, or a 10K, or some 5Ks thrown in there too.
5Ks are a dime a dozen around here so I don't think I will plan this far in advance for any particular one, and see about adding those on the fly during the rest of the year.
10Ks are hard to come by on the local race calendar. I spotted one, in Wilmington on October 15 (Run for the Buds). There is one in Iowa City on October 16 (Run for the Schools). I have no idea what my vacation/travels to Iowa will be like later this year, but either way, it looks like I could plan on a 10K that weekend, whether in Delaware or in Iowa. If it works out and I am in Iowa City that weekend, I'd have to decide whether I want to do the 10K or the half. I might lean toward the 10K to see if I run a PR on the course where I set my PR in 2004; but I might like to improve on my Run for the Schools half-marathon time, too (1:40 on a very, very hot day in October 2007). It's much more likely I will not be in Iowa that weekend, though, so the Run for the Buds looks promising for a fall 10K.
10-milers abound this fall around here. The Bottle and Cork 10-miler in Dewey Beach, DE on September 10 could start off my fall distance racing season. The Cow Run in Salem, NJ is run through the rural NJ countryside on October 2; also on that date, there is the Caffe Gelato 10-miler in Newark, DE. The latter is not fully a road race, but rather tracks through part of White Clay Creek State Park (so, trail-ish). That's only a few miles down the way for me, but maybe I won't feel like running a race that might be necessarily a little slower than it could be due to the race surface. But maybe I won't feel like driving to rural NJ instead. Either way, there is a 10-miler to be run that weekend, if I want to fit one in a week ahead of another race I've got in my sights, a 15K in Delaware.
In 2012 I ran the Delaware Distance Classic 15K (when it was still in Wilmington) and I liked it, but ever since, it has fallen on a weekend not convenient to my fall marathons so I have not run the last three iterations. It has moved to Delaware City, but that's not very far away at all and while I have question marks next to all the "maybes" above, this one on October 9 is one I'm going to plan on running for sure.
There are a number of half-marathons in the vicinity this fall, including the Rock n Roll in Philly in September and the half associated with the Philadelphia Marathon in November, but I don't think I want to submit to 1) the largeness of the fields, particularly with the RnR race -- it's just too stupidly big at this point, and 2) having to decide pretty much now for sure that I'm going to register for them in order to not get shut out. Given my uncertainty about what is looking like an injury, I'm in no position to say that I am going to be FOR SURE running these half-marathons so I'm not going to pony up the $100 or whatever it will cost (ok, I just looked, the Philly half in November is $120, and "prices after June 30 are subject to increase." Cripes. That makes the RnR race sound cheap at $99 (right now).) Delaware has a handful on tap starting in October: a half associated with the Monster Mash marathon in Dover on 10/22, one along the C&D Canal near Delaware City on November 5th, and a half associated with the Rehoboth Beach Seashore marathon on December 3rd. I have put all three of these on my race card, the first and third with question marks; I don't know if I want to go all the way to Dover ("all the way", haha!) to run a half-marathon a week after I plan to have raced a 15K, and I don't know how I will feel about racing in potentially icky December weather in a seaside town. I have decided on planning to aim for the C&D Canal race. It's as flat as a course can get, and judging by last year's results, if I have even just a decent day, I should do some placing (last year's first woman ran 1:31, but second place was 1:42). Of course, speedier ladies could discover it this year, too, and make it more competitive, which would be a positive. November 5th is plenty long enough after the 15K and it can serve as my last race before turning 40.
My location is convenient not just to southeastern Pennsylvania and all of Delaware, but northeastern Maryland as well, so I will look at race calendars for MD and give anything promising a think, too. I like to travel to new places to race, but I think I might stick around a bit closer to home this fall and save my pennies for Boston weekend in 2017.
This all assumes I will recover in reasonable time from these lingering issues and can get back up to decent mileage and efforts, of course. But, as I said, I'm playing optimistic right now, if not so optimistic as to get out the credit card and put some of these decisions in stone!
5Ks are a dime a dozen around here so I don't think I will plan this far in advance for any particular one, and see about adding those on the fly during the rest of the year.
10Ks are hard to come by on the local race calendar. I spotted one, in Wilmington on October 15 (Run for the Buds). There is one in Iowa City on October 16 (Run for the Schools). I have no idea what my vacation/travels to Iowa will be like later this year, but either way, it looks like I could plan on a 10K that weekend, whether in Delaware or in Iowa. If it works out and I am in Iowa City that weekend, I'd have to decide whether I want to do the 10K or the half. I might lean toward the 10K to see if I run a PR on the course where I set my PR in 2004; but I might like to improve on my Run for the Schools half-marathon time, too (1:40 on a very, very hot day in October 2007). It's much more likely I will not be in Iowa that weekend, though, so the Run for the Buds looks promising for a fall 10K.
10-milers abound this fall around here. The Bottle and Cork 10-miler in Dewey Beach, DE on September 10 could start off my fall distance racing season. The Cow Run in Salem, NJ is run through the rural NJ countryside on October 2; also on that date, there is the Caffe Gelato 10-miler in Newark, DE. The latter is not fully a road race, but rather tracks through part of White Clay Creek State Park (so, trail-ish). That's only a few miles down the way for me, but maybe I won't feel like running a race that might be necessarily a little slower than it could be due to the race surface. But maybe I won't feel like driving to rural NJ instead. Either way, there is a 10-miler to be run that weekend, if I want to fit one in a week ahead of another race I've got in my sights, a 15K in Delaware.
In 2012 I ran the Delaware Distance Classic 15K (when it was still in Wilmington) and I liked it, but ever since, it has fallen on a weekend not convenient to my fall marathons so I have not run the last three iterations. It has moved to Delaware City, but that's not very far away at all and while I have question marks next to all the "maybes" above, this one on October 9 is one I'm going to plan on running for sure.
There are a number of half-marathons in the vicinity this fall, including the Rock n Roll in Philly in September and the half associated with the Philadelphia Marathon in November, but I don't think I want to submit to 1) the largeness of the fields, particularly with the RnR race -- it's just too stupidly big at this point, and 2) having to decide pretty much now for sure that I'm going to register for them in order to not get shut out. Given my uncertainty about what is looking like an injury, I'm in no position to say that I am going to be FOR SURE running these half-marathons so I'm not going to pony up the $100 or whatever it will cost (ok, I just looked, the Philly half in November is $120, and "prices after June 30 are subject to increase." Cripes. That makes the RnR race sound cheap at $99 (right now).) Delaware has a handful on tap starting in October: a half associated with the Monster Mash marathon in Dover on 10/22, one along the C&D Canal near Delaware City on November 5th, and a half associated with the Rehoboth Beach Seashore marathon on December 3rd. I have put all three of these on my race card, the first and third with question marks; I don't know if I want to go all the way to Dover ("all the way", haha!) to run a half-marathon a week after I plan to have raced a 15K, and I don't know how I will feel about racing in potentially icky December weather in a seaside town. I have decided on planning to aim for the C&D Canal race. It's as flat as a course can get, and judging by last year's results, if I have even just a decent day, I should do some placing (last year's first woman ran 1:31, but second place was 1:42). Of course, speedier ladies could discover it this year, too, and make it more competitive, which would be a positive. November 5th is plenty long enough after the 15K and it can serve as my last race before turning 40.
My location is convenient not just to southeastern Pennsylvania and all of Delaware, but northeastern Maryland as well, so I will look at race calendars for MD and give anything promising a think, too. I like to travel to new places to race, but I think I might stick around a bit closer to home this fall and save my pennies for Boston weekend in 2017.
This all assumes I will recover in reasonable time from these lingering issues and can get back up to decent mileage and efforts, of course. But, as I said, I'm playing optimistic right now, if not so optimistic as to get out the credit card and put some of these decisions in stone!
Back at it
I spent three weeks not running after being broiled in Vermont. I usually take at least a week, usually two, but I had some nagging aches and sorenesses that I thought I'd give an extra week to recover -- most concerning was the lower abdomen muscle situation that never really kept me from doing what I had to do (except once), but also that hamstring/leg cramp that happened during the race on top of the usual marathon-induced aches and weakness. I'm usually chomping at the bit to get back on the road after the first week, but this time, I rather relished the first two of the rest weeks, sleeping in to 6 a.m. and changing right into comfy clothes upon arriving home after work, taking time to enjoy my other hobbies. I had to be more disciplined during the third week, telling myself it was better to give it all just one more week at least. I traveled to Iowa during the third week and it felt peculiar not to fill up half the suitcase with running clothes, and to not spend an hour each day traversing the east side, but I obeyed my rest plan.
I did go biking three times during those three weeks -- twice road biking (~20 miles each time) and once mountain biking, which was a lot of fun as I had not been on my Rumor since early last fall. (I hadn't been road biking since early last fall, either, but while I enjoy that pursuit, it's not "fun" in the way mountain biking is.) The first road bike outing was a week after VCM, and at the end, my legs felt very like noodles. I had thought I might like to mountain bike the next day, but my legs were not having it. The next weekend, I hit the trails on the 29er and my legs were less noodly, which was encouraging. Road biking the next day, my legs were more or less fine. I didn't feel any of the aches and soreness that I'd ended the spring's running with.
I thought about taking one more week off running, but from an emotional standpoint, I was ready to run again, and my aches and soreness hadn't bugged me while living my life, so I was willing to test that out too. I set my alarm for 5 a.m. Monday, but my internal clock was on Central Daylight Time, so when 5 a.m. came, it felt way too much like 4 a.m., and I bailed. Instead, I ran after work, which wasn't optimal because it was in the upper 80s, but I wasn't going to be running hard and I thought I'd enjoy a trail run for the first time in a month so I'd be out of the sun. I got home, laced up my Peregrine 5, and headed out.
Almost immediately, the lower abdomen/groin discomfort flared up. Not so as I couldn't run through it, but it was discouraging. Three weeks of rest did nothing to calm that down, it would seem. I ran about an hour, feeling it in the background the whole way. I thought that because I'd run with it for quite some time at the end of the training schedule this spring, how much more could it hurt it to run tonight? My right leg was OK, but not great or normal; I could feel that hamstring still.
I didn't run on Tuesday, because my legs were sore -- quads in particular, calves a little tired-feeling. I guess three weeks is plenty of time for your muscles to forget everything they'd only recently gone through. And not just muscles; I ran quite slow on the trails, but my heart rate was higher for the same pace than it ever was this spring. I thought I might be able to attribute it to the heat, but I ran this morning (70F and humid, not too bad, and so lovely around the reservoir) at a pace that would certainly be considered "easy" but 40-60 seconds slower than the corresponding heart rate would have allowed me to run only a month ago.
The lower abdomen/groin thing felt about the same as my quads did, which is to say not too bad, better than on Monday. The hamstring was OK this morning too, less noticeable. I will run again tomorrow and see how it goes. I feel I am trying to be overly optimistic about the lower abdomen, but that's only because I don't want to sink immediately to doom and gloom conclusions (though that is what I really fear, deep down). I have an appointment with a doctor on July 13 to discuss this discomfort. I made this appointment a couple weeks go. It was the soonest I could get in. Ridiculous.
I did go biking three times during those three weeks -- twice road biking (~20 miles each time) and once mountain biking, which was a lot of fun as I had not been on my Rumor since early last fall. (I hadn't been road biking since early last fall, either, but while I enjoy that pursuit, it's not "fun" in the way mountain biking is.) The first road bike outing was a week after VCM, and at the end, my legs felt very like noodles. I had thought I might like to mountain bike the next day, but my legs were not having it. The next weekend, I hit the trails on the 29er and my legs were less noodly, which was encouraging. Road biking the next day, my legs were more or less fine. I didn't feel any of the aches and soreness that I'd ended the spring's running with.
I thought about taking one more week off running, but from an emotional standpoint, I was ready to run again, and my aches and soreness hadn't bugged me while living my life, so I was willing to test that out too. I set my alarm for 5 a.m. Monday, but my internal clock was on Central Daylight Time, so when 5 a.m. came, it felt way too much like 4 a.m., and I bailed. Instead, I ran after work, which wasn't optimal because it was in the upper 80s, but I wasn't going to be running hard and I thought I'd enjoy a trail run for the first time in a month so I'd be out of the sun. I got home, laced up my Peregrine 5, and headed out.
Almost immediately, the lower abdomen/groin discomfort flared up. Not so as I couldn't run through it, but it was discouraging. Three weeks of rest did nothing to calm that down, it would seem. I ran about an hour, feeling it in the background the whole way. I thought that because I'd run with it for quite some time at the end of the training schedule this spring, how much more could it hurt it to run tonight? My right leg was OK, but not great or normal; I could feel that hamstring still.
I didn't run on Tuesday, because my legs were sore -- quads in particular, calves a little tired-feeling. I guess three weeks is plenty of time for your muscles to forget everything they'd only recently gone through. And not just muscles; I ran quite slow on the trails, but my heart rate was higher for the same pace than it ever was this spring. I thought I might be able to attribute it to the heat, but I ran this morning (70F and humid, not too bad, and so lovely around the reservoir) at a pace that would certainly be considered "easy" but 40-60 seconds slower than the corresponding heart rate would have allowed me to run only a month ago.
The lower abdomen/groin thing felt about the same as my quads did, which is to say not too bad, better than on Monday. The hamstring was OK this morning too, less noticeable. I will run again tomorrow and see how it goes. I feel I am trying to be overly optimistic about the lower abdomen, but that's only because I don't want to sink immediately to doom and gloom conclusions (though that is what I really fear, deep down). I have an appointment with a doctor on July 13 to discuss this discomfort. I made this appointment a couple weeks go. It was the soonest I could get in. Ridiculous.
Saturday, June 11, 2016
Something something about the heat being on -- Vermont City Marathon, 2016
Knowing that the weather was going to be hot, no two ways about it, there was always the option of choosing not to run, and given my experience at Boston in 2012, that would probably be the most sensible option, but I had already paid: for the race, for the hotel, for the trip, never mind the price in miles over the last five months. Even if I would have to run slower than I’d hoped, the work I’d done in training, along with smarter execution, should allow me to finish reasonably (and certainly much, much better than the infernal 2012 Boston). This summer weather disappointed me even before the race began, but I couldn’t just pull the plug. I was going to do this race. Saturday night, I laid out my uniform: pale green singlet instead of the bright hot reddish-pink one (so as to not draw as little attention from the sun as possible), the dark blue Nike Epic Lux shorts that have three pockets (to carry my gels). Usually the nerves get started while I do this, but this time I felt only misgivings. I really should not run, I thought. I’m not going to run well and I will probably only end up doing damage.
But we came all this way, and I still hoped I might be able to leverage some intelligence into a half-decent time, if nowhere near the PR I’d hoped to take a shot at. And I could still hope it might be cloudy, right? 80s and overcast is not as bad as 80s and sunny. I tried to drink water every time I thought about it all day Saturday, all evening, and whenever I woke in the night, so that I could start from a full tank, hydration-wise. It made for an interrupted overnight, but I’d rather wake up several times to pee being well-hydrated than sleep soundly and wake up in the hole on that front. I never sleep soundly on race eve anyway, so might as well be getting something out of it.
Morning came muggy and sunny. No wishes had been granted. The sun would be out for the worst of it all.
I ate my oatmeal, wondering if it might be better next time to practice eating a cold breakfast instead of a hot one, just in case race day comes up steaming. I showered, I dressed, I looked out the window at runners leaving for Battery Park well before 7 a.m. Why would you do that? Why make yourself stand out in the heat any longer than absolutely necessary? It was in the 70s already at 7 a.m.! We did not leave the hotel until around 7:30, which was the latest possible. We had two blocks to walk to Battery Street, then up that bear of a hill about four blocks to the park at the top, where the start waited. In 2014, I wore a light jacket when B and I walked over, from a closer hotel, and while I didn’t wear it for long, at least it had been cool enough to have on for those first few minutes outside. This year, I was sorry to have even put on the singlet, and thought briefly about abandoning it and pinning my bib to the front of my sports bra. I decided it would be better to have my torso’s skin covered if it was going to be super sunny, so I left the shirt on. After a little tarrying and photography in the crowded Battery Park (half a thought to use a portapotty though I did not at all feel it was necessary, just wanting to out of habit, the lines deterring me from even that), I said good-bye to B and his parents with plans on seeing them by the hotel, which was between miles 9 and 10, if not before.
I walked up the street in front of the starting line toward the preferred corral, thanks to my 2014 Caesar Rodney time, and slipped in between a few rows of scantily clad men (and a few women) to position myself for the start. I thought about this year’s Caesar Rodney, how cold and horrid it had been, but that little trick of psychology didn’t help. The sun was on us, and already-hot bodies were all around me. Another woman slipped in to stand next to me; I could see from her bib that her name was also Courtney. She turned to me and wished me good-luck; I said the same, and told her that is my name too (though my bib indicated me as CRUSHER). I don’t know why people always enjoy finding others who share a name, but it added a little pleasantness to a moment I was otherwise only feeling sorry for myself. This was going to be awful. It was at least 75 when they finally started the race a little after 8:00 a.m., and not a dry 75 – at least Boston 2012 had not been humid. We were not going to get even that small fortune this day.
For the first four miles, I could not control my legs. I tried, honestly. I know how stupid that sounds; obviously I am in control of my body, so how could I not just slow them down if I wanted to? I tried. I looked at my watch and knew I was going too fast when it read anything less than 7:45 (even 7:45 would probably have been too fast); I would hit the brakes and back off, but then I’d look down and see I was cruising at 7:30 or even 7:2X again.
1 7:38.6
2 7:24.5
3 7:43.4
4 7:34.9
You’re going too fast, you idiot! Get a grip! But this portion had some downhill, and I was streaming along with a large host of others with cheering fans lining the way, so I got carried away in spite of my repeated attempts to rein my legs in. I repeatedly failed. My legs were just going to run whatever the hell they wanted to run, I guess.
Between miles 4 and 8, the route heads out on a divided highway (VT127, past the Ethan Allen homestead) that is shut down on race day. There is essentially no cover on this stretch – though I do recall toward its farther reach that it dipped close enough to trees along the side to afford some shade, however brief and relatively ineffectual. I finally got a grip on pace during this out and back, partly due to willpower but mainly due to physiological responses. There had been a water stop between miles 2 and 3, but not another until a little past mile 4 – by the time I came upon that one, it felt too late. I had been praying to see it come into view well before it finally did; I was thirsty. Not desperately so, but too thirsty for comfort. There was another one about a mile on down, and I was thirsty again when I hit that one. These conditions were ugly.
Where I had been running foolishly well under 8:00/mile for the first four, I finally got down to 8:00 and change during this out-and-back. I took a gel around the water stop between 6-7; ugh. The sticky Gu was unpleasant. Coming back into town from the highway, the course ran up a short but difficult hill; as the route leveled out again thereafter, I considered my condition. I did not feel terrible, but I certainly felt a long way from where you’d hope to feel as you complete the first third of the distance. As we headed back through downtown, I told myself it was only going to get exponentially worse – I knew it would, I had experience with that – and advised myself that it would be OK to drop out and spare myself a terrible time and the accompanying misery. No one would judge me negatively for doing something that, honestly, was eminently sensible. But quitting really is a last resort, and I did not feel that I gotten to last resort territory yet.
I suggested to myself that I would reassess closer to the hotel in a mile or two; if I were going to drop out, it would be easier to do it where I could easily find B and his parents, and quickly escape into a cool hotel room. And by the time we raced through downtown again, and turned the corner to head down Main Street toward Pine (the intersection at which the hotel lies), I felt somewhat improved, and so passed by my personal supporters with a wave and as much of a smile as I could put on my face.
Mile 10 came and went (7:42, thanks to some downhill). I had been running for just shy of 80 minutes, which was not all that shabby; but I could not feel very good about it, because I could feel the weather taking its toll one sweat bead at a time, and the stretch between 10 and 11 was a lot in the sun again. Finally we curved through a residential neighborhood with some tree cover, and it was here that the 3:30 pace group caught up to me. They did not overtake me with gusto, instead easing up and only getting ahead inch by inch, in part because I could not prevent myself from reacting to the spurt of adrenaline that said “Crusher, you do not want to finish over 3:30, maybe you can stay with these guys.” But around mile 12, they had crept farther and farther away, and I finally had to admit that while I could probably let my legs go and stay with them a while longer, it would only be a matter of time before they dropped me again and dropped me hard, leaving me to pay an even steeper price in the end for having tried. It was exceedingly disappointing to accept this and to let that bobbing 3:30 sign go.
I took another gel around the half, where the race course nears the lake. There was a bit of a breeze in this area, which only took the slightest edge off the sweltering heat. I thought to myself that I had less than two hours of running left to do, which wasn’t that bad, was it? Or would it be most rational of me to drop out, cede the fight in submission to the heat, and retreat? Again, I decided I would make that call when I came across B and his parents again; I expected to see them somewhere along Battery, either on the approach to the long hill or somewhere on it, so not too far into the future. The gel helped, and when I passed them at the bottom of the hill, I was feeling decent enough to forge onward.
The hill was tough. It was always going to be tough – it was in 2014 when it wasn’t quite as hot, it would have been even had it been cooler, simply because of its steepness and its length and its location in the race. I was doing OK though pace-wise – still in the 8:00s, that hill’s mile coming through at 8:37. I would get another decent two miles in (if we’re only considering pace, and not the fact that I did not feel decent) before the wheels started wobbling. After the hill on Battery, the course runs along what is probably a very busy road on normal days, with little cover again. It is long and straight, with undulations; you can see the string of runners along the curb for what seems like miles and miles ahead of you. I knew the course turned off this road into a side neighborhood at some point, but it started to feel like I was never going to get there. Somehow, this road kept lengthening itself between me and that turnoff. I grabbed ice for the first time along this road; I rubbed it all over my shoulders, my face, my neck, my head, and put the last small piece in my mouth. That was quite nice.
Before I begin to detail the excruciating crumble that I began to undergo starting between miles 18 and 19, I want to write a little bit about the spectators and fans. Except for that out-and-back along the highway, spectator support is nearly constant, and very regular on the course. Downtown it’s solid, of course, but in the neighborhoods, most houses had people out watching and cheering. (One lady made a dash across the runner-strewn road, precariously carrying a large and extremely fragrant pie. Many neighbors seemed to make race-spectating a party situation.) This year, many of those spectators had their own water stops, or offered ice, fruit, and other items to soothe the hot runners passing by. The race had official sprinklers and misters out after mile 10, but too many spectators to count had their own sprinklers and hoses out, as well. I ducked under countless sprays, which would give a brief but welcome blast of coolness; I’d wipe the droplets on my arms to spread them out for a quick shot of cooling evaporation before it just turned to warm sweatiness again. Fortunately my shoes never got over-wet, but my sunglasses did get spotty, which was moderately annoying to look through mile after mile. (I made the mistake, after one particularly sprinkly sprinkler, of trying to wipe them on the edge of my singlet. That only succeeded in smearing the lenses, and I spent the last 7 or so miles seeing through half a haze. At least, I think I can blame the haze on the sunglasses and not my deteriorating state.) I did not take but maybe one spectator’s water cups, as in the last half of the race, official aid stations were numerous enough, but I did scoop ice on several occasions and once, a moment of utter bliss: a man handed me a sponge that had been soaking in ice water, and I squashed it hard on the top of my head. I had expected coolness, of course; but I was not prepared for the bracing shock of that ice water streaming over the top of my head, down my face and neck, across my shoulders. It was momentary ecstasy. I wish I could go back and thank that man personally. It was only seconds before the sweaty heat overcame the ice water again, but my spirits were lifted for a little while thereafter.
And aside from the sustenance, the crowd were vocally supportive all along the course. I approve of the trend of putting names on bibs as well as numbers; having CRUSHER on mine made it feel like I had hundreds of friends along the roadside watching and cheering for me. Strangers yelling “LET’S GO CRUSHER, YOU CAN CRUSH IT!” and similar is very uplifting as well, even when I know I don’t actually know those people yelling it. And I appreciated it even in the later stages, when I could no longer believe them when they shouted “LOOKING GREAT, CRUSHER!” No, I certainly did not (I have seen the photographic proof), but thank you all for your positivity regardless.
Out of that neighborhood loop, back onto the long busy road for a short while. I knew we’d turn off again at some point, and didn’t it have to be soon? Weren’t we going to head to the bike path and start toward the end, soon? How could we not even be to mile 20 yet? The heat’s claws were working their wickedness; I dropped to slower than 9:00 for mile 20 and hope of anything faster became a foggy, forgotten dream. My right leg started to fall apart – my hamstring began to tighten, a sensation that wrapped itself around my upper leg and into my glute, down to my knee. Is this cramping? I wondered. Can I run through it for the next six miles? Then the thing happened where I was desperate to guzzle every cup of water at the aid stations (coming at least every mile now), but I could only take a couple sips because when it hit my stomach, it hurt. Gatorade was worse.
It was the same feeling that eventually forced me out of Boston in 2014. (In 2012, I had cratered well before this point; I felt sick, among several other disastrous developments, but have no memory of whether drinking water made it worse or not.) I couldn’t allow myself to pass by the water, however, because I was thirsty. It seemed like I could feel all those sips sitting in my stomach, not being absorbed, and after mile 21, I began to experience waves of nausea. They rolled in and out, and while the leg issue seemed to dull after a couple miles, I reached a point where I finally succumbed to the nausea and had to walk. By “succumb” I do not mean to say I threw up, though sometimes I thought I might just feel better if I did – get rid of that unabsorbed water and Gatorade hurting my stomach – but I was desperate not to be that person pulling off to the side of the path to hurl, so I gave up and walked until it eased. Over the last 4 or so miles, I mixed walking and running. I would run for a couple minutes until the nausea swelled again, at which time I’d step off the path to walk for a couple more minutes. After going through mile 22 in 9:29, the final four tick off a litany of awful, humiliating splits:
23 11:04
24 10:21
25 10:40
26 11:36
Yes. I walked in the final mile. I did not want to -- it was too disgraceful -- but I did not have a choice. I tried to run it, but the shame I felt by not being able to even jog the whole last mile was superseded by my desire not to be overcome by the nausea, not this close, so I ran/walked until it eased. I was able to jog the final stretch, though. I recognized the line of rail cars as I approached the very loud finish area, and knew I was almost through this.
In moments, I was running between a chute of the crowd and I thought I heard B as I plodded on, desperate for that finish line; I could not even turn my head back to quickly check if it had been him. I had been running for miles with my chin down, struggling on, and I couldn't spare the energy to try to look. He forgave me. "You weren't looking like you were doing too good there." No, I really was not.
And then, at last; at long, long last; the turn off the pavement onto the grassy area and the final tens of meters to the finish. As I approached the finish line, my name boomed out over the loudspeakers. Yes, that’s me – I’m done, in more ways than the obvious. I felt awful – stomach sick, legs dying. I collected my medal on the other side of the finish, and all I wanted was to lie down and throw up, but I held both desires in check as I slowly moved my way through a hot, defeated crowd, trying to find my way out of the finish pen. I held a cold and wet bottle of water in one hand that I could barely twist open, and was lassoed by a photographer to fake a giant smile holding my medal in front of a VCM backdrop. YES! the photo says, I FINISHED AND I’M HAPPY ABOUT IT!
I was happy to be finished, but I wasn’t happy about the finish. My net time was 3:49. This is nearly thirty minutes slower than I wanted to run this spring; twenty minutes slower than what I would have considered the very upper limit of acceptable. The only thing I could tell myself that was positive was 1) it was still under 4 hours, because there had been a point when I had doubted I would even crack that disappointing mark, and 2) it was still a long, long way from being a personal worst.1
The crowded finish area amplified how awful I felt. I eventually broke free from the mob, and was walking gingerly through a parking lot when I realized that the place I needed to be to meet B and his parents was back on the grassy space I had left; I felt beaten down by that realization. I really had only so very little much left in my legs and system, and I was going to need it all just to make it back to the hotel; here I had expended more than you might have guessed going the wrong way. I honestly did wonder if I would be able to get back to the hotel on my own accord. Nevertheless, I had to find B before making that call; they would never find me over here if I collapsed. I crept back to that madhouse of a grassy area, almost dazedly heading toward the flags with initials on them, the family meeting area; suddenly B was there, his parents were there, and I could safely lie in the grass and not worry that my people were worrying about where I was.
In 2012, I should absolutely, hands-down, have gone to a medical tent at the conclusion of the race. I did not feel quite as shredded this year as I did then, because while I had not run exactly smart this day, I did not run as abjectly stupidly as I had in Boston – and was not so clearly and obviously destroyed, so I did not feel I needed to go to a medical tent. Should I be so foolish as to run another marathon when it’s above 80F, I will simply disregard any thought that I have no need to a medical tent; I probably do. With clarity of hindsight, I realize I should certainly have done so; it might not have been the worst, but I was in bad, bad shape, and an IV would likely have made a world of difference. Instead, I laid on the grass, letting that vague nausea wash up and over and away again, before heaving myself to my feet to creep the six blocks back to the hotel, expecting I’d be OK once I just got back, took a shower, and was able to cool off for a while. (Though I tried to keep up drinking water at regular intervals throughout the following days after this race, I fought the effects of dehydration for at least a week.)
It had gotten to the upper 80s, very nearly 90, and it was humid. In a cruel twist, the sky had begun to cloud over – during the time I had been on the bike path, under tree cover. By then, I don’t think it mattered much – the temperature was already too high and combined with the mugginess was probably stronger than any benefit of cloud cover. In fact, shortly after I had finished my race, the directors, using the Wet Bulb Globe Temperature that takes all these weather conditions into account, decided the conditions were too extreme to continue and canceled the rest of it.
There was controversy about this, of course, though I only read about it online later. Anyone who came across the finish line up to a time of 4:30 was given an official result (due to their probable location on the bike path at the time of cancellation, inability to access them with shuttle buses, etc.) but anyone else was meant to stop and hitch a ride back. Some people ignored the orders, and were upset that they didn’t get a finish time, but the race directors stood by their decisions, which they explained in detail. At times later in the race, I wasn’t sure if I would break 4 hours, but I knew I was well ahead of 4:30 barring an absolute disaster – in which case, I would have bailed, on my own, anyway – I'm glad I didn’t have to deal with obeying orders and sucking up that disappointment on top of everything else.
I had to pause several times on the way back to the hotel. Half a block from the hotel, seated on the front stoop of an office building, I looked up at B, who stood at my side (as he has for every marathon I’ve run while he’s been my boyfriend, except the one in Des Moines) and said “I am not running another marathon this year. Don’t let me try to change that decision.” Normally, I do not consider decisions made during a race or its immediate aftermath to be binding, but I think this time, it is appropriate. As disappointed as I am by the way this race turned out, after this arduous spring when I ran more miles than I ever had before in an equal time period, I cannot immediately turn around to give it another shot – the way I did in 2014 after I quit the Boston race and made up for it in Vermont. It’s too late in the season for a make-up marathon and besides, I went the whole distance this year; wouldn’t be good (AT ALL) for my legs to try to run another any time soon. I am just going to have to accept that sometimes, things just don’t go the way you’d planned them to, and that’s just how it’s going to have to be. I have a very nice qualifying time for Boston 2017 in my pocket – 3:24 is 20 minutes better than the qualifying time for what will be my new age group – so I do not need to worry about reaching that mark (because I certainly did not on Sunday May 29th). I will spend the rest of this year recovering, recharging, and getting ready to get ready for my master’s marathon debut in April 2017.
Also, the next time I face a marathon with temperatures in the 80s, I think I am now more likely to say thanks but no thanks. I’m not sure collecting a medal and being able to say I finished in such torturous conditions is really worth the physical (and psychological) cost.
To conclude this long race report, I want to thank the Vermont City Marathon team and volunteers for putting on such a well-organized race, and heartfelt thanks as well to the citizens of Burlington for making an inevitably miserable day slightly less so. (Special gratitude to the ice-water sponge man.) I don’t know if I will run this race again – I don’t know how many more marathons I have left in me, and I’m thinking I might avoid the late May risk of heat from now on – but I will always fervently recommend this race to anyone that asks; and B and I are already making plans to return to Burlington for non-running pursuits, because the town is so cool. (Even when it is so hot.)
-------------------------------------------
1When your personal worst is 4:18, it’s not a difficult feat to run poorly and still be well under that.
But we came all this way, and I still hoped I might be able to leverage some intelligence into a half-decent time, if nowhere near the PR I’d hoped to take a shot at. And I could still hope it might be cloudy, right? 80s and overcast is not as bad as 80s and sunny. I tried to drink water every time I thought about it all day Saturday, all evening, and whenever I woke in the night, so that I could start from a full tank, hydration-wise. It made for an interrupted overnight, but I’d rather wake up several times to pee being well-hydrated than sleep soundly and wake up in the hole on that front. I never sleep soundly on race eve anyway, so might as well be getting something out of it.
Morning came muggy and sunny. No wishes had been granted. The sun would be out for the worst of it all.
I ate my oatmeal, wondering if it might be better next time to practice eating a cold breakfast instead of a hot one, just in case race day comes up steaming. I showered, I dressed, I looked out the window at runners leaving for Battery Park well before 7 a.m. Why would you do that? Why make yourself stand out in the heat any longer than absolutely necessary? It was in the 70s already at 7 a.m.! We did not leave the hotel until around 7:30, which was the latest possible. We had two blocks to walk to Battery Street, then up that bear of a hill about four blocks to the park at the top, where the start waited. In 2014, I wore a light jacket when B and I walked over, from a closer hotel, and while I didn’t wear it for long, at least it had been cool enough to have on for those first few minutes outside. This year, I was sorry to have even put on the singlet, and thought briefly about abandoning it and pinning my bib to the front of my sports bra. I decided it would be better to have my torso’s skin covered if it was going to be super sunny, so I left the shirt on. After a little tarrying and photography in the crowded Battery Park (half a thought to use a portapotty though I did not at all feel it was necessary, just wanting to out of habit, the lines deterring me from even that), I said good-bye to B and his parents with plans on seeing them by the hotel, which was between miles 9 and 10, if not before.
I walked up the street in front of the starting line toward the preferred corral, thanks to my 2014 Caesar Rodney time, and slipped in between a few rows of scantily clad men (and a few women) to position myself for the start. I thought about this year’s Caesar Rodney, how cold and horrid it had been, but that little trick of psychology didn’t help. The sun was on us, and already-hot bodies were all around me. Another woman slipped in to stand next to me; I could see from her bib that her name was also Courtney. She turned to me and wished me good-luck; I said the same, and told her that is my name too (though my bib indicated me as CRUSHER). I don’t know why people always enjoy finding others who share a name, but it added a little pleasantness to a moment I was otherwise only feeling sorry for myself. This was going to be awful. It was at least 75 when they finally started the race a little after 8:00 a.m., and not a dry 75 – at least Boston 2012 had not been humid. We were not going to get even that small fortune this day.
For the first four miles, I could not control my legs. I tried, honestly. I know how stupid that sounds; obviously I am in control of my body, so how could I not just slow them down if I wanted to? I tried. I looked at my watch and knew I was going too fast when it read anything less than 7:45 (even 7:45 would probably have been too fast); I would hit the brakes and back off, but then I’d look down and see I was cruising at 7:30 or even 7:2X again.
1 7:38.6
2 7:24.5
3 7:43.4
4 7:34.9
You’re going too fast, you idiot! Get a grip! But this portion had some downhill, and I was streaming along with a large host of others with cheering fans lining the way, so I got carried away in spite of my repeated attempts to rein my legs in. I repeatedly failed. My legs were just going to run whatever the hell they wanted to run, I guess.
Between miles 4 and 8, the route heads out on a divided highway (VT127, past the Ethan Allen homestead) that is shut down on race day. There is essentially no cover on this stretch – though I do recall toward its farther reach that it dipped close enough to trees along the side to afford some shade, however brief and relatively ineffectual. I finally got a grip on pace during this out and back, partly due to willpower but mainly due to physiological responses. There had been a water stop between miles 2 and 3, but not another until a little past mile 4 – by the time I came upon that one, it felt too late. I had been praying to see it come into view well before it finally did; I was thirsty. Not desperately so, but too thirsty for comfort. There was another one about a mile on down, and I was thirsty again when I hit that one. These conditions were ugly.
Where I had been running foolishly well under 8:00/mile for the first four, I finally got down to 8:00 and change during this out-and-back. I took a gel around the water stop between 6-7; ugh. The sticky Gu was unpleasant. Coming back into town from the highway, the course ran up a short but difficult hill; as the route leveled out again thereafter, I considered my condition. I did not feel terrible, but I certainly felt a long way from where you’d hope to feel as you complete the first third of the distance. As we headed back through downtown, I told myself it was only going to get exponentially worse – I knew it would, I had experience with that – and advised myself that it would be OK to drop out and spare myself a terrible time and the accompanying misery. No one would judge me negatively for doing something that, honestly, was eminently sensible. But quitting really is a last resort, and I did not feel that I gotten to last resort territory yet.
I suggested to myself that I would reassess closer to the hotel in a mile or two; if I were going to drop out, it would be easier to do it where I could easily find B and his parents, and quickly escape into a cool hotel room. And by the time we raced through downtown again, and turned the corner to head down Main Street toward Pine (the intersection at which the hotel lies), I felt somewhat improved, and so passed by my personal supporters with a wave and as much of a smile as I could put on my face.
Mile 10 came and went (7:42, thanks to some downhill). I had been running for just shy of 80 minutes, which was not all that shabby; but I could not feel very good about it, because I could feel the weather taking its toll one sweat bead at a time, and the stretch between 10 and 11 was a lot in the sun again. Finally we curved through a residential neighborhood with some tree cover, and it was here that the 3:30 pace group caught up to me. They did not overtake me with gusto, instead easing up and only getting ahead inch by inch, in part because I could not prevent myself from reacting to the spurt of adrenaline that said “Crusher, you do not want to finish over 3:30, maybe you can stay with these guys.” But around mile 12, they had crept farther and farther away, and I finally had to admit that while I could probably let my legs go and stay with them a while longer, it would only be a matter of time before they dropped me again and dropped me hard, leaving me to pay an even steeper price in the end for having tried. It was exceedingly disappointing to accept this and to let that bobbing 3:30 sign go.
I took another gel around the half, where the race course nears the lake. There was a bit of a breeze in this area, which only took the slightest edge off the sweltering heat. I thought to myself that I had less than two hours of running left to do, which wasn’t that bad, was it? Or would it be most rational of me to drop out, cede the fight in submission to the heat, and retreat? Again, I decided I would make that call when I came across B and his parents again; I expected to see them somewhere along Battery, either on the approach to the long hill or somewhere on it, so not too far into the future. The gel helped, and when I passed them at the bottom of the hill, I was feeling decent enough to forge onward.
The hill was tough. It was always going to be tough – it was in 2014 when it wasn’t quite as hot, it would have been even had it been cooler, simply because of its steepness and its length and its location in the race. I was doing OK though pace-wise – still in the 8:00s, that hill’s mile coming through at 8:37. I would get another decent two miles in (if we’re only considering pace, and not the fact that I did not feel decent) before the wheels started wobbling. After the hill on Battery, the course runs along what is probably a very busy road on normal days, with little cover again. It is long and straight, with undulations; you can see the string of runners along the curb for what seems like miles and miles ahead of you. I knew the course turned off this road into a side neighborhood at some point, but it started to feel like I was never going to get there. Somehow, this road kept lengthening itself between me and that turnoff. I grabbed ice for the first time along this road; I rubbed it all over my shoulders, my face, my neck, my head, and put the last small piece in my mouth. That was quite nice.
Before I begin to detail the excruciating crumble that I began to undergo starting between miles 18 and 19, I want to write a little bit about the spectators and fans. Except for that out-and-back along the highway, spectator support is nearly constant, and very regular on the course. Downtown it’s solid, of course, but in the neighborhoods, most houses had people out watching and cheering. (One lady made a dash across the runner-strewn road, precariously carrying a large and extremely fragrant pie. Many neighbors seemed to make race-spectating a party situation.) This year, many of those spectators had their own water stops, or offered ice, fruit, and other items to soothe the hot runners passing by. The race had official sprinklers and misters out after mile 10, but too many spectators to count had their own sprinklers and hoses out, as well. I ducked under countless sprays, which would give a brief but welcome blast of coolness; I’d wipe the droplets on my arms to spread them out for a quick shot of cooling evaporation before it just turned to warm sweatiness again. Fortunately my shoes never got over-wet, but my sunglasses did get spotty, which was moderately annoying to look through mile after mile. (I made the mistake, after one particularly sprinkly sprinkler, of trying to wipe them on the edge of my singlet. That only succeeded in smearing the lenses, and I spent the last 7 or so miles seeing through half a haze. At least, I think I can blame the haze on the sunglasses and not my deteriorating state.) I did not take but maybe one spectator’s water cups, as in the last half of the race, official aid stations were numerous enough, but I did scoop ice on several occasions and once, a moment of utter bliss: a man handed me a sponge that had been soaking in ice water, and I squashed it hard on the top of my head. I had expected coolness, of course; but I was not prepared for the bracing shock of that ice water streaming over the top of my head, down my face and neck, across my shoulders. It was momentary ecstasy. I wish I could go back and thank that man personally. It was only seconds before the sweaty heat overcame the ice water again, but my spirits were lifted for a little while thereafter.
And aside from the sustenance, the crowd were vocally supportive all along the course. I approve of the trend of putting names on bibs as well as numbers; having CRUSHER on mine made it feel like I had hundreds of friends along the roadside watching and cheering for me. Strangers yelling “LET’S GO CRUSHER, YOU CAN CRUSH IT!” and similar is very uplifting as well, even when I know I don’t actually know those people yelling it. And I appreciated it even in the later stages, when I could no longer believe them when they shouted “LOOKING GREAT, CRUSHER!” No, I certainly did not (I have seen the photographic proof), but thank you all for your positivity regardless.
Out of that neighborhood loop, back onto the long busy road for a short while. I knew we’d turn off again at some point, and didn’t it have to be soon? Weren’t we going to head to the bike path and start toward the end, soon? How could we not even be to mile 20 yet? The heat’s claws were working their wickedness; I dropped to slower than 9:00 for mile 20 and hope of anything faster became a foggy, forgotten dream. My right leg started to fall apart – my hamstring began to tighten, a sensation that wrapped itself around my upper leg and into my glute, down to my knee. Is this cramping? I wondered. Can I run through it for the next six miles? Then the thing happened where I was desperate to guzzle every cup of water at the aid stations (coming at least every mile now), but I could only take a couple sips because when it hit my stomach, it hurt. Gatorade was worse.
It was the same feeling that eventually forced me out of Boston in 2014. (In 2012, I had cratered well before this point; I felt sick, among several other disastrous developments, but have no memory of whether drinking water made it worse or not.) I couldn’t allow myself to pass by the water, however, because I was thirsty. It seemed like I could feel all those sips sitting in my stomach, not being absorbed, and after mile 21, I began to experience waves of nausea. They rolled in and out, and while the leg issue seemed to dull after a couple miles, I reached a point where I finally succumbed to the nausea and had to walk. By “succumb” I do not mean to say I threw up, though sometimes I thought I might just feel better if I did – get rid of that unabsorbed water and Gatorade hurting my stomach – but I was desperate not to be that person pulling off to the side of the path to hurl, so I gave up and walked until it eased. Over the last 4 or so miles, I mixed walking and running. I would run for a couple minutes until the nausea swelled again, at which time I’d step off the path to walk for a couple more minutes. After going through mile 22 in 9:29, the final four tick off a litany of awful, humiliating splits:
23 11:04
24 10:21
25 10:40
26 11:36
Yes. I walked in the final mile. I did not want to -- it was too disgraceful -- but I did not have a choice. I tried to run it, but the shame I felt by not being able to even jog the whole last mile was superseded by my desire not to be overcome by the nausea, not this close, so I ran/walked until it eased. I was able to jog the final stretch, though. I recognized the line of rail cars as I approached the very loud finish area, and knew I was almost through this.
In moments, I was running between a chute of the crowd and I thought I heard B as I plodded on, desperate for that finish line; I could not even turn my head back to quickly check if it had been him. I had been running for miles with my chin down, struggling on, and I couldn't spare the energy to try to look. He forgave me. "You weren't looking like you were doing too good there." No, I really was not.
And then, at last; at long, long last; the turn off the pavement onto the grassy area and the final tens of meters to the finish. As I approached the finish line, my name boomed out over the loudspeakers. Yes, that’s me – I’m done, in more ways than the obvious. I felt awful – stomach sick, legs dying. I collected my medal on the other side of the finish, and all I wanted was to lie down and throw up, but I held both desires in check as I slowly moved my way through a hot, defeated crowd, trying to find my way out of the finish pen. I held a cold and wet bottle of water in one hand that I could barely twist open, and was lassoed by a photographer to fake a giant smile holding my medal in front of a VCM backdrop. YES! the photo says, I FINISHED AND I’M HAPPY ABOUT IT!
I was happy to be finished, but I wasn’t happy about the finish. My net time was 3:49. This is nearly thirty minutes slower than I wanted to run this spring; twenty minutes slower than what I would have considered the very upper limit of acceptable. The only thing I could tell myself that was positive was 1) it was still under 4 hours, because there had been a point when I had doubted I would even crack that disappointing mark, and 2) it was still a long, long way from being a personal worst.1
The crowded finish area amplified how awful I felt. I eventually broke free from the mob, and was walking gingerly through a parking lot when I realized that the place I needed to be to meet B and his parents was back on the grassy space I had left; I felt beaten down by that realization. I really had only so very little much left in my legs and system, and I was going to need it all just to make it back to the hotel; here I had expended more than you might have guessed going the wrong way. I honestly did wonder if I would be able to get back to the hotel on my own accord. Nevertheless, I had to find B before making that call; they would never find me over here if I collapsed. I crept back to that madhouse of a grassy area, almost dazedly heading toward the flags with initials on them, the family meeting area; suddenly B was there, his parents were there, and I could safely lie in the grass and not worry that my people were worrying about where I was.
In 2012, I should absolutely, hands-down, have gone to a medical tent at the conclusion of the race. I did not feel quite as shredded this year as I did then, because while I had not run exactly smart this day, I did not run as abjectly stupidly as I had in Boston – and was not so clearly and obviously destroyed, so I did not feel I needed to go to a medical tent. Should I be so foolish as to run another marathon when it’s above 80F, I will simply disregard any thought that I have no need to a medical tent; I probably do. With clarity of hindsight, I realize I should certainly have done so; it might not have been the worst, but I was in bad, bad shape, and an IV would likely have made a world of difference. Instead, I laid on the grass, letting that vague nausea wash up and over and away again, before heaving myself to my feet to creep the six blocks back to the hotel, expecting I’d be OK once I just got back, took a shower, and was able to cool off for a while. (Though I tried to keep up drinking water at regular intervals throughout the following days after this race, I fought the effects of dehydration for at least a week.)
It had gotten to the upper 80s, very nearly 90, and it was humid. In a cruel twist, the sky had begun to cloud over – during the time I had been on the bike path, under tree cover. By then, I don’t think it mattered much – the temperature was already too high and combined with the mugginess was probably stronger than any benefit of cloud cover. In fact, shortly after I had finished my race, the directors, using the Wet Bulb Globe Temperature that takes all these weather conditions into account, decided the conditions were too extreme to continue and canceled the rest of it.
There was controversy about this, of course, though I only read about it online later. Anyone who came across the finish line up to a time of 4:30 was given an official result (due to their probable location on the bike path at the time of cancellation, inability to access them with shuttle buses, etc.) but anyone else was meant to stop and hitch a ride back. Some people ignored the orders, and were upset that they didn’t get a finish time, but the race directors stood by their decisions, which they explained in detail. At times later in the race, I wasn’t sure if I would break 4 hours, but I knew I was well ahead of 4:30 barring an absolute disaster – in which case, I would have bailed, on my own, anyway – I'm glad I didn’t have to deal with obeying orders and sucking up that disappointment on top of everything else.
I had to pause several times on the way back to the hotel. Half a block from the hotel, seated on the front stoop of an office building, I looked up at B, who stood at my side (as he has for every marathon I’ve run while he’s been my boyfriend, except the one in Des Moines) and said “I am not running another marathon this year. Don’t let me try to change that decision.” Normally, I do not consider decisions made during a race or its immediate aftermath to be binding, but I think this time, it is appropriate. As disappointed as I am by the way this race turned out, after this arduous spring when I ran more miles than I ever had before in an equal time period, I cannot immediately turn around to give it another shot – the way I did in 2014 after I quit the Boston race and made up for it in Vermont. It’s too late in the season for a make-up marathon and besides, I went the whole distance this year; wouldn’t be good (AT ALL) for my legs to try to run another any time soon. I am just going to have to accept that sometimes, things just don’t go the way you’d planned them to, and that’s just how it’s going to have to be. I have a very nice qualifying time for Boston 2017 in my pocket – 3:24 is 20 minutes better than the qualifying time for what will be my new age group – so I do not need to worry about reaching that mark (because I certainly did not on Sunday May 29th). I will spend the rest of this year recovering, recharging, and getting ready to get ready for my master’s marathon debut in April 2017.
Also, the next time I face a marathon with temperatures in the 80s, I think I am now more likely to say thanks but no thanks. I’m not sure collecting a medal and being able to say I finished in such torturous conditions is really worth the physical (and psychological) cost.
To conclude this long race report, I want to thank the Vermont City Marathon team and volunteers for putting on such a well-organized race, and heartfelt thanks as well to the citizens of Burlington for making an inevitably miserable day slightly less so. (Special gratitude to the ice-water sponge man.) I don’t know if I will run this race again – I don’t know how many more marathons I have left in me, and I’m thinking I might avoid the late May risk of heat from now on – but I will always fervently recommend this race to anyone that asks; and B and I are already making plans to return to Burlington for non-running pursuits, because the town is so cool. (Even when it is so hot.)
-------------------------------------------
1When your personal worst is 4:18, it’s not a difficult feat to run poorly and still be well under that.
Saturday, May 28, 2016
The day before
We arose Friday morning in Burlington, the day already sunny and warm. I didn't go out for a short, easy run. The day grew warmer and warmer, and by noon was already in the 80s. The forecast for Sunday morning has not looked good all week, and the expected temperature has crept up and up each day. It was in the upper 80s on Friday; fully hot when we stopped at the race expo to pick up my packet and t-shirt and other goods. The volunteer who handed me my bib explained to me that it would be extra-critical this year to fill out the emergency information on the back. Discouraging to think about it, but let's face it -- I don't want it to be necessary and not have the info there.
While at the expo, a man got in line behind (or, to be more precise, next to) me, and asked me if I was running the race. I hope my face did not say what my brain thought: why would I be in line here, if not? (Maybe he thought I was with the guy in front of me; if so, that's irritating.) I told him yes, and he said "Great!" Then it was my turn to be helped, and I left him there after I got my packet. He turned up again a little bit later, after I had confirmed that the chip on the bib was functioning correctly and was buying a handful of gels that I will use in the race. Right at my shoulder, he said, "Do those work?" I told him that they do work, or maybe it's all in my head, but either way I seem to have a less awful time getting through the final 6-10 miles if I use them. He said that if I endorse them, then he might just try them -- what was the best flavor? What did I have? Salted caramel? He would try those.
Yikes, dude! I tried to tell him that I wouldn't recommend using them for the first time on race day! Some people's systems do not respond favorably to these and I tested them out over several long and/or tough workouts to see how my insides would deal with them. I am not sure he quite heard me, and I decided to just get out of there. I don't want him to really remember what I look like so that he can blame me if he tries them for the first time tomorrow and has to drop out because he gets an upset stomach.
This morning, I got up around 7 and went out for the short, easy run that I did not do yesterday. I jogged along the path by the lakefront that will be the site of the final miles of the race. A great deal of activity going on down there -- tents being set up, a train of trucks bringing porta-potties, getting ready for some sort of kid's fun run, etc. It was kind of exciting, coming back after going out for 15 minutes, to pass by the grassy space which is where the finish line will be -- I'll be there a little more than 24 hours from now, I hope. The half hour confirmed that my legs do, in fact, still know how to run, they are still fine, there are no heretofore-undiscovered injuries that decided to make themselves known today. I also confirmed that it is, in fact, quite warm, and that there is no getting around it, it's going to be absolutely unpleasant tomorrow. Given the forecast is not likely to dramatically change for the better in the next 24 hours, I think the best that I can hope for is that it will be cloudy. I won't waste time hoping it will be cooler. There is a long out-and-back portion in the first half of the race that will be completely exposed to the sky, and if the sun can just stay covered up at least for that part, it will go a long way. My recollection of the course is that most of the rest of the run will have some degree of cover, and the race has announced they will have extra water, ice, sprinklers, etc. in the later parts to help alleviate the heat-related misery. So, sun -- while I generally love you very much -- please stay tucked away behind clouds tomorrow, at least until noon? Thanks!
The high is predicted to be 85F, with a low of 66F, and a race-start temperature of 72F. That is way outside the range of good, and I have pretty much no experience this spring running in anything that hot. But I have no control over it, obviously, and I am (I hope) smarter than I was in Boston in 2012 when I foolishly shrugged off the warning about the heat. I have time goals for tomorrow, but I'm going to try to be sensible about trying to reach them.
There are a couple "tries" in that statement because there have been times when no matter how hard I work to stay controlled, I have let myself get swept up in things. I can only promise that I will TRY not to. 2012 wasn't so long ago that I have completely forgotten what it was like to be so stupid, and I hope the memory of that will be strong enough to hold me back if I need to.
So, today: lots of water drinking, carb it up for lunch and dinner, lots more water-drinking, and get to the starting line fresh and ready to run in the heat. I just can't worry about it. I hate the phrase "It is what it is" because it's used too much to excuse things that shouldn't be excused, but in this case it really is what it is, and I will run how I can without destroying myself the way I did in 2012. If I start feeling like I did that time, I will drop out.
One last glass-half-empty moment: I really wish I had been able to get at least one 22-er in this training cycle. It didn't work out for different reasons and even though a 22-er isn't necessary, it's just beneficial for the mental battle to know I've gone over that 20-mile hill. But I just can't worry about that, either. That cannot be changed and there is nothing that can be done about it now. I did a number of solid and tough 19-20s, so I can focus on that. And now that that last little negativity is done, let's be as positive as I can be, facing a broiler: the marathon is unpredictable, even on days when the weather is ideal. You can have some idea of how it should play out, but sometimes things go wildly differently -- in both directions. If I run smart, I can still finish well.
While at the expo, a man got in line behind (or, to be more precise, next to) me, and asked me if I was running the race. I hope my face did not say what my brain thought: why would I be in line here, if not? (Maybe he thought I was with the guy in front of me; if so, that's irritating.) I told him yes, and he said "Great!" Then it was my turn to be helped, and I left him there after I got my packet. He turned up again a little bit later, after I had confirmed that the chip on the bib was functioning correctly and was buying a handful of gels that I will use in the race. Right at my shoulder, he said, "Do those work?" I told him that they do work, or maybe it's all in my head, but either way I seem to have a less awful time getting through the final 6-10 miles if I use them. He said that if I endorse them, then he might just try them -- what was the best flavor? What did I have? Salted caramel? He would try those.
Yikes, dude! I tried to tell him that I wouldn't recommend using them for the first time on race day! Some people's systems do not respond favorably to these and I tested them out over several long and/or tough workouts to see how my insides would deal with them. I am not sure he quite heard me, and I decided to just get out of there. I don't want him to really remember what I look like so that he can blame me if he tries them for the first time tomorrow and has to drop out because he gets an upset stomach.
This morning, I got up around 7 and went out for the short, easy run that I did not do yesterday. I jogged along the path by the lakefront that will be the site of the final miles of the race. A great deal of activity going on down there -- tents being set up, a train of trucks bringing porta-potties, getting ready for some sort of kid's fun run, etc. It was kind of exciting, coming back after going out for 15 minutes, to pass by the grassy space which is where the finish line will be -- I'll be there a little more than 24 hours from now, I hope. The half hour confirmed that my legs do, in fact, still know how to run, they are still fine, there are no heretofore-undiscovered injuries that decided to make themselves known today. I also confirmed that it is, in fact, quite warm, and that there is no getting around it, it's going to be absolutely unpleasant tomorrow. Given the forecast is not likely to dramatically change for the better in the next 24 hours, I think the best that I can hope for is that it will be cloudy. I won't waste time hoping it will be cooler. There is a long out-and-back portion in the first half of the race that will be completely exposed to the sky, and if the sun can just stay covered up at least for that part, it will go a long way. My recollection of the course is that most of the rest of the run will have some degree of cover, and the race has announced they will have extra water, ice, sprinklers, etc. in the later parts to help alleviate the heat-related misery. So, sun -- while I generally love you very much -- please stay tucked away behind clouds tomorrow, at least until noon? Thanks!
The high is predicted to be 85F, with a low of 66F, and a race-start temperature of 72F. That is way outside the range of good, and I have pretty much no experience this spring running in anything that hot. But I have no control over it, obviously, and I am (I hope) smarter than I was in Boston in 2012 when I foolishly shrugged off the warning about the heat. I have time goals for tomorrow, but I'm going to try to be sensible about trying to reach them.
There are a couple "tries" in that statement because there have been times when no matter how hard I work to stay controlled, I have let myself get swept up in things. I can only promise that I will TRY not to. 2012 wasn't so long ago that I have completely forgotten what it was like to be so stupid, and I hope the memory of that will be strong enough to hold me back if I need to.
So, today: lots of water drinking, carb it up for lunch and dinner, lots more water-drinking, and get to the starting line fresh and ready to run in the heat. I just can't worry about it. I hate the phrase "It is what it is" because it's used too much to excuse things that shouldn't be excused, but in this case it really is what it is, and I will run how I can without destroying myself the way I did in 2012. If I start feeling like I did that time, I will drop out.
One last glass-half-empty moment: I really wish I had been able to get at least one 22-er in this training cycle. It didn't work out for different reasons and even though a 22-er isn't necessary, it's just beneficial for the mental battle to know I've gone over that 20-mile hill. But I just can't worry about that, either. That cannot be changed and there is nothing that can be done about it now. I did a number of solid and tough 19-20s, so I can focus on that. And now that that last little negativity is done, let's be as positive as I can be, facing a broiler: the marathon is unpredictable, even on days when the weather is ideal. You can have some idea of how it should play out, but sometimes things go wildly differently -- in both directions. If I run smart, I can still finish well.
Sunday, May 22, 2016
Week #21 -- starting to wind down
Summary for week ending Sunday, May 22, 2016:
Number of workouts: 6
Total miles run: 38.87
Average miles per run: 6.48
Miles in May: 137.25
Miles in 2016: 940.13
During taper weeks, I always start to feel anxious -- like I'm not running enough and I'm undoing all the work I have done to date. It feels odd to be done after less than an hour of running, or not have to go back out after work for a double, and I have to remind myself that it's what my schedule says to do, it is what I'm supposed to be doing, and to just relax and enjoy not having to do 10-12 miles a day.
I did most of my running in the morning, doing a few laps around the reservoir each time. I discovered that my Garmin measures differently depending on which direction I run around: if I go clockwise for three laps, my total distance is 5.45 miles. If I go counter-clockwise for three laps, my total distance is 5.38 miles. I wonder what accounts for the nearly tenth of a mile difference?
More life getting in the way this week, so I moved around the week's T workout to Sunday rather than Wednesday or Thursday. It worked out fine. 2 mi E + 2(10 min T) + 30-45 min. The T intervals were OK, not as fluid as I'd have liked but still manageable at 7:10 pace.
With a week to race day, the hay is pretty much in the barn. Just need to spend the next week taking it easy and going out for shortish, easy runs to keep the legs in motion. As anxious as I feel that I'm not doing enough, I'm just going to have to cool it and remember that my legs don't need a lot of work this week.
Number of workouts: 6
Total miles run: 38.87
Average miles per run: 6.48
Miles in May: 137.25
Miles in 2016: 940.13
During taper weeks, I always start to feel anxious -- like I'm not running enough and I'm undoing all the work I have done to date. It feels odd to be done after less than an hour of running, or not have to go back out after work for a double, and I have to remind myself that it's what my schedule says to do, it is what I'm supposed to be doing, and to just relax and enjoy not having to do 10-12 miles a day.
I did most of my running in the morning, doing a few laps around the reservoir each time. I discovered that my Garmin measures differently depending on which direction I run around: if I go clockwise for three laps, my total distance is 5.45 miles. If I go counter-clockwise for three laps, my total distance is 5.38 miles. I wonder what accounts for the nearly tenth of a mile difference?
More life getting in the way this week, so I moved around the week's T workout to Sunday rather than Wednesday or Thursday. It worked out fine. 2 mi E + 2(10 min T) + 30-45 min. The T intervals were OK, not as fluid as I'd have liked but still manageable at 7:10 pace.
With a week to race day, the hay is pretty much in the barn. Just need to spend the next week taking it easy and going out for shortish, easy runs to keep the legs in motion. As anxious as I feel that I'm not doing enough, I'm just going to have to cool it and remember that my legs don't need a lot of work this week.
Saturday, May 21, 2016
More birds
I was doing laps at Paper Mill Park during a tempo run, and there are probably a bazillion geese there at any given time. Mostly they ignore the people around, barely even stirring when they are standing in the path and people walk or run by. I still give them as much space as I can without going way out of my way to avoid them, though. I don't like to antagonize them if they appear to be anxious about me. This time, there was a group of three families, with around 15-20 goslings between them, hanging out in one of the soccer fields. Two parents were keeping guard near the path, and as I approached, they hissed at me. I found myself saying "I know! I'm sorry!" as I passed.
Did I just apologize to geese?
---------------
Another weekend bird encounter: nature is amazing and unpleasant all at the same time.
1) As I ran on a bridge across the White Clay Creek, I saw a blue heron standing in the water, a large, gasping fish hanging out of either side of its long beak. It hopped up a few stones to stand at the top of a short waterfall. I stopped to watch it for a minute or two until I realized that what I was doing was watching the fish dying; I didn't need to see that. I ran off, leaving the heron to its lunch.
2) The grass all around the reservoir was freshly mowed, which smelled wonderful in the sun; but I'm guessing that some small things did not survive the event, based on the presence of three gigantic turkey vultures that were stalking around in the shorn field. As beautiful as the blue heron was, the vultures ... not so much. But it's not their fault they have to have bald, ugly heads. If I had to spend my life plunging my head into gross roadkill too, it would be easier to not have to worry about it being stuck in my hair all the time.
Did I just apologize to geese?
---------------
Another weekend bird encounter: nature is amazing and unpleasant all at the same time.
1) As I ran on a bridge across the White Clay Creek, I saw a blue heron standing in the water, a large, gasping fish hanging out of either side of its long beak. It hopped up a few stones to stand at the top of a short waterfall. I stopped to watch it for a minute or two until I realized that what I was doing was watching the fish dying; I didn't need to see that. I ran off, leaving the heron to its lunch.
2) The grass all around the reservoir was freshly mowed, which smelled wonderful in the sun; but I'm guessing that some small things did not survive the event, based on the presence of three gigantic turkey vultures that were stalking around in the shorn field. As beautiful as the blue heron was, the vultures ... not so much. But it's not their fault they have to have bald, ugly heads. If I had to spend my life plunging my head into gross roadkill too, it would be easier to not have to worry about it being stuck in my hair all the time.
Sunday, May 15, 2016
Week #20 -- life gets in the way again
Summary for week ending Sunday, May 15, 2016:
Number of workouts: 5
Total miles run: 40.91
Average miles per run: 8.18
Miles in May: 98.38
Miles in 2016: 901.26
Tapering unofficially began last week, I suppose, if you look at it from a mileage standpoint, and continued this week, as I was traveling again -- this time in Montreal, QC for a workshop at McGill University. I had never been to Montreal before and while my hotel was seemingly ideally located to a very large park with trails, I did not have time to do any exploring (and, let's be honest, I'm not all that brave about running on trails in a strange city all by myself). I arrived late Wednesday afternoon and took the time to walk around a little but not up to the park. Thursday was a lovely and warm day, but I did not want to go exploring park trails in the morning when I had a firm morning scheduling commitment -- even just going out and back cannot be assumed to go without hitch. Thursday evening I was late getting back to the hotel -- 7 p.m. -- far too late to try to explore the park, so I did a few miles on the treadmill in the hotel.
I had not considered that I was in Canada and that in Canada, things are not really done in miles. I started the belt with numbers that made sense for my treadmill at home and wondered "Why is this so slow??" Fortunately I quickly put two and two together (I am a scientist, after all) and got it going, but then had to do math the whole time to try to tick off the mile splits on my Garmin at the right times. Who wants to have to do math during a run?! It was a decent run, if a bit zzz because I didn't take any music in with me and there was nothing worth looking at on the TV that was right in my face on the console; and nothing of interest out the window, which faced a small parking lot and a Subway across the street.
I had hoped to have time to go up and for a run in the park at the close of the workshop Friday afternoon, but the weather was no longer pleasant -- it had begun raining and was gloomy, and with rain threatening I passed on the park exploration again. And then, being actually quite exhausted from having to be thinking scientifically and being social all day, passed on running on the treadmill again too. Instead, I got up early Saturday to do another ~5 miles (~8K) on the treadmill. There was an older gentleman walking on the machine next to me, but he kept to himself and I kept to myself and had another pretty zzz run that did its job. It's been a while since I did any mileage on the treadmill.
So I did not run as much during the week (for the second week in a row) that I had hoped to/thought I might. Legs were feeling pretty fresh for the last long and tough workout on Sunday, which was 2 mi E + 15 mi M + 2 mi E. The day was decent enough -- cool-ish and though it had rained a lot overnight, it held off during the day. I thought I would do the M miles at around 7:40-7:45 and my legs felt good enough that they kept turning them out at more like 7:35, even when I tried to back off a little bit to be more 7:40-ish. So I just let them do it.
I had kind of thought that, if my legs were feeling it, I would run a little more than 2 mi E at the end and maybe try to get to 22 as I did not get over 20 this training cycle and that had/has me a little worried. But after 15 miles of ~7:35-7:40, anything more than the 2 E I did was going to be junk. So I did the 2 easy and called it a successful workout.
7:35-7:40 might be a little rich for another 11 miles, so unless my legs are totally feeling it, I'm going to really force them to go 7:40-7:45 (if they feel good enough for that, even).
This week the official taper begins, but that will only be formality after the last couple lower-volume weeks.
Number of workouts: 5
Total miles run: 40.91
Average miles per run: 8.18
Miles in May: 98.38
Miles in 2016: 901.26
Tapering unofficially began last week, I suppose, if you look at it from a mileage standpoint, and continued this week, as I was traveling again -- this time in Montreal, QC for a workshop at McGill University. I had never been to Montreal before and while my hotel was seemingly ideally located to a very large park with trails, I did not have time to do any exploring (and, let's be honest, I'm not all that brave about running on trails in a strange city all by myself). I arrived late Wednesday afternoon and took the time to walk around a little but not up to the park. Thursday was a lovely and warm day, but I did not want to go exploring park trails in the morning when I had a firm morning scheduling commitment -- even just going out and back cannot be assumed to go without hitch. Thursday evening I was late getting back to the hotel -- 7 p.m. -- far too late to try to explore the park, so I did a few miles on the treadmill in the hotel.
I had not considered that I was in Canada and that in Canada, things are not really done in miles. I started the belt with numbers that made sense for my treadmill at home and wondered "Why is this so slow??" Fortunately I quickly put two and two together (I am a scientist, after all) and got it going, but then had to do math the whole time to try to tick off the mile splits on my Garmin at the right times. Who wants to have to do math during a run?! It was a decent run, if a bit zzz because I didn't take any music in with me and there was nothing worth looking at on the TV that was right in my face on the console; and nothing of interest out the window, which faced a small parking lot and a Subway across the street.
I had hoped to have time to go up and for a run in the park at the close of the workshop Friday afternoon, but the weather was no longer pleasant -- it had begun raining and was gloomy, and with rain threatening I passed on the park exploration again. And then, being actually quite exhausted from having to be thinking scientifically and being social all day, passed on running on the treadmill again too. Instead, I got up early Saturday to do another ~5 miles (~8K) on the treadmill. There was an older gentleman walking on the machine next to me, but he kept to himself and I kept to myself and had another pretty zzz run that did its job. It's been a while since I did any mileage on the treadmill.
So I did not run as much during the week (for the second week in a row) that I had hoped to/thought I might. Legs were feeling pretty fresh for the last long and tough workout on Sunday, which was 2 mi E + 15 mi M + 2 mi E. The day was decent enough -- cool-ish and though it had rained a lot overnight, it held off during the day. I thought I would do the M miles at around 7:40-7:45 and my legs felt good enough that they kept turning them out at more like 7:35, even when I tried to back off a little bit to be more 7:40-ish. So I just let them do it.
I had kind of thought that, if my legs were feeling it, I would run a little more than 2 mi E at the end and maybe try to get to 22 as I did not get over 20 this training cycle and that had/has me a little worried. But after 15 miles of ~7:35-7:40, anything more than the 2 E I did was going to be junk. So I did the 2 easy and called it a successful workout.
7:35-7:40 might be a little rich for another 11 miles, so unless my legs are totally feeling it, I'm going to really force them to go 7:40-7:45 (if they feel good enough for that, even).
This week the official taper begins, but that will only be formality after the last couple lower-volume weeks.
Wednesday, May 11, 2016
Race! Half-marathon at the Delaware Marathon Running Festival
All I really wanted from this race was to not feel like crud and to do better than I had done at the Caesar Rodney a month earlier. With legs that had not really trained through, and good weather, I got what I wanted.
It was in the 50s at race start, which was just about right. It was a 7:00 a.m. gun though, which I did not particularly like -- you know that getting out of bed in the morning at the crack of dawn is not my favorite thing. Portapotty lines were long, so I took a chance on the next-door Amtrak station and discovered that the indoor facilities (particularly the upstairs option) had not been widely discovered. Yay! Even so, I did not get to the starting area until about 5 minutes to the gun, and it was tightly packed so that I could not make my way very far up and was stuck toward the back with people who were definitely not going to be running under 1:40. Well, there wasn't any risk of actually winning this race so it would have to do. The throng around me ensured I didn't take off like a shot, which was a benefit of being crammed so far back -- I did mile #1 in 7:28. I settled in.
There was no wind to speak of, and the temperature was comfortable. I was comfortable. I aimed to keep my miles at least 7:20, as long as it didn't start to feel like a stretch, and it did not. I let my legs do what they wanted as long as they did not push to a point where it felt like I was reaching. Even on the uphill mile (~7), I felt pretty strong. In fact, up until around mile 8 or 9, I was feeling better and better as I went on. After 9 or so, my legs started to feel kind of robotic/wooden, but they still responded to my pace orders -- it was a race, I told them, so race. Miles 10, 11, 12, and 13 were all 7:10 or better, with mile 13 being the best: 6:56. In those last three, I made use of that long downhill and then the downhill in the last half mile or so, and told myself again that this is a race; if your legs can do it, make them do it. And so they did.
I kept an eye on who was ahead of me, and if I saw a woman wearing a "HALF" tag on her back (to distinguish us from the 26.2 runners, they made us wear bibs on our backs), I made a point of reeling her in. There was a woman in the last mile that I wasn't sure I was going to get, but going up the hill on King Street on the way toward the finish, I caught her after all, which was satisfying. I aimed at the next woman ahead of me, but I ran out of real estate before I could get her.1 I glanced up at the race clock over the finish line as I crossed -- it was 1:36:XX.
I thought, "Well, good enough" though a teeeny bit disappointed it wasn't a liiiiittle bit faster -- and then, after stopping, I stopped my Garmin and looked down at it.
It said 1:35:05. What? OH RIGHT -- being so far back at the start, I hit the start mat a minute after the gun. So, OK, I was a liiiittle bit faster. I was pretty excited about that, even exulting "YES!" out loud.
My official time for the race is 1:35:04. It is about 30 seconds slower than my PR. It was good for 4th in my age group; I was 12th female; and 45th out of 891 half-marathon finishers. Frankly, after that 10-miler in Lewes, I needed this shot of confidence.
The only disappointing thing about the day was the fat-free chocolate milk they had at the post-race tent. Come on! Who wants that after finishing a race?! Give me at least 1%!!!
-----------------------------------------
1After looking at the results, it seems not to matter: she does not seem to appear in the half-marathon results, as the person that is right before me (4 seconds faster) is a 42 year old man and his race photos indicate that he is not the person who I saw just ahead of me! The next faster woman than me had a gun time almost a whole minute faster than mine, so that wasn't her either. I don't recall now that she had a HALF tag on her back -- maybe she was a full marathoner who bailed, but I thought the website said if that happened they'd just convert the result. So I don't know what's up with whoever she was.
It was in the 50s at race start, which was just about right. It was a 7:00 a.m. gun though, which I did not particularly like -- you know that getting out of bed in the morning at the crack of dawn is not my favorite thing. Portapotty lines were long, so I took a chance on the next-door Amtrak station and discovered that the indoor facilities (particularly the upstairs option) had not been widely discovered. Yay! Even so, I did not get to the starting area until about 5 minutes to the gun, and it was tightly packed so that I could not make my way very far up and was stuck toward the back with people who were definitely not going to be running under 1:40. Well, there wasn't any risk of actually winning this race so it would have to do. The throng around me ensured I didn't take off like a shot, which was a benefit of being crammed so far back -- I did mile #1 in 7:28. I settled in.
There was no wind to speak of, and the temperature was comfortable. I was comfortable. I aimed to keep my miles at least 7:20, as long as it didn't start to feel like a stretch, and it did not. I let my legs do what they wanted as long as they did not push to a point where it felt like I was reaching. Even on the uphill mile (~7), I felt pretty strong. In fact, up until around mile 8 or 9, I was feeling better and better as I went on. After 9 or so, my legs started to feel kind of robotic/wooden, but they still responded to my pace orders -- it was a race, I told them, so race. Miles 10, 11, 12, and 13 were all 7:10 or better, with mile 13 being the best: 6:56. In those last three, I made use of that long downhill and then the downhill in the last half mile or so, and told myself again that this is a race; if your legs can do it, make them do it. And so they did.
I kept an eye on who was ahead of me, and if I saw a woman wearing a "HALF" tag on her back (to distinguish us from the 26.2 runners, they made us wear bibs on our backs), I made a point of reeling her in. There was a woman in the last mile that I wasn't sure I was going to get, but going up the hill on King Street on the way toward the finish, I caught her after all, which was satisfying. I aimed at the next woman ahead of me, but I ran out of real estate before I could get her.1 I glanced up at the race clock over the finish line as I crossed -- it was 1:36:XX.
I thought, "Well, good enough" though a teeeny bit disappointed it wasn't a liiiiittle bit faster -- and then, after stopping, I stopped my Garmin and looked down at it.
It said 1:35:05. What? OH RIGHT -- being so far back at the start, I hit the start mat a minute after the gun. So, OK, I was a liiiittle bit faster. I was pretty excited about that, even exulting "YES!" out loud.
My official time for the race is 1:35:04. It is about 30 seconds slower than my PR. It was good for 4th in my age group; I was 12th female; and 45th out of 891 half-marathon finishers. Frankly, after that 10-miler in Lewes, I needed this shot of confidence.
The only disappointing thing about the day was the fat-free chocolate milk they had at the post-race tent. Come on! Who wants that after finishing a race?! Give me at least 1%!!!
-----------------------------------------
1After looking at the results, it seems not to matter: she does not seem to appear in the half-marathon results, as the person that is right before me (4 seconds faster) is a 42 year old man and his race photos indicate that he is not the person who I saw just ahead of me! The next faster woman than me had a gun time almost a whole minute faster than mine, so that wasn't her either. I don't recall now that she had a HALF tag on her back -- maybe she was a full marathoner who bailed, but I thought the website said if that happened they'd just convert the result. So I don't know what's up with whoever she was.
The early birds
Morning is the red-winged blackbird's time, its multi-tone call evoking the Iowa countryside ripening green and gold in sultry summer months. Two Canada geese stand ankle-deep in marshy water, keeping dutiful eye on five fluffy, camouflaged goslings learning how to live geese lives. Ducks, mallards and one all dark, a stranger, float on the glassy reservoir, sometimes rocking forward tail over beak to snap up tasty underwater morsels. Mourning doves whuff disconsolately away as I approach, and commoners - robins and swallows mostly - take flight to avoid me as well. As I round a bend in the path, my eye is suddenly caught by the jewel of the morning run, standing at the rim of the small lake: a blue heron, tall and haughty, unconcerned as I slow to stare at its unexpected, regal presence.
Morning runs used to be a chore, uncomfortable and dragging, but in recent weeks they have been among some of the most satisfying and engaging miles I've done - cool temperatures, good legs, and seldom do I share the reservoir path with anything but the (literal) early birds.
Sunday, May 8, 2016
Week # 19 -- life gets in the way
Summary for week ending Sunday, May 8, 2016:
Number of workouts: 4
Total miles run: 38.40
Average miles per run: 9.60
Miles in May: 57.47
Miles in 2016: 860.35
After a day of resting on Monday, Tuesday's run felt much better, and not just because the weather was outstanding. Legs recovered, abdomen not an issue. Did almost 10 miles, with the miles seeming to fly right on by because it wasn't same-old, same-old, but on familiar and beloved hometown sidewalks and a little bit through Hickory Hill Park.
Wednesday, I hoped to do the 22-miler. However, I was back to feeling like total crud and it did not happen. I only got halfway (11.21 mi), and I think I was lucky to even get that far. Just shy of mile 10, I was at the corner of Scott and First, and about to head down Scott which would have committed me to at least 4 more miles. Sometimes, I do the thing where I go past a point of no return to make myself do what I have to do, but I got only a few meters past the intersection when my legs just stopped. My brain said "Do not do it. You will regret it. You will end up walking a long way." For once, I heeded the warning -- it was not just laziness. I turned around and went home, struggling a bit even to do that last mile-ish. I was disgusted with how bad I felt, and anxious about how I was not going to get a 22-er in unless I did an extra 9 after the race on Sunday.
I did happen to run into an old friend from high school while heading through Hickory Hill Park around mile 8. She was out doing some hiking and hunting for mushrooms with her youngest son. This was after I had stopped at home to get water and a gel and had considered bailing then, but knew I had to try to get a little more in. I was feeling wretched, and seeing my friend was the only good thing about that whole morning.
I had intended to run some distance on Thursday, but this is where life intruded; other situations came up involving my family, so I did not get out, instead spending it in doctor's offices and the U of I hospital. Too bad on a number of levels: the weather was the perfect spring weather we've largely missed out on this year. (And back in Delaware, it was raining all week.)
Friday I flew back east, and because of the rain, PHL was all messed up and my afternoon flight from ATL was very delayed and I didn't get home until quite late. No running.
I got a few easy miles in on Saturday, and while I did not run nearly as much as I had hoped to while in Iowa, I could at least say that my legs ought to be pretty nicely rested for the half-marathon. The half went quite well -- better than I'd anticipated -- and I will summarize that in the next post.
Number of workouts: 4
Total miles run: 38.40
Average miles per run: 9.60
Miles in May: 57.47
Miles in 2016: 860.35
After a day of resting on Monday, Tuesday's run felt much better, and not just because the weather was outstanding. Legs recovered, abdomen not an issue. Did almost 10 miles, with the miles seeming to fly right on by because it wasn't same-old, same-old, but on familiar and beloved hometown sidewalks and a little bit through Hickory Hill Park.
Wednesday, I hoped to do the 22-miler. However, I was back to feeling like total crud and it did not happen. I only got halfway (11.21 mi), and I think I was lucky to even get that far. Just shy of mile 10, I was at the corner of Scott and First, and about to head down Scott which would have committed me to at least 4 more miles. Sometimes, I do the thing where I go past a point of no return to make myself do what I have to do, but I got only a few meters past the intersection when my legs just stopped. My brain said "Do not do it. You will regret it. You will end up walking a long way." For once, I heeded the warning -- it was not just laziness. I turned around and went home, struggling a bit even to do that last mile-ish. I was disgusted with how bad I felt, and anxious about how I was not going to get a 22-er in unless I did an extra 9 after the race on Sunday.
I did happen to run into an old friend from high school while heading through Hickory Hill Park around mile 8. She was out doing some hiking and hunting for mushrooms with her youngest son. This was after I had stopped at home to get water and a gel and had considered bailing then, but knew I had to try to get a little more in. I was feeling wretched, and seeing my friend was the only good thing about that whole morning.
I had intended to run some distance on Thursday, but this is where life intruded; other situations came up involving my family, so I did not get out, instead spending it in doctor's offices and the U of I hospital. Too bad on a number of levels: the weather was the perfect spring weather we've largely missed out on this year. (And back in Delaware, it was raining all week.)
Friday I flew back east, and because of the rain, PHL was all messed up and my afternoon flight from ATL was very delayed and I didn't get home until quite late. No running.
I got a few easy miles in on Saturday, and while I did not run nearly as much as I had hoped to while in Iowa, I could at least say that my legs ought to be pretty nicely rested for the half-marathon. The half went quite well -- better than I'd anticipated -- and I will summarize that in the next post.
Sunday, May 1, 2016
Week #18 -- finishing up out of town
Summary for week ending Sunday, May 1, 2016:
Number of workouts: 5
Total miles run: 46.15
Average miles per run: 9.23
Miles in April: 208.46
Miles in May: 19.07
Miles in 2016: 821.95
Arriving in the Midwest on the last day of May, the weather was vile, pouring rain pretty much non-stop from time of arrival until early evening. I was not going to run in that, as I was too tired from rising at 3 a.m. for a very early flight to even guilt myself into toughing it out. By the time it had eased up, I was full of Chicago-style deep dish from Wig and Pen, so ....
The weather was marginally better Sunday -- I got my workout done in between rainy moments. I did a tough tempo workout on Sunday. Typically my first days of running in Iowa don't feel that good -- not sure why, perhaps mostly a combo of poor eating and poor sleeping over the last couple days. No exception this day, and I made myself run hard even when it wasn't feeling good. 2 mi E + 4(5 min T) + 10 mi E + scheduled 4(5 min T) + 2 mi E. I did the first part OK, though legs were not very responsive -- tempo intervals on the track at my high school and 10 easy miles on the well-known roads of the east side. Very slow and not because I was forcing myself to do 9:00/per, it's just what my legs did. Was feeling the muscles in my lower abdomen start to act up a bit, and when I went back to the track for the 4(5 min T), I got started on the first interval and it was too painful. It didn't ease up and I couldn't make myself run through it, so I bailed on the T and started to jog home. As I jogged, the discomfort cooled it enough for me to keep out for a few more slow miles, and I finished up with 19 on the day. Not especially happy about the abdomen muscle situation, not too happy that I didn't get those last T sessions in, but it was solid mileage and as good as it was going to get, so I will have to be satisfied with that.
The weather is meant to improve over the rest of the week, so at least that part should be easier. Going to have to take a day to let these lower abdomen muscles cool it. Because I have a half-marathon next Sunday, I'm going to switch Q workouts for the week -- do the longy-long on Wednesday I think, and then use the race as the long T workout.
Number of workouts: 5
Total miles run: 46.15
Average miles per run: 9.23
Miles in April: 208.46
Miles in May: 19.07
Miles in 2016: 821.95
Arriving in the Midwest on the last day of May, the weather was vile, pouring rain pretty much non-stop from time of arrival until early evening. I was not going to run in that, as I was too tired from rising at 3 a.m. for a very early flight to even guilt myself into toughing it out. By the time it had eased up, I was full of Chicago-style deep dish from Wig and Pen, so ....
The weather was marginally better Sunday -- I got my workout done in between rainy moments. I did a tough tempo workout on Sunday. Typically my first days of running in Iowa don't feel that good -- not sure why, perhaps mostly a combo of poor eating and poor sleeping over the last couple days. No exception this day, and I made myself run hard even when it wasn't feeling good. 2 mi E + 4(5 min T) + 10 mi E + scheduled 4(5 min T) + 2 mi E. I did the first part OK, though legs were not very responsive -- tempo intervals on the track at my high school and 10 easy miles on the well-known roads of the east side. Very slow and not because I was forcing myself to do 9:00/per, it's just what my legs did. Was feeling the muscles in my lower abdomen start to act up a bit, and when I went back to the track for the 4(5 min T), I got started on the first interval and it was too painful. It didn't ease up and I couldn't make myself run through it, so I bailed on the T and started to jog home. As I jogged, the discomfort cooled it enough for me to keep out for a few more slow miles, and I finished up with 19 on the day. Not especially happy about the abdomen muscle situation, not too happy that I didn't get those last T sessions in, but it was solid mileage and as good as it was going to get, so I will have to be satisfied with that.
The weather is meant to improve over the rest of the week, so at least that part should be easier. Going to have to take a day to let these lower abdomen muscles cool it. Because I have a half-marathon next Sunday, I'm going to switch Q workouts for the week -- do the longy-long on Wednesday I think, and then use the race as the long T workout.
Thursday, April 28, 2016
No Red Shoe race for Crusher
After last night's tempo workout (which went well overall), I've decided that I don't want to race a half-marathon this coming Monday in Iowa City, not when I have another already scheduled and paid for on the 8th. I am not backing anything off this week in anticipation of running a race, so I would be even less fresh than I was for the 10-miler last week (where I called the race the week's quality tempo workout, and if you tally up the race, the 20 miles the following day, and the miles and hard workout I've been getting in this week, my legs will have done a lot of work in the last seven days). If I felt anything like I felt in the 10-miler, even if I paced the half a little better I probably still wouldn't run better than 1:40, and that wouldn't make me very happy. I don't feel like paying for a 13-mile tempo workout. I'll get my scheduled 20-mile mix of miles and tempo intervals done on my own and cool it a bit during the following week so I can go into the already-paid-for half-marathon in Wilmington on legs that have taken a little easier.
Another reason I'm backing off on doing this race is that I think I'm starting to feel the accumulating miles. These weeks are the biggest and toughest of the training schedule, and during them I'm asking a lot out of my body, which I have already asked a lot out of. Since I started running marathons, I have never run this much in a four-month stretch (on pace for a theoretical ~2400 miles this year, a lot more than I've ever done) and I feel like I'm running on the edge of doing too much, but haven't gone over that line yet. Maybe that's normal when you bump up weekly mileage long-term for the first time, but I'm the type to worry every day that tomorrow's long miles or interval workout will be what pushes me over the edge and I'm hurt and won't be able to do Vermont City. I'm pretty thrilled that so far I've made it without anything that's hindering me from running, but any little twinge anywhere and I'm chewing my fingernails hoping it doesn't last or turn into worse. I think I'm going to need a long recovery after the VCM. Just have a month left of hard work, and then I can take a vacation from a tough schedule.
Another reason I'm backing off on doing this race is that I think I'm starting to feel the accumulating miles. These weeks are the biggest and toughest of the training schedule, and during them I'm asking a lot out of my body, which I have already asked a lot out of. Since I started running marathons, I have never run this much in a four-month stretch (on pace for a theoretical ~2400 miles this year, a lot more than I've ever done) and I feel like I'm running on the edge of doing too much, but haven't gone over that line yet. Maybe that's normal when you bump up weekly mileage long-term for the first time, but I'm the type to worry every day that tomorrow's long miles or interval workout will be what pushes me over the edge and I'm hurt and won't be able to do Vermont City. I'm pretty thrilled that so far I've made it without anything that's hindering me from running, but any little twinge anywhere and I'm chewing my fingernails hoping it doesn't last or turn into worse. I think I'm going to need a long recovery after the VCM. Just have a month left of hard work, and then I can take a vacation from a tough schedule.
Sunday, April 24, 2016
Week #17: toughen up
Summary for week ending Sunday, April 24, 2016:
Number of workouts: 6
Total miles run: 54.27
Average miles per run: 9.05
Miles in April: 181.38
Miles in 2016: 775.80
With the race on Saturday, I moved my miles around so that the quality tempo would be the race and the easy, general mileage would be the rest of the week. Tuesday I doubled and went outside for the AM run rather than hitting the treadmill. It was around 6:30 and absolute perfection: in the mid-40s, no wind, sun on its way up. I felt outstanding, like I could have gone all day. I felt I loved, loved running. Alas, I did have to call it quits after an hour and go to work.
The rest of the weekday running was fine. I took Friday as a rest day for a couple reasons and ran the Tommy 10-miler on Saturday.
I still had a long run to get in on Sunday. Because the Flyers unexpectedly won Game 5, there was a Game 6, and they scheduled it for noon today. Noon!? When was I supposed to get 20+ in if the game was in the damn dead middle of the day??
I guess in the morning; don't like to have 20+ miles hanging over my head all day and couldn't risk a mega-overtime game eating up the hours.1 I had kind of hoped to sleep in a little bit after not getting the best sleep Friday night, but that went out the window. I got up at 7 and felt exactly like I was having to go to work, going down to eat breakfast and then back up to get dressed and head out the door by 8. At least it was a very nice early-ish Sunday -- why couldn't it have been this nice yesterday? Mid-40s and sun, a little wind but nothing bad. I thought I'd try to get a little hilly running done today as I have not done much really hilly mileage lately and Vermont City is getting closer. I did a couple loops around Paper Mill Park to get my legs going -- they were not especially interested, unfortunately -- and then headed up Paper Mill Road. After that couple laps, I felt ok. I wouldn't say good, but not bad. I meandered up and down the long hills of Paper Mill Road and then around down Possum Hollow Road, which generally feels cool and serene as it is an off-the-main-drag road, but on my way back up I started to feel yesterday's race. I headed back down Paper Mill Road and when I finally made it back to the park, I decided that was going to be all the hill running I would do today. I'd kind of thought I might do my second session up Polly Drummond but the very thought made me sore and tired. I was at about 10K when I paused at my car. I had a gel and set about getting in a few more miles. I decided to take the rest of the run in 3-4 mile segments, which would make the next 16 miles manageable, if perhaps a little dull looping around and around at the park. Wouldn't be the first time I killed high miles there (and won't be the last). The weather was fine, it was early enough that the park wasn't busy, and I ate up the distance.
Water and Gatorade at 10 miles; I thought then that the whole 22 on the schedule might be a reach. I was starting to hurt. Not a real hurt yet, but a creeping heaviness in my legs and some tightness in my abdominal muscles. By my next break around 13.5 miles, it was amplifying. Legs starting to hurt, lower back getting in on the action, but I was still running ok. Easy pace, just a little robotic and heavy. I stopped again just short of 17 miles, and I made my decision. 20 would be adequate. If I got to 20 and felt I could eke out another 2.5 laps for the whole 22, then that would be gravy, but if I got to 20 and was too hurty to get there, then that was fine.
It had warmed up some, but not awfully. I changed to short sleeves after keeping comfortable in long sleeves for a while, and it's too bad that my legs were so beat up, because it would have been just the best day for a 22er. I'm sort of surprised by how fast the second 10 miles seemed to go by because usually when I'm hurting the distance just totally drags. I got the Iowa City High fight song stuck in my head after 15 miles, which amused me but actually worked quite well with the cadence of my pace. I thank the weather for being so pleasant; I think that's what helped it pass by. I'm not sorry I jammed the tempo and the long run right up against each other. I knew what I was getting into. I didn't go to the well yesterday and I got good time out of my feet and legs today.
Taking my usual Monday rest day and I will see about recovery. Easy miles Tuesday, possibly Wednesday; if I'm feeling ok Wednesday I will do the week's first quality workout (tempos) then, otherwise Thursday. I will decide at that point if I'm going to feel good enough to do the half-marathon in Iowa City on Sunday as another quality tempo workout. No big deal if not, but I still have a tough workout to do even if I don't race.
Vermont City is five weeks away. I still have some work to get done.
Number of workouts: 6
Total miles run: 54.27
Average miles per run: 9.05
Miles in April: 181.38
Miles in 2016: 775.80
With the race on Saturday, I moved my miles around so that the quality tempo would be the race and the easy, general mileage would be the rest of the week. Tuesday I doubled and went outside for the AM run rather than hitting the treadmill. It was around 6:30 and absolute perfection: in the mid-40s, no wind, sun on its way up. I felt outstanding, like I could have gone all day. I felt I loved, loved running. Alas, I did have to call it quits after an hour and go to work.
The rest of the weekday running was fine. I took Friday as a rest day for a couple reasons and ran the Tommy 10-miler on Saturday.
I still had a long run to get in on Sunday. Because the Flyers unexpectedly won Game 5, there was a Game 6, and they scheduled it for noon today. Noon!? When was I supposed to get 20+ in if the game was in the damn dead middle of the day??
I guess in the morning; don't like to have 20+ miles hanging over my head all day and couldn't risk a mega-overtime game eating up the hours.1 I had kind of hoped to sleep in a little bit after not getting the best sleep Friday night, but that went out the window. I got up at 7 and felt exactly like I was having to go to work, going down to eat breakfast and then back up to get dressed and head out the door by 8. At least it was a very nice early-ish Sunday -- why couldn't it have been this nice yesterday? Mid-40s and sun, a little wind but nothing bad. I thought I'd try to get a little hilly running done today as I have not done much really hilly mileage lately and Vermont City is getting closer. I did a couple loops around Paper Mill Park to get my legs going -- they were not especially interested, unfortunately -- and then headed up Paper Mill Road. After that couple laps, I felt ok. I wouldn't say good, but not bad. I meandered up and down the long hills of Paper Mill Road and then around down Possum Hollow Road, which generally feels cool and serene as it is an off-the-main-drag road, but on my way back up I started to feel yesterday's race. I headed back down Paper Mill Road and when I finally made it back to the park, I decided that was going to be all the hill running I would do today. I'd kind of thought I might do my second session up Polly Drummond but the very thought made me sore and tired. I was at about 10K when I paused at my car. I had a gel and set about getting in a few more miles. I decided to take the rest of the run in 3-4 mile segments, which would make the next 16 miles manageable, if perhaps a little dull looping around and around at the park. Wouldn't be the first time I killed high miles there (and won't be the last). The weather was fine, it was early enough that the park wasn't busy, and I ate up the distance.
Water and Gatorade at 10 miles; I thought then that the whole 22 on the schedule might be a reach. I was starting to hurt. Not a real hurt yet, but a creeping heaviness in my legs and some tightness in my abdominal muscles. By my next break around 13.5 miles, it was amplifying. Legs starting to hurt, lower back getting in on the action, but I was still running ok. Easy pace, just a little robotic and heavy. I stopped again just short of 17 miles, and I made my decision. 20 would be adequate. If I got to 20 and felt I could eke out another 2.5 laps for the whole 22, then that would be gravy, but if I got to 20 and was too hurty to get there, then that was fine.
It had warmed up some, but not awfully. I changed to short sleeves after keeping comfortable in long sleeves for a while, and it's too bad that my legs were so beat up, because it would have been just the best day for a 22er. I'm sort of surprised by how fast the second 10 miles seemed to go by because usually when I'm hurting the distance just totally drags. I got the Iowa City High fight song stuck in my head after 15 miles, which amused me but actually worked quite well with the cadence of my pace. I thank the weather for being so pleasant; I think that's what helped it pass by. I'm not sorry I jammed the tempo and the long run right up against each other. I knew what I was getting into. I didn't go to the well yesterday and I got good time out of my feet and legs today.
Taking my usual Monday rest day and I will see about recovery. Easy miles Tuesday, possibly Wednesday; if I'm feeling ok Wednesday I will do the week's first quality workout (tempos) then, otherwise Thursday. I will decide at that point if I'm going to feel good enough to do the half-marathon in Iowa City on Sunday as another quality tempo workout. No big deal if not, but I still have a tough workout to do even if I don't race.
Vermont City is five weeks away. I still have some work to get done.
Saturday, April 23, 2016
Tommy Ten-Miler wrap-up
I did not run on Friday, having to get up earlier than usual to go to work and traveling to Lewes / Rehoboth Beach in the afternoon. I would have liked to get a few miles in, just to tally up a few more miles on the week, but it wouldn't hurt my legs to take another rest day this week and sometimes life just twists a little bit and it happens. The weather wasn't very nice in (s)lower Delaware Friday afternoon; rain, off and on heavy. Forecast implied it might be the same Saturday morning, which was not appealing, but I'd deal with it.
Had some difficulty finding somewhere suitable to eat. I would have been happy at any old Italian place just to have a plate of spaghetti, but wanted B to have better options too. We ended up at a restaurant on the boardwalk in Rehoboth Beach, one I will leave nameless because I don't want to give it a bad name just because my experience wasn't exceptional -- it wasn't really their fault, if I hadn't been looking for a specific type of fare it would have been just fine. I wanted the chicken parm with its pile of noodles, but it turned out (after we had settled in at the bar and ordered) that they were out of that and it was off the menu for the night. There was only one other noodle-based dish -- a mac and cheese that was all seafoody, so it wasn't really an option. I ended up with a grilled chicken sandwich and my only carb-loading for the night consisted of the bun and fries (do they really even count?). I tried to tell myself if didn't matter if my calorie store really came from noodles or something else, I wouldn't be depleting my stores over only ten miles anyway, right? I wasn't getting ready for a marathon. It's just tradition; I pretty much never have anything but pasta the night before the race.
I am not sure it was enough calories, whatever their source. I had a granola bar in the hotel while watching the Flyers, just to try to top off the tank, but in the morning I felt very hungry. I was also very tired. I had extreme difficulty getting to sleep, for a variety of reasons, top among them being a jazzed-up excitement because the Flyers had won game 5 when they had absolutely zero business winning that game by all statistics and reasonable expectations; add to that the usual pre-race brain activity (where I pretty unwillingly fantasize the race outcome to both extremes, I'm either dominating in super-PR time or I am crashing and burning all to hell) and some snoring by B, it was a couple hours before my brain cooled it enough to drop off. I tried to hydrate before going to bed (but not so much that I would spend all night dreaming about having to pee, and then waking numerous times to actually pee), but the few times that I did wake, I always felt very thirsty. I got up at 6:30, feeling a little sandy-headed, hungry, and thirsty.
Breakfast in the hotel: a bowl of oatmeal and a piece of wheat toast and peanut butter. Nothing so different from what I eat at home pre-long run, just different oatmeal. Still felt a little hungry but was afraid of eating too much and it sitting in my stomach when the race started in about an hour and a half. Tried to drink more, but not so much that I would think I needed to pee every five minutes once we got to the starting area in Lewes. Pretty sure I was overthinking everything, it was just ten miles, after all, not a marathon.
It was not raining when we left for the start, around 7:45. It was heavily overcast, warmish and very humid after a night of rain. The radar suggested it might rain during the race, and I debated wearing a cap because I hate to have rain in my face -- but it was so warm I hesitated, as a hat would only amplify the warmth. Once again, probably overthinking it; it was only ten miles, so I decided against the hat and would just take the rain in my face if it happened. It wouldn't be for three hours like it was in Boston, so it would be ok enough. (It ended up not raining, but I thought during the race that a little rain might feel good.)
I only felt like I had to use the porta-potty once while we were there, and that was mainly because I figured I should before the start more than any actual pressing need. This was maybe a warning sign, and I sipped water while waiting around for the start.
It was a little chaotic around the starting line, and there was a delay with starting for one reason or another; there was a "kiddy K" that we had to wait for as well. I had already said goodbye to B and was standing in the midst of the crowd, and had no water with me, and the longer we had to wait around, the more I regretted that. I had taken a gel around 8:20, anticipating the 8:30 start, but it wasn't until almost 8:45 that we finally got going. Nothing was timed right for me, and when I started, I was thirsty and I don't know if the gel was doing any good by then.
I had to struggle to get around slower runners in the first 100-200m, stepping alongside the road into some muddy grass, and my legs immediately alarmed me; no spring in them, my quads a little stiff. I tried to set aside any worry about that, as it often takes me a mile or two to get into the rhythm and feel comfortable, but by 1-2 miles, I was not feeling much better. I ticked off a couple miles around 7:10, and knew then that it was too fast for how not-good I felt, but every time I tried to back off on the pace, I'd look down a little bit later and I'd be back around 7:15 or so. I just couldn't manage to keep myself under control, which was frustrating. So I decided to just go with it, if I blew up later it wouldn't be the worst thing. There would be some solid tempo miles out of it no matter what happened.
There wasn't water until mile 2, and the swallow I got from the cup wasn't enough. Not another stop until a little before mile 4 or so. Another swallow that wasn't quite enough. Just after mile 4, the flat, paved path we were running on ended and became a flat, packed-dirt path under trees. Instantly I felt slower without the spring-back of the harder pavement. There was no one around me. I had been running quite alone since before mile 2, when I passed two guys going up over the bridge across a narrow canal. I had been able to see a guy and a girl maybe 100-150m ahead of me for a while, and they were still on up ahead, but too far to even pretend to keep contact with and there was no one anywhere close behind me. Having to do all the mental work alone on an unfamiliar course while feeling less than good is tough. Between mile 4 and 5, I slowed way down. After averaging around 7:11 for the first 4 miles, my split for mile 5 was 7:27. This is partly due to the canopy of trees overhead, which confuses the Garmin a bit, but mostly due to my pace falling off. It was disappointing, but though I tried to surge a little and pick pace back up, I now had the opposite problem as I did earlier: instead of not being able to hold down I now could hold up.
A while after mile 4, the leaders started filtering back past me. They were very spread out. Two women were ahead of me; first place was waaay out in front of me, second place (the girl I could see) maybe 1, 1:30 ahead? After I went around the turnaround (no timing mat, which surprised me), I saw just how alone I was. The next runners were a couple/three minutes back. For a while though, I felt a little refreshed and faster (even though I was slowing) because I was passing a bunch of people going the other way. I was glad to leave the tree cover and leave the dirt path and get back to the asphalt, because I would feel better without the ground absorbing my footfalls and the Garmin would be more accurate. Unfortunately, even with these two factors, I was not much faster, in fact I stayed around 7:30 for the next 3 miles or so.
(I had doubts that a gel would do me much good, but I took one anyway, between mile 6 and 7 which was where this photo was taken.)
I started to think I was gaining ground on the second place woman, but she was still quite a good distance ahead of me. It just seemed the distance narrowed, but I was going to run out of real estate before I caught her. If it had been a half marathon, I might have (assuming I didn't crater even more during that further three miles). She ended up about 45 seconds ahead. I squeezed my pace a bit during the last mile, managing 7:20, but it wasn't good enough to catch her and it wasn't enough to really bring my time to anything I would say I was happy with. I am just glad that I could squeeze that little more out of myself. I was pretty well cooked, thirsty and hot and very swampy sweaty. The finish is a straightaway down a flat road, which I sailed down completely alone. B was near the finish, snapping pics. Two girls at the finish line stretched a banner across for me to run through. I was briefly confused, because I knew I was in third place -- was there someone finishing first for some other division somehow right behind me?? -- but no, they were stretching it for me. I thought that was a little odd and maybe even patronizing for third place, but I ran through it and felt a little fraudulent. I should only be breaking a banner for first place.
But I was first place in my division, I guess, so perhaps not such a fraud (but still, odd). They gave awards for first overall M and F, and everyone thereafter would be age-groupers. Frankly I'd rather be awarded third overall than 1st in F30-39, but I'll take the medal and enjoy seeing my name in the leaderboard in third place.
As you see, my chip time was 1:14:29. 3rd female overall, 1st F30-39, and 10th overall out of 120 finishers. Not my best, not my worst 10-mile. I wish I'd been able to pace it better (I don't know what my problem was, there) and I wish I'd felt better but I think things just didn't come together on a warm and humid day. Not too disappointed in the end. I didn't really back off for this race (unless you count taking Friday off) so wasn't exactly fresh for it, and if nothing else, I got in a pretty decent tempo workout. And I got to see the ocean at Cape Henlopen afterward.
I want to mention that the volunteers on the course were great. I want to thank them for spending their Saturday morning holding up traffic for me (and the rest of us) as I crossed intersections and for cheering me on -- their enthusiasm was almost all that stood between it feeling like a real race rather than a long tempo workout all on my own on a new path. Thanks for saying I looked great/strong/amazing, because I sure didn't feel great/strong/amazing! If I didn't intend on having terribly dead legs next April from running my best Boston ever, I'd come back to defend my third place finish.
Had some difficulty finding somewhere suitable to eat. I would have been happy at any old Italian place just to have a plate of spaghetti, but wanted B to have better options too. We ended up at a restaurant on the boardwalk in Rehoboth Beach, one I will leave nameless because I don't want to give it a bad name just because my experience wasn't exceptional -- it wasn't really their fault, if I hadn't been looking for a specific type of fare it would have been just fine. I wanted the chicken parm with its pile of noodles, but it turned out (after we had settled in at the bar and ordered) that they were out of that and it was off the menu for the night. There was only one other noodle-based dish -- a mac and cheese that was all seafoody, so it wasn't really an option. I ended up with a grilled chicken sandwich and my only carb-loading for the night consisted of the bun and fries (do they really even count?). I tried to tell myself if didn't matter if my calorie store really came from noodles or something else, I wouldn't be depleting my stores over only ten miles anyway, right? I wasn't getting ready for a marathon. It's just tradition; I pretty much never have anything but pasta the night before the race.
I am not sure it was enough calories, whatever their source. I had a granola bar in the hotel while watching the Flyers, just to try to top off the tank, but in the morning I felt very hungry. I was also very tired. I had extreme difficulty getting to sleep, for a variety of reasons, top among them being a jazzed-up excitement because the Flyers had won game 5 when they had absolutely zero business winning that game by all statistics and reasonable expectations; add to that the usual pre-race brain activity (where I pretty unwillingly fantasize the race outcome to both extremes, I'm either dominating in super-PR time or I am crashing and burning all to hell) and some snoring by B, it was a couple hours before my brain cooled it enough to drop off. I tried to hydrate before going to bed (but not so much that I would spend all night dreaming about having to pee, and then waking numerous times to actually pee), but the few times that I did wake, I always felt very thirsty. I got up at 6:30, feeling a little sandy-headed, hungry, and thirsty.
Breakfast in the hotel: a bowl of oatmeal and a piece of wheat toast and peanut butter. Nothing so different from what I eat at home pre-long run, just different oatmeal. Still felt a little hungry but was afraid of eating too much and it sitting in my stomach when the race started in about an hour and a half. Tried to drink more, but not so much that I would think I needed to pee every five minutes once we got to the starting area in Lewes. Pretty sure I was overthinking everything, it was just ten miles, after all, not a marathon.
It was not raining when we left for the start, around 7:45. It was heavily overcast, warmish and very humid after a night of rain. The radar suggested it might rain during the race, and I debated wearing a cap because I hate to have rain in my face -- but it was so warm I hesitated, as a hat would only amplify the warmth. Once again, probably overthinking it; it was only ten miles, so I decided against the hat and would just take the rain in my face if it happened. It wouldn't be for three hours like it was in Boston, so it would be ok enough. (It ended up not raining, but I thought during the race that a little rain might feel good.)
I only felt like I had to use the porta-potty once while we were there, and that was mainly because I figured I should before the start more than any actual pressing need. This was maybe a warning sign, and I sipped water while waiting around for the start.
It was a little chaotic around the starting line, and there was a delay with starting for one reason or another; there was a "kiddy K" that we had to wait for as well. I had already said goodbye to B and was standing in the midst of the crowd, and had no water with me, and the longer we had to wait around, the more I regretted that. I had taken a gel around 8:20, anticipating the 8:30 start, but it wasn't until almost 8:45 that we finally got going. Nothing was timed right for me, and when I started, I was thirsty and I don't know if the gel was doing any good by then.
I had to struggle to get around slower runners in the first 100-200m, stepping alongside the road into some muddy grass, and my legs immediately alarmed me; no spring in them, my quads a little stiff. I tried to set aside any worry about that, as it often takes me a mile or two to get into the rhythm and feel comfortable, but by 1-2 miles, I was not feeling much better. I ticked off a couple miles around 7:10, and knew then that it was too fast for how not-good I felt, but every time I tried to back off on the pace, I'd look down a little bit later and I'd be back around 7:15 or so. I just couldn't manage to keep myself under control, which was frustrating. So I decided to just go with it, if I blew up later it wouldn't be the worst thing. There would be some solid tempo miles out of it no matter what happened.
There wasn't water until mile 2, and the swallow I got from the cup wasn't enough. Not another stop until a little before mile 4 or so. Another swallow that wasn't quite enough. Just after mile 4, the flat, paved path we were running on ended and became a flat, packed-dirt path under trees. Instantly I felt slower without the spring-back of the harder pavement. There was no one around me. I had been running quite alone since before mile 2, when I passed two guys going up over the bridge across a narrow canal. I had been able to see a guy and a girl maybe 100-150m ahead of me for a while, and they were still on up ahead, but too far to even pretend to keep contact with and there was no one anywhere close behind me. Having to do all the mental work alone on an unfamiliar course while feeling less than good is tough. Between mile 4 and 5, I slowed way down. After averaging around 7:11 for the first 4 miles, my split for mile 5 was 7:27. This is partly due to the canopy of trees overhead, which confuses the Garmin a bit, but mostly due to my pace falling off. It was disappointing, but though I tried to surge a little and pick pace back up, I now had the opposite problem as I did earlier: instead of not being able to hold down I now could hold up.
A while after mile 4, the leaders started filtering back past me. They were very spread out. Two women were ahead of me; first place was waaay out in front of me, second place (the girl I could see) maybe 1, 1:30 ahead? After I went around the turnaround (no timing mat, which surprised me), I saw just how alone I was. The next runners were a couple/three minutes back. For a while though, I felt a little refreshed and faster (even though I was slowing) because I was passing a bunch of people going the other way. I was glad to leave the tree cover and leave the dirt path and get back to the asphalt, because I would feel better without the ground absorbing my footfalls and the Garmin would be more accurate. Unfortunately, even with these two factors, I was not much faster, in fact I stayed around 7:30 for the next 3 miles or so.
I started to think I was gaining ground on the second place woman, but she was still quite a good distance ahead of me. It just seemed the distance narrowed, but I was going to run out of real estate before I caught her. If it had been a half marathon, I might have (assuming I didn't crater even more during that further three miles). She ended up about 45 seconds ahead. I squeezed my pace a bit during the last mile, managing 7:20, but it wasn't good enough to catch her and it wasn't enough to really bring my time to anything I would say I was happy with. I am just glad that I could squeeze that little more out of myself. I was pretty well cooked, thirsty and hot and very swampy sweaty. The finish is a straightaway down a flat road, which I sailed down completely alone. B was near the finish, snapping pics. Two girls at the finish line stretched a banner across for me to run through. I was briefly confused, because I knew I was in third place -- was there someone finishing first for some other division somehow right behind me?? -- but no, they were stretching it for me. I thought that was a little odd and maybe even patronizing for third place, but I ran through it and felt a little fraudulent. I should only be breaking a banner for first place.
But I was first place in my division, I guess, so perhaps not such a fraud (but still, odd). They gave awards for first overall M and F, and everyone thereafter would be age-groupers. Frankly I'd rather be awarded third overall than 1st in F30-39, but I'll take the medal and enjoy seeing my name in the leaderboard in third place.
As you see, my chip time was 1:14:29. 3rd female overall, 1st F30-39, and 10th overall out of 120 finishers. Not my best, not my worst 10-mile. I wish I'd been able to pace it better (I don't know what my problem was, there) and I wish I'd felt better but I think things just didn't come together on a warm and humid day. Not too disappointed in the end. I didn't really back off for this race (unless you count taking Friday off) so wasn't exactly fresh for it, and if nothing else, I got in a pretty decent tempo workout. And I got to see the ocean at Cape Henlopen afterward.
I want to mention that the volunteers on the course were great. I want to thank them for spending their Saturday morning holding up traffic for me (and the rest of us) as I crossed intersections and for cheering me on -- their enthusiasm was almost all that stood between it feeling like a real race rather than a long tempo workout all on my own on a new path. Thanks for saying I looked great/strong/amazing, because I sure didn't feel great/strong/amazing! If I didn't intend on having terribly dead legs next April from running my best Boston ever, I'd come back to defend my third place finish.
Wednesday, April 20, 2016
Week #16: keep going
Summary for week ending Sunday, April 17, 2016:
Number of workouts: 6
Total miles run: 51.48
Average miles per run: 8.58
Miles in April: 127.11
Miles in 2016: 721.53
Mixed running on trails and paved paths. Managed not to fall again on the trails (though had a close call on Friday), leg though scraped up did not bruise as badly as when I fell in February so is not as uncomfortable. Weather very much improved over the week, warming to the 60s and 70s. This did bring out a lot more people to have to run around but I'm feeling magnanimous so won't kvetch (too much) about them walking three across, forcing me to step off into grass. (How can even two people manage to take up the entire width of the path?!) Satisfying tempo workout on Thursday (2 mi E + 3(10 min T) + 2 mi E where my legs felt better with each T segment -- the new normal seems to be that it takes me a few miles to really feel good and in the groove. The T didn't feel quite as free as on Sunday but not a reach to keep appropriate effort. Very glad I decided not to do the trail race on Saturday as that Thursday workout left my legs tired and Saturday morning's easy run was a drag.
Long run on Sunday ended up being 17 instead of 19 with 12 at MP rather than 15. Discovered a new place for flat long running: the Michael Castle Trail along the C&D Canal. It was very sunny and warmish -- in the 60s. Starting at Biddle Point, I ran easy east toward Delaware City until the trail ends (for now -- it's clear they are working on extending it all the way to Delaware City), about 1.8 miles, then turned back and picked up pace while running west past my starting point toward the US13 / DE1 bridges. I thought I'd run that direction for 2 miles and then turn back, stop at the car for water and a gel. That would be around 7 miles, I thought, just about when I like to take my first gel of a long run. It turned out to be too long; I should have stopped for water when I was on my way past the car around 3.5 miles. I had considered it, but didn't want to take a break after having only done about a mile or so at pace, just getting started, preferring to get a little more at pace in before stopping. MP had started out feeling pretty comfortable but by the time I got to the DE1 bridge, it was starting to feel more work-y and I was thirsty. The trail is totally open to the sky, with no cover whatsoever -- at least on the 4-5 mile stretch of it I was on -- except for those brief moments passing under the bridges, which are negligible -- and that was great for the Garmin and being more accurate with apparent pace, but it was not great for physiology. The sun was very warm and took a tough toll, one that I have not experienced yet this year. Because I had never run here before, I was not familiar with the landmarks, so even though it was out-and-back, I did not really have a good sense of how much I still had to run until I made it to the car. It wasn't very enjoyable, but when I saw the beat-up looking dock next to the trailhead, I was elated.
It's so very hard not to guzzle water when you're at such a point. I sucked down a gel and washed it with a few more swallows of water, managing to restrain myself. It felt like enough, and then I started running east again. It was not long before I felt thirsty once more.
The damage had been done. If I had stopped for water at 3.5 mi, it might have mitigated the effects of the sun and heat early, and I might have gotten another couple solid miles at MP in. As it was, it was all I could do to get in 11, and I barely count the 12th because I was fading fast. More liquids, another gel, and I even carried a water bottle with me for the last 3-4 "easy" miles. (Very uncomfortable, very hard not to hammer the whole bottle at once.) Given how awful I felt, I was satisfied enough with what I ended up having done. I had started to feel a little like the way I did in Boston 2014, when I had to drop out: stomach feeling a little queasy, never getting better and even a little worse even after drinking. In the 2014 race, I quit at mile 18; Sunday, I quit at 17. More lessons learned (the hard way, unfortunately): water is more important than getting in time at pace. If I could drink on the fly in training the way I can in a race, it would be easier, but unfortunately, unless B rides a bike right along with me (which he has done a couple times in the past), I'm stuck having to take short breaks. (I won't wear one of those fuel belts with bottles.) Funny how every year, I run in sun and warmth, but the first times of the season often catch me off guard and I don't do it right. A day with weather like Sunday's is deceptive; just standing around, it was pleasant, a nice breeze, even maybe a slight bit cool, but running with no shade was down right hot. 60s and 70s are extremely lovely, but too warm to be "great" for running at elevated efforts over long distances.
07:44.8, 07:42.4, 07:45.6, 07:42.6, 07:42.1, 07:45.5, 07:48.5, 07:45.5, 07:40.4, 07:41.1, 07:49.2, 08:00.7
The trail along the canal is great though -- absolutely sea level with only a little rippling that you barely notice (except when you're exhausted -- somehow even the smallest ups and downs are hard then). There were a lot of people out on bikes enjoying the pretty day, but no one interfered with my running at all, and I only saw two other runners; a handful of walkers, but the majority of users were on bikes. Early in the run, a ship turned into the canal under the DE9 bridge and cruised along parallel to the path. It was the Demeter Leader, and, according to Google, is a vehicles carrier from Panama; myshiptracking.com indicates it docked at Baltimore at 21:37 on Sunday. It made almost no sound as it passed by, pretty much only the whush of the water in its wake. It was amazing that such a gigantic beast of a ship could make less noise going by than a car. It was also a little eerie because there was no sign of people on the ship, so it was just a silent, almost alien-seeming long and huge blue and white box moving by. Other than that, only speedboats and other personal watercraft whizzed by occasionally. Mostly it was quiet but for the sounds of birdlife. Except for feeling pretty cruddy as I went on, I enjoyed it there. It's another place for pace work to keep in my pocket. Closer than the Schuylkill trail and better, actually, because of the openness.
Upcoming week: days of easy mileage and then Saturday morning is the Tommy 10-miler in Lewes. Longest long run on Sunday.
Number of workouts: 6
Total miles run: 51.48
Average miles per run: 8.58
Miles in April: 127.11
Miles in 2016: 721.53
Mixed running on trails and paved paths. Managed not to fall again on the trails (though had a close call on Friday), leg though scraped up did not bruise as badly as when I fell in February so is not as uncomfortable. Weather very much improved over the week, warming to the 60s and 70s. This did bring out a lot more people to have to run around but I'm feeling magnanimous so won't kvetch (too much) about them walking three across, forcing me to step off into grass. (How can even two people manage to take up the entire width of the path?!) Satisfying tempo workout on Thursday (2 mi E + 3(10 min T) + 2 mi E where my legs felt better with each T segment -- the new normal seems to be that it takes me a few miles to really feel good and in the groove. The T didn't feel quite as free as on Sunday but not a reach to keep appropriate effort. Very glad I decided not to do the trail race on Saturday as that Thursday workout left my legs tired and Saturday morning's easy run was a drag.
Long run on Sunday ended up being 17 instead of 19 with 12 at MP rather than 15. Discovered a new place for flat long running: the Michael Castle Trail along the C&D Canal. It was very sunny and warmish -- in the 60s. Starting at Biddle Point, I ran easy east toward Delaware City until the trail ends (for now -- it's clear they are working on extending it all the way to Delaware City), about 1.8 miles, then turned back and picked up pace while running west past my starting point toward the US13 / DE1 bridges. I thought I'd run that direction for 2 miles and then turn back, stop at the car for water and a gel. That would be around 7 miles, I thought, just about when I like to take my first gel of a long run. It turned out to be too long; I should have stopped for water when I was on my way past the car around 3.5 miles. I had considered it, but didn't want to take a break after having only done about a mile or so at pace, just getting started, preferring to get a little more at pace in before stopping. MP had started out feeling pretty comfortable but by the time I got to the DE1 bridge, it was starting to feel more work-y and I was thirsty. The trail is totally open to the sky, with no cover whatsoever -- at least on the 4-5 mile stretch of it I was on -- except for those brief moments passing under the bridges, which are negligible -- and that was great for the Garmin and being more accurate with apparent pace, but it was not great for physiology. The sun was very warm and took a tough toll, one that I have not experienced yet this year. Because I had never run here before, I was not familiar with the landmarks, so even though it was out-and-back, I did not really have a good sense of how much I still had to run until I made it to the car. It wasn't very enjoyable, but when I saw the beat-up looking dock next to the trailhead, I was elated.
It's so very hard not to guzzle water when you're at such a point. I sucked down a gel and washed it with a few more swallows of water, managing to restrain myself. It felt like enough, and then I started running east again. It was not long before I felt thirsty once more.
The damage had been done. If I had stopped for water at 3.5 mi, it might have mitigated the effects of the sun and heat early, and I might have gotten another couple solid miles at MP in. As it was, it was all I could do to get in 11, and I barely count the 12th because I was fading fast. More liquids, another gel, and I even carried a water bottle with me for the last 3-4 "easy" miles. (Very uncomfortable, very hard not to hammer the whole bottle at once.) Given how awful I felt, I was satisfied enough with what I ended up having done. I had started to feel a little like the way I did in Boston 2014, when I had to drop out: stomach feeling a little queasy, never getting better and even a little worse even after drinking. In the 2014 race, I quit at mile 18; Sunday, I quit at 17. More lessons learned (the hard way, unfortunately): water is more important than getting in time at pace. If I could drink on the fly in training the way I can in a race, it would be easier, but unfortunately, unless B rides a bike right along with me (which he has done a couple times in the past), I'm stuck having to take short breaks. (I won't wear one of those fuel belts with bottles.) Funny how every year, I run in sun and warmth, but the first times of the season often catch me off guard and I don't do it right. A day with weather like Sunday's is deceptive; just standing around, it was pleasant, a nice breeze, even maybe a slight bit cool, but running with no shade was down right hot. 60s and 70s are extremely lovely, but too warm to be "great" for running at elevated efforts over long distances.
07:44.8, 07:42.4, 07:45.6, 07:42.6, 07:42.1, 07:45.5, 07:48.5, 07:45.5, 07:40.4, 07:41.1, 07:49.2, 08:00.7
The trail along the canal is great though -- absolutely sea level with only a little rippling that you barely notice (except when you're exhausted -- somehow even the smallest ups and downs are hard then). There were a lot of people out on bikes enjoying the pretty day, but no one interfered with my running at all, and I only saw two other runners; a handful of walkers, but the majority of users were on bikes. Early in the run, a ship turned into the canal under the DE9 bridge and cruised along parallel to the path. It was the Demeter Leader, and, according to Google, is a vehicles carrier from Panama; myshiptracking.com indicates it docked at Baltimore at 21:37 on Sunday. It made almost no sound as it passed by, pretty much only the whush of the water in its wake. It was amazing that such a gigantic beast of a ship could make less noise going by than a car. It was also a little eerie because there was no sign of people on the ship, so it was just a silent, almost alien-seeming long and huge blue and white box moving by. Other than that, only speedboats and other personal watercraft whizzed by occasionally. Mostly it was quiet but for the sounds of birdlife. Except for feeling pretty cruddy as I went on, I enjoyed it there. It's another place for pace work to keep in my pocket. Closer than the Schuylkill trail and better, actually, because of the openness.
Upcoming week: days of easy mileage and then Saturday morning is the Tommy 10-miler in Lewes. Longest long run on Sunday.
Subscribe to:
Posts (Atom)