The Devil Mountain

I love bicycling up and down mountains. Ironically I live in Champaign-Urbana, IL (i.e. the flattest place on Earth). The past several times I’ve travelled to San Francisco for WWDC I have ridden Mt. Tamalpais, just to the north of the city in Marin county. I decided to mix it up a bit this year, so after the conference ended on Friday I grabbed my bike, hopped on BART, and travelled to Contra Costa county in the east bay to ride Mt. Diablo.

I started at the Walnut Creek BART station. From there I headed down Ygnacio Valley Road (which had a little more traffic that I was expecting). From there I turned onto Walnut Ave. (not Walnut Blvd.). I turned right at the traffic circle at Oak Grove Rd., then I took a quick left onto North Gate Rd. This leads into Mt. Diablo State Park. Before the ride I read that bikes didn’t have to pay so I blew through the park gate.

Mt Diablo map

Mt. Tamalpais rises 2500 ft in around 10 miles, whereas Mt. Diablo rises 3500 ft in 10.1 miles (average 6.5% gradient). So Mt. Diablo is noticeably steeper most of the way.

Mt Diablo elevation

Mt Diablo gradient

Mt. Tamalpais has a fair amount of shade, while Mt. Diablo is almost completely out in the open. So I baked in the sun. This was somewhat unexpected, as the weather had been 60˚ F and overcast all week long in San Francisco. As soon as I left the city the temperature was much, much hotter.

Traffic was light. I think I saw more bikes on the road than cars. Incidentally, most of the cyclists were all decked out in cold weather gear like jackets. Meanwhile I was sweating like a hog and shedding clothes. The flies apparently liked the way I smelled, because a swarm of 6-8 of them followed me the last 6 miles of the climb.

Just like both the West and East peaks of Mt. Tamalpais, the road up Mt. Diablo throws in a 16% gradient to just before cresting the summit, though this steepest section on Mt. Diablo was much longer. I was afraid to stop for fear that I wouldn’t be able to get started again. It was that steep.

Rob at summit of Mt. Diablo

A very sweaty Rob at the summit of Mt. Diablo

The views were spectacular the whole way up. The lack of trees (and guardrails) allowed an unobstructed view. The view from the top did not disappoint either. I could see miles in all directions. I couldn’t quite see San Francisco. I think there was a shorter range of mountains/hills between Mt. Diablo and the city that blocked the view.

View from summit of Mt. Diablo

view to the north from the summit of Mt. Diablo

The ride down was super fast (well above the posted 25 mph speed limit). I recorded the whole thing with my Flip video camera. Here it is at 5X speed.

Anyway, the ride was awesome. I’m a little sad I didn’t get a chance to ride Mt. Tam also, but maybe I’ll do that next year.

Ride Information
Date: 2009-06-12 1:33 PM PDT
Mountain: Mt. Diablo
Road Elevation: 3849 feet
Climb Distance: 10.1 miles
Climb Ascent: 3471 feet
Climb Average Grade: 6.5%
Climb Maximum Grade: 16%
Ride Distance: 32.75 miles
Ride Total Ascent: 4400 feet
Ride Maximum Speed: 35.9 miles/hour
Ride Start: Walnut Creek, CA (200 feet)
Ride End: Walnut Creek, CA (200 feet)

The Cable Car Museum

As Melissa mentioned we visited the Cable Car Museum on Saturday. It was relatively small and easy to take in, but quite fascinating at the same time. The fairly primitive technology behind the cable cars is remarkably clever.

Melissa & Fig at the Cable Car Museum

Melissa & Fig at the Cable Car Museum

There are three operating cable car routes in San Francisco (California, Powell-Hyde, & Powell-Mason), but there are four separate lines (California, Powell, Hyde, & Mason). The museum lies roughly in the middle of these four lines. In addition to the cable car museum, this building also houses the motors and pulleys that actually operate the cable cars.

Motors pull the cable cars

510 HP electric motors pull four steel cables (three pictured) at 9.5 mph, bearing the load of every cable car in the city

Cable & grip

This display shows how the grip clamps onto the cable under the street.

Motors motors keep the wheels turning. A system of large underground pulleys allow the cables to turn corners.

The Bell Ringing Contest

We arrived in San Francisco last Sunday. When we took our first cable car ride of the trip that evening I noticed signs everywhere advertising the 47th Annual Cable Car Bell Ringing Contest. I thought nothing of it. I met up with Melissa & Laura for lunch on Tuesday right when the contest was taking place a short distance away at Union Square… so we grabbed some lunch to go and watched the bell ringing contest.

