The iPhone App

App

You may recall that I was slightly busy from shortly before Will was born until early October. Well, my big project was finally released yesterday. The Wolfram|Alpha iPhone application is now available in the iTunes app store.

The app has generated quite a lot of buzz over the past 24 hours, mostly because the price is significantly greater than the vast majority of iPhone applications. While I was intimately involved in the development of the application, I am completely in the dark about the business and marketing side of the product. On the bright side, most of the reviews speak relatively highly of the app itself, even though many are quite critical of the price.

Since I work primarily on Mathematica, I’ve been fairly uninvolved with the Wolfram|Alpha project prior to this iPhone app. I’m still not an expert on innards of Wolfram|Alpha but I do understand the big picture a little better than I did before.

1.0.0

If you’ve never used Wolfram|Alpha before, go ahead and give it a try on the website. It’s kind of hard to describe what it does, simply because it’s not like any other application you’ve ever used before. Despite certain visual similarities to web search engines like Google or Yahoo, Wolfram|Alpha is not a search engine. It doesn’t find web pages that might be related to your query, it computes factual answers to your query (except when it doesn’t).

Typically this means your query must be constructed in a slightly different way (perhaps using slightly different language) than you would use for a search engine. It’s worth taking the time to experiment to see what works and what doesn’t work. Perhaps my best description of Wolfram|Alpha is that it is a combination of a calculator and an encyclopedia.

The iPhone app features optimized input and output for the interesting and useful Wolfram|Alpha computation engine.

W|A knows all sorts of interesting facts. For instance, Robert was a more popular given name than William in the U.S. for most of the 20th century (though William recently overtook Robert… a sign of things to come?).

The app provides a number of ways to share the interesting results you find. Click the “share” button in the upper-right corner, or press and hold on a result.

The app also has numerous built-in examples to help you get started.

It also contains a complete history of all your queries.

Many of the computations have parameters that can be fine tuned for more precise results.

So there you have it. The app was a lot of fun to write, even if the release schedule was a bit hectic. The next version should be even better.

Late night coding

The Birth Day

This kid sucks. I mean that literally, of course. William is a sucker. He will suck on anything near his mouth, he will suck hard, and he will not stop sucking. His favorite thing to suck is his entire fist.

We got around 2-2.5 hours of sleep (spaced out over three naps) after William was born in the wee hours of the morning yesterday. We had a few people come to visit. We received plenty of phone calls and emails from our wonderful friends and relatives. Thank you all so much for your kind words and support. The consensus seems to be that he will go by Will (or possibly Guillermo en Español).

We will go home tomorrow morning. It will be a nice birthday present for Melissa. Until then it’s likely to be more eating, sleeping, sucking, and pooping… more for some of us than others.

Grandma Nancy

Grandma Nancy

Grandma and Grandpa Raguet

Grandma and Grandpa Raguet

Will sleeps

Will sleeping

William & Mom rest

Will and Mom

John & Cara with William

friends John & Cara

John practices his footbal hold

John practices his football hold

Grandpa and Grandma Schofield

Grandpa and Grandma Schofield

Grandma Barb with William

Grandma Barb

Rob & William

Daddy & Will

Team Ragfield

Team Ragfield

The Boy

Melissa went into labor yesterday, three days before her 30th birthday, about 10 days prior to her due date. We went to the hospital mid-afternoon. At 1:19 AM this morning (August 12, 2009) William Miles “Fig” Raguet-Schofield came into this world, waterlogged and tender. Melissa and William are both doing fine.

I am utterly exhausted after merely assisting with a day-long labor. I can’t even imagine how Melissa must feel. She’s one tough cookie. I can only assume the boy will be just as tough.

William & Melissa

Waterlogged and tender

Rob & William

Note that Fig’s hair is longer than mine

Fig

Feet

The Highest Point in Tennessee

I enjoy cycling. Long time readers might recall that a long term goal of mine is to cycle to the highest point (well, highest paved road) in every U.S. state. The first one I checked off the list was Tennessee, four years ago today.

