Showing posts with label hike. Show all posts
Showing posts with label hike. Show all posts

September 9, 2012

August 2012

Running

Howl at the Moon

August was consumed by tapering for Howl at the Moon, running Howl at the Moon, and recovering from Howl at the Moon. Over half of my miles in August came in that one day. The rest of my runs were very short, but the average distance per run was heavily skewed by Howl. My knees took a real beating during the last 10 miles of that race, so I've been super cautious with my recovery to ensure I don't have any long-lasting injuries as a result.

MonthDistance# WorkoutsAvg per Workout
January78.06 Mile98.67333 Mile
February75.2586 Mile98.36206 Mile
March126.15 Mile149.01071 Mile
April146.28 Mile169.1425 Mile
May166.75 Mile189.26389 Mile
June54.83 Mile77.83286 Mile
July115.76 Mile912.8622 Mile
August91.81 Mile910.2011 Mile
Total854.899 Mile919.39449 Mile

Running 2012 8


Cycling

Team & race volunteers

The weird thing about my knee pains is that while I have recovered reasonably well with respect to running, I can't say the same about cycling. 10 days after Howl I went to my regular Tuesday night practice race and by the end my knee was killing me. I took another week off of cycling. The next week I intended to go back but I didn't make it 2 miles from home before my knee started to hurt. I took 2 more weeks off of cycling. At this point I've only done one serious ride in the past 6 weeks, and that one didn't go well at all. Now that road racing season is over I can just wait this thing out and make sure it's gone before starting up in earnest again. I'd like to do some cyclocross racing this fall, so hopefully I'm back to 100% soon.

BikeDistance# RidesAvg per Ride
Pocket Rocket18.7 Mile53.74 Mile
Thundercougarfalconbird63.17 Mile321.0567 Mile
Total81.87 Mile810.2338 Mile

MonthDistance# WorkoutsAvg per Workout
January25.33 Mile212.665 Mile
February40.08 Mile313.36 Mile
March213.43 Mile2010.6715 Mile
April253.27 Mile2311.0117 Mile
May322.147 Mile2413.4228 Mile
June282.57 Mile1321.7362 Mile
July260.12 Mile1616.2575 Mile
August81.87 Mile810.2338 Mile
Total1478.82 Mile10913.5671 Mile

Cycling 2012 8


Walking/Hiking

In the pack

I made up for the lack of cycling with a bunch of walking and hiking. This doesn't hurt my knee at all, and I'm more convinced than ever that walking/hiking is actually remarkable effective training for long/ultra distance running. It allows you to put in a lot of time on your feet, working your legs, without the impact of running.

MonthDistance# WorkoutsAvg per Workout
January51.53 Mile163.22063 Mile
February42.92 Mile182.38444 Mile
March41.15 Mile142.93929 Mile
April31.89 Mile122.6575 Mile
May37.5107 Mile132.88544 Mile
June39.4 Mile182.18889 Mile
July2 Mile2Mile
August64.99 Mile252.5996 Mile
Total311.391 Mile1182.6389 Mile

Walking 2012 8


Swimming

It's both fortunate and unfortunate that I don't have to swim much to maintain my fitness for swimming. I just have little motivation to spend time in the pool, when I could be doing any number of things that are even more enjoyable. There's a chance I might to one more triathlon this year, but that depends on whether my knee feels well enough to bike.

MonthDistance# WorkoutsAvg per Workout
January000
February000
March000
April1750. Yard2875. Yard
May8050. Yard71150. Yard
June4100. Yard31366.67 Yard
July2993.61 Yard3997.871 Yard
August2150. Yard3716.667 Yard
Total19043.6 Yard181057.98 Yard

Swimming 2012 8

April 30, 2012

January - April 2012

Running

IMG 0635