Union Square

Cable Car bell ringing contest at Union Square

When we first arrived the amateurs had already started, and let’s just say it wasn’t quite what we were expecting. Fortunately, the professionals (actual MUNI cable car employees) started soon and they were much better. Granted, there’s only a certain level of creativity one can express with a single bell, but it was all good fun.

Bell ringer

The pros show how it’s done

The Twin Peaks

On my 6 a.m. bike ride this morning I headed towards Golden Gate park. When I reached Market & Castro the “bike route” split off from Market up this hill, so I continued up the hill. I reached the top at an intersection. To the left it continued to go up, so I turned left. A few turns later, after a mile and a half climbing at 10% gradient, I found myself at the top of Twin Peaks (nearly the highest point in the city). Even though the air was hazy the view was spectacular.

San Francisco panorama

San Francisco panorama

Market Street

Market Street & downtown

You can see this hill from anywhere in the city, but for some reason I always assumed the top wasn’t publicly accessible so I never tried to ride up before.

After descending the hill I rode through Haight-Ashbury, Golden Gate Park, along the Pacific coast, then back downtown.

TwinPeaks ride map

ride map

TwinPeaks ride elevation profile

ride elevation profile

The Keynote

As I write, Melissa & I are at Chicago O’Hare airport waiting on our (delayed) flight to San Francisco. I am attending Apple‘s Worldwide Developer Conference (WWDC) this week. Melissa is along for the ride.

Since I started working full time as the primary Mac OS X developer of Mathematica at Wolfram Research in 2001 I have attended this conference every year except 2006. That year the conference was scheduled (Apple has been really bad lately at waiting until the last minute to schedule this huge conference) during the week Melissa & I were moving to Nicaragua, so I missed out. The conference is exciting every year, but none was more exciting for me than 2005 when I (along with my boss Theo Gray) participated on stage during Steve Jobs’ keynote address.

Note: some of this information was confidential at the time, but is now mostly publicly known. I can’t imagine any of the details I mention below would still be considered sensitive information.

On Wednesday night the week before WWDC I got a call at 9:30 pm from Theo. I was almost ready to go to bed. He asked if I would be able (and willing… but more able :) ) to fly to California at 6 am the following morning. I suppose I could, but why? Theo went on to tell me that Apple had a super secret project and they wanted our help, but he wouldn’t tell me what the project was.

I have since learned that he actually knew what the project was at the time of that call, but he couldn’t tell me. Stephen Wolfram, the founder and president of Wolfram Research wouldn’t sign off on the idea until he knew what was going on. Steve Jobs told Stephen Wolfram & Theo what the project was and they agreed to take part… but they couldn’t tell anyone else.

I spent the next two hours packing (including the Dahon, my folding bike at the time) before going to bed. Early the next morning I arrived at the Champaign airport. Apple purchased my one-way ticket to San Jose (by way of Chicago). An Apple limo picked me up at the San Jose airport and drove me straight to Apple’s campus in neighboring Cupertino. Luggage still in hand I entered 3 Infinite Loop (I think). A few minutes later I was in a meeting with Ron Okamoto, Vice President of Worldwide Developer Relations.

Ron told me what the secret was, that Apple was building a Mac which used an Intel x86 processor. They had ported all of Mac OS X to this new architecture (Darwin, the open source core of Mac OS X, already ran on x86). They intended to demonstrate this new x86 version of Mac OS X on Monday’s WWDC keynote. They wanted to demo a 3rd party application running on the x86 Mac. They chose Mathematica to be that 3rd party application. He asked me if I thought it would be possible to get Mathematica up and running on Mac OS X Intel by Monday.

Uhhhh.

That’s a potentially huge task. Our code is fairly portable (at the time Mathematica ran on several Unix platforms in addition to Mac and Windows), but supporting new platforms usually takes a fair amount of time. Ron told me Apple was prepared to provide significant resources to make this happen, including a small team of Apple developers and immediate access to any other relevant Apple developers. I was cautiously optimistic.

(Now 30,000 feet over Iowa)

We travelled across De Anza Blvd (luggage still in hand) to a different Apple building where I was ushered into a conference room with a single desktop computer sitting on the conference table. It was in the same metal case as Apple’s high end desktop computers at the time, the PowerMac G5. I think the case even said “G5” on the side. From the outside you couldn’t tell the difference between this machine and a G5 unless you carefully peeked through the holes on the front and noticed it didn’t have the huge heat sink the G5’s had.

