Robotic Rodeo -- Day 2 -- Somebody taunted murphey

The day started out early--about 3 AM Pacific time. We headed straight to Fort Benning to set up for our demo in the chilly morning air, fortified by a breakfast of soggy, lukewarm egg muffins.

From that high point, the day rapidly went downhill. The radios, which had worked so beautifully the day before, gave up the ghost with a vengeful permanence. If I had known at that point that it was simply the first taste of what was to quickly come, I might have followed suit.

The demo was at 10:30, a couple hours away. At first we didn't panic, assuming that the radios could be resuscitated. As time ticked away and radios remained stubbornly silent, however, the Antenna Products people became more and more frantic. A team of heart surgeons racing to beat a rising flood wouldn't even have approached their intensity. We were working on issues of our own so we couldn't watch, but Davin kept us updated on their progress. It went something like this:

"They're checking the connections."
"They're checking the linux kernel."
"They're reinstalling linux."
"They're opening up the radios."
"They're checking the circuit boards."
"They're replacing the circuit boards."
"They're stomping on the radios."
"They're rebuilding the radios from scratch."

The Antenna Products people were under a lot of stress, and Davin finally decided to stay at our own booth after one too many over-the-shoulder suggestions got him threatened with a fist to the face (these were big Texas guys). I don't think the guy was joking, either. At one point, one of the Antenna Products guys came over and said that the boss had just fired two people back home.

Like I said, though, we were dealing with problems of our own. For some reason, an ugly bug had chosen that morning to rear its head in our code. I finally had to give up working on that because we had to attempt to implement our fall-back comms solution: off-the-shelf wireless Internet.

Since we hadn't worked with it hardly at all, and we were down to our last few minutes before the demo, that predictably didn't go well and we finally gave up on that as well. What we didn't realize until later was that most people were having communication issues, due in part to the sheer number of people in the same tent all trying to use the same frequencies.

Also, it didn't help that someone had brought a massively overpowered radio that was drowning everyone else out. That was our suspicion by that point (confirmed later) and Davin got the person-in-charge to make an announcement over the PA for everyone NOT doing a demo to turn off their radios, but of course the vendor didn't. Their comms worked great.

The time for our demo to start came and went with us still trying to get a robot working. We finally gave up on the comms and simply planted our robot at the front of the demo area. If nothing else, we could demonstrate how you could plug and unplug two different sensors and they would automagically work.

Except one didn't. As we discovered later, the actual cord for the sensor had gone bad. The cord. When was the last time you ever saw a cord go bad? That's right, never. It just doesn't happen. Davin glossed over the issue as best he could, but at the end of the day it was a totally disastrous demo. The one tiny saving grace was that most of our audience was just a busload of school kids who had been trucked out to look around, and they don't usually have fat, multi-million dollar contracts to give out.

The rest of the day was spent working over radios, robots, and sensor cords. By evening time, everything was coated with dust and we were all hungry and tired, but at least the radios were starting to work. Mostly due to everyone else going home and freeing up the airwaves. We finally packed up and followed suit. Davin had pushed off all the unofficial demos he had promised people to the next day, so it would be a late night. Hopefully, the next day would be better.

Robotic Rodeo -- Day 1 -- Setting up

Wednesday was setup day. The rodeo was held right on the military base, with the building-sized tent set up on an old firing range, to judge from the number of empty shell-casings that littered the ground. I contemplated throwing a few of them into John's backpack, just to make things a little more exciting when he tried to go through airport security on the way home, then thought better of it. If he were wrestled to the ground and tazed, it might hold up the whole security line and I'd miss my flight as well.

The tent had probably 50 booths, otherwise known as "folding tables." Since our company had turned borrowing other companies' equipment into an artform (our robots, laptops, radios, pretty much everything but the code we brought had been bummed off someone), we saw no reason to stop at the rodeo and talked AMREL, a laptop company, into letting us share their booth. We were even generous enough to give them one of the two tables on the second day.

