Sunday, October 13, 2019

Fall Marathon Training Update

I realize that I have not blogged about my training much since the summer. It's been going well, and I am long overdue for a recap.

My two goal races are the Columbus Half marathon (next weekend) and the California International Marathon (December 8). I'll also run my 14th consecutive Turkey Trot on Thanksgiving. Usually I run my tune-up half marathon closer to the full marathon, but I really wanted to go back to Columbus. I ran a strong marathon there in 2014, and it was my first Boston Qualifier. I went back in
2015 and set a huge PR in the half marathon. It's a fast course that's well organized with easy logistics, and only a short flight.

The California International Marathon (CIM) has been on my list for some time, but the long flight has always discouraged me. Long flights tend to exhaust me and put me off my game, but so many people have said that CIM is a fast course and that I need to experience it. In the spirit of running races I'm excited about instead of the most convenient fast race, I decided to go for it this year. Even if it doesn't go well, at least I can understand what all the hype is about. Greg and I are going to fly out on Thursday morning, which should give us plenty of time to recover before the Sunday race. We're both running it!

The training has been going really well in terms of executing all of the workouts according to the plan, almost always hitting my desired paces, and staying healthy. Usually at this point in training, though, I am looking to see some kind of fitness gain. While I have definitely gained endurance, I haven't run any speed workouts that are any faster than previous cycles. I realize that the purpose of a workout is to build fitness, not to prove fitness, and that it's important to trust the process and trust the plan.

That doesn't mean I'm not looking for progress along the way. It excites me when I run a workout that exceeds my expectations and I realize "whoa... I just got way faster!" It could be because I've only been training consistently since early August, or it could be because it hasn't cooled down to my sweet spot yet, which is anything below 50 degrees. Also, many of my workouts have been short track intervals (100m, 200m, 300m repeats) which are so short that they really don't indicate marathon fitness like a long tempo would.

As I mentioned in my 10K race report last weekend, I think I raced really well, and it would have been nice to have the confidence boost of a PR if the conditions had cooperated. There is, however, confidence to be gained with strong execution, and I have demonstrated strong execution many times over the past two months.

Training Stats
If you've been following my blog, you know how much I love to analyze my training data. My current running streak is 70 days long, with no days off. It's a total of 571 consecutive miles, which comes out to an average of 8.2 miles a day. This run streak began in early August, as soon as I was recovered from my bike accident.

Unfortunately, I am still not 100% recovered from that accident. I have a hematoma in my groin, and it occasionally hurts for no apparent reason. If I am still experiencing intermittent pain after the marathon, I will get some imaging done on it. I'm not going to do anything about it between now and then, so I might as well give it more time to go away on its own.

This graph shows my training by week since the streak started.

In terms of individual workouts, my longest run so far has been 18 miles, which I ran just two days after the 10K, on a Tuesday before work. My legs were definitely tired by the end, but I got it done at an average pace of 8:12.

Yesterday, I ran a workout that was 40 minutes easy, 30 minutes at marathon pace, 10 minutes easy, 30 minutes at marathon pace, 10 minutes easy. That's a total of 2 hours. In the first 30 minutes at marathon pace, I ran 4.15 miles at an average pace of 7:14. For the second 30 minutes at marathon pace I ran 4.12 miles at an average pace of 7:17. My legs were trashed by the end!

My goal is to be right around 3:10 at CIM, so I would need a marathon pace of 7:15. Aerobically, this pace felt manageable for a longer period of time, but having so many miles on my legs from a hard week of training was definitely making it feel hard by the end. I also need to keep in mind that at CIM I will be wearing faster shoes and the course will have more downhill than up. Cold weather would also be nice!

With 1 week until the Columbus half and 8 weeks until CIM, I think I am in a good spot: building fitness, not seeing material gains yet, but feeling strong and healthy for more intense training to come.

Tuesday, October 8

Sunday, October 6, 2019

Fall Classic 10K Race Report

After my clever title for yesterday's post, I am fresh out of creativity today! As the title states, I ran the Potomac River Running Fall Classic 10K this morning. It was the inaugural running of the race as the "Fall Classic" although that course is used multiple times throughout the year as other races. I had never run this course before, although I had run a 5K that overlapped with some of the course.

Let's back up. Way back in the spring, when I was planning out my fall race schedule, I had the Boo! Run for Life 10K on tap for today. There are lots of things I love about the Boo! 10K. Its a pancake flat course with no turns, so it always yields 6.21 miles exactly. I set a PR there in 2014 and 2015. I've set other PRs on that course as the "Veteran's Day 10k" too, back in 2009 and 2011. And also the "Jingle All the way 10K". So yeah, it's fast.

Even though I was registered for the Boo! race, I decided earlier this week to switch to the Fall Classic. Here's why:
  • Boo! is in Washington DC, which tends to be 4-5 degrees warmer than the suburbs in the mornings. The Fall Classic is about 25 miles west of the city, which tends to be slightly cooler. This wouldn't make a difference if it were a cool morning, but 64 vs. 60 can make a real difference. 
  • The Fall Classic in Ashburn has gently rolling hills, which can be fast, and is better preparation for my marathon, CIM.
  • The Fall Classic is part of a race series, which would earn me points in the series.
  • The Fall Classic has better prizes: gift cards to Potomac River Running. I was the 2nd place female finisher at Boo! back in 2015 and I didn't win anything other than a certificate.
  • The Fall Classic would be logistically easier, as it's closer to my house and you can park near the start/finish.
All of this being said, I figured that my time would be slower at the Fall Classic due to the curvy nature of the course and the Garmin likely reading more than 6.21. But, since didn't think I would PR in warm, humid weather, I figured that time didn't matter as much as the other things. 

Anyway, my race was 62 degrees with about 85% humidity. Dew point 57. I think it only ended up being like 2 degrees warmer in the city, but whatever, I had made my choice. This race wouldn't be about my finish time but about effort and execution. I was kind of sad about this because I do believe myself to be in shape for a PR. And I don't often run 10Ks. My PR is from February 2017, so I feel like it has overstayed its welcome. 

I did not, however, rule out the possibility of a PR, I was just being realistic. I was still going to run as hard as possible. But that looks a lot different in 62 degrees vs. 22 degrees. 

Before the Race
As I said earlier, this race is pretty easy in terms of logistics. It was a 20-minute drive, followed by packet pickup at the running store. Greg wasn't running the race but he did run the warm up with me. I warmed up for about 1.5 miles on what I thought was the end of the course. The course is a loop, and I had studied the course map beforehand. As I warmed up, I was mentally preparing myself for this route to be the finish. As I warmed up, I drank my Generation UCAN.

I then went back to the car and changed shoes into my Nike Vaporfly Next%. Followed by going to the porta potty, and then running another half mile in the Vaporfly to get a feel for them. Previously I had written about the Nike Vaporfly 4%. I didn't love this shoe because the fit was sloppy. So I tried on the new "Next %" at the running store, and they fit so much better. Then, I tried on the original Vaporfly to compare. At that point, I realized that I could slide the original Vaporfly off of my foot without untying them! I figured I probably shouldn't run in a shoe that was so loose it would slide right off even when tied tightly. So I bought the Next % and used them in this 10K.

Soon it was time to line up. I saw my friend Lisa at the start line and we chatted briefly before the gun went off. 

Miles 1-2
Based on the elevation profile, I wanted to run these miles at goal pace, or maybe slightly slower. There were some gently rolling hills but nothing major. One woman shot out ahead of me, but I didn't see any others so I was pretty sure I was in second place. These miles were a little windy. The
Mile 1
headwind was annoying, but it also had a cooling affect so I didn't mind it too much. I focused on staying relaxed and settling in.

When I came to mile marker 1, I had already run 1.05 miles according to my Garmin, so I hoped that the marker was simply misplaced. But then when I hit the second mile marker, my Garmin was still ahead on distance, so I was mentally prepared for my Garmin to yield more than 6.2 miles. But I knew this going into the race based on Strava data and the curvy nature of the course. 

