Yoink!

Well, it's now the end of the year.

Some closing up stuff that has gone down. We had awesome performances for the end of the Shakespeare class. Unfortunately I didn't get to take pictures of the performance, but I did get a decent number of behind-the-scenes stuff. Hopefully the college professional photographer got good shots. Also, we got recorded, so maybe I'll get a copy and be able to watch it from not on the stage. Or behind the stage. I mean, I didn't have all that many lines anyways.


^This is indeed Matthew Lawson posing as the Old Lady over Kevin Oelze. In case you're new to this blog, Matthew was my roommate Frosh and Soph years and ended up as Proctor of East, President of Gonzo Unicycle, all-around cool guy, director of the LAC... basically became awesome. Oh, and he brought his trusty staff to graduation.


^Here's Prof. Dodds, who also was the prof for Robotics. We got 4 professors (including the one running Shakespeare) to play the madmen in the play. So awesome. They got the loudest applause besides the main actors.


^Liz Flannery did AWESOME costumes for us. She had help, especially from Glennis here on the right. That's Michael Braly. He was the scheming Cardinal.


Clinic is Done. We've turned in pretty much all our work and it's sealed up in a box. The only thing left was a lovely jaunt up to Oregon on Monday to present at Intel on Tuesday. I was a little nervous because we're showing our work to some of the best digital engineers in the nation. Luckily we got really far. Unfortunately we couldn't send the chip to fabrication due to complications. But, we have pretty pictures of a core of the chip. Also, a young up-and-coming frosh William Koven has volunteered to work over the summer to fix everything up and get it to fabrication. This means fixing up the research group's designs that they wanted to get on the chip as well. Oof. Overall I'm simply relieved it's over even if I am a little bugged out we didn't make it across the finish line. I don't like settling for "close enough."

Robotics went very well. We got the robot to run around and localize where it is in a map. Maybe not the craziest thing to ever come out of a lab, but pretty cool nonetheless. Other fun projects were things like an outfitted Barbie truck that followed directions using a webcam or Roombas using the Wiimotes to follow one another and be controlled. Overall, lots of cool stuff.

Graduation was... nice. Very cool message from the speaker, even if he does have public speaking problems. He did warn us at the beginning of the speech. It was a nice little "the world's a mess, but people are looking for solutions and you guys are now equipped to go out there and kick ass helping fix the world." Not in those exact words of course. Tahir was our student speaker and he had a nice little speech about the 3 tenants of success. Humility, Moderation, and Cooperation. We were actually all pleasantly surprised at his speech skills. In fact, no one noticed that those three tenets spell out HMC until the very end. Very suave. We also had an awesome rendition of the Star Spangled Banner featuring Elaine Shaver on the lead and Matthew, Marissa, Scott, Michael, and Sarah filling in as backups. It was in the style of a barbershop quartet, and was expertly done.

A whole bunch of people came out that I didn't expect for my graduation. Besides the obvious family members there were a few like my Great Uncle and Aunt or some Church friends who surprised us a bit. I'll be writing thank you cards very soon.

Now, I get to prep for the rest of the real world. For example, I have a nice internship in Austin, Texas with a company called Intrinsity. I'll be doing some work in preparation for a Clinic at HMC this next year. We'll be flying out on Sunday to get moved into the apartment. Gotta figure out a good way to pack my computer. After that I'm off to UC Davis for a Masters. I'll be working with Prof. Bevan Baas on some really cool expandable architectures. I'll be living with Michael Braly up there in a nice little house that his parents own. Michael's job this summer is to remodel the place from an office building to a two bedroom house. His dad will be watching out for him. His dad's pretty neat too; he watched one guy remodel their house once and then Mr. Braly did the next two remodelings himself. Sounds a lot like my dad who just picks stuff up so that he doesn't have to pay other people to do it.

Anyways, that's all for now. I'm not sure how much I'll post on this now that I'm out of HMC. But, there's plenty of fun archived stuff if you're interested. Peace out, and Have Fun.

Oh, one last video.

BIG Update

So, sorry I haven't been updating. It's been very, very busy.

First of all, looking ahead. I have accepted a position at Intrinsity, a chip company in Austin, Texas. This means I am currently in serious crunch time as I try to find a place to live in and a car so I can get around. Intrinsity is actually sponsoring a Clinic at Mudd next year, so my job is to set up the stuff for the Clinic. They were hoping that the person they hired would also stick around and actually do the Clinic, but I guess they decided I was good enough. Or they think I'm just that stellar so I overpower that fault. I don't really know.

After the summer I will be attending UC Davis for my Masters. I will be working with Professor Bevan Baas and working on some really cool stuff in chip design. He's been working on a really interesting architecture where the chip is composed of several miniature cores that each do a specific thing. Then, you can string these together to create a processing pipeline. It makes it really fast and low power, especially for pipelined processes like digital signal processing.

Currently, I'm trying to save Clinic. We found out that there's this tool we MUST use to lay the chip out and connect it to the pads. MOSIS, the fabrication group we're working with, claims no one every gets it right by hand routing. So, I get to learn the new tool. I'm getting pretty close, but it's been really hard and I'm still unsure if I can pull this off. Plus, we have to get our Final Report all sorted out and approved, prepare for presentations, and finish wiring up everything for the chip. We don't have a few critical parts, so I'm getting very nervous about this.

