We then spent most of the day hanging around Portland together, including a visit to the mighty and wonderful Powell’s City of Books (one of the last, great independent book stores) and checking in at GECCO to get my registration stuff. Tom totally loved Powell’s (“I could get lost in here!”), and has in fact spent large amounts of my money and his time there this week while I was at the conference. We also went out and saw Toy Story 3 that night, which turned out to be every bit as good as everyone’s said it is – lots of fun and very well written.

Day 8 was our last college visit in this part of the world, as we headed up to Olympia, Washington (2 hours north of Portland) to visit Evergreen State College. This was a real eye opener for both of us. I knew Evergreen was cool (and another of the small number of public liberal arts colleges in the U.S.), but didn’t know a lot of the details, and I think we both found the unusual curriculum and environment really interesting and thought provoking.

I had arranged beforehand to meet some of the computing faculty at Evergreen so we could learn a little more about their program as part of a program review we’re doing at Morris, so after the information session and tour we met up with Sherri Shulman and then headed over to meet her husband and fellow CS faculty, Neal Nelson. When Neal walked in, there was this very weird moment where we both those we knew each other but weren’t sure why. Duh, duh, and double duh – Neal was my undergraduate thesis advisor at Reed! I’d lost track of him when he left Reed in 1988, and I somehow thought he’d gone into industry so I wasn’t even looking to find him anywhere in our travels. Given all that and the the fact that his name doesn’t particularly stand out (and that I’m really crap with names), I totally didn’t consider the possibility that I knew this Neal guy we were going to see. After recovering from that somewhat awkward start, Sherri, Neal, and I had a really excellent conversation that ran a couple of hours easy. Lots of catching up on old times, as well as discussing undergraduate computing curriculum with limited resources in a public school – many thanks to both of them for all their time!

After returning to Portland, we went to Papa Haydn’s, possibly the best source of wonderfully scrumptious and rich desserts that I know of in the U.S. I had a wonderful Autumn Meringue and it was just like being a college student again (without the metabolism of a 20 year old). We used to walk out to Papa Haydn’s from Reed (maybe a 30 minute walk) several times a year and indulge, and was so cool to go back and find that it really hadn’t changed much in all those years.

That night was the opening reception at GECCO, so Tom and I hung around for a few hours eating little snacky things and chatting with various folks. Tom had never met most of my EC friends and colleagues, and he was very cool at meeting a bunch of strangers that are, even worse, all science nerds to a very high degree. Luckily it’s a really cool group of people, and I think he actually enjoyed himself.

By Day 9 I’d actually skipped out on the bulk of the first two days at GECCO, so at this point I essentially abandoned my son to the wilds of downtown Portland and started pretending to be a scientist for a bit. He spent most of his time hanging at Powell’s and reading books, while I listened to people talk about their cool evolutionary computation research.

That night I did actually skip out on the last session, though, and went back to Reed to join a bunch of faculty that have a regular Friday beer and food gathering at Woodstock Wine and Deli up the hill from campus. Jim had invited me to join them, and it was a great chance to meet some people I knew that I’d missed before (like Ray Mayer) and a bunch of other faculty that are new to the college since I was a student there in the dim past.

I wasn’t the only one meeting up with old friends, as Tom met up with Perry Webster from Morris (currently attending the University of Portland) and hung with her and a family friend pretty much the whole evening, which was a neat chance for him to spend a little time with people more his age :-).

Day 10 was much the same, although I stayed at the conference pretty late because the poster session and associated reception was that evening.

Day 11 (today) was the end of the conference, including eating lunch in the hotel sports bar with a bunch of very enthusiastic Europeans watching the World Cup final! Eli Mayfield (UMM ’09, now a grad student at Carnegie Mellon studying natural language processing) gave a talk today, and did a really excellent job. Tom and I went out to Jake’s Famous Crawfish with Eli and Bill Tozier. Jake’s was a great seafood house back in the day, and they didn’t disappoint, providing us with excellent food to go with the fine conversation. That was a great way to end our time in Portland!