Mile 1: 6:49
Mile 2: 6:47

Miles 3-4
I was content with how I handled the first two miles. Ideally they would have been closer to 6:45, but I still had four miles to go, and anything could happen. Shortly after I hit mile marker two, there was a water station. I poured an entire cup over my head in an effort to cool down. I wasn't "hot" per se but the air was thick and sticky. 

I knew that these miles would both be net uphill, so I needed to stay strong. I maintained my placement; nobody passed me and I didn't pass anyone. I had no idea how far behind me the third female was. 

Mile 3: 6:56
Mile 4: 6:52

Miles 5-Finish
I did not get discouraged by how slow miles 3-4 were, as they were uphill. However, I was envisioning them being closer to 6:50. The good news was that the final two miles would be net downhill.

But first, we turned into a neighborhood, ran about 0.05 miles into it, did a hairpin turn, and came back out. I guess they needed to add 0.1 mile somewhere, and this is where they did it? It was super annoying but it wasn't a surprise as I had studied the course map. At that point I was kind of wishing I had run the race in the city, but then I wouldn't get my nice downhill finish!

Heading toward the finish line
I was confused at the very end because we didn't finish like the course map had indicated. We didn't turn where I expected to turn so that threw me off a little. But ultimately that meant fewer turns overall, so I think it was for the best.

My original plan was to run these miles hard and go sub 6:40. I did run them hard, but sub 6:40 wasn't happening. I was at a point where I was struggling to maintain my effort.

Mile 5: 6:49
Mile 6: 6:44
Laso 0.29: 6:38 pace

Official time: 42:52, good for second place female. First place ran 40:02, so there was no catching her.

After the Race
Before I had a chance to mentally process the race, I knew I needed to do the post-race workout prescribed by my coach. He wanted me to stop for no longer than 5 minutes, and then do a Fartlek of 3 x (3 mins, 2 mins, 1 mins) all with 90 seconds of steady running in between. Wow. Greg, who had been taking photos, went back to the car with me and I changed out of my Vaporflys and into the adidas which I had warmed up in.

I thought there would be no way I could run fast after just finishing a 10K, but I was pleasantly surprised:

3 minutes at 7:34
2 minutes at 7:03
1 minute at 6:54
3 minutes at 7:11
2 minutes at 6:58
1 minutes at 6:36

I stopped after two sets because my legs were toast. I think that was the point, as this is part of marathon training. But I have my limits! All of that yielded an extra 2.62 miles at an average pace of 7:58. The awards ceremony started about five minutes after I finished, so I was glad I stopped when I did.

Final Thoughts
I feel good about this race. It's annoying that the weather was what it was, especially since yesterday morning it was in the low 50's at 8:00. But I can't control the weather and I made the best of it.

I missed my PR by 1 minute, 1 second. But considering this course was "longer" than my PR course, the pace was about 6 seconds per mile slower. So, kind of close, which is good.

New zebra socks
Before the race I had looked at Strava data from about 5 different runners on this course. The distances ranged from 6.25-6.27. I paid very close attention to the tangents so I think I ended up with 6.29 because this course was different at the end then what the Strava runners ran. Plus, as I said, the
mile markers seemed off from the very beginning. I don't really care though, since I wasn't going to PR. My point is that my pace is closer to my PR pace than my time would suggest.

Greg wanted to look up the Boo! Run for Life 10K results and find out what the winning time was. I told him not to. If my time was faster than the winning time, I would probably be kicking myself. I made my choice to run the hillier, curvier, "longer" course, and I'm good with it.

I'm very hungry for a PR. I think I'm in excellent shape, but I don't really know since all my tune-up races have been in 60+ degrees.

I like the Vaporfly Next % much better than the original version. I don't think they made me a ton faster in this 10K than I otherwise would be, but I could see how they would really help during a 10-miler and longer. I'll probably continue to wear them in future 10Ks, but I think I have settled on my adidas Adios for the 5K distance.

Next up is the Columbus half marathon in two weeks. Please, PLEASE, let there be good weather. The half marathon PR is also dated: January 2018. I think sub-1:30 might be too ambitious but I think 1:30:xx is totally in the cards if the stars align.

Saturday, October 5, 2019

Rapid Reboot Recovery Review

How many "R" words can I fit in a blog title? Today I'm sharing my thoughts on the latest trend in recovery for endurance athletes: compression boots. Specifically, the Rapid Reboot brand. I absolutely love the name they came up with since puns are my absolute favorite. When you wear these boots, you are re-booting your legs by increasing circulation and speeding up your body's natural recovery process.

I first became interested in these compression boots about a year ago when I started seeing runners on Instagram wear them. Either at recovery clinics, or in their homes, many runners were singing the praises of how fast they would recover from workouts with these boots. The price tag (anywhere from $800-$1500, depending on the manufacturer and model) was steep and I had kept myself injury free and recovering well by getting massages every one to two weeks.

But this fall, I knew my training would be more intense than ever. I'm about a month ahead of where I was in my training last year at this time, and my marathon is on the same date that it was last year. So, that means an extra month of even harder work. I reached out to Rapid Reboot, a brand name I loved for its creativity, and asked them if they would give me a pair to review on my blog and my Instagram. They agreed, so here we are!

I don't often review products on my blog, and I only review products that have helped me in my training and racing. Rapid Reboot sent me the boot and hip combination set. They are not meant to be worn at the same time, so I rotate. They came in a duffle bag and were very easy to un-package and setup. There's a main control unit, which plugs into the wall, and you plug either the boots or the hip piece into the control unit.

Below is a photo of the main control unit. You can select your time (10, 20, 30 minutes), the amount of pressure, and which areas to focus on. Once all of the options are chosen, you hit start and the boots or the hip piece begin to fill up with air.

It feels exactly like getting your blood pressure taken, with the pressure increasing and decreasing in a back-and-forth way. You don't need to set the amount of pressure very high for it to work, and I start to get just a little uncomfortable at 100 mmHg, so I never go above that. It's like a massage in that it feels good, but hurts a little bit, letting you know stuff is happening! It works because the compression stimulates blood flow, which is exactly what eliminates the accumulation of waste products from training. The faster that can happen, the more training load you can tolerate, the fitter you will become.

Do I think they help speed up recovery? Yes. I ran a 16 miler last Saturday and used the boots on Saturday afternoon and Sunday. On Monday, I was able to run 10.7 miles with 8 at marathon pace in the middle without any lingering soreness from the 16-miler. Would I have been sore without the boots? There's no way to answer that question, but I will say that the 16-miler took a lot out of me because it was warm and humid, and I ran a hilly route.

Would I spend my own money on them? Someone asked me this on my Instagram and I said yes. I can justify the cost by getting massages less frequently (although I will still get them after races). Also, I am 40 years old and I know that recovery will start to get harder over the next 5 years. Might as well get a recovery tool now in preparation! I'm of the mindset that if I want to keep setting PRs in my 40's, I need to take any advantage I can, like the Nike Vaporfly!

I really like the convenience of being able to do this at home, and the fact that I can multi-task. I currently am wearing the boots as I write this blog.

Add a comment below if you have questions, and use discount code Elizabeth for 10% off on the Rapid Reboot website.

The hip attachment- goes around glutes and hips.

Saturday, September 14, 2019

Dulles Day 5K on The Runway

I ran the Dulles Airport Runway 5K this morning, which was my 3rd 5K in six weeks. I ran the Leesburg 5K on August 18 and the Great American Labor Day 5K on September 2. Each of these races was faster than the one before it, and I am now done with the 5K until my Turkey Trot.

Before the Race
The race started at 7:30, and is only 4 miles from our house. I expected it would take no longer than 10 minutes to get there so I planned to leave the house at 6:35. We ended leaving at 6:40, which I thought was still okay, since I already had my bib. All I needed to do when I got there was to warm up for 20 minutes.

