Agent Plus Environment

Learning is awesome

My favorite part of just living is how much I learn.

Here are some pieces of advice you might find useful, some cool skills I’ve acquired (maybe you’ll be inspired), and a couple other things, too:

Because lists are awesome, too…

• A GPS is only helpful in localizing large vehicles, particularly when you’re trying to use the GPS to direct navigation. When your vehicle is smaller than the error margin of plus or minus two meters (e.g., an RC car), it doesn’t work so well! (This from last summer, at NASA Langley.)
• Pens with lights attached are a fantastic invention. I got a combo flashlight-pen at GHC last year. It writes. It lights up. This pen lives next to the pad of sticky notes by my bed. Now all my middle-of-the-night ideas are legible!
• If you’re working on a big important project, always work on it, every day. Could be a thesis. Could be a novel, or a software project. Even on the days when you really don’t want to work on it and you’re entirely unmotivated, work on it anyway. Do a tiny little bit, then do a tiny little bit more, and maybe you’ll convince yourself that you are in the mood to work on it after all. If not, at least you did a little bit, right?
• Just how cool people think NASA is. Specifically, how cool people think it is when they find out I interned there, twice. I continue to be surprised. Quite seriously. Are my standards for what counts as super awesome too high? Do I just expect everyone else to be similarly awesome, making my accomplishments average on the scale of awesomeness? Maybe I do … everyone has the capacity for brilliance. Maybe not everyone fulfills that capacity, but I think you’re suppose to take this as your cue to go be brilliant.
• I earned my Amateur Radio Technician’s license. I am now qualified to talk on the HAM radio bands! I know more than I used to about electronics, antennae, and radio frequencies. I’m still working on learning Morse Code.
• Philosophy of mind. I know a decent amount on the subject from my cognitive science background, but there’s always more to learn! A friend and I have delved into some fun readings: Aristotle’s conception of matter and form, Aquinas on the immateriality of mind, Lawrence Shapiro on embodiment and reductionism, and many more. I’m re-reading Shapiro’s The Mind Incarnate, which I initially read in my second cognitive science class ever, some three and a half years ago.
• How to successfully relocate to a new city in a new state. Yeah, I did that. It involved a lot of talking to people, a lot of driving, and a lot of paperwork and standing in lines.
• Just how flexible my sleep schedule can be. I used to be a stickler for getting my full eight hours every single night of the week. I realized over the summer that I can function just fine on a weird schedule of eight hours, then three hours, then seven hours, then maybe five, followed by nine or ten hours to catch up… I’ll write more on this sometime. Carol Worthman wrote a particularly relevant chapter on sleep for Evolutionary Medicine and Health that I plan to outline for you.
• The rudiments of tae kwon do. According to the instructors at the Goddard Tae Kwon Do club, I have a decent roundhouse kick. I’d like to learn more — I’m still very much the beginner white belt.

And a whole slew of technology-related items:

• - Octave, essentially an open-source Matlab.
• - R, a statistical computing language and environment.
• - The rudiments of time series analysis.
• - ROS, an open-source platform for robotics work
• - Mobile Robotics Programming Toolkit (MRPT) libraries, also open-source and also for robotics work.
• - PCL, the point cloud library, useful for feature detection in point clouds.
• - Simultaneous localization and mapping (SLAM) algorithms, as well as other common mapping and path planning algorithms.
• - How to use subversion.
• - Random little things about Ubuntu, including the “alt-f9″ shortcut to minimize the current window
• - How to use the Tobii T60 eye tracker.
• - And so much more …

I wonder if I can double this list by this time next year..?

A month after graduation, I’m well on my way to learning all sorts of crazy new things.

This summer, I’m learning about…

• HAM radio. On Tuesday, I attended the first of a summer-long amateur radio FCC licensing class. I know very little about radios and their components – the president of GSFC’s amateur radio club told a story about how easy it was to build a circuit to convert 5 volts down to 3.3 volts, and kept throwing out electronics jargon. I’m looking forward to increasing my knowledge of the subject!
• Computer innards. On a similarly technical note, my laptop’s hard drive stopped spinning up last week. With the help of a computer engineering friend, I opened up the laptop and replaced the drive. Didn’t even lose a screw! It’s a small step into the world of computer hardware, but that was the first time I’ve opened up a computer, so it counts for a lot.
• Multiple realizability. That is, that people can take entirely different paths to the same place. People with ridiculously different beliefs can still be thinking exactly the same thing at exactly the same time on ridiculously frequent occasions.
• Tae Kwon Do. An activity I’d never done before: martial arts! All the interns/apprentices in my lab this summer were encouraged to try it out, since the GSFC club is so friendly. We’ve learned miscellaneous self-defense maneuvers and more ways of kicking than I remember names for – I even got to kick through a board!
• And software… My lab group is using a variety of software tools and open source code libraries that are new to me: ROS (the Robot Operating System), a code repository via SVN, the MRPT libraries, the point cloud library (PCL), and many more. I’m remembering C++, delving into path planning algorithms, and reading up on SLAM (simultaneous localization and mapping). Yes, it’s a whirlwind of acronyms.