Now we’re off to bed, and tomorrow we drive south to Tule Lake and Lava Beds National Monument. With a little luck we may hook up with Wayne Manselle in Eugen on the way!

So different from in the winter

The cool part is that most of the photos are mine! This set on Flickr shows all the photos they used, although many of them actually look much better in the calendar. Their staff did a really great job of straightening, cropping, and adjusting the lighting on the shots that they used, and it really made the photos look really nice. Thanks to whoever did the excellent work! Christian Lindig informs me (see the comments) that the design work was done by Margot Behr. Thanks for the great work, Margot!

It was really weird when I first looked at the calendar, because I really wasn’t sure how many of the photos were mine. There were two or three that I immediately recognized as mine (like the image at the top), but there were quite a few indoor detail shots that seemed like the kind of thing that I’d take (like the dragon below), but which I didn’t really recognize. There were also several of buildings that could have been mine, but could have been taken by most anyone. Going through, them, though, I was able to determine that all but two were in fact mine. The cropping (and to a lesser degree the cleaning) that the Dagstuhl folks did often threw me as it sharpened the focus in cool ways that I hadn’t seen or thought of.

Iron dragon at Dagstuhl

There are two photos in the calendar that aren’t mine, both taken in specific conditions that I’ve never been there for. One is a really cool panorama with a beautiful fresh coating of snow and the other is the grounds around the chapel in the summer.

• Models of Computing Systems
• Fuzzy logic and fuzzy sets
• Refactoring

I’ve taught Refactoring several times and have a pretty good handle on that. Fuzzy Logic I’ve taught once before and am pretty comfortable with. The Systems course, however, is one I’ve never taught before and am still struggling with on a number of levels, including the textbook.

Any suggestions and ideas on any of these would most certainly be appreciated. I’ll say a little more about each course below the fold for those who want all the gory details.

Models of Computing Systems This is one of our three core courses (the others being Algorithms and Computability, and Software Design and Development), is a 5 credit course (4 hours of lecture and a 2 hour lab each week), and is intended to expose students to computing systems using a layer model that includes as major topics

• Assembly language and a quickie overview of basic architecture
• Operating systems basics, with an emphasis on processes, process management, and threading/concurrancey
• Computer networks
• System administration, including the installation, configuration, and management of common tools like web servers

I’m planning to use x86 assembly for the first item, and the sysadmin work will happen on Linux boxes. I’m planning (still in a vague way at the moment) to try to use computer security issues to motivate/illustrate a number of key concepts in this course. Things like file system and disk structure can be pretty abstract, for example, but I’m thinking that doing a lab where we see how those decisions lead to lots of “erased” data being recoverable might make it seem more “real” and significant.

I realize that no book is going to cover all these things, and on-line resources plus lecture can provide the necessary background for several of these. This course has typically using a “standard” OS book like Silberschatz, et al, but this is large and expensive and really only addresses one of the four topics. If anyone knows of a good book that would touch meaningfully on more than one of these areas, though, that would be really helpful.

Fuzzy logic This is a 2 credit elective course, and should provide a reasonable background in the theoretical definitions and concepts in fuzzy logic, as well as giving the students a chance to apply those ideas. (My current plan is to write robot race car drivers using fuzzy notions of concepts like fast, slow, near, and straight.)

I’m probably more interested in solid coverage of the theoretical material than the applications side. The students will benefit from a good introduction and reference on the mathematical material, and I can probably handle the motivation and application side in class pretty well.

When I last taught this (Spring, 2006) I used An Introduction to Fuzzy Logic for Practical Applications by Kazuo Tanaka, translated by T. Niimura. That book actually worked quite decently. There were some predictable translation issues, but nothing that we couldn’t manage.