Unfortunately, there was crazy traffic as we approached the Air and Space Museum parking lot. This Dulles Day race has both a 5K and a 10K, which were sold out at 2,500 runners. That's a lot of cars all trying to get to the same place at the same time.

At 6:50, I started to get nervous because we were still stuck in traffic. At 7:00, I hopped out of the car, and ran to the race start while Greg (who wasn't running the race) parked. We were only half a mile from the parking lot, but I wanted to start my warm up at 7:00, so it was a good opportunity to run. One of the traffic cops said "it's better running than it is driving!"

I was wearing my Brooks Ghost shoes and carrying my Nike Vapofly shoes in a bag. To get through security faster, I took the shoes out of the bag, scrunched up the bag in my hand, and went through the "no bags" line. After security, we had to walk through the Air and Space Museum to get out to the race course. I continued to jog slowly, but a museum official told me I needed to walk. Bummer! Oh well, it wasn't long before I was outside again and I continued my warm up.

I didn't know when I would see Greg, especially since he would have to wait in the longer bag line.
He had a cooler with ice and my Energice pop. After about a mile, I waited in a porta potty line as I changed into my Nike Vaporflys. Then, I warmed up for a mile in them. I heard the announcer say that they were delaying the start by 10 minutes. I'm pretty sure this was because of all the traffic.

Based on my last 5K, I determined that I prefer the Adidas Adios Boost for the 5K distance. However, the runway is concrete, so I figured the bounce of the Nike Vaporfly would be advantageous. I plan to return to my Adidas for the Turkey Trot.

I still hadn't seen Greg, so I hid my Brooks shoes behind a car parked on a grassy area and lined up. Just a few minutes before the start, I saw Greg and he offered me the Energice pop, which had since melted. I drank about half of it. I lined up in the second row, and I heard the man in front of me say, "my plan is to walk, and then run, and then walk." (He's not shown in the picture).

My goal for this race was to beat my Labor Day time by 20 seconds, which meant sub-20:50. I thought that was reasonable, given that I'd have two extra weeks of training under my belt, and the runway is flatter than the Labor Day course. The reason why I haven't been trying to come close to my 19:58 PR is primarily the weather. All of these races have been very humid, which equates to slower times. This morning, it was 67 degrees with 90% humidity.

Mile 1: 6:43
Mile 1, photo by Cheryl Young
The race started and the man in front of me, who was in the first row, literally walked off the start line. I bumped into him a little bit. I knew he would be slower, but I didn't think he would actually start off with the walking! Anyway, once I got going, I focused on the number or women ahead of me. There were four of them. At first, it seemed like maybe I would be in a position to win the race, but towards the end of the mile, the first two women had pulled ahead quite a bit. I passed the two other women, putting me in third, but then another woman passed me, leaving me in 4th place at mile marker 1.

My plan was to run this mile in 6:40. Based on my race report from 2015, and my Strava data, I knew that the first mile had an incline with a gain of 25 feet. My goal pace was around 6:37, so I planned to run negative splits, speeding up during the last "down hill" mile. My actual split was 6:43 and it felt really hard. I didn't have a lot of "pep" and I wasn't sure if that was because of the concrete, the humidity, or if I was just having a blah day. I pushed on.

Mile 2: 6:48
I really struggled here. I ran this mile next to a kid who looked to be about 10 or 11 years old. He was strong and he pulled me along. I had been planning to run this mile at goal pace of 6:37, but that was not happening. I just did my best to stay strong and not let any women pass me.

I think this course is mentally exhausting. There is not much to look and you can see almost the entire course. There is no variation to keep you engaged, so it's easy to coast. I don't consider myself a particularly strong hill runner, but I think I got some power from those hills two weeks ago that I wasn't finding today.

Mile 3: 6:42
I kept pushing on, just trying as best as I could to maintain the hard effort level. The kid I was with
Mile 3, photo by Greg Clor
dropped back so I was on my own. With about a quarter mile to go, I saw Greg taking photos. That coincided with the downward slope of the runway, so I was able to pick up the pace. I knew I had secured 4th place female, so now it was just a matter of what my finish time would be. I had originally envisioned this mile being sub-6:35, but that didn't happen.

The last 0.13: 6:02 pace
I saw the clock and I thought I could get under 21:00, so I sprinted as hard as possible.

I ended up with an official time of 21:02.

Although this race was faster than my Labor Day race, I wasn't as happy with it. I know I gave all I had to give, so I'm not disappointed in my performance. It was simply a "meh" day with "meh" energy levels on a "meh" course. I don't think it's an indication of my fitness level, and I'm still confident in my ability to run a 10K at a faster pace than I ran today in early October.

After the Race
I reunited with Greg, we chatted for a bit, and then I ran 1.4 miles to cool down. The awards were wonky. Instead of age groups of 20-29, 30-29, etc. they were 21-30, 31-40, 41-50. Since I'm 40, this meant I was one of the oldest women in my age group, instead of the youngest like I have been for the past year.

I had read my 2015 blog post a few days before the race, and as a 36 year old, I missed getting an age group award because a 40-year old beat me. I was annoyed by that. This year, I was that 40 year old who took first place in the 31-40 category. And, one of three women who beat me was 42! So if they had done normal age group brackets, I would have placed second. So this age group thing screwed me over in 2015, but worked to my advantage this year. Also, I was inspired by a 55-year old woman
who beat me. She ran 20:30 and was the third female. When I am 55, I hope to be running that fast!

I won a $25 gift certificate to the Dulles Airport Marriott restaurant. Yay! Thankfully, we live close to the airport so it will be easy for us to use this.

Official results:
  • I placed 1 out of 232 women in my age group, 31-40.
  • I placed 4 out of 772 total women
  • I placed 22 out of 1,446 total runners

Final Thoughts
  • I ran 4 5K races this summer: Firecracker, Leesburg, Labor Day, and Dulles Runway. Of those races, I think I ran to my full potential at Firecracker (21:26) and Labor Day (21:09). Leesburg was a total bonk, and today was "meh". It's a good reminder that you can't always feel 100% at every race.
  • My average heart rate today was 168. For my previous three 5K races, it had been 172. I am not sure if the hills in those races forced me to a higher heart rate, or if today I simply didn't have the energy needed to run at that effort level.
  • To the above point, my heart rate suggests that if I had been feeling more peppy, my fitness supports a faster time. . . probably in the realm of my original goal of sub-20:50.
  • I've now run this race twice and I don't think I like it that much. The concrete is hard on the legs and the lack of variation makes it difficult to stay engaged. 
  • In 2015, I ran 21:35, which I think was a much better performance given my fitness level at the time. You can read the full 2015 report here.

Monday, September 2, 2019

Great American Labor Day 5K Report

This morning I ran the Great American Labor Day 5K in Fairfax Corner, VA. This course is used for several races throughout the year, and I have run it about five times in the past. Last year, I ran this exact race as a tempo run in 22:25. I was just coming back from mono at that time, so I didn't want to push it too hard. It's not known for being a fast course with its constant hills, but since I've run it so much, I find it to be a good benchmark.

This year, I decided to run it because I wanted to get a few 5Ks under my belt right before marathon training started. My last 5K, Leesburg, was one of my slowest 5Ks in a long time (22:08). Partially due to the weather, and partially due to the fact that I hadn't regained all the fitness I lost from taking time off post bike accident. And I went out too fast. I came into today's race looking for some redemption. 

My goals for this race were as follows:
Photo by Cheryl Young
  • Run hard, get a good workout in on the hills
  • Test out the Nike Vaporfly
  • Set a course PR
Before the Race
I didn't sleep all that well last night. I attribute that partially to taking an hour-long nap yesterday. That wasn't really planned; I just fell asleep on the couch and didn't wake up for an hour. My sleep was restless, but I got a solid 6 hours, so I wasn't really worried.