Running has been going well. Extremely well. I almost hate to admit that because it probably means I will injure myself at any moment. But hopefully not. I've been focusing a lot on my form as I try to transition to a forefoot strike pattern (rather than a heel-strike pattern). It's hard to try to correct 18 years of bad form. Really hard. But I'm making progress. I ran farther in April 2012 than I did in any other month in the last 10 years, and I haven't had a hint of knee pain. Of course, some of that has come at the expense of really sore calves on account of using different muscles that are much less well developed. I'll take sore calves for a few hours over semi-permanent knee pain 10 times out of 10.

I found a great place to run barefoot: the glorious artificial turf on the WUSTL track infield (some people might call it a football field). Of the 146 miles I ran in April, 19 of them were completely barefoot, and some of those were pretty fast (5:32). The majority of the remaining miles were in my wonderful new Luna Sandals (yes, sandals), with the rest in my Vibram FiveFinger Bikilas, Merrell Trail Gloves, and New Balance MT 110s. I guess I have something of a shoe fetish (yet I still run barefoot). I just pick the thinnest shoes I can get away with based on the route I have in mind, and take them off whenever I can.

MonthDistance# WorkoutsAvg per Workout
January78.06 Mile98.67333 Mile
February75.2586 Mile98.36206 Mile
March126.15 Mile149.01071 Mile
April146.28 Mile169.1425 Mile
Total425.749 Mile488.86976 Mile

Running 2012 4


Cycling

IMG_4020

Photo by Jeff Schleicher

I've been a regular at the Tuesday night crits, though I did miss a couple. I've been lucky to get two training rides a week. Considering where I started at the beginning of this year I've already come a long way, but I still have a long way to go. Looking at my race results over the past year or so it's pretty clear where my talent lies.

Single digit placings are better than double digit placings. If I want to achieve more success in cycling races I'm going to have to spend more time (which I don't have) practicing. Or maybe blood doping.

BikeDistance# RidesAvg per Ride
Bianchi34. Mile93.77778 Mile
El Fuego20.04 Mile120.04 Mile
Lynskey13.64 Mile26.82 Mile
Pocket Rocket27. Mile64.5 Mile
Thundercougarfalconbird158.59 Mile531.718 Mile
Total253.27 Mile2311.0117 Mile

MonthDistance# WorkoutsAvg per Workout
January25.33 Mile212.665 Mile
February40.08 Mile313.36 Mile
March213.43 Mile2010.6715 Mile
April253.27 Mile2311.0117 Mile
Total532.11 Mile4811.0856 Mile

Cycling 2012 4


Swimming

Yes, the numbers are small. I just started late in the month. What's promising, though, is just how quickly I was able to pick this back up after months off (and if you don't count that week in September, years off).

MonthDistance# WorkoutsAvg per Workout
January000
February000
March000
April1750. Yard2875. Yard
Total1750. Yard2875. Yard

Swimming 2012 4


Walking/Hiking

MonthDistance# WorkoutsAvg per Workout
January51.53 Mile163.22063 Mile
February42.92 Mile182.38444 Mile
March41.15 Mile142.93929 Mile
April31.89 Mile122.6575 Mile
Total167.49 Mile602.7915 Mile

Walking 2012 4

June 16, 2010

The many hills of San Francisco

Last week the whole family was out in San Francisco while I attended Apple's Worldwide Developer Conference (WWDC). This was my ninth WWDC (two in San Jose and seven in San Francisco), missing out only in 2006 when Apple held the conference in August (for some reason) the week after we moved to Nicaragua.

The conference was good, even if the ridiculously growing size does get a little more frustrating each year. The technical sessions are all covered by non-disclosure agreements, so I won't discuss any of them (as if you cared).

The keynote (which some of you may remember I participated in back in 2005) was also good. Unfortunately, due to the size of the conference I keep showing up earlier and earlier to get in line for the keynote and I keep ending up farther and farther back in line. I showed up a little over three hours early this year. The line was nearly one mile long, and I barely squeaked into some of the back rows of the conference room filled with over 5,000 people. The new iPhone looks pretty awesome. In fact, William just bought me one for Father's Day. Wasn't that nice?