Living most of my life in flat, flat central Illinois I have a special appreciation for mountains. The first mountain I rode was Mt. Tam in California, in 2004. I rode it again in 2005, at which point I was hooked. I needed more mountains, but I had none near home. So I started looking around for places where I could take trips to ride mountains.

Having spent every summer during college working in central Appalachia I was somewhat familiar with this mountain range, plus it’s an easy day’s drive to get there. But where to go. If I was going to take a special trip I wanted some big, big mountains. The two biggest are Mt. Mitchell (6,684 feet, the highest point in North Carolina, near Asheville, also the highest point east of the Mississippi river), and nearby Clingman’s Dome (6,643 feet, on the TN/NC border, the highest point in Tennessee).

Iris packed for vacation

What started out as kind of pie-in-the-sky wishful thinking quickly turned into a week-long family vacation in August 2005 (i.e. best vacation ever®). We packed the Insight full of camping gear, food, clothes, and two (yes, two) bikes and headed to the Great Smoky Mountains National Park.

Camping at Great Smoky Mountains National Park

We camped in the park (just outside of Gatlinburg, TN) the first night and woke up bright and early, ready to tackle Clingman’s Dome: me on the bike, my wonderful wife driving the support vehicle. The ascent was 20 miles long and rose around 5,000 ft. The road wasn’t terribly steep (4-5%) since it was in the national park and it was built so RV’s could make it up.

View of Gatlinburg, TN

The first mile or two was very easy. I was cruising along at 16-17 mph thinking this will be a piece of cake. The gradient increased gradually until I was closer to 8-10 mph, where I would remain for most of the climb. I didn’t know what to expect with such a long climb (twice as long as the only other mountain I had climbed), and since I have a double chainring I switched to a mountain bike cassette with a 32-tooth cog before the ride. I could have gotten by comfortably with a 28. My regular road cassette only had a 25. This would have been usable, but much more difficult.

Clingman's dome

The first 12.5 miles on Newfound Gap Road had just a little bit of traffic, but it wasn’t bad. All the cars were going very slowly anyway, so my presence didn’t seem to cause any problems.

Newfound Gap

At Newfound Gap I stopped to get new water bottles from Melissa, then turned off onto Clingman’s Dome Road for the final 7.5 miles. There was very little traffic on this road. Aside from a short downhill this road was also a little bit steeper.

Rob at top of Clingman's Dome

What had been foggy and overcast weather all morning turned into a light drizzle at the summit of Clingman’s Dome. Fortunately, we made another trip back there a few days later for a better view from the observation tower at the top.

View from Clingman's Dome

Appalachian Trail at Clingman's Dome

I chose to descend the other side of the mountain, into North Carolina, rather than go back down the way I came up. Like the other side, this side wasn’t terribly steep, but it did have some long straight sections that relatively safely allowed for high speeds.

Rob on Clingman's Dome descent

This was only the third time I had ridden a mountain, so my descending skills were a little lacking. Nonetheless I was able to get up to 48 mph or so on the descent.

Clingman's Dome descent

At the bottom Melissa picked me up and we drove off to the next campground where we would continue our great adventure. I really enjoyed the ride up to and back down from Clingman’s Dome. It was challenging, but not ridiculous (like Mauna Kea). It was a good warmup for Mt. Mitchell a few days later.

Clingmans Dome map

Clingmans Dome  profile

I had some GPS wonkiness that caused the square looking sections

Ride Information
Date: 2005-08-08 7:39 AM EDT
Mountain: Clingman’s Dome
Road Elevation: 6318 feet
Climb Distance: 20.0 miles
Climb Ascent: 4837 feet
Climb Average Grade: 4.8%
Climb Maximum Grade: ?
Ride Distance: 50.6 miles
Ride Total Ascent: 5895 feet
Ride Maximum Speed: 48 miles/hour
Ride Start: Elkmont Campground, GSMNP, TN (2285 feet)
Ride End: Oconaluftee Vistior Center, GSMNP, NC (2046 feet)