Before leaving the house, I ate an English muffin with peanut butter and mixed up a serving of Generation UCAN with some water to take with me. Greg did not run this race-- he was playing the role of photographer and cheerleader. We arrived about an hour before the race started and picked up my bib. After pinning it on, I used the porta potty and then warmed up wearing my Brooks Ghost.

After about fifteen minutes of warming up in the Ghost, I switched to the Nike Vaporfly. I ran about half a mile in those, just to get a feel for them pre-race. They felt loose. I didn't want to tie them too tightly, though, because I did that on Saturday and my feet hurt afterwards. So I made sure they were secure but not too tight. My heel was slipping in them, but a lot of people said that was an issue with this shoe, so I accepted it as normal and didn't try to fix it.

After the second warm up, I returned to my car and had an Energice ice pop, and put a few ice cubes in my sports bra. I then headed for the start line with about five minutes to go.

It was 71 degrees with a dew point of 70. Thankfully it was overcast, unlike Leesburg. This weather wasn't abnormally warm for this time of year, but we had been treated to a full week of cooler weather leading up to the race. I had been spoiled. 

I thought that I could still get a course PR, beating my time of 21:31 from November 2016, when the weather was ideal. Since Leesburg two weeks ago, I had executed a number of really strong track workouts, all focused on speed. I even noticed my heart rate being lower in general, both during runs and my resting heart rate. I was in good shape, so it would all come down to execution and the impact of the humidity.

Mile 1: 6:39
Mile 1, photo by Greg Clor
The race started and swarms of runners shot out ahead of me. I remained patient, as I prefer to ease into a race instead of gunning it at the start. I wanted to keep my eye on how many women were ahead of me, and there seemed to be about 6 right from the beginning. I started to pass people at the bottom of the first hill, which was about 3/4 of the way into the first mile. 

I had planned for this mile to be around 6:40, if not slightly faster, so I was right on track. I didn't look at my watch too much, but this was naturally the pace I ran. I knew from past experience not to go out too fast on the first downhill. I also had fears of bonking like I did in Leesburg, so I was more cautious.

Mile 2: 6:46
The rolling hills continued throughout this mile, creating a net even elevation. I continued to pass the people who had taken that first down hill quicker than me. As I passed one man, who looked to be in his late 50's or early 60's, he said to me, "You are the one who was screaming. That's really annoying." I was shocked. I know I make loud noises when racing, but no one has ever complained to me about it. If anything, people ask me if I'm okay, or they encourage me along with "you got this" or other such phrases.

I let it sink in for a few seconds and then I looked at him and muttered, "that's really rude." And then I passed him. I took one last quick glance behind me to catch a glimpse of him, so I could make sure he didn't pass me later in the race. I was really surprised that someone would waste their energy in a 5K to tell someone else that they were annoying. It's pretty much impossible to talk when running 5K effort, so you really have to be obnoxious to expend the energy to make such a comment. 

Mile 3: 6:50
Mile 3, photo by Greg Clor
More rolling hills, with the final hill being super long. I was starting to get really tired, but I stayed strong. I did not want anyone passing me at this point, particularly not the guy who insulted me. The shoes were super bouncy. Even though I was low on energy and I felt like I was slowing down, my watch indicated otherwise. This final mile was all about staying strong mentally and continuing to push up the long hill.

Last 0.14: 6:00 pace
I gunned it to the finish and was elated when I saw the clock. That course PR was mine!

I finished in an official time of 21:09, which is a course PR by 22 seconds. It's 0:59 faster than my time at Leesburg two weeks ago! I was thrilled.

I re-united with Greg and changed back into my Brooks Ghost for a short cool down. During the cool down, I ran into my friends Hannah and Alex, who were run-walking the race. Hannah is 36 weeks pregnant, and Alex ran a marathon last weekend. Kudos to them for showing up and getting it done!

I ended up winning first place in my age group, and coming in 4th overall. I was very happy with this.

After the Race
Once I finished cooling down, I spotted the guy who had told me my noises were annoying. I had beaten him by 12 seconds.

Me: "Hello. Were you the person who told me I was annoying?"

Him: "Yes. It was so loud. It was like this:" screams right into Greg's face

Greg: "Don't scream in my face."

Him: "You were so loud the first half, but you were ok for the second half.  I was running with you during the second half and you weren't doing it then. It was so loud in the beginning that it affected my race. I actually pulled a hamstring."

Greg: "You're saying her screaming made you pull a hamstring?"

Him: "This conversation isn't going anywhere. Good luck in your future races."

Normally everyone I meet at races is so nice and exhibits good sportsmanship. This was certainly different.

I'll be the first to admit that I make loud noises when I race. They are like mini screams that kind of just come out when I am working hard. Particularly when I am going up hill. As I said above, nobody has ever insulted me for it, although they have sometimes expressed concern.

Vaporfly Thoughts
I had a really good race this morning. Was it because of the shoes? I don't think so. Even though the weather was crappy, I think I had built up a good amount of fitness post bike accident. I had been going to the track twice a week and really hammering it. I also executed the race well by not going out too fast and staying strong on the final hill.

Many runners were wearing the Vaporfly today. I looked down at the start line and probably one in every three runners had a pair. I liked the shoes but I didn't love them. I think I might love them for a 10K or longer. 

My biggest issue with them, aside from the loose fit, was that I didn't feel as engaged with the ground. When I'm running fast, I like to get feedback from the ground beneath me and derive power from that. In this race, I felt like I was getting power from the shoe and not from the road. I'm undecided if I will wear them in my next 5K. I will likely wear them in my next 10K. 

I'm glad I did this race. I think it's good to work on speed before entering marathon training and this race was a chance to do just that. Plus, it's also nice to have a top 5 overall finish and to win the age group.

Sunday, September 1, 2019

Keeping up with the times: Nike Vaporfly thoughts

If you could run just a little faster without having to train any harder, would you? The Nike Vaporfly 4% shoes had me asking serious questions about why I run.

For those of you who have never heard of the Nike Vaporfly 4%, they are supposed to make you run faster. They were introduced in 2017 at a price of $250. When they first launched, they were nearly impossible to find because retailers would sell out of them immediately. There was a ton of hype around them and runners everywhere were trying to get their hands (or feet) on these shoes! A few months ago, Nike released the Vaporfly Next %, which is supposed to make you even faster.

Nike Vaporfly 4% 
Does the Nike Vaporfly actually make you faster? Many runners have supported this claim, saying that they believe the shoes helped them shave some time off of their PRs. My friends who wore them told me that they were really bouncy and had a lot of cushion. Supposedly, you also recover faster from long runs due to the extra cushion in the shoe. Normally a highly cushioned shoe does not equal fast, so I was intrigued. One major caveat about the shoes: they wear out faster than a normal trainer. If you normally get 300 miles on your shoes, you might only get 200 on your Vaporflys (Vaporflies?). They are not recommended for daily use and are mainly intended for the marathon and half marathon.

When they first came out, I decided they weren’t for me. If I set a PR, I didn’t want it to be because of the shoes. I didn’t think I would get as much satisfaction. It’s not cheating, but it’s an advantage that I wouldn’t have had previously. What motivates me most in running is setting goals and accomplishing them. Could I really feel accomplished if I thought that a special shoe was the reason I PR’ed?

So I didn’t go near the Nike Vaporfly and continued to race in the same shoes I had been racing in. But each time I showed up to a race, more and more runners were wearing the Nike Vaporfly! At Sugarloaf, for example, I looked down at the start line into a sea of Nike Vaporfly. And then another footwear brand released a shoe with similar technology: a carbon plate. I realized that this was the future of racing shoes, and they were only going to become more popular. Soon, each running shoe brand would have their own version.

At the same time, more and more runners are qualifying for Boston, which made the B. A. A. lower their qualifying times by five minutes last year. Runners are generally much faster than they were five years ago, and I do think the Vaporfly has played a role.