Over the course of the rodeo, we borrowed additional robot parts from Segway, tools from AMREL, and additional antennas and radios from Antenna Products. We took AMREL's demo slot (you can't really demo a laptop, right?) and crashed the last 10 minutes of one of Segway's demo slots. In the afternoon, Davin talked AMREL into buying us lunch.

I felt a little bad about all our mooching, especially since it was more of a cycle than straight-up borrowing. We'd take one of Antenna Product's radios, break it, give it back, and borrow the next one at the same time. They could barely fix their equipment fast enough to keep up with us. Davin had to promise them ever-increasing future profits from our partnership just to keep them from beating us with wrenches.

The two robots we took to the rodeo, sans all their radios, laptops, and other hardware accoutrements
Left to right: Segway RMP 50, Segway RMP 400

By the end of the day, however, everything was looking rosy. With the help of Antenna Products, who made the radios, we got the RMP 400 to venture further from Home Base than he ever had before. The laptops were in fine form and the computer programs had brought their A-game. Our first demo was at 10:30 the next morning and our confidence was high.

There was one thing we forgot to take into account, however: Murphy's Law. We would discover three things the next morning.

1) Having an early demo slot is a bad idea. If something goes wrong, you have no time to fix it before showing--or not showing--your demo to top military and civilian leaders whom you've specifically invited.

2) It's a lot easier to make your radios work when there's not 49 other companies trying to make their radios work at the same time. Especially if one of them is nefarious.

3) Working radios are kinda essential for a good demo. When your robot is tethered to your control computer with a three-foot cable, it's hard to explain the advantages of your system to, say, a bomb-disposal technician.

If you've got an iron stomach and don't mind a little carnage--at least someone else's--tune in tomorrow for the next compelling segment in our ongoing saga: Robots Gone Wild: How Boeing Almost Lost Their Entire Robotics Team to a Crazy Robot From 5D Robotics, Inc. Fortunately, the Driver Managed To Evade the Military Police, Since I Really Didn't Want to Spend the Next 10 to 15 Years With Three Off For Good Behavior at Fort Benning, Charming As It Is.

Also, we need to talk with our saga-naming people.

Latest project: robotic bike

Our latest project at work has been robotizing a bicycle. Here's what we have so far:

Robotic Rodeo -- Day 0 -- The Seventh Carry-on

Tuesday morning, three of us from 5D Robotics, Inc. arrived at the San Diego airport. Our destination, by way of the Atlanta, GA airport, was Fort Benning, GA. Our mission over the course of the week was to demonstrate 5D Robotics' capabilities at the Robotics Rodeo.

Everyone knows that a trip of this importance does not go flawlessly. We got things off to a quick start.

You have to understand that the three of us arrive at the airport with 11 items of luggage in tow. Two suitcases or carry-ons each, two large crates of equipment, a carry-on-sized battery charger for military-spec batteries, a banner in long tube, plus a Segway robot. Even after checking what needed to be checked, we had six carry-ons between us. It should be understandable that a little confusion might arise about whose luggage belonged to whom and what exactly we had in tow.

Going through TSA security, John (names have been changed) is pulled aside. He's carrying the battery-charger as one of his carry-ons and that many wires and electronics in a military-green case is a little suspicious. He's taken to a nearby table for interrogation and trying to expedite our traveling, Davin takes a suitcase off the conveyor belt that he thinks belongs to John.

John is finally released by TSA and Davin hands the suitcase he grabbed back to John. John, of course, thinks that the suitcase belongs to Davin, and that Davin was just trying to pawn the job of carrying his luggage off on him. "Why does Davin even have three carry-ons?" John wonders to himself. "He's a Platinum member of Delta's frequent flier program. You'd think he'd learn to pack lighter." Being the nice guy he is, though, John says nothing and takes the suitcase.