We're also really deep into the Shakespeare production. Ironically, this year the class is putting on a play by John Webster, someone who was in Shakespeare's troupe, but isn't Shakespeare. It's a lovely tragedy where every major character dies by the end. Except for the male protagonist's friend. I'm a minor character, so I don't die. I forgot to bring my camera to the coffin building session AND the dress rehearsal. Gr.... Oh, in case you missed it, I helped build a coffin. It's a bit large, but very coffin shaped. It's 1.5 feet high, 6 feet long, and 2.2 feet wide at the widest point. We joke that we could store the Duchess, the kids, and Antonio all in the same coffin.

Robotics has been going... oddly. Due to time issues I haven't logged as many hours as I'd like into the project, and unfortunately have forced one of my team members to pick up my slack. We're trying to get the robot to know where it is using Monte Carlo Localization. I'm implementing the motion and sensor models into the system. We'll be using the IR Range finders to do estimations of how close it is to a wall. Should be really cool once we get it working.

Other than that, it's been fairly OK. I managed to score a 1TB external harddrive for $100 off of Newegg, so I now have somewhere to store stuff before I leave campus. I've been filling it with Anime mostly.

Anyways, that's it for now. I'll leave you with a video that pretty much sums up the stupidity of the Internet comments.

Refresh

I've received word that I might be getting more traffic soon. Something about acceptance letters or something like that. Weird.

Anyways, this is once again late because I am a lazy jerk who doesn't remember to write these things on Friday like I'm supposed to.



Spring Break was... interesting. I managed to cram in 24 Hours of gaming. Well, I actually didn't game all that much since I was organizing and keeping the gaming session going, but I had fun nonetheless. I blame my mom for indoctrinating me to be a good host and deriving pleasure out of making sure others are having a good time. But, that's another story. I then commenced to cram in as much Clinic as I possibly could for the next few days. Thursday evening I went home so that I could wake up at 4 in the morning on Friday and drive to Goleta, CA for an interview with Raytheon. The drive up was actually pretty nice. Two hours of basically empty freeway in the dark of night. The interview itself was pretty fun. I think I impressed them with my awesome Mudd knowledge and ability to problem solve on the spot. I might have to review how I answer questions like "How do you like being the technical lead of your team." To be honest, it's sometimes a very thankless job and I'd rather I only had my own work instead of being the go to guy in the team for help. But, sometimes you gotta do what you gotta do to make the project work, and I'm more than willing to shoulder the job. Then I had traffic on the way back. So, it took me four hours to get home. Then Saturday I got to watch my brother at his Drumline competition (yeah, he's just that cool). Sunday was church and a nice lunch at my grandmother's for my mom's birthday. Then back to school. And now, more Clinic. Yay!

In other news, I'm in the Shakespeare class. It's a pretty cool class. We get to read several Shakespeare plays, discuss them, and get cool lectures about Elizabethan drama and social issues at the time. For the second half of the semester we prepare and then perform a Shakespeare play. Well, except this year we chose a play by some other dude, but it's very nice olde English. It turns out Matthew Lawson, East Dorm Proctor, my roommate Freshman and Sophomore year, unicycler, LAC supervisor, and in general insanely awesome person extraordinaire is in charge of music. He happens to know I play the flute. So, now I'm learning the recorder. If you have any tips, let me know. I currently sound really stupid. Like, those really bad 5th graders who are being forced to play the recorder and they don't want to stupid. I've been told there is a way to sound really good, and I'd really really like to figure it out.

In yet other news Room Draw is now in effect. Since I'm a graduating senior, I don't have to deal with it. =] Unfortunately, it will consume most people's conversations for the forseeable future. And, being the social guy I am, I'd like to be having conversations with people. I guess I'll have to have topics that are more interesting that the drama of Room Draw. See this post if you're interested.

Anyways, that's all that mattered to me for this post. This is Trevin Murakami, and you've just been filled in.

My Professor Knows Magic

I kid you not.

Just this last weekend, I was bashing my head against a certain bug. It's called an iteration loop error. In Verilog, parts of the chip don't have any delay in them. Since this is a rough simulation, that's usually OK and in the real world (or better simulations) we'll see delays and all is well. Iteration loops occur when there is a signal loop (i.e. a signal is dependent on itself) and keeps changing indefinitely. In the real world, this never happens. But, due to the zero delay in Verilog, it can in simulation.

So, I spend most of Friday, Saturday and Sunday chasing around this bug not only in simulation but in my mind. It appeared to come from the flip flops, a certain digital structure that can capture a value on its input on the rising edge of a clock signal, and hold it as its output until it samples another. Very handy. To hold these values, there's certain loops that, in theory, should open and close and not create a feedback loop. However, I finally gave up and worked on other parts of Clinic and asked Prof. Harris to help me. He suggested adding in delays everywhere, setup the wave, and then bring him over to check them out.

So, on Wednesday, I setup the simulation with delays everywhere, and it appears to have fixed the problem. While this is all well and good, we want to isolate what caused the problem in the first place. Magic fixes don't actually fix the problem. So, with Prof. Harris watching, I start to remove the delays in the Verilog code. Eventually, we get back to code with no delay. Puzzled, I then try to re-create the iteration loop bug. It doesn't show up. I then turn to Julien Massas and ask him to try to re-create the bug, since his code was the first to show the error. It also doesn't exist in his code.