With this realization, I figured I should hop on board and give the shoes a try! After all, running is a competitive sport, and I started to feel like I was at a disadvantage for NOT wearing the Vaporfly. How would I feel if someone in my division beat me wearing the Vaporfly? Annoyed! So I bought a pair and will race a 5K in them tomorrow. Watch this space for a race report and more thorough review.

I took them out yesterday for a test run and I liked them. Very springy and cushioned. I just wish the heel was more snug. The latest model, the “Vaporfly Next %” has a snugger heel, but it comes with a lower drop and that’s not good for my Achilles. If they work in the 5K, I’ll try them in a 10k, and all the way up. If they aren’t going to work for me, better to find out now.

Back to my original dilemma: will I feel less satisfaction from setting a new PR by wearing these shoes? No. I’ve accepted that the Nike Vaporfly 4% is one of the most popular racing shoes today, and I’m keeping up with the times. Literally.

Sunday, August 18, 2019

Hot, hot, hot 5K!

The Leesburg 5K/20K race is notorious for having warm, sunny, humid weather. After all, it's in the middle of August, when the DC Metro area is at its steamiest. Last year I ran the 20K as a training run as I was coming back from six weeks with mono. I registered for it as a training run again this year, simply hoping to beat my time from last year.

Photo by Cheryl Young
On Wednesday, I looked at the forecast and saw that the starting temperature would be around 72, heating up to 80 by the end, with the dew point being 72-73. And sunny to boot. Yikes! When I realized that I wouldn't even run a training run in that weather, I decided to drop down to the 5K. Earlier this summer, I ran 10 miles "easy" in similar weather, and shortly after that I purchased my treadmill. Given my immune system issues which are triggered by running hard in warm weather, I didn't think running this 20K was worth the risk.

Even the weather for the 5K was forecast to be miserable, so I told my coach I was going to run it as a workout. He pushed back on that, and told me I should race it all out. He said it would be a good opportunity to run hard and test my fitness. I don't really think I can test my fitness with a dew point of 72, but I agreed that I would run it as a race and give it my all.

As for my bike injury and hematoma, that's mostly cleared up. I no longer have pain with running. The bump is still there in my groin, but it has shrunk down significantly, and at this rate should be gone in another week. I saw the last of the bruise yesterday, too.

Before the Race
Greg and I were a little late leaving our house (6:15) so we were more rushed than we would have liked, but it all worked out okay. I picked up our bibs while he used the bathroom. I ran into my friend Amber, who I had met at the Rock 'n' Roll New Orleans half marathon just over a year ago. One of the reasons I like to do this race, despite the crappy weather, is that a lot of people come out for it. It's a good way to see friends and socialize. It's a fairly competitive race, too, as many local runners use it as a tune up for fall goal races.

Greg and I put our bibs on and I drank my Generation UCAN. I also had an Energice ice pop, which would have been better to have after my warm up and immediately before the race, but the logistics of going back to the car made that impractical.

I started my warm up and Greg headed for the start line of the 20K. The 20K started at 7:30 and the 5K at 7:48. Weird timing, but I liked the precision! I had run the 5K back in 2017, and I knew there was a coffee shop on my warm-up route where I could go to the bathroom. However, the coffee shop was no longer in business, so I found a gas station instead. I like to go to the bathroom 15-20 minutes before I race just to make sure everything is "out" that is coming out. 

On my way back, I was able to see the 20K runners, including Greg, shortly after they had started. Given how hot I already was on my warm up, I was relived that I was not among them. Finally, 7:48 arrived and it was time to get going.

Mile 1
I did not have a goal time for this race. I thought I would be happy to go sub-22:00 in these conditions, but I didn't really have a goal in mind. I knew that the first two miles were mostly uphill and the last mile was downhill, so I made sure not to go out too hard in the beginning.

I knew that Amber was in much better shape than I was, and yet I found myself near her for the first half mile. I looked down at my Garmin and I wasn't going all that fast, and I felt fine, so I just maintained that effort.

Except-- it was definitely way too fast. I clocked in at 6:52, and even though that seems conservative for me, it was not given that there was 40+ feet of gain and it was very warm and humid.

Mile 2
This mile has a lot of turns and I knew to expect them. We ran around a large school and it was mentally exhausting. Even though this mile wasn't as hilly as the first mile, I was running out of steam already! I only glanced at the Garmin a few times and I wasn't surprised to see how slowly I
was running. I didn't have any pep and I was exhausted. I was not feeling this race at all.

Shortly into this mile, I passed a high school cross country guy. A number of them had lined up at the start wearing the same jersey, so it was obvious that their team had come out for the event. As a 40-year old woman, it did feel good to pass a high school cross-country male! That perked me up mentally.

After that, I needed something to motivate me to maintain my effort, so I reminded myself that I wanted to be the first Master's Female. I didn't know if they had an official Master's award, but if they did, I wanted it to be mine. And if not, I wanted to win my age group. There was a turnaround which allowed me to see who was ahead of me. I knew 3 out of 6 of them, and they were all younger. And it's really hard to tell how old someone is when they are in running clothes, especially when you are trying to race at full effort. I just assumed they were all younger than me so that I would still be motivated to push hard. My Garmin beeped at the end of the mile in 7:06. Not pretty, but I was still maintaining my placement.

Mile 3
I knew this mile would be downhill, and I needed that badly. If you execute this race properly, your last mile should be your fastest. Probably by at least 10 seconds. This was not the case for me. I tried my best to simply hang on to the effort level, even though I felt like I was running through molasses and I was dead tired.

The only thing I cared about was making sure no women passed me, and I was confident that they wouldn't if I simply maintained the effort. My time for this mile was 6:55. Not what I would have expected for a downhill mile! Keep in mind, I have run faster miles than this at the end of half marathons.

The last 0.18
As I turned onto the final stretch, which is uphill, I saw that there was a woman about 8-10 seconds behind me. That motivated me to start my final kick early. I didn't want her trying to pass me. It worked and I was surprisingly able to run a pace of 6:32 up that hill. Amazing what I can do when I'm threatened by competition!

My final time was 22:05 according to my Garmin, and 22:08 according to the official results. I know that the distance of my Garmin will usually not match the official results, but the official time should be the same or faster. I always start my Garmin before I cross the start line mat, and I stop it after I cross the finish line. So I don't know how they added an extra 3 seconds, unless they didn't get my net time, just my gun time. This has happened a few times in the past, and even happened at the last 5K I ran through this same race series. But last time, I wasn't even listed in the results at all so I had to talk to them. Since this isn't a PR for me, I didn't care enough to talk to them about it, but it's annoying.

After the race
Once I regained my ability to speak, I congratulated Amber who had finished over a minute ahead of me! I then cooled down and waited for Greg to finish his 20K. I figured I would run him in the last 0.2 miles, but when I tried, he was too fast for me, and I couldn't keep up. Turns out, his last mile was faster than my last mile! He's in excellent shape right now and does much better in the heat than I do.

Shortly after Greg finished, they started handing out the 5K awards and I won first place in my age group, which was the main goal. I do not think I would have placed in my age group at all if I had run the 20K, so I made the right choice.

Final thoughts and takeaways
I kind of bonked today, and I'm okay with that. I think it was a combination of going out too fast, not being in 5K shape (had to take 9 days off after the bike accident), and obviously the heat/humidity. I ran 4 miles at an average pace of 7:05 just over a week ago in cooler weather and on a flatter route.

Prior to this race, I had assumed that my max heart rate was around 190. This was based on running with my new Garmin + HR monitor for the past two months, and seeing it get up to 187 at the Firecracker 5K in July. Well, today it got up to 196!  And it averaged 186 for the last 0.18. This definitely shows that I ran the race to my fullest effort level and I was not slacking.

I ran this race over 40 seconds faster in 2017, but I was in really excellent 5K shape back then, and it wasn't quite as warm that year. It's not a helpful or relevant comparison, so I'll stop there.

I was the 7th overall female and it was a competitive field. The Leesburg 5K is a popular local race and the first two females ran 18:xx.