I was greeted by the team of Apple engineers (Matt, Eric, & Ronnie) who would be providing technical assistance in the porting process. This place was not only hidden from the public, but it was hidden from the rest of Apple. Very few people at Apple were even aware this project existed. The four of us got busy.

I sat down at the Macintel and immediately began working. The experience wasn’t just familiar it was identical to any other Mac I had used. I was blown away by how seamless Apple had made the transition. The whole OS was there it all its glory, including every bundled application (even Xcode). I could just work exactly like I do on any other Mac.

But wait, sometimes I use BBEdit to edit text. I guess I won’t be able to do that since it (or any other 3rd party application) hasn’t been ported yet. “Why don’t you just go ahead and try it?” Matt said to me as he tried to hold back a smile. It hit me immediately. “You’re kidding, right?” I downloaded BBEdit, double clicked the icon, and it ran. I ran just like it does on any other Mac. Apple had incorporated (with technology licensed from another company) a PowerPC translation layer into the OS. This meant that nearly all existing Mac applications would run on the new Intel machine, with a slight performance penalty. This was amazing news, as it meant the new machines could be adopted immediately by users rather than waiting until all their applications were ported. Very exciting.

Back to work. We started with MathLink. This is a low level library used by both the Mathematica user interface (FrontEnd) and the computation engine (Kernel). With one set of flags MathLink builds for Mac OS X PowerPC and with different flags it builds for x86 Linux (or Windows, etc.). It only took a few minutes of experimentation with the Makefile and headers to find the right set of flags to treat the OS as Mac OS X and the architecture as x86. The elapsed time from entering the conference room to having a built, fully functional MathLink library was probably around 20-25 minutes. As we progressed our excitement grew.

Xcode target architecture

Next was the Mathematica FrontEnd. I normally spend all my time working on the FrontEnd, so this part didn’t worry me much. The FrontEnd is built with Xcode, which had a new “architectures” setting checkbox. We checked the checkbox for the Intel architecture (actually, we didn’t because Intel was the default target architecture when building on Intel… but we did verify the checkbox was properly set). Within 4-5 minutes the FrontEnd built with only a couple of minor build errors which were easily fixable. After 10 minutes working on the FE we had it built and running. It wasn’t running flawlessly, but it was a very good start. I had only been at the secret Intel machine for around a half hour. This was getting really exciting.

The next step was the one which caused me the most concern, the Mathematica Kernel. The reason for my concern was that I don’t often work with the Kernel. I knew how to build it (the build system is somewhat complicated) and I knew roughly how the code was organized, but there are all sorts of minor details which could really slow down the process. It relies on many external libraries (open source and commercial) and custom build tools. Fortunately, the Kernel, like MathLink, already ran on Mac OS X PowerPC and Intel Linux & Windows. It took a while longer to figure out some of the proper build flags, and some of the build errors weren’t entirely obvious.

This is where Matt, Eric, & Ronnie really came through. They had each spent a lot of time porting open source applications to Mac OS X Intel to learn what types of issues developers might run into along the way. Each time we encountered some sort of problem in an open source library one of them would go off on their own for a few minutes to resolve the problem while the rest of us kept hammering away. Every few minutes we would get further and further along in the build process with new issues popping up all the time. It was like an assembly line. In parallel.

After about 90 minutes (2 hours from when I entered the room) we had the Kernel running, the FrontEnd running, and the two processes were able to talk to each other through MathLink. Again, it wasn’t perfect, but nearly everything just worked.

News spread up the ranks. Within minutes we had high level executives stopping by to see the first 3rd party commercial application running on Mac OS X Intel. By early evening Theo (who took a later flight) arrived frantically asking what he can do to help. He was a bit shocked, and very pleasantly surprised, that it was mostly done.

Friday we worked to fix bugs and showed off the software to an ever growing number of people. Since Mathematica already ran on Intel processors on other platforms, most of our cross platform code was byte order agnostic. There were a few cases where Mac specific code was assuming big endian byte order, particularly related to Quartz (bitmap drawing) and OpenGL. There were also some issues with Quickdraw PICT drawing.