Now, I know we didn't change all that much from Sunday to Wednesday, and I'm very very sure it was still broken on Sunday. So, my only explanation is that the presence of Prof. Harris fixed it. Or, it somehow managed to hide itself in fear of his awesome l337 skillz and will resurface sometime next week, right before our deadlines.

In other news, I'm still searching for what I'll be doing after graduation. Grad apps are in (well, 3 out of 5, the other 2 are due next month) and under review, my resume is floating in databases around the globe, and JPL has declined to offer me a position. One of my physics friends already got into one of his Grad schools, so he's very very happy and much more relaxed. I blame it on his Indian heritage (Asiatic India mind you). Plus, as an engineer I can find work without a grad degree. He can't. So, extra kudos for him being so awesome and way smarter than me.

To close, I'll drop a screenshot of my resume. Just in case you were curious.

Re-Entry

Um, I'm back in school. Just FYI.

As it turns out, it hasn't been altogether a bad week. Robotics is gonna be awesome and Shakespeare is gonna be awesome. Clinic has carried over from last semester (still on the critical path of you screw up the project fails).

So, the real question is what to do about my 3 Hums. One hasn't met yet since the professor is at a conference for this week. However, I know the professor, and it's gonna be on the Philosophy of Science. The second one is about Asian history, specifically the recent modernization and post-colonialism. After all, that's all we Westerners really know since most of the ancient stuff is still being translated/dug up/hidden by the government. Decisions decisions.

Now, the bad stuff. Mostly clinic. I'm currently figuring out a few new tricks to make testing easier in the future. Unfortunately this is a pain to learn and puts me behind on other stuff. Basically, I've managed to overwork myself again. I stayed up very late Friday morning (sun didn't come up while I was awake, so it's not an all-nighter!) finishing some tests. As par for course, I was the only one to get those tests done, mostly because it's the easiest piece to test and I've been ahead of the rest of the team for some time now. I also have to debug a nasty problem that was mucking up everyone's simulations, so that didn't help everyone else progress either. As I said, I'm on critical path, and just barely making my deadlines means the whole team falls behind.

Also, I can't just mess around anyone. That means stuff like Mass Effect and Fallout3 and learning Japanese are back on hold. =[

In other random news, apparently Nvidia has managed to give us 3D vision from our monitors. Basically it uses the same technology that is used in 3D movies today, but created on the fly from your graphics card. The downside is it requires 1) a 120Hz monitor, 2) a GeForce 8 series or better graphics card, and 3) that you wear glasses. Now, the glasses are apparently not the yellow abominations you return after watching other 3D cinema and are apparently pretty stylish. Plus, the Nvidia team apparently to be doing a good job of letting you know what does and doesn't work. Plus there's the disorientation that you're in 3D now. Especially in First-Person-Shooters where we've been trained to think we're looking at a 3D world already with perspective and enemies behind cover 20 yards away. But, it's supposed a pretty sweet gig. Not gonna change your world or make or break new games, but a nice feature that if you have disposable income to spend on, is kinda cool. I don't have that disposable income handy. =]

Here's to an exciting semester! Cheers!

Speaking to the Void

 

This is quick snapshot of the lovely little doohicky I have on this Blog called Google Analytics. It shows that every day this blog sees about 5-10 viewers. Most don't stay for long, and the majority (over 50%) come from a referring site. I surprisingly am also getting quite a bit of traffic now from search engines. This blog is in fact NOT the top result from searching my name, Trevin Murakami. So, obviously people aren't searching for me. BTW, the HMC page that details and links to this blog are the top hit, just in case you were wondering and didn't want to Google me.

So, anyways, it just goes to prove people (besides you) actually read this thing. And by read I mean not really since only on a few days does the average time on the page creep above 30 seconds.

Um, I head back to school this weekend. Back to more deadlines and such. I think the Verilog I built for the chip is solid, but I haven't gotten a full-on test going yet so I wouldn't want to publish it. I'm now in the midst of building a bunch of supporting schematics so I can start wiring pieces together. The toughest part is getting things straight in my head. There's certain subtitles about the design and some things like ordering can actually matter. For example, a schematic that places objects to the right or left of each other will more likely than not produce a layout design in the same shape. This can be a good thing (good schematics make layout easy) or a bad thing (bad schematics make layouts a living hell). Plus, I have to make decisions about how we're actually building everything, and there's stuff like fixing mistakes others have made.

Overall, though, I haven't been doing that much work. Every night I play games. I still haven't finished off my giant pile of games to play, although I did beat Portal: Prelude which was sufficiently awesome. Also, around 10pm a lot of people regularly are showing up to play DotA online, which has been fun. It's good to learn from peers instead of just playing a random set of players and feeling very angry about stuff. If you play with and without friends, you'll understand what I mean. So, with any random housework excluded, I typically am getting around 5 hours of work done each day. Which isn't too bad, considering technically I'm still on break and stuff is about on the schedule I set. There's always the chance something goes horribly wrong next week and I have to suffer, but oh well. I don't think anyone else is doing work over break, except for grad applications and thank you cards.