Don’t ever stop

This one’s a life update post, but it’s also a “here’s some cool science!” post.

A few days ago, I graduated from Vassar College with a Bachelor of Arts in Cognitive Science and a correlate in Computer Science. I was decorated with general honors, departmental honors, membership to Psi Chi, and membership to Sigma Xi. My time there was awesome.

What’s next?

No lazy summer!

Well, no lazy summer break for me! I’ve already spent three days in my summer lab at NASA Goddard Space Flight Center, where I’ll be working on a number of software development projects. The primary one is a LIDAR-assisted robotic group exploration project, in which we’re going to have a small fleet of robots — a mothership and some workerbots — use 3D LIDAR data to autonomously map and plot paths through an area. This kind of robot fleet could, eventually, be used to explore other planets. One of the big challenges will be dealing with the 3D image data. I’m looking forward to learning more image processing algorithms!

Another project is the redesign of the Greenland Robotic Vehicle, a big autonomous rover that’ll drive across Greenland, collecting a data about snowfall, mapping, and exploring. Did you know there’s ice on that country two miles thick? I may also get to play with a robot that has stereo vision.

You can see some of these robots (and what life in the lab may be like) in this great video about last year’s interns.

So far, I’ve met a bunch of intelligent, friendly folks, started catching up on already-written code, and begun to delve into the platforms, libraries, and algorithms we’ll be using and developing this summer. Our mentors have already proven themselves to be enthusiastic and helpful. Just yesterday, one of them told us,

“You’re engineers at NASA. You want to go where things are, and then go beyond.”

That may end up being our theme for the summer.

A little overwhelming?

There’s going to be so much going on. It’d be easy to get overwhelmed — especially now, jumping in and floundering around in the code, the projects, the people. So much to learn.

But as I sat in the lab today, reading about ROS, going through tutorials, reading about PCL and feature detection in point clouds, digging through last summer’s confusing pile of C# and C++ programs, I realized I wasn’t overwhelmed. And it was because of all the other experiences I’ve had that’ve gotten me to this point.

Confidence. My first URSI summer, flailing through Microsoft Robotics Studio and complicated conceptual theories. Figuring out how to deal with webcams and image data my second URSI summer, reading papers on optical flow and implementing algorithms. Last summer: excavations of an open source flight simulator, the Aeronautics Student Forum, dealing with different work styles and communication styles in my LARSS lab. And more.

I think about all those experiences, and I’m not afraid of this summer. I could almost be overwhelmed — perhaps thinking that everyone else has more of the right kind of experience; I wasn’t trained as a classic engineer — but I know I can succeed. My non-engineering, cognitive science background sets me apart and lets me look at problems a little differently than everyone else. I’m an asset.

I know how to learn. I know how to do research.

I can conquer this summer.

A comprehensive Cognitive Science and Computer Science internship resource list

As my undergrad years draw to a close, I’ve compiled a list of internships and related opportunities for students in Cognitive Science and Computer Science. Most programs are also open to students in other engineering and technology fields and are not limited to undergraduate students!

Take a look! Pass along the page to anyone you know who may find it useful. Although deadlines for some summer 2011 programs have passed, many have March or April deadlines, and many of the semester or year-round programs have later deadlines.

Aeronautics Student Forum

Wednesday, August 4th. 10AM. The Aeronautics Student Forum.

My lab is lined up in the front row, fidgeting, exchanging nervous glances. We trade seats between the other students’ presentations, taking turns with the laptop to read over the half-done powerpoint.

The motion tracking camera system is set up (we were in the building until 10pm the previous night, testing our hardware and software, ensuring it’d all be ready to demo). One of the cameras lurks beside the white screen, ominous, a constant reminder that it’s our turn in an hour, and like or not, we don’t have our finalized slides and some of us don’t even know for sure whether we’ll be speaking.

It was nerve-wracking.

It was also remarkably exciting.

Presentations, preparation, control

I usually plan presentations out to the last sentence. I know I’m not an improv whiz, so I practice my talk out loud over and over. Any slides I have, they’re done at least two nights ahead of time. Practice, preparation, organization. No need to worry because I have everything under control.

This presentation at the aero forum was the opposite.

The previous week, to the relief of my labmates, I’d tried to organize everything (the slides, the talks, the demo). But our mentor, Garry, told us not to worry about any of it. He kept repeating that: don’t worry. It’s just a presentation.

None of us were convinced.

It wasn’t until Garry sat down with me and explained what he had in mind–how he was going to help compile photos and diagrams into a logical order–that I trusted he was right. No need to worry. He had given scores of presentations. He had good ideas. He frequently pulled things together last-minute. It’d be okay.

In short, when he explained that, I consciously relinquished control. I mentioned control (and the lack thereof) in the context of volleyball games with my lab. The same idea comes into play here: Setting perfectionism aside, trusting that someone else is competent enough to get the job done. Teamwork. All that good stuff.