Will in the big city

While we were there I purposely didn't adjust to the different time zone so I would continue wake up early to go for a ride on the Pocket Rocket each morning before the conference. The first morning I tackled Twin Peaks, which, at over 800 feet above sea level, is one of the highest points in the city. Shortly after the climb begins it kicks straight up to 17%, which was a tough first hill for someone who lives in Illinois. It stays steep for a good long three city blocks before leveling out to a more reasonable 11-12%. Of course, it was super foggy that particular morning, so I couldn't see anything at the top. If I could have seen anything it would have looked like this (photo from last year).

Market Street

Anyway, I had to hurry straight back in order to stand in a really long line for hours. It was just eight miles with a total of 850 feet of climbing entirely in the third and fourth miles.

The next day I rode up one of the steepest hills I've found in the city (Kearny between Broadway and Vallejo, the road is closed to traffic). It's somewhere in the ballpark of 25-30%. I had to lean really far forward to keep from tumbling over backward. Yes, that steep... but only for a block. After that was Telegraph Hill up to Coit Tower. This climb was used in the prologue of the Tour of California the first few years of the race.

Financial district

But that was just the first few miles. I followed the bay shoreline to the Golden Gate Bridge and rode across to the Marin Headlands. I intended to climb Hawk Hill, but the road was closed half way up so I took a detour to somewhere I'd never been before, which was amazing.

Marin

Marin

Beach

Tuesday's ride had 2200 feet of climbing in 26 miles.