Speaking of grad apps, people have been asking me what ever am I going to do once I graduate. First of all, yes I will graduate this semester (unless Prof. Harris holds me over to fix stuff on Clinic). As for what I'm going to do, it kinda depends. I eventually will need a Masters. How I get it is a good question. There's the straight to more school. Short, sweet, about 1 year to do. Then there's work and school, much more economical (work typically pays) but there goes your evenings and it'll take more like 4 years. Or work, then school. Except then you run into the situation 1) will your employers let you go (and pay if you're extra lucky) for a year and 2) you go from positive income to negative income (the usual route, employers typically don't like you leaving for a year). With other responsibilities (family if you're at that point) that can be hard to swallow.

As for where, I don't know. I am applying to USC, UCD, UCSD, UCLA, and University of Texas at Arlington. For jobs, I've been 2nd round interviewed at JPL, but that's about it. A few groups called to make sure I was still in the market, but we haven't had any formal chats yet. And then there's the economy so hires are gonna be slim and late in the year. However, some companies are still hiring fresh grads since it gives them new blood, especially the aerospace industry since all their guys are gonna retire soon and they haven't been hiring new grads for a while.

So, that's where I am right now. As if the anonymous internet cared.

Plans for Break

Man, I am failing at the prep blog early game.

Anyways, today it's time to detail plans for Break. This is akin to New Years Resolutions where you make a list, feel good about it, try to follow it for about 1-2 days, then lapse back to your old habits. Unless you're still young and in that malleable age where your parents can smack you around and make you shape up.

So, here goes. (in no particular order)

1) Relax. Probably the easiest to pull off. Make sure I'm not sleep deprived.

2) Work on Clinic. Mind you this is rare. Most people forget about Clinic and spend a week when they get back in the Spring remembering everything. Unfortunately, my Clinic, in my personal opinion, needs a jump start and some serious catch up. To make sure stuff goes smoothly next semester, I'm catching up on stuff I need to do. This mainly means getting my processing element completely built, fixing up the code to describe the entire chip (i.e. stable architecture good. See VLSI gripes from last semester about what unstable architecture does), and maybe even getting to know the layout tools early.

3) Games. I've been doing such a good job repressing my gamer side this semester. I still haven't gone through the massive number of games released this year, even the ones during the summer. So, I need to do a bit of catch up. I even have a copy of Fallout 3 sitting in my room, ready to be installed.

4) Family. In case you didn't know, Mudd kicks us out of the dorms for Winter Break. They are locked down and you have to turn in your key or be fined lots of money. So, we're all at home. Except for the crazies who find an apartment or something, but I don't know any of them. Thus, I find myself at home with family. And, my family is very hospitable. Thus, we will be having gatherings and parties pretty much every day until somewhere in the first week of January. We're also going to take a trip up North (i.e. Sacramento) to see some of the rest of the family. If I'm lucky, Michael and I might even be able to meet up with a professor at UC Davis for a little jaunt.

5) Grad School Apps. I've got many more to do. That means more 2500 word essays about my motivations to join their programs. Whee! Luckily I don't have to fill out pages of how awesome I am and my club activities, unlike my brother for undergrad applications. It's pure grades, Letters of Rec, and Statement of Purpose.

Well, I'm pretty sure I'm stuck with 4 and 5 being necessary. I'm also pretty sure I can get 1 done. It's a question of 2 and 3. 2 should take precedence if I don't want to look at Prof. D. Money Harris and say, "sorry, I let down the team again."

Have a nice Holiday Season all 3 of my readers.

Level up to Freedom

Well, the worst is over. Or should I say yet to come.

First, fun YouTube stuff.



Now those look like really badass freeform maps. Too bad I still have to wait for the PC version.

Anyways, back to reality.

It's finals week. Ironically, I only have two finals left. MicroPs, 6502 Chip Research, and Clinic all ended last week. OK, so Clinic didn't really end, I still have a few items I need to get done over break so that the project can continue on smoothly, but I don't have deadlines of death hanging over me anymore.

The last two finals I have are a paper for Philosophy, and a 1.5 hour final for Great Works of Western Music. Definitely not in the same class as the Clinic Midyear.