We reach the gate, seven carry-ons in tow. Being a Platinum-level member of Delta's frequent flier program, Davin has a seat in the first-class section while John and I will slum it in coach. First-class people get to board first and as they are invited to come forward, John finally tires of lugging Davin's third suitcase. "Here, take this with you," John says, shoving the suitcase at Davin. "Being first-class, you'll have an easier time getting three carry-ons past the gate agent than either of us."

At this point, Davin thinks that John is now trying to pawn his luggage off on Davin, but he takes the suitcase anyway. The gate agent manning the microphone sees Davin coming with his three carry-ons and quickly makes an announcment--"We remind our passengers that there are only TWO carry-ons allowed per passenger"--but it's too late. Pretending not to hear, Davin gets past the ticketing agent and is free.

Arriving in Atlanta, Delta does its best to give us all heart attacks by cleverly moving our equipment crates from the regular baggage carousel to the oversized-baggage area, but we finally locate at and load it into our rental minivan. We drive for an hour and a half down to Columbus, GA, finally arriving at our hotel late at night. As we unload the minivan, John turns to go inside with a single backpack in hand. This is too much for Davin. "Do you want to take your stupid suitcase?" he asks, shoving the seventh carry-on at John.

John looks at it. "It's not mine," he says. Davin looks at me. "It's not mine," I quickly say. Davin frowns. "It's not mine," he says.

We stole someone's luggage. From security.

We take the bag up to my hotel room and start digging through it. We don't see any identification on the outside (Owner: "It's a carry-on! There's no possible way it could get lost.") and there's nothing inside but a stack of brand-new clothing with tags still attached and, inexplicably, a complete roll of about 5o Hefty trash bags.

Doing a second inspection of the outside of the bag, I finally notice a tiny scrap of sticker left over from some long-past flight with the name "Doe/Jane" on it. Since we took the bag from security, we don't even know which airline the person may have been flying, so I just call Delta.

It takes several minutes to get across to the baggage claims lady that we were in fact trying to return luggage rather than looking for a lost bag of our own, but she finally understands. "Well, just bring it back to the airport when you fly home," she says. Since that won't be for another another three days, Davin gets online and starts searching for every Jane Doe he can find. There are several, so he sends emails to the most likely ones.

One of the Jane Does, according to Google, ran a 17-minute mile in some race, which might explain her lack of catching up to us if she was, in fact, the one we had stolen the bag from. "Wait!" she calls out in her wavery voice, shuffling after us with her walker as we casually stroll off into the distance. "Come back with my suitcase! It has all my trash baaaaaagggggs!"

Anyway, by that time it is late and we are tired. "The day could have been worse, though," Davin points out. "Someone could have stolen our bags instead of vice versa. At least Jane Doe has the clothes she's wearing, and you can pick up trash bags practically anywhere. We wouldn't get very far at a robot demo without a robot though."

As we would find out the following day, however, there are more things than just losing a robot that can make a presenter start sweating at a robot demo. Stay tuned for the next installment of "Murphy's Law: An In-depth Exploration."

Nothing like a good addiction to while away the hours...

If ever there was a time to give up smoking, you'd think it would be when you were trapped half a mile underground with limited ventilation, limited diet and exercise opportunities, and other people who might not share your same opinion of the health benefits of cigarette smoke.

Apparently not.

According to CNN one of the first requests made by 33 miners trapped 2300 feet underground was for cigarettes.

Credit Scores

Child has an excellent credit score, but no income.

I have an income...but as we found out today, no credit score. Not a bad credit score, just no credit score. Apparently credit cards don't build your credit if you're responsible and pay them on time, and (car) loans over seven years old don't count.

That leaves us with basically four options as far as obtaining a house goes.

1. Wait a year to buy a house while I build credit by taking out loans I don't need and paying interest I don't want to. Note that credit scores are a black box, so this isn't actually guaranteed to give me a credit score.

2. Wait a year to buy a house while we save enough money to put down 20% on a home, jump through all sorts of crazy hoops to prove to our mortgage lender that I'm a responsible buyer despite the lack of a credit score, then almost double the amount of interest we pay on our mortgage.