I'll be running two more 5Ks before I settle into marathon training, and I am excited to see how those go. Hopefully, much cooler!

Saturday, August 3, 2019

I will never be a cyclist.

Just hours after I published my "Running in Oslo" post last Saturday, my international running adventures came to an abrupt stop.

Greg and I had signed up for a group bike tour of Oslo on Saturday afternoon. There were 14 of us, and we were led by a local guide who worked at the rental bike shop. We had signed up for this "Oslo
By Bike" excursion a few months ago, and it was my idea. Greg was actually shocked that I wanted to ride a bike. I hate bikes! The last time I rode a bike was in 2007 when I rode 11 miles through Tuscany. And prior to that, I hadn't ridden a bike since around 1994.

But biking is always the analogy people use to talk about things you never forget how to do. It's like riding a bike, they say. If this had been a mountain bike ride, or a really long ride, I wouldn't have signed up for it. But it was only seven miles and it was two hours long. I figured it couldn't be that difficult. I could run, or even walk, that distance faster.

When I first got on the bike, it wasn't a familiar feeling. I had to remember how to balance, steer, etc. Unfortunately, there was no clear area in which to do this. The bike rental place was in the middle of the city and there were swarms of people everywhere. In, fact, we had learned yesterday on our boat tour that this was the busiest time of year in Oslo because many people had time off from work and it was a very popular tourist spot. Plus, the weather was warm and sunny which is not typical for Oslo.

I spent the first part of the bike tour frustrated and scared. We were led through crowded plazas, over speed bumps, up and down curbs, weaving through masses of people. This photo shows one of the areas we rode through, as seen from the boat the day before at the same time of day.

One of the crowded areas we biked through
We all had to keep stopping and starting and everyone was really frustrated with it. If I were a pedestrian in that area, I would have been annoyed by such a large group of cyclists plowing through the crowds.

Finally we were on a bike path and I felt more comfortable, and like I was starting to get a handle on the steering, the gears, etc. The guide then took us through a wooded area on a gravel path. It was hilly and curvy and there were roots sticking up, so it was much more difficult than anticipated. Finally I didn't feel like the worst cyclist in the group because I was able to go up the hills just fine and my athleticism kicked in.

We stopped at a beach for about 15 minutes (this is why the tour was long--we kept stopping). Greg snapped a photo of me and I posted it to my Instagram Story, saying that this was the last time anyone would see me on a bike. At that point, I knew that I had no desire to ride one ever again, That said, I was proud of myself for stepping outside of my comfort zone and getting on a bike. I wasn't looking forward to the way back, though, knowing we'd have to bike through that busy plaza. I also thought it was kind of a miracle that I didn't have an accident and wondered if I should take the bus back and end it on a high note.

Instagram Story mid-ride
We got back on the bikes and rode through the woods again. Only this time, I wasn't able to maneuver the bike as well I should have been able to. Since the path was wide, we were not riding in a straight line, and people were riding next to me. There was a fairly steep hill that curved around, and as it curved, I wasn't able to properly steer while also getting up the hill, so my bike hit the back of another rider's wheel, and I went tumbling. Nobody else fell, but I was on the ground with just a minor scrape. It was really scary, but since I wasn't hurt, I got back on the bike, vowing to stay away from the other riders.

We got back onto the bike path, which was great, but then it was time for the crowded plazas again. I don't know why I simply didn't get off the bike and walk it back to the shop. We were close enough at that point. If I really stopped to think about it, I would have done that, but instead I felt like I had to keep following the group over the curbs, the speed bumps, and the train railways.

There were actually two tour guides-- one in front and one in back. The one in the back told the one in the front that she needed to slow down on multiple occasions (every time we stopped), but she didn't slow down. At one point, the tour guided us to drive in the middle of the train railway. This area was clearly for trains only- not pedestrians or cyclists. To do this, I needed to cross over one of the railways to get in between them, as there was no room left on the right side of the railway. As I did this, my tire got stuck inside the rail and the bike stopped. I fell onto the bike, ramming my pubic bone directly into the bar. I screamed in pain and in fear. It was maybe the worst pain I had ever experienced.

I walked away from the train track full of fear, and Greg and the tour guide from the back of the group came toward me. The other riders and the guide in front had no idea that I had fallen. Since we were so close to the bike store and the cruise ship, the tour guide from the back took our bikes from us and we walked back to the ship to get an X-ray. It hurt to walk, but thankfully, I was able to walk.

Back on board, I found that the entire left side of my groin was hugely swollen. They did an x-ray and found that nothing was broken. I was in extreme pain, but they weren't able to give me anything except for Advil and an ice pack. I really liked the nurse and the doctor, but they weren't specialists in this kind of thing and weren't able to give me stronger pain medication. That night, Greg and I ordered room service as I continued to ice the area.

4 days post accident
The swelling and the bruising were severe over the next five days. Today, one week later, the bruising is still dark blue over much of that entire area, and looks worse than this photo, extending all the way down to almost my knee. Seeing so much swelling and bruising made matters worse, as it was a constant reminder of how harsh the blow was.

I tried my best to enjoy the rest of the trip, which included stops along the coast of Norway, ended in Bergen. I was in constant pain, and walking wasn't easy, but it didn't seem to aggravate the issue. The worst part was not knowing the extent of the damage. All I knew was that the area was very swollen and painful, and I had a sizable hematoma. Regardless, Greg and I had paid a lot of money for the trip and been looking forward to it for over a year, so I wasn't about to let this accident ruin it for me. As I wrote about in my previous two posts, I love running around new areas on vacation. So it was definitely a bummer to not be able to run in the port stops during the rest of the trip.

We returned home on Thursday evening, and I saw a doctor yesterday. The swelling is gone, but I have a big bump on the left side of my pubic bone, which is the hematoma itself. Even at rest I have a small level of pain, and running definitely aggravates it. My doctor was able to isolate the muscle group that was impacted, and it's the lower abdomen. Thankfully, all of the adductors are in great shape. I never realized that the lower abdomen was used so much in running, but it is painful with each toe-off, so I guess it's pretty critical.

So as of now I have the constant pain of the hematoma, as well as an inflamed/irritated lower abdominal muscle that is painful to run on or to move in certain ways. I do not know when I will be able to run again.

I think this injury is difficult for me on a number of levels, mostly because it feels like something was taken from me.

1. I wish I would have followed my gut instinct and gotten off the bike instead of following the group over the rail tracks.

2. I have been taking it easy all summer with running and had planned my race schedule around being able to start training more seriously after this trip. Instead, I'm digging my hole deeper and will need to rebuild before progressing. I really thought I'd be able to crush a 10K in early October, but now I'm doubtful.

3. I don't know when I will be able to run again, so I am dealing with uncertainty and things being up in the air. And even if I am able to run, I don't know how long it will take to be completely pain-free.

Now that I've gotten that off of my chest, I do have the perspective that I am lucky the accident wasn't worse. I wasn't seriously injured and I can walk. Nothing is broken. This isn't as bad as having mono because I am still able to walk around, go to work, and live my non-running life.