I also have grad school apps to finish. =[ UCLA was Monday, the next is due Jan 2 but I want to get it in at least a week early. Just in case bad stuff happens. It's actually weird that the graduate school applications are so much shorter than the undergraduate applications. It's mostly biographical info, letters of recommendation, and your statement of purpose. No pages upon pages of filling out what activities you did or anything like that. It's not a question of you being a leader or an activist. It's a question of whether or not you're a good enough investment for their research.

Looking back, the Clinic didn't go quite as far as I'd hoped. We barely got Rev0 out for our processing elements. We wanted to get to Rev2, which requires two optimization look overs of the schematics. I blame the processes not getting done on time as well as some other fun dynamics. Here's a few rules for surviving:

Rule #1: Start early and expect to fail. This is big. Do NOT ever start the morning before. Ever. It will not work. And then you'll be crying and having panic attacks at 2 in the morning. Believe me, one team member practically broke down every Monday.

Rule #2: When the going gets tough, the tough call for backup. Chances are, other people know more than you. As a matter of fact, I can guarantee you that in a team, each will have special knowledge that is useful to the team. So, if you're stuck, ask someone else to help. Bonus if it takes that person one glace to know what went wrong. In our case, this is often Prof. Harris. We've actually likened him to an extra super mind that just intersects our plane of existence. Lolly is actually convinced one day he'll just phase out of our plane for a little while. Michael and myself designed two major processes, so chances are we know what the problem is. We had to do a lot of "shoulder camping" this semester to help get stuff going.

Rule #3: Take notes. Seriously. Forgetting what we said yesterday may be the sleep-dep talking, but you can avoid it by taking notes. Notes last way longer than your short-term memory.

Rule #4: Stay Alive. This means sleep and be healthy. This is directed at Lolly who was in a perpetual state of sleep-dep and sickness for the second half of the semester. I blame her uncanny ability to commit to way more than she can handle. She sometimes handles it all, but mostly she ends up overworked. Well, I consider it overworked. In theory, if you followed the above rules, this shouldn't be too big of an issue since you won't be spending 20 hours a week on Clinic. You'll just be spending more like 13 hours.

In the other front, MicroPs final project was a success. Julien Dage and I built a MIDI synthesizer. We take the MIDI signals from a keyboard and synthesize music out. Sounds easy, looks easy, isn't so easy. For one thing, the MIDI protocol has some weird special cases. It also is a current loop signal. We want a voltage signal. Oops. Then, we have the problem of how to make music. Huh. We used an interesting system where you can move through a hardcoded table at varying speeds to get different pitches. It saves you lots of memory, which means you can store higher resolution waves. Unfortunately, it wasn't as awesome as we'd hoped due to speed and variable size issues. But, we did make it work flawlessly for up to five notes. Later when they post our presentation videos I can link it. Not too interesting, but it demonstrates it works.

Well, that's all for now. I'll be on break after this week, so expect sporadic updates on my travels and holiday awesomeness.

The End is Nigh!

It's the home stretch. Last few weeks of school. For some, this would be heartwarming. Last few things to clean up, time to go out and start Christmas shopping (Amazon.com, you are one of my saviors), and all that.

Not true for me.

Let's recap.

In Clinic, Prof. David Harris commented last week we had about "6 weeks worth of work, and about 3 weeks to do it". This is also the same guy who casually looks at the problem I've been trying to fix for the last few days and solves it in a few minutes. So, yeah, we're in trouble. The key factor is to get what we call Rev1 done of the schematics. This first involves getting Rev0 done. Rev0 means your schematics simulate correctly (or at least as expected) in Verilog and SPICE. The SPICE simulations barely got up and running last week. And, as conventional wisdom says, these kinds of things are so simple that they'll work the first time. WRONG. Assume everything will fail, plan ahead, then double the time you expect that will take, and you're still probably missing something. Trust me. Something ALWAYS goes horribly wrong. Luckily, I have Schematics simulating in Verilog. Or, at least I did. Some weird bug has arisen and one of my schematics doesn't work anymore. See? Even when you think it's done, it isn't. Gr.... The scary part is I'm perhaps the closest to finished out of my team. As much as I'd like to pat myself on the back, it also scares me how behind we are as a team. I'm usually the person lagging behind. Then again, I crash if I don't get at least 6 hours of sleep, so I guess they get the chance to lap me by doing all-nighters. Not that I advocate all-nighters, just that it's not a viable option for me if you expect me to be cognizant the next day.

Next, MicroPs. I'm building with another student, Julien Dage, a MIDI synthesizer. It takes in MIDI signals from a keyboard and uses wave tables in the memory to synthesize music. Unfortunately, there's a few problems. First, it takes too long to process each individual note we want to play. I think, according to simulation, that I can get 3 notes. I want 8 notes. Options now include tweaking code at the assembly level, re-writing a part of the code to use a faster system, and slowing down how fast we output music. We also are having issues on the analog side of things. Curse that real world and all it's foolish inaccuracies. I demand more binary values!

Next, Hums. Philosophy final paper, Music final exam. Um. Yeah. Not quite as scary, but I still have a few loose ends I have to tie up. These are the only two classes that I'm either on schedule or ahead of schedule. Go figure.

Next, GameSHMC. I'd like to petition for more money for our budget. However, that means I have to prepare a presentation on why we deserve more money for the year.

Next, Family. Right now I'm at home. Thanksgiving was full of good food. Unfortunately, I can't access all the stuff I need to do the above mentioned work. Well, I can access the Clinic stuff, except it takes five times as long to get anything done. On the other hand, I can't snub my family. We've compromised and I'm heading back later today to do more work. Still gotta schedule moving back after this semester is over.

Next, everything else. I have a giant list of games on my door that I haven't played. Heck, I haven't even played stuff that came out over the summer, let alone the stuff people are raving about that just came out like Fallout 3 and Left 4 Dead. Oh, and that Red Alert thing. Sorry, I'm not quite as avid a RTS player, although I do love blowing up the computer with nuclear weaponry.

Anyhow, that's where I'm at. No time left and everyone wants me to cash in yesterday.

Back to work.

Searching in the Real World

There's this mythical place where you get paid to do homework and your problems sets actually determine the lives of hundreds, thousands, or even millions of people. WHOA!

Turns out I need to get into this world soon. I'm a graduating senior (or, at least I hope I've graduating), so that means grad school and jobs. It also means I get to feel really weird about myself.