Friday evening some of the Mac rumors sites (original CNET article appears to have been removed) reported that Apple would be announcing the switch to Intel processors at Monday’s keynote. Rumors like this had been published for years, so it wasn’t that out of the ordinary, but this report was different. It contained many specific (correct) details rather than just wild speculation (like every previous report like this). It was clear someone in the know had blabbed. The conference room was silent for a few moments. Oh well. Until Monday, it’s still just a rumor.

Saturday morning we drove up to San Francisco to prepare for the WWDC keynote. We had a rehearsal where I met and shook hands with Steve Jobs. I had heard horror stories about his temper, but he was in a great mood when I met him… sitting perfectly relaxed, legs crossed, smile from ear to ear. I could tell he was excited.

Theo practiced his speech, asking Jobs for feedback along the way. The funny thing was that Steve was so happy he kept telling Theo “say whatever you want” or “talk for as long as you want.” Meanwhile I set up the demo machine (and backup demo machine) with our freshly built Mathematica for Mac OS X Intel.

Monday morning before the keynote Theo & I hung out in the VIP lounge. Woz (Steve Wozniak, the other co-founder of Apple) was there, Sergey Brin (co-founder of Google and former Wolfram Research intern) was there, along with many other influential people in technology.

Once the keynote started we sat in the front row on the far right side. Midway through the keynote Jobs called us up to the stage. Theo described our experience porting Mathematica to Mac OS X Intel over the previous few days. I drove the demo machine as he talked. It was a big hit. Theo captivated the audience. At one point Theo mentioned my name, which immediately caused 4,000 people to turn their heads to stare at me. It was a little awkward (which is quite evident in the video). Had I known that was going to happen I think I could have played it a little more cool. Anyway the demo was a success. Mission accomplished.

Note that a few minutes of the demo were edited out of this video for some reason.

That wasn’t all for that WWDC. On Tuesday I gave a 10 minute presentation during Bud’s science session about Mathematica on Mac OS X, detailing how we utilize various OS features. This went more smoothly for me as I had actually been preparing for it for a few weeks. Later that week I spoke about Mathematica for a minute or two in Ernie’s 64-bit session. I went from participating in zero sessions my first four WWDC’s to three sessions in 2005, back to zero sessions every year since. Perhaps that was my 15 minutes of geek fame (actually, the total time I spent on stage was almost exactly 15 minutes).

Last year I attended a reunion for the non-profit organization where I worked in college, ASP. A guy who I hadn’t seen in 8 years came up to me and asked me if I was in a Steve Jobs keynote a few years ago. “I thought that was you…”

Anyway, tomorrow’s 2009 WWDC keynote won’t be as exciting for me, though I’m sure it will still be exciting. I won’t be participating in the keynote. At least, if I am they haven’t told me yet. Always with the secrecy.

The End of May

Photo of the Day

May 2009 Photo of the Day

Blog

The top searches that led to my blog in May:

  1. dahon helios [xl]
  2. my name is rob (or: rob is my name)
  3. bike friday pocket rocket
  4. mathematica 8 (again, doesn’t exist and I’ve never mentioned it)
  5. iPhone camera remote
  6. highest point in PA
  7. camel clutch

Running

Rob at start of Rockford Marathon

Most of my training and racing efforts in May were geared toward running. I raced four weekends in a row (sprint triathlon, 5K, marathon, 5K), all of which were quite successful. Now comes the time of year (i.e. the heat of summer) when I scale back my running and work more on cycling and swimming.

Month Distance # Workouts Avg per Workout
January 109.34 Mile 10 10.934 Mile
February 55.83 Mile 7 7.97571 Mile
March 108.792 Mile 10 10.8792 Mile
April 74.85 Mile 8 9.35625 Mile
May 64.5669 Mile 9 7.1741 Mile
Total 413.378 Mile 44 9.39496 Mile

Cycling

Rob finishes the bike

I did no cycling races (aside from the triathlon) and only a little training in May. My bike mileage was half of what it was in May of last year and I’m a good 800 miles behind where I was last year at this point. I’ve completely given up two of my four/five weekly training rides from last year to spend more time with the family.

Having said that, I’m doing surprisingly well on the bike. I think it’s mostly my running fitness carrying over and making up (slightly) for my lack of training miles.

May 2009

Bike Distance # Rides Avg per Ride
Bianchi 48. Mile 12 4. Mile
Big Red 3.2 Mile 1 3.2 Mile
El Fuego 14.5 Mile 2 7.25 Mile
Pocket Rocket 7.2 Mile 2 3.6 Mile
Thundercougarfalconbird 274.93 Mile 7 39.2757 Mile
Total 347.83 Mile 24 14.4929 Mile