Wednesday I took a break because I felt a little twinge in my calf after Tuesday's ride and I didn't want to risk making it worse. Fortunately the twinge only lasted a day and by Thursday morning I was back at it. I hit Twin Peaks again, this time better prepared for the steepness. Instead of turning around there I continued on through Golden Gate Park, Ocean Beach, past the Cliff House, the Legion of Honor, the Presidio (along the bike course for the Alcatraz Triathlon I did in 2003), across the bridge to the Marin headlands, and partway up Hawk Hill before turning around and heading home. Just for kicks I rode up Russian Hill and Nob Hill on the way back through town. Russian Hill on Hyde street is 23% for a few city blocks--too steep to sit, too steep to stop (you wouldn't be able to start back up).

City

Grade

Thursday's ride was 2800 feet of climbing in 27 miles.

Friday I tackled Mt. Tamalpais for the Nth time. Last year I rode Mt. Diablo instead, so I was happy to be back on familiar ground. After cool weather all week it was super hot on Friday. This made the mountain that much more difficult. I doubt I made my fastest ascent of the mountain that day, but I steadily knocked out each of the 10 miles from bottom to top.

Mt. Tam may not be as high as Mt. Diablo, but it sure is a lot more scenic, offering a lot more wooded areas, as well as ocean views.

Mt Tam

Mt Tam

Mt Tam

Mt Tam view

Mt Tam view

San Francisco from the top of Mt. Tam

Bridge and Mt Tam

Here's the opposite view: Mt. Tam from San Francisco

Friday's ride was 4114 feet of climbing (2500 on Mt. Tam) in 50 miles.

Saturday I skipped a ride in favor of lots of walking and hiking with the family. Here's William and me hiking the coastal trail, which was part of the run course for the Alcatraz Triathlon I did in 2003.

Two sweaty guys hiking the Coastal Trail

We all had a great trip. Check out William's blog for lots more family photos.

December 7, 2009

The Strangest Marathon

I was moving along at an easy pace. The guy in front of me had just taken a downhill section of the trail very gingerly and nearly tip-toed across a creek crossing. I passed him on the uphill section on the other side of the creek and began to pull away. Then, out of nowhere, I hit the wall. Well, not exactly. I'm not talking about the glycogen depletion "wall" where my fuel reserves have run dry. This was something entirely different and unfamiliar to me. This small incline got my heart beating so fast I was gasping for air only to find I was physically unable to maintain my modest pace. My worst fears had come true. I stopped to walk up the hill. By the time I reached the top I was seriously contemplating dropping out of the marathon.

This was at mile four.

One week prior I was in great spirits, having wrapped up my long training runs and raced fairly well at the FOLEPI River Trail Classic. I showed up at work on Monday feeling as good as possible and left work that evening with a sore throat. My throat got worse through the night and was a full blown illness by Tuesday morning. I went to work (even though I clearly shouldn't have) only to discover my coworkers were already sick.

By Wednesday my throat started to get better, but the snot and sinus pain got worse. By Thursday evening I was finally starting to feel like I was getting over the sickness. I still wanted to race. I trained really hard for Tecumseh and I wasn't going to let the sniffles take that away from me.

Friday I travelled to the Nashville, IN area with fellow Buffalo Ken, Brian, and Jen. We stayed at the same paintball/cabin place as last year (though with far fewer people this time). Despite feeling back to normal that morning, by Friday night I felt terrible again. Ugh.

I awoke Saturday morning before the race feeling as fresh as a daisy. Whatever I had seemed to finally work its way out of my system. I thought. We drove to the race finish area, picked up our packets, and loaded up onto the buses to the starting line miles and miles away.

Tecumseh course map

Last year I started way faster than I wanted to, but it was kind of necessary because of the congestion on the single track trail that started 2-3 miles into the race. I vowed to start off slower this year. I ran nice and easy the first mile only to look down when my GPS beeped to read 7:20. The exact same time as last year (and faster than my first mile at the Rockford Marathon where I ran my PR in May). That was the bad news. The good news was that I felt spectacular. Even though that pace felt super easy I made a conscious effort to slow down anyway. For the trail was not nearly as congested as it had been the previous year at this point. Despite the superior weather conditions (sunny rather than snow storm) everyone else was moving slower.

I hit the second mile at 7:29. So much for slowing down. It still felt really easy. I was barely exerting any effort. Still, I decided (once again) to consciously slow down. I hit the third mile in 7:23. Oh, come on. This was too easy. That would be the best I felt all day. We entered the single track trail through the woods, ran down a hill, over a creek, and started back up the other side when my world began to fall apart. This was not going to be my day.

After the first miserable uphill I walked I tried to shake it off and continue on like nothing had happened. I got back up to a comfortable pace on the flat sections of the course, but on the next uphill I found myself gasping for air and walking once again. If after four miles I wanted to quit, then after six miles I really wanted to quit. At this point I decided to stop racing. At the current rate I couldn't possibly have finished. Instead I slowed down (a lot) in the hope of just dragging myself to the finish line, regardless of time or place. Tecumseh was now a training run. Or so I told myself.

Rob at Tecumseh Marathon

I ran super slow the next four miles, frequently stepping aside to let people pass me on the trail. At the 10.6 mile aid station Ken passed me. Prior to the race I was voted by the others the mostly likely to finish the fastest of our group, and as such I was entrusted with the only key to Ken's car. Here, 16 miles from the finish and still slowing down, I quickly whipped out the key from my back pocket and handed it to Ken, who kept it for the remainder of the race.

I ate a banana at this aid station and it actually started to bring me back to life. For the first time in many miles I didn't feel like I was about to die. Ken pulled quite some distance ahead as I walked up the next few hills. Once I got to the flat and downhill sections I just ran a comfortable pace and I actually caught back up with his pack. The thought entered my mind that I might actually be able to keep up with him until the end. Of course, the next uphill section would put that thought out of my mind and I fell behind again. But what goes up must come down and before I knew it we were together again (briefly) at the 15.8 mile aid station. We were running different races, but by not keeping up with him I had just kept up with him for five miles. We ascended once more, and once more I was alone.

Prior to this point I just felt bad for much of the race, but around miles 16-17 I actually started to get tired. I wasn't picking my feet up, and as a result I stumbled a few times. I almost went down around mile 17, though I was able (with great determination) to stay upright. But this came at the cost of both calves, both hamstrings, and my right hip cramping at the same time while I tried to catch myself. Shaken, I walked for a bit with my head hung low. After a couple minutes I heard someone yell at me from behind, "Hey, you missed the turn."

You have to pay attention.

I got back on the trail and started running, fighting cramping muscles. There was a big hill at mile 19, a moderate hill at mile 21, then it was mostly downhill to the finish. I got another banana in me and, again, it brought me partly back to life. I was able to pick up the pace a little and before I knew it I had caught up with and passed Ken... just in time to trip and go down. I remained on the ground long enough to work out the cramp in my calf. Then I was back up and moving quickly again.

I had to concentrate really hard through a short, beautiful section of pine forest where the tree roots stuck up really far from the trail. As much as I had been dragging my feet I thought for sure I was going to hit the deck again. I didn't.

My pace continued to increase. I wasn't running for a faster time. I was running to get to the finish faster so I could stop running sooner. People often joke about doing exactly this, but I'm completely serious here. I took a short break to walk up the final hill with less than a mile remaining then ran all the way through the finish. Heading into the chute I caught up with a young woman who heard me cough right behind her and took off that last few meters. I congratulated her on the fast finish after the race at which point she informed me she thought my cough sounded like a woman and she really wanted to keep her top 10 finishing place. Ha!

Another 26.2

I finished in 4:20, my slowest marathon yet (by a mere two minutes). Last year, on the same course, in the snow storm, I ran 3:54. That was a really great race for me. I knew I didn't have the fitness for the same performance again this year, but (given the better conditions) I thought for sure I would be able to equal that time. No dice.

This was a very strange race for many reasons, perhaps the strangest I've ever run. I felt great, then crappy, then okay, the crappy, then just fine (and so on). I ran fast, then slow, then moderate, then slow, then fast (etc). I was freezing, then comfortable, then hot, then cold, then hot, then cold. I actually ran about 8 miles wearing a single glove because my left hand was cold but my right hand was not.

The really strange thing, though, is that none of these dichotomies coincided with each other. I ran fast while feeling good. I ran fast while feeling bad. I ran slow while feeling good. I ran slow while feeling bad. I was hot while running slow. I was cold while running fast. And every other permutation of the aforementioned states.

Anyway, I wasn't thrilled with the outcome of this race, but I did finish and I did learn some valuable lessons. Namely, you can't run as fast when you're sick as you can when you're healthy, AND trying to do so will make for a fairly unpleasant experience.

October 25, 2009

The Tale of Two Trails

The Allerton Trail Race was this morning. As you may recall, I've been scouting the course the past two weekends.

On the 11th the course was flooded pretty badly in four places. Everywhere else the trail was muddy, but runnable. The water came right up to the edge of the trail.

On the 18th the water was a couple feet lower and there was no real flooding.

On the 25th (race day) the right height was, well, this chart speaks for itself.

Sangamon River height

The water was 3.5 feet higher than it was when there was serious flooding. Half the trail was literally under water. Fortunately, the race organizers changed the course to keep this a running race rather than a swimming race. The new course used some parts of the old trail, but added a few new parts that have never been used before.

Despite my best intentions of starting out easy, I started out fast. I quickly settled into 10th place before the end of the first mile. We crossed the big meadow where the finish line is located, but we were just getting started. The big rolling hills slowed me down, but they slowed everyone else down too. We ran back into the woods towards the minotaur before heading down a large set of stairs, only to immediately turn around and run right back up them.

A short distance later we hit water. This wasn't a crossing, it was knee deep standing water on the trail. For 200 meters. I leaped through it only to find the trail very uneven and root-covered under the water (where I couldn't see it). After a couple hundred meters the people in front of me finally decided it was better to run through moderately dense brush beside the trail than to brave the water any longer. I followed suit, as I'm sure did everyone behind.

With the frigid water behind my wet calves were now numb and I was running even slower. As we approached the Sun Singer I noticed the leader was heading back down the trail towards me, having already circumnavigated the Sun Singer. I thought this was peculiar because some of the race volunteers informed me that the new route included a half mile section of road... but the only road around was straight ahead (i.e. not the direction the leader was running). This meant one of two things, either my good friends gave me incorrect information, or the leader was off the course. Ugh.

As I reached the Sun Singer I witnessed a bit of chaos. A few people had run all the way around it and were now wondering where to go. The volunteers did not know. When I got half way around I noticed painted arrows on the road indicating a turn which none of the first 5-6 runners took. I was in a group of 4 who all made that turn.

Further chaos ensued about a half mile later when the 3 new leaders (who were not the original 3 leaders) continued down the road past another painted arrow on the road indicating a turn. Again, the group of 4 I was in made the turn. Suddenly I was in the lead pack. One of the runners from the lead pack (who had been off the course twice at this point) turned around and quickly caught up to us, while the others disappeared.

Here's a (time-accurate) comparison of my 2008 (red) vs. 2009 (blue) Allerton trail race. Something funky happened with my GPS in the last half mile of the 2009 race. I didn't cut the course, I swear!

I finished the race reasonably well. I almost caught up to the guy I had been chasing (10 meters behind) since the half mile mark. I barely edged out (by split second) a challenger from behind. I finished 5th place. I probably deserved 10th.

I have mixed feelings about the results. On the one hand, from the sportsmanship point of view, other racers deserved to finish ahead of me. On the other hand, trail racing is not like track or road racing. You really have to pay attention to the course markings. All of the turns the lead runners missed were marked. Granted, the course was new and nobody had run it before.

I won a hat for finishing 2nd in my age group. Fig seemed to like it.

Fig's new hat

July 30, 2009

The P6000

Last November I was very happy with my Canon 50D purchase. Melissa was a little stunned and confused when I started toying around with the idea of getting another new camera. I was taking more and more photos I wanted a little point and shoot camera I could take with me everywhere. I shopped around a lot and eventually settled on the Nikon P6000.

Has it lived up to my expectations?

Yes.

And no.

Nikon P6000

Let's start with the pros. The P6000 is smaller and more portable than my than my DSLR, so I was able to take it with me more often than the 50D. The quality of photos is excellent. It's not DSLR quality, but it's better than any other point and shoot camera I've used.

Like DSLRs, it can shoot in RAW format, which I have used with this camera exclusively. This allows for better control when making adjustments (things like exposure, brightness, etc) on the computer after the fact.

It has built-in GPS. This was a big feature for me. It automatically embeds latitude/longitude when a photo is captured so I can later find the exact location where the photo was taken. This is the first mainstream consumer camera to have this feature, though it won't be the last. This is such a wonderful feature it will only take a few years until cameras have it.

It has a built-in time lapse mode. Again, this is another feature so fantastic all cameras will come with it in the future. In fact, how is this not standard already?

Nikon P6000

Now on to the cons. It's big. Well, it's all relative I suppose. The primary reason I got this camera was I thought it would be small and I could take it with me everywhere. It's somewhat small, but not small enough to take everywhere. It easily fits in a jacket pocket, but not as well in pants/shorts pocket. It also has enough weight to it that it pulls on the pocket noticeably. For most people this wouldn't be a problem, but I was riding my bike with it every day and it just wasn't ideal.

Next, GPS. Wait, didn't I list that under the pros section? Yes. For you see, this is a wonderful feature, but the GPS in this particular camera doesn't work as well as it should. Even with a perfectly clear, unobstructed view of the sky it takes a very long time to acquire a fix on the GPS satellites -- at least a minute or so. That means even in perfect conditions for GPS you can't just take the camera out, turn it on, snap a photo, and have GPS data embedded. The only way to get the GPS data is to take the camera out and turn it on well ahead of time, wait, wait, snap a photo, leave the camera on (because you don't want to have to wait around again next time). I got it working sometimes, but it was a hassle. Next, when conditions were not ideal (i.e. obstructed view of sky, like in a forest) the GPS didn't work at all. I tried several times in the forest and could not get signal no matter how long I waited. Grrrrrr.