I do blame myself for not trusting my instincts and for following a group of people who were riding in areas that I felt unsafe in. (Later, the other people on the bike tour said that they felt unsafe, too, and didn't find the ride enjoyable because of all the obstacles. One person also got their tire stuck in the railway, but he was able to stabilize himself and not fall.) But, on the other hand, I am not beating myself up too much because I was just trying to get the most out of our time in Oslo, even though it meant hopping on a bike.

Saturday, July 27, 2019

Running in Oslo

Wednesday, July 24: Alborg, Denmark
After leaving Warnemunde, Germany, our cruise ship headed for Alborg, Denmark. We were sailing for the first half of the day, which meant it was impossible to run outside. We could have opted for the treadmill, but neither of us were interested in that and we had planned a few days off on this trip, too.

Alborg (or Aalborg) was fun. We had signed up for a Danish Beer Walking tour, but due to low registration, the excursion was cancelled. This ended up being a good thing because we got our money back and discovered we could easily do the exact same thing on our own for less money.

We paid about $20/each and that got us 6 drink tickets and small souvenir glasses that say "Aalborg Beer Walk" on them. Totally a tourist thing to do, but hey-- we are tourists! There were 8 participating brew pubs of which some were closed at that time of day (2:00). We ended up visiting three different pubs and getting two beers at each. Don't worry- they were small pours in the souvenir glass!

It was a fun way to explore the town while also tasting different beers. One of the brew pubs was an actual brewery that brewed their own beer and that was awesome.

Thursday, July 25: Gothenburg, Sweden
Our next stop was Gothenburg, Sweden. We docked at 8:00am, which meant we couldn't get off the boat until 8:00am. . .  which meant the sun was already really high in the sky. I didn't mind too much; at least I was staying acclimated to the heat!

Gothenburg, Sweden
We didn't really have a plan for where we were going to run in Gothenburg, which I liked. We just followed a running path along the water, and occasionally veered off it into parts of town. We encountered a few steep hills whenever we went away from the water, and wandered into some small residential areas. My favorite part of this run was going through a small park area that was well shaded. Overall, I felt energized and strong. We ran for 75 minutes, as prescribed by my coach, and ended up with 8.5 miles.

The cruise offered a free excursion called "Gothenburg Panorama" which we learned was simply a bus ride around the town. We decided we would rather explore by foot, so off we went! I wasn't overly impressed with Gothenburg, to be honest. It was nice, but there wasn't anything particularly distinguishing about it. We mostly walked through the park along the canal. It was enjoyable, although we were struggling with how hot it was. It's been about 10 degrees above average here for the entire duration of our trip. I don't mind it so much, but I had been expecting highs in the 70's, not highs in the 80's.

There isn't too much else to say about Gothenburg. I would have much preferred to visit Stockholm, which is still on my bucket list, but the cruise didn't travel there. We were hot and tired from walking around in the sun so we returned to our ship at around 4:00. That allowed us to use the ship's free self-service laundry before dinner! What a great amenity, given how long the cruise is and how sweaty the clothing has been getting. Of course, I don't trust my running clothes in those machines with their soap, but we washed pretty much everything else. We then ate dinner, walked around the ship and went to bed. Before we move on to Oslo, here is another photo of the Gothenburg run:

My favorite part of the Gothenburg run

Friday July 26th: Oslo, Norway
We arrived in Oslo on Friday morning. We cruised through the Oslofjord to get there and the views were stunning. The Olsofjord is absolutely gorgeous there we watched from the top deck of the ship as we slowly pulled into the port.

We were able to get off the ship at 8:00am. There was another runner waiting to get off right away too--and he was wearing a Boston Marathon hat! Turns out, this guy had run over 60 marathons, and many of them were Bostons. Given that most people on this cruise are in their 60's and 70's, and the boat only holds 900 passengers, we did not expect to meet another runner, let alone such an avid marathoner!

The three of us started our run together, and we decided it would be best to stick to the waterfront. I love running close to water, and it also makes it easy to find your way back! After about two miles, the other runner told Greg and I to go ahead and he stayed back. Even though it was once again very
Oslo, Norway
sunny and warm, I felt great. For me, 72 degrees usually equals 95-100% humidity, so anything less than that makes 72 feel tolerable. I loved this route. The path was easy to follow, there were plenty of other runners, and the views of the water were beautiful. There were definitely some hills, but nothing too crazy. Once again, we planned for 75 minutes, which ended up being 8.6 miles.

After finishing the run, we showered, had a quick breakfast, and went back out to explore the castle that was literally right next to our cruise ship. Running at 8:00am meant missing the "real" breakfast, which closed at 9:30, but there was a smaller cafe place open that served waffles. Anyway, we explored the castle for a bit, which was super cool, and then got ready for our afternoon excursion: a boat tour of the city.

This boat tour was AMAZING. Seriously the best thing we have done so far on this vacation. It was an old fishing boat built in 1940, which held about 150 passengers. Thankfully, the boat was only half full so there was plenty of space to move around and take photos. There was also a bar on the ship, and two included drink tickets for beer and wine. There was even a cover over part of the boat so we had shade. This was a lifesaver since it was 85 degrees out! Combined with the breeze from moving so quickly, the weather was close to ideal.

We passed by all of the Oslo landmarks that you can see from the water, and sailed down the Oslofjord and back. A tour guide explained everything over the loud speaker which was nice. It was
Oslo boat tour
so relaxing and beautiful and just perfect! During the boat tour, the guide mentioned that Oslo had an Ice Bar. I had heard about the Ice Bar in Stockholm, and had always wanted to go.

An ice bar is a bar that's made of ice, and it's supposedly 20 degrees to keep everything frozen: the bar, the sculptures, the tables, the seats, etc. After the boat tour, Greg and I headed into the city to check it out. They handed us heavy ponchos and gloves and in we went. Once again, this was a total tourist thing to do, and it's not a place that the locals hang out. But it was cool-- literally! I don't think it was 20 degrees, but it was cold, and the drinks were really good. I had a cocktail that was green, and Greg got a blue cocktail.

We were only in the Ice Bar for about half an hour, and then I got really cold, so we left. We took the scenic walk back to our ship, and I determined that Oslo is now one of my favorite cities. It's so beautiful with fountains everywhere and the architecture is a mix of old and new.

Saturday, July 27th: Oslo
The boat stayed docked in Oslo overnight, which meant we didn't have to wait until 8:00 to start our run. Ironically, this was the only day where my body naturally "slept in" and I didn't wake up until 6:15. I had thought we'd be able to start our run at 6:30, no problem! Anyway, I planned to fill my hand-held water bottle with one of the bottles that they give you as you exit the ship. But at 7:00am, the water bottles aren't available. So I went to the bar nearby, and asked the bartender to refill my bottle. I was (more than) slightly annoyed because before she could fill my bottle, she had to make someone an alcoholic beverage. At 7:00am! I selfishly believed my need for water to be able to start my run was far more important than someone's need to drink alcohol at 7:00am, so I became irked.

One thing I've learned about myself on this trip, which I kind of already knew, is that if I can't get my run started when I want to, I become irritable. I'm like a caged tiger, just raring to go.

The Oslo Opera House: we ran up that roof
Finally we were off. This run was a lot of starting and stopping for multiple reasons. First, my Garmin was acting funky. It's a brand new Garmin, but sometimes the buttons stick, which means it will randomly stop, and I won't even know it. In this case, we wanted to stop and take photos, but I couldn't get my Garmin to stop because of the sticking button. Second, there were a lot of great photo opportunities so we stopped on purpose. Third, we weren't exactly sure where we were going, so we stopped to look at the Google Map and get our bearings.

I hate stopping during my runs, and we probably stopped like 8-10 times. But, it was all for a good cause. We were exploring the city and take photos.

To start, we headed about half a mile from our cruise ship to the Opera House. This is a famous landmark here in Oslo, and we had learned from the boat tour that you could walk up on the roof. So, what did we do? We ran up the very steep roof until we reached the top! Once at the top, we took photos, and then ran back down to the bottom.

After that, it was time to find our planned route, which was up the canal path. Greg read that this was one of the best places in Oslo to run, and that it was flat. LOL! So not flat. The hills were so steep on this path that I had to walk at times. The surface of the ground kept changing: gravel, stone, dirt, concrete, wood, asphalt... pretty much anything you can imagine. I should also mention that it wasn't easy getting to the start of the path. We ended up having to run through a train station because we didn't see any other way to cross the tracks. Definitely an adventure.

Vigeland Park, Oslo
Finally, I told Greg that I was done with that path. It was really beautiful and interesting, but I couldn't handle all the hills and the changing of surfaces, etc. I think we ran about two miles on it, so we definitely experienced it. Fortunately, we stopped at a road that was a straight shot to Vigeland Park, which was also on the list of the top places to run. And we had seen this on a map previously and it looked nice.

We ran about two miles through the city to get to the park, and once we were there, it was totally worth it. Beautiful fountains, sculptures, monuments, flowers, etc. However, it wasn't very large. I would have been happy to run laps around the park, but it was unclear which way to go so we kind of just zig-zagged through the park until we found ourselves running on a gravel trail. The gravel trail became very hilly and all of a sudden we realized we were on a trail, and not in the park. So we stopped again and looked at the Google Map.

We quickly found our way off of the trail, back into the city, and headed for the cruise ship. We ran a total of 10.1 miles and made a huge loop around the city. I had been planning for a little more, but I was ready to be done at that point. I had not anticipated so many hills and it was also quite hot and sunny.

Stay tuned for more as we continue on the cruise up the coast of Norway.

Wednesday, July 24, 2019

Running in Copenhagen

Hello from Europe! This is my 400th blog post and I am writing it from the deck of the Viking Sky cruise ship, on the North Sea between Denmark and Sweden. We are sailing this morning, so I have some free time to write.

Sunday, July 21: Copenhagen arrival
Nyhavn, Copenhagen
We took an 8-hour overnight flight direct from Dulles to Copenhagen, arriving at 7:15am local time. Crammed in the back of economy class, neither Greg nor I were able to really sleep, and we estimate that we each got maybe a total of one hour.

We arrived at the cruise terminal at 8:00am, and we had to wait for two hours before we could board the ship. I took the opportunity to sleep more, since the cruise terminal chairs were more comfortable than the airplane seats.

We finally boarded the ship, took a quick tour, and then ate lunch before heading out to explore the city. We were both struggling pretty badly, given that we only had one hour of sleep, but walking around Copenhagen energized us. Neither of us had ever visited there, so everything was new to us. Our first stop was Nyhavn, the city's scenic and historic waterfront. Whenever you see a photo of Copenhagen, you likely see this waterfront. Of course, it was way more crowded and touristy in person than in the photos, but still really cool.

After Nyhaven, it was off to Stroget, a huge pedestrian shopping plaza. It was here that I broke my 5-week chocolate fast. My doctor recommended that I eliminate all caffeine from my diet, so I had not had an ounce of chocolate since early June. I didn't go crazy with the chocolate, but Greg and I shared an ice cream sundae that had chocolate candies in it. Afterwards, we returned to our cruise ship where we had an amazing gourmet meal. Once again, we found ourselves struggling due to lack of sleep, so we skipped dessert and proceeded to sleep for about ten hours.

Monday, July 22: Copenhagen
Our first order of business upon waking up was to go run! Sunday was obviously a day off from running, so I was excited to run in a new country and add Denmark to my list of countries I've run in.
The Viking Sky, Copenhagen
We didn't really know where we were going so we just winged it. We ran off the cruise ship, down a long stretch, passing by the famous statue of the Little Mermaid. We then ran through a park, which was a big loop, and returned to the boat. We had planned to run for an hour and 15 minutes, but in order to get back in time before breakfast closed, we cut it short a little. I ended up running 7.5 miles in 1 hour, 6 minutes, at an average pace of 8:55.

After breakfast, we left the ship to explore more of Copenhagen. Greg had our path all mapped out, so I just followed. To get into the city, we walked the same path that we had run on, but this time we were able to stop and take a photo of the Little Mermaid statue. There were also about 50+ Santa Clauses hanging around the statue, which I later learned was the annual Santa Claus World Congress, which occurs every July in Copenhagen. Some of the Santas formed a band to play Christmas music. It was quite a sight to see.

Then we walked through two parks, the second of which was King's Garden. King's Garden is perhaps one of the most beautiful parks I have ever been in. There are colorful flowers everywhere, and if you look up, you can see all the historic buildings surrounding the park. We then walked
King's Garden, Copenhagen
through the Stroget shopping district (further than we had been before) and that led to the Tivoli Gardens amusement park. Even though we had no interest in riding the rides, we bought tickets to enter the park to check it out.

We didn't spend long in Tivoli, but it was really fun and beautiful to walk around. Afterwards, we proceeded to Christiansborg Palace where Greg took photos. So many beautiful and historic sites all in one day!

We had explored all of this by foot, so by the time we got back to our cruise ship, I had logged 30,000 steps for the day, with only 13,000 of those being from running. It was exhausting but fun.

Tuesday, July 23: Warnemunde, Germany
On Tuesday, the plan had been to go to Berlin. The ship docks in the beach town of Warnemunde on the Baltic Sea, and then they transport you into Berlin, which is 145 miles away. This required waking up at 5:00am and meeting in the ship's atrium at 5:50.

It was hard waking up that early (which is like waking up at 11:00pm, east coast time) but we did it. Shortly after waking up, Greg started talking about staying in the town we were docked in and not making the journey to Berlin. With only 30 minutes to make a decision, we started Googling stuff, and we realized that the train ride into Berlin would be 3 hours each way, and it wasn't air conditioned. We wouldn't have a full day to explore the city (more like 4 hours) and the majority of our day would be spent on a warm train. So, we decided to skip it. Kind of crazy to miss a trip to Berlin, but we later learned that the train ride was actually 3.5 hours each way (best case) and we preferred to spend our vacation relaxing. Plus, we were docked in a really nice area!

It was now 6:00 and we realized we could get off the ship and go run. Originally we were planning for Tuesday to be another "off" day, but now we had the time and freedom to go run around the port. I decided we should do the tempo run that had been scheduled for Wednesday. On Wednesday, we would be sailing all morning, so we planned to run the tempo on the treadmill. Now, thankfully, we could run it outside in Germany.

We looked on Google Maps and the route we really wanted to take required getting on a ferry, so we
Warnemunde, Germany
settled for running on the boardwalk of the beach. We found a one-mile stretch that was pretty empty at 6:00am, so after warming up, we ran back and forth on that 4 times, until our Garmins reached 4 miles for the tempo.

It was 63 degrees, sunny and windy, so the run was somewhat challenging. But at least it was flat and not as humid as back home. I hadn't run a tempo run since the Sugarloaf Marathon in May, so I was definitely rusty. I guess the Firecracker 5K was a nice dose of speed, but still- I wasn't really in "tempo" shape.I set the pace and Greg kept up. Our splits were 7:05, 7:05, 6:57, 6:58. It was definitely hard, and I struggled mentally during the third mile, but I was determined to make it all the way through and not quit.

It was a huge sense of accomplishment when we finished. Best of all, this meant no treadmill tempo the following day! We did a cool down jog back to the ship where we showered and had a leisurely breakfast.

It was then time to explore Warnemunde. We had seen a good part of the town on our run, but now that we were back there, all the shops had opened and the place was bustling with visitors. We went down to the beach, which was gorgeous and full of people. However, the beach area between the boardwalk in the ocean was so wide that there was plenty of room for everyone. This beach was at least twice as wide as the beaches on the east coast that I've been to. Greg took some photos, we went
Chillin' in Warnemunde
into a few shops, and then returned to our ship to relax for the rest of the afternoon.

Even though Berlin would have been an adventure, we were content simply relaxing on the ship deck near the pool. We even took advantage of the afternoon tea service aboard the ship, which consisted of tea, scones, and all the little finger sandwiches.

After digesting our teatime snacks, we headed down to the gym for some strength work. I am doing the "Marathon Legs" strength training program which is available through McMillan Running and it requires doing the program twice per week. I've now been at it for a full month and I've really progressed. I am finally able to complete all the required sets and reps prescribed for week one, and ready to progress to week two.

We then had another gourmet dinner, and spent the rest of the evening hanging out on our state room balcony as the ship set sail. This morning, we are still sailing, headed toward Alborg, Denmark. I am not sure when I will check in again, but stay tuned to find out about our time in Alborg and Gothenburg, Sweden (Thursday).