Allow me to put things in perspective. I have a 3.06 GPA. Cumulative. Floated with some As in humanities classes. Did I forget to mention Harvey Mudd battles grade inflation? Then again, I get to brag about helping build a chip. Twice. Except the first one doesn't work.

Turns out most graduate programs have a minimum requirement of their applicants. Even more interesting is that the cutoff is usually a 3.0 undergrad GPA.

As an extra bonus, I'm interested in chip design and robotics and nanotechnology. Bonus points if you mash all three together. This means I kinda need a graduate degree to progress in the field. I guess I could try being like my dad who worked his way up the ranks and is now the senior systems engineer at his company even though he only has a BS. But, the economy also decided to tank. So, hiding in grad school for a bit isn't such a bad thing.

Then again, what if I don't get into grad school? Don't worry, I'm applying for full time jobs elsewhere! This means spamming my resume and brushing up on my interviewing skills. Oh, and deciding if I'm really interested in moving to Oregon or Texas to nab that job. No offers yet. Here's hoping.

In other fun news, I recently discovered I was building the wrong processing element for the chip for Clinic. Oops. Luckily, everyone else appears to have the correct PE, and it's the simplest of the PEs. Unfortunately the code I currently have doesn't pass the test vectors, so I'm also debugging it now. Oh, and I became head of the microarchitecture, which means I need a full chip in Verilog code by Tuesday. Oh, and I'm heading up the Verilog testing so I need to fix Cadence so it will output Verilog so we can test the schematics. Oh, and there's this MicroPs project I'm working on where we're going to make a MIDI transceiver for a keyboard and generate music. Oh, and there's the debugging of the chip we built last year. Oh, and there's these two other humanities classes I'm in. Oh, and I'm going home for a bit on the weekend.

It's gonna be a busy weekend.

It sounded good on paper....

Today's episode will be covering things you think at first are good ideas, but in reality may not be.

Let's start with a simple one. Pure democracy. Everyone has a single vote, majority wins. Yay power to the people and all that. The only problem is this relies on an informed governed/voter population. Unfortunately, the USA is really really bad at this. We rely too much on the echo chamber of the media for our 30 second sound bites to tell us how awesome this one idea is. So, maybe having smarter people in power would be nice. Problem is, this same population has to vote them in. Oops. Solution, inform your public. Yay mandatory schooling! Just make sure you make people learn. But, that's for another rant.

Here's one closer to Mudd. Clinic. Pretty awesome on paper. You're working with a liaison and as an undergrad you're getting real world experience. Awesome! However, you're trying to solve real world problems while in school. Oh, you mean you forgot you still had to do Hum papers or that lab for the other class? Oops. Bonus points if your liaisons don't actually know what the problem really is. One Clinic team (which will not be named here) has a really cool project. However, we're past the half-way mark and they still don't have a good grasp of the problem. It's a problem that relies heavily on sample data, but they don't seem to have any accurate data. Plus, many times they ask for information, the liaison says "figure it out," they come back and present their solution, and the liaison goes "yeah, that's what we were thinking." As much as I'm a fan for finding things out myself and giving people freedom for creativity, sometimes the optimal solution is already known. Please share. So, be warned that Clinic is a huge undertaking. Probably worth it, I'll let you know at the end of mine, but a giant time suck. Plus, you've got to do it in conjunction with other classes. Unless you were awesome, planned ahead, and don't have many classes during Clinic.

Now, another of my gripes. Diversity. Yay multiple views and experiences. The question then becomes, are we doing things for the sake of diversity? It's become a huge question in the College Application Process if a college is accepting and rejecting people based on nationality or gender. After all, we love having numbers with huge non-white and female incoming classes. Makes the news, good stuff for publicity. However, are you lowering the quality of the incoming class? Cheapening the brand of a degree? This also hurts the minority who have to second guess if they're there because they deserve it or because it was a "diversity" choice. Blargh. FYI, I'm a minority. Unfortunately, Asians have this weird idea that we aren't underprivileged, so we don't give out many Asian scholarships. Also, we're one of the largest minorities in the West Coast schools, so we typically don't get preferential treatment. As the saying goes, UCI is the University of Chinese Immigrants and UCLA is University of Caucasian Lost in Asia. =]

Back to recent events, Halloween was pretty awesome. I hope Kyle posts about his Dr. Horrible costume, because it was made of win. If you don't know what Dr. Horrible is yet, go here. But yeah, I didn't dress up. Thought about it, then decided to be a sleep deprived engineer. Turns out it worked well. =] Other favorites were a Music Pirate, a Hamlet/Westley/Random dude in black with a sword, the entire Evil League of Evil including Bad Horse (another Dr. Horrible reference), a random lady costume as an excuse to wear her corset, and Martin dressed up a Room Draw. Yeah, that thing we're not supposed to talk about. East had Trick or Cheese. Each suite buys Cheese, sometimes crackers too, and you go around sampling cheese. This is the counter to Trick or Drink in West. There was also a group who took tin foil, wrapped themselves up, and went to Chipotle. Chipotle gives free burritos to people who come dressed as a burrito, and since they wrap their burritos in tin foil, well...

Anyways, time to get back to my lab. I'm implementing processor interrupts today. yay!

Photo Blog: Intel Site Visit