Refactoring This is also a 2 credit elective course. I’ve taught this course several times, and I’m likely to again use a combination of Fowler’s Refactoring and Kerievsky’s Refactoring to Patterns. Fowler is the “standard” in the field; the first five chapters of his book are absolutely classic material on the realities of software development and should be read by pretty much anyone who aspires to write good software. Kerievsky’s book builds on Fowler and does a really nice job of demystifying design patterns, converting them from magical insights codified by geniuses into things you could discover on your own through careful refactoring. When I last taught it I think I had Kerievsky as the required text and Fowler as the optional book. Given that together they still add up to less than $100, I’m tempted to require them both. We have lots of copies of Fowler in the lab, though, so I might just require Kerievsky again. Ideas/thoughts on this would definitely be appreciated.

One of the problems we’ve run into in this course in the past has been attempting refactorings on code with limited automated testing. Without good tests you lose your courage to refactor mercilessly, or you have false courage and end up breaking things without realizing it until (sometimes much) later. With only 2 credits to work with, however, you don’t want to spend two weeks writing unit tests for a system before you can start refactoring it, especially when you don’t really understand what the units are and what they’re supposed to be doing. This time I’m planning to use BDD tools like Cucumber, RSpec, and JBehave this time to more cheaply write high level acceptance/functional tests that exercise the key parts of the system in meaningful ways without getting bogged down in a bunch of poorly understood unit tests. We’ll see how that goes.

Wrap-up

So, there they be. Any thoughts, ideas, or suggestions would be greatly appreciated, especially on the Models of Computing Systems course.

As computation becomes smaller and cheaper and more powerful, the big question remains “What are we going to do with all that?”. Cell phones and iPhones are one answer to that question, but in some sense a boring one because they’re mostly just littler laptops. Siftables, on the other hand, are representative of some of the genuinely new possibilities that these technologies enable, and are therefore much, much cooler :-).

To be honest, it’s not the best talk in the world, and probably not as compelling demo of the possibilities as one might hope for. That said, I can definitely see these being a blast, especially as people come up with cool new ways to use them.

Also, many apologies for the silence here. I’ve been much more active on Twitter than here; things have been super busy, and the 140 character world of Twitter has been much more amenable to my life and schedule than thoughtful blogging here. Lame, perhaps, but the truth nonetheless. Figuring out the balance is going to be a challenge, but that’s not today’s activity.

I was debating whether to install this software (which in theory supports Mac OS X), so I did some Googling first. There wasn’t anything very concrete, but there were some suggestions that Apple had included this kind of software in OS X at some point, and that Apple’s was much better than APC’s.

So I plugged in the provided cable that ran from the battery backup to a USB port, and Lo! and Behold! it immediately recognized the battery backup and nifty new options appeared in the Energy Saver panel of System Preferences! I set it to shutdown when the battery was down to 95% of capacity, and unplugged the battery backup from the wall, and it shut down beautifully. Without APC’s software.

Problem solved!

Thanks to all those that contributed to the many technologies great and small that allowed me to figure this out quickly and without having to call people, or post questions, or any of those annoying things.

photo credit: hradcanska

Today I got an e-mail with the receipt. As an attachment. In “.MDI” format. Whatever the hell that is.

I was pretty sure we were going to find out that this was a M$ format before I’d even bothered looking, as it’s almost always people that have been sucked irretrievably into the M$ vortex that blithely send out files in annoying proprietary formats without considering the possibility that not everyone has sunk loads o’ dosh and a major organ into M$ software. I was right. It turns out that it’s Microsoft Document Imaging format, which apparently scans physical documents and converts them into TIFFs. But instead of then using the open, nigh on universally supported TIFF, they wrap (I’m guessing) that in their own goofy MDI format so people like me can’t open the documents.

Charmed. I’m sure.

Nothing I tried (and I tried quite a lot of things) would open this MDI file up, so I (nicely) wrote back and asked if he could re-send the file in an open format, like plain text or PDF. A model of restraint, I was. Really.

They promptly sent a second message with a new attachment in “.doc”. Good on the promptly. Less winning on the “.doc”, since that’s clearly not an open format. Happily, however, NeoOffice was able to open it up, sparing me a second round of e-mails with this nice person.

And what, after all this fun, did this remarkable M$ Word document contain?

A single, small image.