January-May 2009

Bike Distance # Rides Avg per Ride
Bianchi 300. Mile 64 4.6875 Mile
Big Red 7.17 Mile 3 2.39 Mile
El Fuego 54.42 Mile 7 7.77429 Mile
Pocket Rocket 120.93 Mile 25 4.8372 Mile
Thundercougarfalconbird 1027.65 Mile 24 42.8188 Mile
Total 1510.17 Mile 123 12.2778 Mile

Swimming

The spring session of Masters Swimming ended with another practice meet. I dropped my 500 yard freestyle time from 7:10 at the last meet to 6:48 at this meet.

After a couple weeks of little-to-no swimming the summer session of Masters Swimming started up and it has been going well so far. The morning schedule works out better for me (i.e. doesn’t conflict with group run and/or bike workouts), so I may be swimming as many as four times per week (rather than two times per week throughout the school year).

This bodes well for my chances at the Olympic distance triathlon(s) this summer. This category of race is more swim-heavy than other distances. Between July and September of last year I dropped my 1500 meter swim split from 28+ minutes to 25+ minutes, and I’m already doing much better than that so far this season. It’s conceivable I could swim four minutes faster, bike the same time, and run one minute faster at this year’s Evergreen Tri, knocking five minutes off my time from last year. I would be extremely pleased with that.

Month Distance # Workouts Avg per Workout
January 1.87452 Kilo Meter 3 0.62484 Kilo Meter
February 14.9504 Kilo Meter 6 2.49174 Kilo Meter
March 19.5224 Kilo Meter 7 2.78892 Kilo Meter
April 13.3502 Kilo Meter 6 2.22504 Kilo Meter
May 12.7806 Kilo Meter 7 1.82579 Kilo Meter
Total 64.7782 Kilo Meter 30 2.15927 Kilo Meter

The Memorial Day Weekend

This Memorial Day weekend flew by. We got a lot accomplished, but not as much as we had hoped. I can’t help but feel partly responsible.

I had Friday and Monday off work, which is pretty rare. I celebrated by sitting around in my underwear until noon or so on Friday. I followed that up with my first post-marathon run, five miles easy. It went well. I had some tight muscles with a few aches, but no major injuries. I spent most of the afternoon mowing the lawn and doing other miscellaneous yard work. In the evening we went to Target to look at baby items.

Kickapoo mountain bike trails

Kickapoo mountain bike trails

Saturday morning I mountain biked at Kickapoo with Gene and Greg. I haven’t been there in a few months, so I wasn’t quite at the top of my game. The trails were a little muddy, but not nearly as bad as they could have been. Gene and Greg took me onto the “new” section of trail, which was absolutely ridiculous. Most of the trail is challenging, but this new part was downright sadistic. The single track trail was very narrow (18″?), cut into the side of a very steep hill, slanted downward, with tight and steep switchbacks. I made it through okay. Actually, it was dangerous. There, I said it. The rest of the trail pales in comparison.

Fields

Many unplowed fields across Illinois and Indiana had bright yellow flowering plants (which I assume are weeds) this weekend.

Saturday afternoon we drove to Indianapolis. First we visited Babies-R-Us to look at cribs and other various items. Next we went to Aimee & Brett’s house to pick up a few baby items they wanted to give us. Then it was on to Aunt Jeanne’s house to meet up with the family. Finally, we went to Zionsville to my uncle Dennis and (new) aunt Sally’s wedding reception (the main event of the trip). The reception went well, and it was great to catch up with the cousins, aunts, & uncles. Sally is a wonderful woman and she and Dennis seem very happy together.

Dennis & Sally

newly married Dennis and Sally

Sunday morning I got a little cleaning done in the office, but not as much as I (or Melissa) hoped. It’s never as much as I hope. I also worked for a little while setting up one of my old computers for my grandparents in Bismarck. After lunch we went swimming (our first family swim). Then we went shopping for new stoves. We’ve been on the brink of getting a new stove since Christmas. I think it’s finally going to happen this week.

Memorial

Danville National Cemetery at the VA on Memorial Day

Monday morning I drove over to Danville for the Memorial Day 5K race at the VA. It rained during the race, which kept the temperature somewhat cool, but also made the roads a little slick. Right from the start a large pack of high schoolers shot out to the front. I tagged onto the back of the pack, maybe 12-15th position for the first half mile. I was running way too fast and I knew it. What were all these jokers doing?