Well, we just had our Site Visit to the Intel Campus up near Portland, Oregon.

To get there, we had to catch a 6:15am flight, which meant we left HMC at around 4:45am.









































We made a wrong turn, and wasted some time, but got to the airport on time for loading.




During the flight, we got to spend some quality time with Professor David Money Harris and go over stuff we were still a little hazy on and some new ideas we were working on. Here is Braly going over some ideas for a floorplan for the chip. Sorry, spacing was tight. That's Julien's head in the background.







Being in the morning, we had a nice sunrise as we took off. =]














More quality time, this time going over the delay calculations. I wasn't sure I did them right, but after a brief talk with Prof. Harris, I was glad I estimated as close as I could get. Made me happy. However, Lolly and Julien weren't quite as comfortable, so they got some time to review the calculations while Michael and I tried to take a quick nap.



























We couldn't take pictures in the buildings, so no pictures of the presentation nor the really cool lab. I also forgot to take a picture of the nice lunch we had. It was thai food and Braly approved of the quality, so it must have been the good stuff.

But we did get to take a nice picture with the whole team and our liaisons. Left to right: Prof. Harris, Julien, Michael, Sanu, Ram, and Lolly.

It is now about 4pm, so after a cool lab tour and more ideas on how to make our chip, such as about five ways to have a backup clock for the chip, we started driving back to the airport. These two knocked out before I did. =]

Due to some traffic, we got to the terminal at around 6:10pm for a 6:35pm flight. So, Professor Harris drove up the rental, we popped out, grabbed our stuff and started to run. Down a flight of stairs, shooting across the street from the parking structure, into the terminal. A quick glance around to find the Southwest terminals, print our boarding passes, dashing to security, and as we scurried to the gate

we realized the flight had been delayed. Probably one of the few times you're ever glad it was delayed.

The weird thing was I was in the back, so I kept thinking how epic this looked, the classic mad dash to the airplane with the Professor in the lead, and I wanted to take a picture. Problem was, I was running at full speed too.

Luckily, this meant a quick dinner. I also joked with Julien, who is a french exchange student, that now he'd had a Quizno's sandwich for breakfast, thai food for lunch, and a burrito for dinner. Michael joyfully added, "welcome to America." Interestingly, Julien has quite the appetite and once we got back to Mudd planned on making a trip to Jay's Place for more food.

Out we leave the terminal.

Oh, and by the way, Lolly really hates pictures of her, so by now she was threatening physical violence on my person if I kept taking pictures.

Chilling waiting for the shuttle back to the parking lot where we stashed the Clinic van.

Back at Mudd, safe and sound, much wiser than we left, and a heck of a lot more tired. It's 11pm in this picture.

And that's that. A full day spent traveling and talking with people way more knowledgeable than us. We did get quite a bit out of it, such as some fun times together and learning about how Intel tests its chips. Oh, and we got to see the teraflop chip Intel built a few years ago. Crazy awesome stuff.

Now I just have to finish the MicroPs lab, a presentation on Haydn, VLSI research, Clinic Verilog code hacking, Cell library components......

What's Important in Life

At least according to Prof. Jacobsen.



In other news, my Clinic will be to make a shiny chip to help speed up cryptography algorithms. Return to the team Michael Braly, adding in an exchange student Julien, and other friend but not on this blog yet Lolly Simoni.

Oh, and Crack starts up today.

Yay for busy school week!

In Review

End of semester.

I should have seen it coming. Granted, I did see it coming. I saw it and survived. Doesn't change the fact it was painful.

This last semester was E102, E106, E158, E166, MUS080, MUS084. In order, that's Big Stems, Material, VLSI, High-Speed PCB, Music Theory I, and Jazz Improv, using the shortened nomenclature. I'm not going to say "Introduction to CMOS VLSI Design", more typing means you have to read more random babbling.

Overall, it doesn't look that bad. 16.5 credits. Recall that the maximum is 18 before you have to petition for an overload, and to graduate you need to average 16 credits per semester. Plus, the music theory shouldn't be bad, I've played piano and flute for many many years and Jazz Improv is a similar thing.

The kicker is the Engineering classes. Specifically, High-Speed PCB and VLSI are project based classes, which means the second half of the class is mostly devoted to doing something big and shiny. E4 is an entire semester of projects, some of which, I might add, were a really really tough this semester. I just built fences my year. Fences that had to stand up to people climbing over them and leaning on them and had to be freestanding. But I digress.

Also, turns out I'm not a super musician. I have what looks like a lot of hours, but in reality doesn't boil down to that much skill. Piano played second fiddle for most of High School and Flute was mostly employed in the Band. Granted I was one of the best flutes, Section Leader even, but that doesn't translate to being able to pick up Flight of the Bumblebee or something. But Theory. I should be able to handle that. Well, except the whole sight singing and dictation part. Plus, Jazz improv isn't like playing Bach's Invention No. 1.

I'm not saying it was a bad semester. It was pretty awesome. I helped build a chip. When I talk about crosstalk, the interviewers get confused as to why an undergrad knows these things. I have learned Masters level stuff about systems and control. And I can kinda jam on the piano, or write four part counterpoint. It's just there were definitely times when I felt at the end of my rope. Mostly due to time constraints.