3. Save money until we can pay cash for a house. Note that this would actually be our daughter's house, since given California prices, Child and I will be kicking the bucket about the time we finished saving. Since the plan is for Ash to be supporting us in our old age, not vice versa, this option is out.

4. Steal one under cover of darkness and move it somewhere convenient like the beach, or perhaps my work's parking lot. I'd have to look into how much it costs to hire someone to move a house though. And they'd probably run a credit check.

Backwards

I'm teaching Ash the alphabet backwards, but I'm thinking about teaching her the numbers backwards also. We'll start at infinity and work our way down.

Writing Meeting

So I finally found a writing group locally and attended a meeting last night...and this morning.

Yes, it went that long.

Pros: nice people, decent critiques.

Cons: I arrived at the meeting at 7:30 p.m., and got home at 1 a.m.

When I arrived, it was only the host and I. My first irritation was that it was 15 minutes after the meeting was supposed to start that the next person came in, and 45 minutes or more before most of the people had arrived and we actually started the meeting. Apparently this wasn't uncommon. From the joking as people straggled in, I gathered this was the usual modus operandi.

The second major irritation was that it took five hours to critique what every other writing group I've attended has done in two. The problem started because we didn't get each other's entries ahead of time. Each person showed up with their submissions and started by reading them aloud at the meeting. Seven submissions, ranging from two pages (mine) to six or seven pages, and you're talking probably 45 minutes just for the reading alone.

Without any advance preparation, you're critiquing on the fly, which is inefficient and doesn't allow for any sort of thought-gathering or organizing, which means most critiques were stream-of-consciousness. Throw in one or two people who like to ramble, and there was a very low signal-to-noise ratio.

That said, the critiques were good enough, but again, nothing that couldn't have been accomplished in half the time with a little more organization.

I'm not sure I'm going back. The usefulness of the critiques didn't really seem to outweigh the late bedtime and frustrating meeting procedure. Maybe I can find another group that follows the sort of format I'm a little more appreciative of...or perhaps start one.

You're kidding, right?

The above poll from CNN.com astonished me. I can completely understand there being a huge variety of opinions about the wisdom of building an Islamic center near Ground Zero, but there should be no question as to whether they have the right. Isn't religious freedom one of the foundation stones of our country?

(Granted the poll is unscientific, and I wouldn't be surprised if many of the respondents confused the "right" to build an Islamic center there with it being a "good idea" to build an Islamic center there. If that's the case, though, then I can rant about the poor comprehension skills of poll respondents.)

Slow down there, big guy!

Today I biked from our new home to my new job for the first time. According to Google Maps, the route I took was 5.1 miles, which isn't terribly far, but the terrain is very hilly. A lot of ups and downs. I was planning on it taking about 45 minutes, so I allotted an hour, but managed to make it in about 30 minutes. Not nearly as bad as I was afraid it would be.

Of course, it was overcast, calm, and a cool 65 degrees, but even when we get to the hot summer weather it shouldn't take longer, just be more uncomfortable. (Mostly for my coworkers, since they'll have to smell my sweat.)

A few blocks before the office, there's a giant hill. As I approached it on my bike, I glanced up to the snowcapped top, where I could see wispy clouds and giant condors slowly circling. (I might be exaggerating: they were probably just vultures, lying in wait for hapless bikers foolish enough to challenge the hill.)

Anyway, I was halfway up the hill, in the lowest gear, barely going fast enough to keep from falling over, when I saw one of the giant snails that I've been noticing since we moved to California. I kid you not, my first thought was: "At least I'm going faster than him."

Pretty sad.

P.S. I called the snail "him" because only a guy snail would be stupid enough to set off on a trek across four lanes of traffic when your top speed is 6 inches/hour. He wasn't even at a crosswalk.

Stir-fry

Sorry about more geek humor, but this made me laugh.