Entrance to the VA on Memorial Day

The 5K course followed the road around the VA, which was lined with flags for Memorial Day.

The second half mile I slowed down, but all the kids around me slowed down even more. I moved my way up through the pack. I reached the first mile in 5:36. I ran mile two in 5:50, by which time I had moved into 4th place. My heart rate was through the roof and it was starting to wear on me. The last guy I passed tagged along behind me and stayed with me for the third mile. He passed me back with around a quarter mile left. My last mile was 5:55 and I finished in 5th place (out of a record 398 participants), 1st in my 30-39 age group. I was worried I might still be feeling the effects of the marathon eight days prior, but my legs felt perfectly fine. It was a tough race, mostly because I started too fast (didn’t I just learn not to do that?). Well, racing a 5K is a world apart from racing a marathon. Incidentally, my heart rate hit 194 in the last tenth of a mile, which I believe is the highest I’ve ever recorded (my theoretical max heart rate is 195).

After the race I went to visit my grandparents. They’ve been having some health problems recently and I hadn’t seen them in a few months. They seemed to be doing fairly well, all things considered. My dad and I worked to get their computer problems straightened out. Then we had a pizza lunch before hitting the road. I drove my dad back to Danville in the new car, which he seemed to enjoy.

Finally we spent this evening at a cookout with Cara & John at our house. John got a nifty remote controlled speedboat for his pond. Good times.

The Twitter

I’ve been using the Twitter micro-blogging service for around 16 months now. I’m a fan. I’ve spent a bit of time recently data-mining Twitter (mostly work-related). I took a quick glance at my own usage patterns in this blog post. I’ll spare you the mathematical details and provide the condensed version here.

I’ve been using Twitter for 1 year, 3 months, and 21 days.

I’ve posted 1487 status message updates (tweets).

I’ve averaged 3.125 tweets per day.

Ragfield Twitter usage

I’ve typed a total of 107,442 characters.

I’ve averaged 72.25 characters per tweet (roughly half the allotted amount).

My shortest tweet was “bed”.

I’ve used 19,188 unique words (18,528 if you don’t count numbers).

My most commonly used word is “the”.

I’ve used 7,883 unique nouns.

My most common topics are: bike, work, time, ride, think, run, like, morning, race, mile(s), home.

I’ve used 4,300 unique verbs.

My most common actions are: bike, work, ride, think, run, race, see, know.

The users I mention most frequently are:

melissa_raguet 84
spoonshake 69
esmithrunner 32
erik_d 28
dbfulton 18
gutzville 14
ultrashea 11
erik__d 9
adamengst 9
chockenberry 6

The Tale of Two Marathons

I found my performance at the Illinois Marathon to be unsatisfactory. I enjoyed terrific preparation, but suffered from poor execution. I physically recovered fairly quickly so I decided to do something unprecedented (for me) and run another marathon only five weeks later. This marathon would be different. It had to be. I had a plan. And I was going to stick to the plan come hell or high water.

Melissa and I drove up to Rockford, IL on Saturday. The Rockford Marathon was quite a bit smaller than the Illinois Marathon. There would be just a few hundred participants in the full marathon (as opposed to a few thousand), while several hundred more would run the half marathon. We battled heavy winds the entire trip. When we stepped out of the car at the packet pickup location I briefly forgot what month it was. In addition to the awful winds it was bitterly cold.

We stayed with Melissa’s sister, brother-in-law, and nephew on Saturday night. We had great fun catching up and playing with two-year-old Logan.

Logan

The next morning I awoke a little before 5 a.m. I immediately checked the temperature, which read 35˚. This was going to be a long morning. I crept downstairs to eat a Clif Bar, two cinnamon brown sugar pop tarts, and a banana. Normally before a race my stomach is very upset, but not this time. I felt perfectly calm. I felt no pressure. This was a good sign.

By the time we stepped outside I was pleasantly surprised to find very calm winds and the temperature didn’t feel nearly as cold as I anticipated. I was concerned that it might be too cold to wear shorts, but it wasn’t.

We arrived at the race right on schedule. After a quick trip to the porta-potty it was time to start.