The best part is, I now go off to an internship. So, I probably won't post anything for a while unless I feel bored or something really Mudd-y happens. And when I get back, I get to do Clinic, MicroPs, Rigid Dynamics, Intro to Philosophy, and Nationalism and Music. Plus some independent study testing the chip we built.

You'd think I'd learn.


In the meantime, enjoy:

Slang/Jargon you Might Hear

Here's some terms you might see pop up in the blogs or hear if you visit the campus. While not canonical definitions, they should help give you a good idea of the general meaning of the word/phrase.

5^th year – a student who is taking a 9^th semester at Mudd due to scheduling

AC – pronounced “ack”, short for Academic Computing (computer lab) or Academics, usually referring to the academic end of campus as opposed to the dorm/residential end

Bio – Biology

Clinic – The act of the College outsourcing it undergrad students to a company who pays for the students to fix something for them. Often considered a timesuck due to high levels of involvement. Required to be done by CS and Engineering Majors in order to graduate.

Crack – anything addictive. Usually associated with a game, for example World of Warcraft or Civilization 4.

CS – Computer Science

DOS – Dean of Students, includes several students who help organize random events about once a week, things like a trip to Mt. Baldy or showings of movies on the giant inflatable screen with themed snack or bed races

Flame war – an argument often carried out on e-mail lists or a forum between two or more parties, often but no necessarily including personal attacks, ad hominems, and/or continuing longer than anyone not involved cares. Usually, but not required, it starts out as a civil argument.

Graduate – the goal of most Mudders to do. Afterwards they disappear into the Real World, sometimes reappearing with tales of how easy life out there is yet wishing they were still here to hang out with us.

Graduate Student – these don't exist at Mudd

Honor Code – Rule #1: Don't be a jackass. Created under the assumption that if given the choice, people will do what is right. Covers both academic and social responsibilities and fosters a strong mutual trust and sense of community between students, staff, and faculty.

Hygiene – Something many people maintain, but there are those who don't upkeep it as much as others would like. Degradation of this stat is usually from the Sleep dep status effect.

LAC – Linde Activity Center, contains lots of cool stuff including fitness center, computer lab, ping pong table, and a printer. Also the hub for intramural sports and Dean of Students (DOS)

Nerd – what everyone has at least a little bit of inside them

Northie, Eastie, Westie, Southie – Student who identifies with North, East, West or South Dorm respectively. These dorms are not positioned according to the cardinal directions, South is the north most dorm and north of West and west of North.

Mudder – a student who is currently or previously enrolled in Mudd and is associated with Harvey Mudd College.

Prank – a humorous setup organized and executed to be relatively harmless but humorous for both parties involved, the prankster(s) and the prankee(s). Must be reversible within 24Hrs and you must leave contact information. Can be on a No Prank List to pranks in general or specific pranks from being performed, but you can not do any such pranks to others.

Prefrosh – a prospective student who is not currently enrolled in Harvey Mudd but potentially wishes to in the future. Sometimes visiting from the Real World to observe or even stay the night.

Proctor – not be be confused with a Resident Assistant (RA) at other institutes, the Proctor(s) of each dorm are there to help keep the students safe, provide emotional counseling, and look out for the well being of the members of the community. They also have keys to let you into your room if you locked yourself out and are required to host a number of events for the dorm.

Prof – short for Professor, as in Prof Yong or Prof Ran. Teachers of classes, people with office hours so you can talk about homework, your best friends and worst enemies, especially when they give out tests.

Real World, the – a mythical land out there where people have jobs, earn money (usually), and are much less sleep depped.

Sleep dep – short for sleep deprived, often a result of homework, projects, all-nighters, waking up early for class, or messing around instead of sleeping.

Timesuck – A sophomore suite in East or anything that takes up a lot of time, such as Clinic.

Wank – An action. To complain.

I'ma Eng-in-neer

If you thought of a game sound file reading that, well, I think enough said.

So, I happen to be an engineer. Cool. Not a railroad engineer, I mean the kind that builds stuff and optimizes things and figures out new applications for the latest and greatest technology.

At Mudd, we don't have Electrical Engineering Major, nor Aerospace Engineering Major, but instead have a General Engineering Major. Why? It's because of the idea that becoming a super specialized Engineer could be a bad thing. What if that area suddenly isn't useful? How do you cope with changing demands? Will you be able to communicate effectively with others in other disciplines? At Harvey Mudd, we try very hard to give you the breadth of knowledge to be a nimble engineer in the professional world, but there's also a commitment to allow you to specialize in your passion.

And here's the problem. To do both, you've gotta learn alot. Which is why the Engineering Major at Mudd is notorious for being a giant time suck. In fact, according to oral lore, once upon a time Engineers were required to overload at least one semester just to graduate. The Accreditation Board decided that wasn't good, and so told HMC to fix it. They did, by reducing the number of credits of certain courses. However, the class load remains the same.

It's not all bad, though. I mean, you get to build a processor chip in the VLSI class. Our new E80: Engineering Field Experience now offers you the chance to shoot off rockets and take the data from the flight for analysis (assuming it didn't blow up). And best of all, we get really cool Clinic Projects which let us as undergrads essentially work as if outsourced to some professional company. For example, Raytheon, DirecTV, and CIMIT all have Clinics going on at Mudd. Cool, huh?