Today I was on an airplane, browsing through some third-party computer code looking for a particular programming function (a block of code that performs a given task). In the file I was looking in, all the functions manipulated strings of characters functions, so all of them were prefixed with "str," short for "string," and pronounced "stir."

I passed such functions as strcpy (copy a string of characters), strcmp (compare two strings), and strlen (get the length of the string), then I came across another one: strfry.

The description of the function? "Sauté string briskly."

It was so out-of-the-blue in the staid programming code that I started laughing. Even though it obviously wasn't the function I was looking for, I had to do a little more digging to find out what the function did. Apparently it randomizes the order of the letters in the string. Apt.

Open Source Software

I love Ubuntu and open-source software. I love that I can download and install an entire operating system and a comprehensive suite of software...in half an hour. For absolutely free.

5th of July

Yesterday, Child and I went to my brother-in-law's family's land to relax a little. While there, Child took Ash out on an inner-tube for a little casual floating around the pond. The water was freezing cold (so I heard; water isn't my thing, particularly freezing cold water), so most of the kids stayed on the inner-tubes.



Of course, the problem with that was that when Child started floating downstream, she could either get into the ice-cold water, or end up in the Gulf of Mexico. Due to logistical reasons (I was holding an iPhone) her husband was unable to save her, but fortunately my brother-in-law swam to her rescue.

TCPlease make up your mind

Sorry about the geeky post. People not interested in network protocols can skip it.

I was trying to figure out which network protocol (UDP or TCP) a robot was using, but I wasn't getting much help from the robot provider.

Email: Communication will be TCP/UDP (Can be TCP/IP if you prefer).
Documentation: Robot Control uses a standard TCP/IP protocol.
Code comment 1: This controller opens a TCP/IDP connection
Code comment 2: Waiting for data on port UDP

Half those statements don't even make sense. I finally had to look at the actual code to figure out that it was, in fact, using UDP.

Long Week

Drive to Utah. Attend wedding reception. Attend baby blessing. Attend family reunion. Fly to California. Look for a place to live. Fly to Utah. Drive to Idaho. Attend wedding reception. Pick up extra baby for three weeks.

Whew. It's been an exhausting week. Let's start from the top.

The week began with my cousin's wedding. The reception was held in my aunt's back yard, and seemed to go very well. If there's one thing my extended family is good at, it's making up food for large numbers of people. It's a skill honed over years of family reunions, but even so I was impressed with the spread (can you tell I'm a guy?).

Child's one disappointment was that the fudgeballs on toothpicks turned out to be meatballs on toothpicks, but not before I rescued one that was about to go into her mouth (after first putting it there). The six chickens in the backyard also enjoyed the reception, or so I gathered from their delighted pecking at the continuous stream of food conveyed from the tables to their coop by numerous small children.

That was on Saturday. On Sunday, we attended the baby blessing of a small niece. She was very well-behaved for a two-week-old and the blessing went well.

That evening, we discussed the placement of two small children (1 1/2 years, 6 months) who are currently parentless due to their parents being in jail (for the umpteenth time). If anyone tries to tell you that drug use affects no one but the drug user, feel free to laugh in their face. I could probably list 500 people (by role, if not by name) whose lives were negatively impacted by the drug use of these parents.

Of course there's their children (who deal with physical and emotional neglect, if not abuse, which will probably destroy the rest of their lives, as well as future generations), their friends, parents, siblings, a constant stream of people they steal from to sustain their drug habit (including parents, friends, and family members), judges, lawyers (actually, maybe it's a positive impact there!), policemen, jail employees, drug program employees, religious leaders, landlords/motel employees...that's just off the top of my head.

I could rant on for several more paragraphs (and started to, before erasing it), but that's probably a topic for later. Moving on with the week...