I wanted to finish with a time faster than I ran at the Illinois Marathon, but that goal was really secondary. My primary goal for this race was to run negative splits. This is the term used by runners to refer to a race when the second half is run at a faster pace than the first half. Running negative splits is easier physically, but it’s much harder mentally. It takes a tremendous amount of discipline to pace yourself correctly in the early part of the race. I’ve been running competitively for 15 years and I’ve only been able to run negative splits in races just a few times… but these were my fastest races.

My target pace would be 7:15 per mile with a goal finishing in 3:10:00. I wanted to start the race around 7:25 per mile. I positioned myself 5/8 of the way between the 6:00 per mile sign and the 8:00 per mile sign. Before I knew it we were off.

Rob at start of Rockford Marathon

I wore a yellow shirt so Melissa could spot me along the course. Unfortunately, a few others must have had the same idea.

I started very easy. For the first few blocks people were moving past me like I was standing still. 1/2 mile into the race I began to worry. They can’t all be running too fast, can they? I felt like I was running way too slow. This can’t be right. The first few miles of the Illinois marathon felt easy to me, but they definitely didn’t feel slow. This felt both easy and slow. I breathed a sigh of relief as I passed the first mile marker in 7:24. It was exactly where I wanted to be.

The first part of the race absolutely flew by. I was concentrating on breathing as easily as possible and running as efficiently as possible to save my energy. Around mile six, content with my easy start, I decided to pick up the pace a bit to hopefully start running closer to 7:15 per mile. I left the group I had been running with, never to see them again. After mile five not a single person passed me the remainder of the race. I can’t begin to tell you what kind of a confidence booster that is. Incidentally, not a single person passed me in either of my previous two races. This streak can’t continue much longer.

Rob at mile 11 of Rockford Marathon

I saw Melissa out on the course around mile 11. She was kind enough to take the arm warmers I no longer needed. It was turning out to be an absolutely gorgeous day. Neither too hot nor too cold, it was perfect running weather.

By the half way point I had made up all the time I lost in the early miles. I was exactly on my 7:15 pace.

Rockford Marathon course map

Once the marathon runners split off from the half marathon runners I saw relatively few people. Most of the racers were in the half marathon. At several points in the last half of the marathon I would go minutes at a time without seeing another competitor.

I saw Melissa again at mile 14 after flying down a fairly steep hill. I wouldn’t go so far as to describe Rockford as hilly, but it’s far hillier than Champaign-Urbana. To my pleasant surprise, despite very little hill training, I handled the rolling terrain with relative ease.

Rob at mile 14 of Rockford Marathon

Nothing went even remotely wrong until mile 15 or so when I began to notice a blister between the first two toes on my left foot. I ignored it as best I could, but the pain became worse and worse. I began to dread every step. By mile 16 or 17 I was fairly certain it was bleeding. Everything else was going so well, I wouldn’t let this problem stop me. I ran through it and eventually blocked it out. After the race I discovered the very large blister had completely ripped off and my toes were quite raw. It will take a few days to heal, but I’m not worried.

I couldn’t believe how good I felt at this point in the race. Mile 16 & 18 were the two fastest miles I ran the entire race (mile 17 & 19 were good also, but they were slightly uphill). I kept going faster and faster.

A slight hiccup came just after mile 22 when the course went onto a multi-use path through the woods. I ran for nearly a mile without seeing a single course marker, volunteer, or competitor. I had no idea whether I was still on the course and it was beginning to really freak me out. Did I just run this well only to screw up now? Luckily I was still on the right path.

It was becoming harder and harder to maintain my pace. By mile 25 I cracked and could no longer hold my sub-7:15 per mile average. I still finished reasonably strong, but I definitely slowed down the last two miles.

Rob finishing Rockford Marathon

I crossed the line in 3:09:05. It was a 13 minute personal record for me. It was a Boston marathon qualifying time (the Ragfields are going to Boston). It was a negative split. Actually, I don’t know my exact 1/2 marathon split so I’m not certain. It was only 3-5 seconds different either way (which is fairly remarkable if you think about it). I guess it would be better to describe it as even splits.

I noticed when I crossed the finish line my timing chip didn’t cause an audible beep. It had caused a beep at all the checkpoints, but not at the finish line. This caused me to worry. I had just run a Boston qualifying marathon time, but if something went wrong with the timing system it may not have counted. I tracked down a race volunteer who was able to check for me, and indeed the timing system did not register me when I crossed the line. Fortunately, they got it all straightened out and my time does appear correctly in the official results (actually, it took two tries to get it right… but they got it right). The race timers were very helpful in getting the matter resolved.

Rockford Marathon finisher medal