A I mentioned, we came back to Clingman’s dome a few days later and parked at Newfound Gap. From there Melissa & I rode together the last 7.5 miles to the top. Despite her fear, I think she really enjoyed the ride. Conquering that mountain was certainly difficult for her. She often mentions that experience in the same breath as other difficult moments in her life (i.e. marathon #1, marathon #2, marathon #3, etc.) that have helped her learn to persevere.

The Homer Fireworks

“Celebrate the independence of your nation by blowing up a small part of it.”

My friend John and another coworker of mine were helping out with the fireworks show at Miller Aquatics and Health Club, just outside of Homer, on Wednesday. They invited us out to watch, though I didn’t think I’d be home from my bike ride in time to make it out to Homer by 9 pm. Fortunately, I was home in time and we decided at the last minute to go.

The show was really well done and we sat very, very close to the launch site, so we had a different perspective than I’ve ever had for fireworks before. As you can imagine, I brought my camera to try to get some good shots of the fireworks. It took some getting used to, but I think by the end I started to get some good photos.

It's that time of year

The iPhone

The original iPhone was announced at Macworld Expo in January 2007 while Melissa & I were living in Nicaragua. It was amazing, a phone that ran the same beautiful, wonderful operating system as my desktop and laptop computers. The crowd at the Macworld keynote was disappointed the device wouldn’t be available until June. No matter, I wouldn’t return to the U.S. until August.

I ordered my iPhone in July and had it shipped to my parents’ house so it would be waiting for me upon our return. Around the same time I also ordered a new (non-i) phone for Melissa. We arrived at my parents’ house on a Sunday evening. The iPhone was there, in all it’s glory, but I couldn’t actually use it yet. Apparently, because of the way I set up our account with AT&T, I needed to activate Melissa’s phone first. This required talking to AT&T customer service, which wasn’t open on a Sunday evening.

The disappointment only lasted a few short hours, which was nothing compared to the months of waiting I already endured. I got everything straightened out with AT&T first thing Monday morning and my iPhone was up and running. I loved it.

Cracked screen

Two months later, while I was locking up my bike at work, I dropped my padded carrying case about two feet onto the concrete. The phone slid out face down. I was concerned the concrete might scratch the glass. Even worse, the glass cracked. It was still usable, just less beautiful… but not enough to warrant $199 to replace the screen.

In April 2008 the iPhone (and iPod Touch) developer program was announced and I signed up right away. As a software developer I am exited by the prospect of running my own code on my phone/PDA (much as I did with three previous Palm OS devices, and three Windows Mobile devices). At first Apple highly recommended not using your primary phone for development purposes, so I bought a refurbished iPod Touch.

The iPhone 3G was unveiled in June 2008 to much fanfare. I didn’t really care that much as AT&T still does not offer 3G data service in Champaign-Urbana. I was excited about the built-in GPS and larger storage capacity, but not enough to upgrade. Fortunately, my employer acquired on which I have been able to use. Score. In the meantime I set up my old iPhone for Melissa.

Finally, earlier this month the iPhone 3GS was announced. More storage, better camera, video recording, built-in digital compass. My AT&T contract was nearly up so I qualified for upgrade pricing. It didn’t take much convincing for me to order one. It was Fig’s Father’s Day present for me. It arrived last night and I’ve been using it all day today.

All in the family

from left to right: my original iPhone (now used by Melissa), my iPod Touch (used for development), my employer’s iPhone 3G (soon to be returned), my new iPhone 3GS

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 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 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 New Car

Rob & Melissa say goodbye to Iris

We’ve been putting this off for a few months, but this morning we finally traded in our beloved 2002 Insight for a new 2009 Prius. It was sad to see the Insight go, but we needed a car with a back seat now that Fig is on the way.

The new car

the new Prius in our driveway

Bulbous

the front of the Prius through a fisheye lens

We had a very pleasant experience buying the car from O’Brien Toyota in Urbana. It did take much longer than either of us expected (nearly four hours!). I guess it’s good to be thorough though.