Family reunion! For a change, the weather was sunny instead of rainy, but for some reason my extended family apparently has a fascination with alpine retreats. Just once I'd like to camp at an altitude lower than 8,000 feet. The scenery might be nice, but it's frigid at night. Not so bad when you're snuggled in a double-wide sleeping bag with your wife, bad when there's a baby sleeping between you who hates being under covers. Worse when your allergies kick in the moment you step out of the car, and apparently morph into some sort of cold, complete with fever and hyper-sensitive skin. Add to that the dry alpine air that dries your lips to the point that it hurts to smile, and you don't have a very relaxing vacation. Ah, the good ol' days of Missouri, with the warm air, warm lake, warm river, and chipmunks that don't pee on your air mattress...

But I shouldn't dog the family reunion too much. It was nice seeing everyone again, and...well, yeah, that's about it. When you're trying to deal with two squirmy kids, both of who need constant holding and one of which will stick any alpine detritus she can find into her mouth, everything else is mostly a blur.

Wednesday morning we drove to Salt Lake City, flew to Long Beach, rented a car, drove to Carlsbad, and checked into our motel. Kudos to Child for putting so much effort into our itinerary; everything went very smoothly. The company was paying for the trip, but in an effort to keep costs down we stayed at a Motel 6 for $55 a night. Granted, that price didn't buy us amenities such as a toilet seat lid, alarm clock, a working TV, or a continental breakfast, but they threw in morning coffee and the soothing sounds of the nearby interstate for free.

Our daily activities in Carlsbad consisted mostly of driving, eating, and looking at houses and apartments. We hooked up with a real estate agent who went far, far out of his way to accommodate our brief stay (I guarantee his commission, should we end up purchasing a house through him, will not have been worth it). We found a few possibilities, but I think we're going to end up just renting for a few months after we first move there while we continue looking. It's very hard to purchase a house when you're living in a different state, and I don't even want to try.

My mental view going to California was a picture that consisted mostly of traffic and gang wars. Although we didn't see any overt gang members, Child claimed she heard gunshots during one night and the traffic was everything I feared. Every road seemed crowded, and even though people complain about Utah drivers, they have nothing on California drivers. Because of the thick traffic moving at high speeds, if you have to change lanes, you just have to swerve out in front of another driver. The hope is that their car is enough more expensive than yours that they don't want to get in a wreck, and so slam on their brakes to let you in.

Returning to the airport Friday evening during rush hour on I-405, I found out why Karen (our GPS unit) had taken us by a toll road on Wednesday when we first arrived. Traffic was stop-and-go for about 15 miles on the regular interstate, adding about an hour to our travel time. Watching the estimated arrival time on Karen slowly converge with the departure time of our flight, I simmered in my juices and mentally kicked myself for trying to save the company $4.75 ($4.75 for a toll?! What is this, California?! Oh, right...) but it was too late to change horses at that point.

After exiting the interstate, we made sure to stop at every traffic light on the way to the airport. Finally reaching the airport, we hurled our rental car key at the Alamo people, sprinted to the JetBlue kiosk in the terminal...and found out that our confirmation code didn't work. Neither did scanning the barcode or looking up our flight by our credit card. A desk attendant called for people leaving on the SLC flight, so we ran over to her and she finally got us checked in. We reached the gate at the very end of pre-boarding, so we actually had a few minutes to spare, but that's cutting it too close for my liking. In a normal-sized airport (Long Beach is a small one), we wouldn't have gotten through security nearly as fast.

Arriving in SLC around 10:30 PM, we picked up our car and headed down to Provo to spend that night. It's normally a 45 minute drive, but we didn't arrive at Child's parents' house until after midnight. There was nighttime construction going on along I-15, so the entire interstate narrowed to a single lane for several miles. More stop-and-go traffic. After dealing with it on the other end of our flight, I wasn't particularly happy to see it again--much less in the middle of the night when I was exhausted and just looking to crash in a nice soft bed.

We finally made it, slept for a few hours until Ash decided that it was morning time, then got in the car and drove four hours back to Idaho. After unloading the car and putting everything away, all I wanted to do was nap but it was time to go to the wedding reception of another cousin. At least they had cream puffs.