Interestingly, since the marathon was so small (249 finishers), I ended up in 15th place overall and 3rd in my 30-34 age group. That was certainly unexpected.

So that was the story my 2nd marathon this spring, my 4th road marathon, my 5th marathon, my 9th marathon or beyond. I ran faster than I’ve ever run for such a long distance. I did it at a very even pace (only 28 seconds difference between my fastest and slowest miles, compared to a difference of 3:03 at the Illinois Marathon). I felt better than I’ve ever felt in such a long race. And with any luck, I’ll recover faster (the jury’s still out on that one).

I’ll leave you with a brief comparison of my performances in these two spring marathons.

Illinois Marathon Rockford Marathon
Time Split HR Time Split HR
Mile 1 00:06:51 06:51 151 00:07:24 07:24 145
Mile 2 00:13:47 06:55 162 00:14:48 07:23 153
Mile 3 00:20:38 06:51 166 00:21:59 07:11 156
Mile 4 00:27:23 06:44 168 00:29:20 07:21 156
Mile 5 00:34:08 06:45 168 00:36:45 07:25 158
Mile 6 00:41:04 06:55 170 00:43:51 07:05 159
Mile 7 00:47:56 06:52 171 00:51:00 07:08 161
Mile 8 00:54:53 06:56 169 00:58:04 07:04 159
Mile 9 01:01:38 06:45 173 01:05:11 07:06 160
Mile 10 01:08:27 06:48 174 01:12:22 07:11 160
Mile 11 01:15:28 07:01 176 01:19:38 07:15 158
Mile 12 01:22:23 06:54 176 01:26:48 07:10 161
Mile 13 01:29:15 06:52 178 01:34:03 07:14 164
Mile 14 01:36:07 06:52 177 01:41:11 07:08 165
Mile 15 01:43:10 07:03 179 01:48:18 07:06 167
Mile 16 01:50:33 07:22 178 01:55:17 06:59 168
Mile 17 01:58:18 07:45 180 02:02:29 07:12 167
Mile 18 02:06:09 07:50 180 02:09:28 06:59 169
Mile 19 02:14:31 08:21 179 02:16:30 07:01 172
Mile 20 02:23:15 08:44 176 02:23:33 07:02 170
Mile 21 02:32:05 08:49 176 02:30:43 07:10 169
Mile 22 02:41:53 09:47 169 02:37:46 07:02 172
Mile 23 02:51:19 09:26 166 02:45:06 07:20 172
Mile 24 03:00:57 09:38 164 02:52:10 07:03 174
Mile 25 03:10:38 09:41 164 02:59:38 07:27 174
Mile 26 03:19:59 09:20 166 03:07:04 07:25 175

My aerobic threshold is around 174 beats per minute. In the Illinois Marathon my average heart rate was 174 at mile 10. In the Rockford Marathon my average heart rate didn’t hit 174 until mile 24. My legs hurt as bad at mile 15 in the Illinois Marathon as they did at mile 25 in the Rockford Marathon. I just can’t get over the stark contrast between these two races when I had roughly the same level of fitness for both. If this doesn’t convince you to run even-to-negative splits in a marathon, I don’t know what will.

Many thanks to Melissa for her awesome support and wonderful photos.

The Twin Cities Threesome

As you may have already read on Melissa’s blog, Team Ragfield participated in the Twin Cities Twosome 2x5K relay race yesterday. Melissa, six months pregnant with baby Fig, ran the first 5K leg in 26:55 before handing off the baton (a tongue depressor) to me (we practiced the hand off ahead of time).

I was moving a lot faster than most of the other runners on the course, and there were a lot of walkers out as well. I spent most of the time weaving through people, trying to balance my desire to run as little out of the way as possible with my desire not to knock some poor oblivious person over.

My mile splits were 5:40, 5:58, 5:57 and I finished my 5K leg of the relay right at 18:15. I had a good, solid race, though it wasn’t quite as spectacular as last week’s run. Sure, I was 16 seconds faster at the 3 mile mark (17:35 vs. 17:51), but I didn’t already swim and bike beforehand yesterday.

Anyway, with two strong performances we placed 3rd in the husband/wife division in our first attempt at the Twin Cities Twosome. Though, I’m pretty sure we were the only threesome on the podium.

Go Team Ragfield

award medals and baton

After the race I ran around a bit for a total of 12 miles on the day. This was my last semi-long run before the Rockford Marathon next Sunday.