The camera has a built-in ethernet jack. It works... so why is this a con? Because it's a completely useless feature. Practically speaking it can only be used when your computer is nearby (in which case you could just as easily plug it into the computer). If it had wireless, rather than wired, networking perhaps someone might actually use it.

Finally, the battery life is quite poor (by my standards). This is probably mostly due to the GPS. When I was using this camera every day I had to charge it every other day, even with light use (only a couple photos per day).

These things said, it's still a good camera... but I no longer use it. I have since purchased a smaller, lighter, (waterproof even) point and shoot camera which does not have GPS or take quite as good photos as the P6000... but I truly can take it with me everywhere.

This camera just wasn't right for me. It could be right for other people though. If you want a high quality point and shoot camera, and you're not concerned with ultimate mobility, and you accept the fact that the GPS is a nice bonus for the camera rather than a true selling point, I would have no problem recommending this camera. Anyone want to buy mine?

Anyway, here's a few of my favorites from this camera:

Commute

Moon over Memorial Stadium

Red arrows mark the trail

Greenhouse

The lonliest cart

Puddle

Rob & Melissa say goodbye to Iris

March 15, 2009

The Forest Glen Maple Syrup

Today was the Maple Syrup Open House at Forest Glen park. The park holds this event each spring where they demonstrate how they make maple syrup and have a pancake dinner. I've run at Forest Glen four or five times this winter so I've been looking forward to this event for a while. When I told Melissa about it she was very excited, so we just had to go. And since my parents live somewhat near the park, and they love pancakes, we invited them to come along as well.