While at the reception, Child and I picked up one of the afore-mentioned children from my parents (the six-month-old). We'll be caring for him for the next three weeks, then returning him to my parents when we move to California.

It's been a long week.

Yellowstone

Yesterday we finally got around to visiting a scenic wonder in our metaphorical backyard: Yellowstone National Park.

It's an amusing place to visit because you'll be driving along, minding your own business, then suddenly hit a traffic jam of cars in the middle of nowhere. People will be running along the road carrying binoculars and cameras, with new arrivals parking haphazardly wherever they can find a spot and hurling themselves from their cars to join the crowd.

The reason, of course, is that Wildlife has been spotted. A wolf, a bear, or perhaps a particularly scenic buffalo all warrant the mass destruction of several hundred yards of roadside wildflowers if there doesn't happen to be a pullout handy. The downside is that sometimes, you have to have a 200X zoom lens on your binoculars to actually see the Wildlife, so those of us who weren't smart enough to bring binoculars with that magnification are left squinting into the distance trying to figure out if the black spot we're looking at is an elk or a tree stump.

Of course, a lot of the more common wildlife know that their only chance for personal recognition is to make themselves readily accessible. Buffalo were especially good at this, and could be found near the road at many locations. By the end of the trip we were buffalo connoisseurs, only deigning to stop if the buffalo was closer than 5 yards to the road, had particularly well-groomed fur, and perhaps threw in a little song-and-dance number.

At the beginning of the trip, though, we weren't sure what we'd find so we snapped pictures of whatever black stumps we could find:


Pictured below: Roaring Mountain. It was interesting enough, although I didn't actually hear any roaring. Or snarling, hissing, or even grumbling for that matter. Maybe I just wasn't paying attention. It seemed to be a common theme throughout our trip that the sights we saw didn't quite live up to the pictures we saw in the various Yellowstone-sponsored publications. Either Yellowstone has a dedicated Photoshop crew, or we just hit the park at a bad time of year.


Pictured below is another prime example. This is supposed to be Mammoth Hot Springs, which in all the pictures I've seen has brilliant colors and pouring waterfalls. We were lucky to see a trickle of water from one or two pools, and the predominant color was grey. The below patch of dried-mustard yellow was pretty much the only other color we saw. Ash's expression accurately mirrors my own feelings.


The below picture was the best part of Mammoth Hot Springs, and it wasn't even at the Hot Springs proper. It's from the little loop that goes behind and above the main hot springs.


For lunch, we stopped in the little town by Mammoth Hot Springs, where three doe elk had smartly positioned themselves near the picnic tables to take full advantage of lunching vacationeers. Their migration patterns seemed to be dictated by the flow of tourists rather than the seasons, and about the time that lunch finished they moved off across the main square to take up a new position by the botique stores to catch the after-lunch window-shopping crowd.


Ash's hightlight of the trip was the strawberry she got to eat at lunch. Would that we all were satisfied with so simple a delight.