The image looks like a scan of a small bit of a spreadsheet. A small bit. No names (theirs or ours), dates, or any other standard “invoice” information. Just 10 lines of text, four of which are labels, four of which are actual entries (the rental amount, VAT, etc.), with the rest being sub-totals and totals.

In other words, a ton of machinery to obfuscate a quite small bit of information.

I just hate it when that happens…

Regular readers here will likely remember various past posts extolling the virtues of Dagstuhl, this really wonderful computing research facility in Germany. I’ve been lucky enough to attend several seminars on the Theory of Evolutionary Algorithms in the past, and have taken (and posted) quite a few photos from those trips.

A few months ago I had the (totally) unexpected pleasure of being contacted by Christian Lindig, a member of Dagstuhl’s scientific staff, and asked if I would be willing to return to Dagstuhl for the specific purpose of taking photographs for them. They’re apparently in the process of re-doing all their brochures and such, and liked what they’d seen on Flickr.

As a result I’ve spent a very pleasant few days back at Dagstuhl in some gorgeous spring weather (I’ve only every been here in the winter before), enjoying the company of a fine group studying the Design and Analysis of Randomized and Approximation Algorithms. (They’ve been very patient with an intruder who always seemed to be waving a camera about, and for this I am grateful.)

I’ve taken something over 1,000 photos, with a few more planned for tomorrow morning before I leave. Some of the participants have asked if the photos will be made available. I have uploaded everything I’ve taken this week to my “events” account on Flickr, all under a Creative Commons license, which means that participants are welcome to download and use any that they wish, as long as they provide attribution. (Note that I am not, and can not, provide any sort of permissions from individuals photographed – that’s their right and prerogative. If you want to use someone here in a beer ad, you need to get their permission first.)

Where are they all?

• Everything I’ve taken this week is on my “events” account.
• I also have a Dagstuhl set on my “real” Flickr account that has some of my favorites (with cleaning, cropping, etc.) from my various visits to Dagstuhl. At the moment this set is heavy on shots from previous trips, but I hope to add more from this visit as time allows.
• Earlier this year I posted everything (without cleaning or editing) from the Jan/Feb seminar on Evolutionary Algorithms to my “events” account.

It’s not yet clear what all Dagstuhl may do with these, but they will contact anyone who is recognizable in a photograph for permission before using your image in any of their materials. If anyone objects to being included in these vast oceans of photos, please let me know and I’d be happy to remove the photo in question.

Thanks again to Christian for inviting me out to Dagstuhl, and to the Randomized and Approximate Algorithms group for being patient “hosts”. Enjoy the photos!

I’ll try to post at least sporadically in the upcoming weeks, but I suspect things are likely to be light here well into the summer.

There’s a YouTube group devoted to this thing, and the number and variety of little clips there also speaks well to the Phun’s flexibility. We even have one person building a binary adder, and another a working pinball machine. Very, very cool.

The sad, sniffle, miserable bit is that Phun doesn’t run on Macs at the moment. It supports for Linux and Windows, though, and there are people working on a Mac port, so my fingers are crossed. It just seems like it would be too damn much fun to play with.

Just finished my GECCO reviewing, and I must say that is seriously sucks when people don’t attend to even the most basic of issues. Two things almost guaranteed to majorly annoy a reviewer:

• Weird random floating fragments of text that are obviously the disemboweled remnants of some cut and paste action.
• Only 8 entries in the bibliography on a subject that has been heavily researched for over a decade.

And just guess the average publication date of 8 fine references.

1985.

Yeah, over 20 years ago.

3 entries were books (two of which were over 10 years old), and the only 2 journal articles were from 1938 and 1964 respectively.

Strangely enough, I didn’t encourage acceptance of that paper.

The really depressing thing is that most of our (undergraduate) students at UMM would do better than this.

No, maybe that’s the uplifting thing.

Maybe the really depressing thing is that I see papers with this kind of bibliography fairly often. I’d almost recommend some sort of automatic rejection system for obviously stupid bibliographies, but then people would just start padding their bibliographies with random citations to get past that blockade.

Sigh.

photo credit: markopoulos