Melissa and I arrived a little early so we could get a short hike in before the pancakes. First we hiked to the observation tower.

Forest Glen observation tower
Forest Glen observation tower

Forest Glen observation tower
that's a lot of stairs

Melissa & Rob at Forest Glen observation tower
Melissa and Rob at the top

View from Forest Glen observation tower
view of the forest

Melissa descends observation tower steps
Melissa descends the tower's many stairs

Next, we continued on the path down the hill towards the Vermillion River. We passed the beloved backpack trail on the way. The water in the river seemed high and fast-moving.

Crooked tree shadow
a crooked tree casts a shadow on the backpack trail I usually run

Vermillion River
the Vermillion River looked high

Melissa & Rob at Vermillion River
Melissa & Rob

Noon was approaching, and this was the time we agreed to meet my parents for pancakes, so we hiked back up the hill and drove over to the Maple Syrup Open House area. We got in line a few minutes after noon. My parents arrived shortly thereafter. We were having a good time, but we couldn't help but notice the line wasn't moving very quickly.

The line for pancakes and maple syrup was long
the line for pancakes was long

It took us right at two hours to reach the front of the line, get our pancakes, and sit down to eat (what became) a late lunch. The pancakes were good. The syrup was good. I'm not quite sure it was worth waiting two hours in line, but at least the weather was beautiful.

After lunch Melissa & I walked a short distance to the recreated pioneer homestead, where the syrup was made. They collected sap from 400 or so maple trees in the park all winter. Then they heat it up to evaporate away most of the water, leaving just the sugary syrup behind.

Homestead
one of the pioneer homestead buildings

Maple
they collected maple sap in buckets and bags all winter long (old photo)

Maple sap drips into a collection sack
maple sap drips into a collection bag

Maple syrup building at Forest Glen
this building housed the evaporator machine which converted the sap into syrup

Evaporation device converts watery maple sap into syrup
the evaporator was heated by a wood stove

Melissa in front of the evaporator
Melissa watches sap become syrup