Some of the buffalo were clever enough to bring along the kids, knowing that tourists are unable to resist taking pictures of baby-anything. (Child took dozens of pictures of a "baby geyser," which I would have classified as a gurgling golf-hole but since it was 1/10th the size of a normal geyser, it was apparently much more attractive. I don't pretend to understand.)



On the plus side, I did manage to catch a shot of the elusive 8-legged buffalo. Seldom seen (i.e., photographed less than 500 times a day), he slipped across the road like a 2000 pound shadow before fading into the grass a few feet from the roadside.


The obligatory Old Faithful shot. Our timing was excellent; it began to erupt right as we walked across the field towards it. Other than that...yeah. Old Faithful. In its defense, it's probably kinda hard to live up to the hype it gets.

The Fountain Paint Pots. Bubbling mud holds a strange fascination for me. Maybe I should see a psychologist. I think it's because geyers are all up in your face, shouting, "Hey, here I am, everyone look at me," while mudpots are more like, "Heh heh heh, you have no idea what I'm plotting beneath this opaque, mysterious liquid, but I'll give you a few cryptic hints in the form of a sulphuric-smelling bubbles."

Yeah, I should probably see a psychologist.

Monkey Business

Friday afternoon (5/28/2010), Child and I left Idaho and drove the four hours down to Provo. There, I dropped her off at her parents' house and drove another four hours down to southern Utah. In the North Wash area, some friends and I hiked a canyon known as "Monkey Business."

I'm not sure if some of the people want their names posted, so I'm going to leave them off. (I've become a little more sensitive to this issue as of late...)


Sometimes it's hard to tell where a canyon really begins. Most of the time, a few shallow gullies through the desert come together into a wash, which eventually turns into a canyon. The wash we started down came to a nice, abrupt drop-off, though, albeit one that could be hiked around and downclimbed.



I liked this multi-level shot. Traffic jam in the canyon. Actually, someone else was taking a picture from the front, but for some reason I liked this better. I think it gave a better idea of the 3D nature of canyons.


So the below picture isn't anything particularly spectacular, but it amused me. It looks like S. is squeezing through a tight spot, which he is...only this picture isn't right-side up. It's sideways.


The picture below is actually the correct view. He's lying on his side, squeezing under a boulder.


I realized after picking my favorite pictures from this trip that none of them were just normal pictures of the canyon. It's like anything you do a lot: the activity itself becomes a little ho-hum, and it's just the little out-of-the-ordinary things that become interesting. Anyway, I scrolled through the pictures and found this one just to show off the canyon itself.


This picture was taken by one of the girls that came on our trip, and I just liked it for some reason. It doesn't have the pretty orange and reds of some of the other parts of the canyon, but it has a very...canyony feel to it.


One of the most common canyon creatures you'll see are small lizards. Like the canyon frogs, they have the ability to climb straight up the walls, and they're fun to watch as they scurry around.


This was one of Child's favorite pictures so I threw it in.


I liked this one. We reached a narrow section of the canyon that was easier to stem over than go through. A lot of the time, the group was spread out so much that it was hard to get a picture of more than a couple people at a time, but this time I managed to catch them all together.


This is what's known as a "guided rappel." The trick is to guide the rappeller into the pool of water.



And everyone's least favorite part: the climb out. This climb is known as the "Kelsey Exit," named after the man who first found it, I believe. I've actually been up it once before while leaving a different canyon, and it has only gotten worse. The rock is primarily rotten sandstone, so everything you touch is sandy and slippery. Not only is it steep and hard to climb, but you constantly feel as if your handholds and footholes are going to break, crumble, or slide. Not fun.


But it finally came to an end. Freedom!

Biscuits and...oatmeal?

News flash: despite their similar visual appearance, biscuits and oatmeal doesn't taste nearly as good as biscuits and gravy.

And why in the world would you put oatmeal in a crockpot, much less right next to an identical crockpot containing gravy? Sure, they had giant labels reading "Oatmeal" and "Gravy" on them, but who reads those?

Highly mathematical average

Before a comet or asteroid hit Jupiter last year, astronomers had calculated that an impact like that would happen on average every 350 years.

How did they arrive at that number? The lay-person might (amusingly) think that they had simply taken the only two other known impacts (Shoemaker-Levy in 1994 and a possible impact observed by Giovanni Cassini in 1640), subtracted the two, and got the value of 354 years, but not so!

According to arXiv, arriving at that number involved taking those two impacts, adding "crater counts on Jupiter's large moons and various theoretical calculations", and THEN deciding it was 350 years.

I am suspicious.

Allergies

There's nothing quite like waking up at 3 AM because your eyes are itching like crazy and you can't breath. Relatedly, slowly suffocating in your sleep gives you strange dreams.

And I think evolution got it backwards. Sitting up, it's slightly easier to breath but hard to sleep. Laying down, it's harder to breath, and therefore still impossible to sleep. Why not make it easier to breath when you're laying down? I'd rather spend my days (and nights) flat on my back...although I guess that would make doing my job rather difficult.