Coming together last-minute

Garry showed up not long after 10AM, printed copies of the finalized powerpoint in hand. As our time slot approached, my labmates and I shuffled discretely through the slides, still worried, still anxious.

Our turn came. We trooped up to the podium, all nine of us. We spoke. Twenty minutes, all told (not too long, really), plus the demo. We explained our newly established Autonomous Vehicle Lab, its capabilities, and what the audience would see in the demo. We flew our quadcopter. We demonstrated object tracking and obstacle avoidance.

It went well. It went better than well: our presentation was splendid.

Everyone knew what to say. Everyone was clear, concise, and comprehensible. Perhaps it was because we were not prepared that we were prepared: rehearsing, in our minds, coherent sentences about our parts of the project. Recapitulating our work with the quadcopters, the DGPS system, the Vicon cameras, the many vehicles and pieces of software. Unsure of what we would need to say, and thus, preparing for the worst.

If not for Garry’s persistent “don’t worry about it”s, I would never have experienced a presentation this way. I’d have planned out that talk and every one after, never daring take a chance on not preparing enough and not practicing enough. Now I know. Our aero forum talk was proof: Things can come together last-minute.

That said, I think I still like having my slides done more than an hour before the presentation. As engrossing an adventure as it was, last-minute isn’t going to become my style.

A new sport

One of the difficult parts of playing a new sport is that I’m not good at it yet.

My lab played volleyball this summer. Every Wednesday after work, we trotted out to the grass behind the conference center, doing our best not to complain about the humidity and heat. We greeted the other two teams in the league (both of which had clearly played volleyball before–not just in gym class in high school, or, in my case, once during a summer program five years ago), we helped set up the nets, and we began bumping a ball around.

Volleyball was not where any of us excelled. Sure, by the end of the ten weeks, everyone in the lab had improved. We could do what might be called a volley. I could be in the right place at the right time to hit the ball, even if the ball then flew off in completely unintentional directions. When I served, the probability that the ball would both get over the net and stay in bounds was greater than chance (if I remembered to stand on the right, that is, because my serves always flew too far left). It was great fun.

It was also frustrating. I knew that given enough practice, I could be a half-decent volleyballer. Instead of the game being a matter of physical skills and pure luck, it could evolve into a complex, strategic battle, with us setting up plays and plotting out how to outwit the other team. But ten weeks isn’t quite long enough to get us to that point. (Sometimes, I’m impatient.) We lost just about every match played against the other teams.

Losing is hard to watch

My lab had split into two teams and recruited a few extra interns, so most days, the five or six of us on my team rotated through four spots on the court. This meant that some games, I stood on the sidelines during the game point.

That was difficult.

I had no direct control over whether we won or lost. I had to stand there, watching, as hands missed the ball, as the ball smacked the dusty grass, or flew too far out of bounds. I had no power over how hard my teammates tried (whether they desired to win enough to dive after the ball; whether they were tired and sweaty and just wanted it to be over). I could be a cheerleader, but I could not actively influence the outcome of the game.

That was new.

My usual sport is fencing: highly individual, always solo. When you’re on the strip, it’s just you. If you mess up, if you lose, you only have yourself to blame. Even in team competitions, you’re just adding up the scores you and your teammates have separately acquired. You don’t realize, unless you’ve been part of a team, how important it is to trust your teammates. And that’s what made volleyball difficult: because none of us were that good, it wasn’t easy to trust my teammates to be there, backing me up, putting in their best effort to win even though the games were casual and couldn’t be taken seriously given our level of experience.

The thing about trust is, most times, it has to be earned.

Trust and control

Fortunately for my lab, playing volleyball is not what we did full-time. When working on our summer project–establishing the Autonomous Vehicle Lab–I learned I could trust my labmates to have my back. We all cared about the outcome; we could trust each other to each do our part. Not being in control of every little detail (and occasionally standing on the sidelines) was okay, because I knew my labmates were trying just as hard as I was to debug their programs and get the quadcopters flying.

I guess the moral of the story is (besides the obvious “teamwork requires trust”), if you ever have the chance to play a new sport, do so. You never know what you’ll learn.

Words are still great.

Having devoured the remainder of China Miéville’s Perdido Street Station and started on The Scar, I thought I ought to share my continued collection of wordly wonders. (Don’t forget to check out the first half of the list!) Some novel, some familiar but infrequently encountered and marvelous, and all commendable to have in one’s vernacular.

• palimpsest
• bonhomie
• jurisprudence
• desquamate
• abbatoir
• ululate
• prurient
• efflorescence
• phalanx
• salvo
• etiolate
• scurrilous
• conniption
• rictus
• ordure
• priapic
• agglutination
• ossified
• puissance
• stygian
• protuberant
• obstreperously
• pudenda
• phlogistic
• opprobrium
• aggrandizement
• tinnitus

Oh, and I have to ask: Do you have any favored words–unusual, rare, or just plain fun to say? I’d like to discover more!