After making the worst fuzz pedal ever and Orange Ya Glad (which was fine, but didn’t add quite as much as I wanted and adds a weird buzz even when you’re not playing on some speakers), I just wanted a normal fuzz pedal. After doing a bit of reading, I found that the Red Llama overdrive pedal (by Way Huge) is a classic, and after watching a few YouTube demos, it seemed good (to be honest, people are crazy about the “different” sounds of various fuzz/distortion/overdrive that various antique/obscure transistors or configurations will give you, but they all sound pretty similar to me, and I suspect people think they’re hearing differences more often than there actually are).
This is a fun one.
It’s also a testament to how nifty and easy it is to quickly whip up a project with Arduinos, provided you have enough of a “critical mass”, as I’ve called it before, of other stuff that you might end up needing.
How was this one born? Well, there was a Halloween grad student party our school was throwing, on a Friday night. It’s… honestly, really the type of thing I, or any grad student, should go to. We’re mostly isolated from other grad students, and these parties have typically gotten pretty raucous when I’ve gone to them. However, that night, I really wasn’t feelin it. I got home from work/the gym kind of late, hadn’t eaten, and the party was downtown. I think it might’ve also been raining or something, adding to the “I don’t want to go out” side of the scale.
Here, I’m beginning my ML journey by reading: A. C. Mueller and S. Guido – Introduction to Machine Learning with Python, 2017
These will very much be just random notes, thoughts, and questions on the book as I go along.
Recently, my friends and I went to the NYC Maker Faire, and on the way back had a ~3 hour car ride. We got to talking about vegetarianism, saying how for the most part, despite most of us taking a devil’s advocate position at some point, we all agree that we don’t really have a defensible position for eating meat. Yet, we’re all fairly carnivorous. In fact, during the height of that conversation, we were going out of our way to get to a Five Guys burger place, so… the irony was not lost on us.
As of this writing, I just defended and I’m considering various options for what I’ll do next. That’s a whole other story, but the important part for this post is that, probably for whatever I do, I’ll be coding.
I’ve coded a decent amount in my life. I started with dinky web stuff wayyy back, then picked up a now-tattered and probably outdated “C++ for Dummies” book in highschool. I did small programs with that, as well as some silly things for crappy AVR projects I did. In college, I used mostly Java because that’s what the computer science classes I took asked for. Towards the end of college, though, I was working on my own research, and used C++ instead (why? I honestly don’t remember. Wait, I just did! My advisor had heard of some multiprocessor module for C++ that he wanted me to try, so that’s why I didn’t stick with Java).
Hey there, nonexistent reader! You may have (not)iced that I’ve been gone for a while. That’s because I just defended my PhD, and I was pretty balls to the wall busy for the last few months getting ready for that. I made a few posts here and there, but towards the very end I realized I really had no time for a blog that no one reads anyway. Maybe I’ll make a post about the whole before-and-after experience at some point.
Anyway, my friends and I just got back from a weekend trip to the NYC Maker Faire. Max has a friend who got us a few free tickets, which was sweet; they’re not inexpensive, something like $35 for a single day pass I think? So she definitely saved us some buxx. I had never been before. It was pretty perfect weather and in Queens, so all said and done not too crazy to get there.
A bit of background: our lab is kind of ancient. It’s also enormous; my advisor owns most of our hallway. The group was once very big (one of those 20-30 people powerhouses), but these days it’s fairly small (~6, plus a couple undergrads at any given time). However, we still have all the space from those massive days of yore, so a lot of the space is… well, let’s just say a lot of the lab space hasn’t been touched in a while. I mean, every room is still used, but there are definitely nooks and crannies that, if owned by a lab that had to be more economical with its space, wouldn’t remain as untouched as they are when I find them.
This is my first boat. It’s pretty silly, but was a lot of fun to make.
During the summer before my senior year of undergrad, I was staying at college and doing research on dilute gas simulations using Monte Carlo methods. My roommates and I had rented an apartment for the year (haha, holy hell…Worcester apartments are a special kind of grimy) and the lease started at the beginning of the summer. My roommates hadn’t moved in yet though, so I had the whole house to myself.
I…honestly don’t remember why, but I decided to build a boat. There were a few small lakes and reservoirs near Clark (University, my undergrad school) but I’m not sure I even had one specific one in mind. I had a lot of time, and the space in my house to build it in, so why not?
As part of an ongoing project, I wanted to see how low I could get the power consumption of Arduinos to go. The reason is as follows. When getting back into Arduinos a few months ago, I wanted to try a telemetry project of some sort, collecting data remotely and sending it back. Ideally, the idea would be to collect data from different places and analyze the aggregate in some cool way, but that’s a story for another post.
The point I was going for, though, is that I wanted to put these Arduinos in places that wouldn’t have constant access to power, so that already means using a battery. Using a battery to power an Arduino isn’t a big deal (plenty of people do it for portable projects), but once you’re looking at long term powering without recharging, it’s a different story.
This is silly and derpy, but here we are. Read on if you’re having trouble getting to sleep.
Often for research, we need to make a thin film of photoresist, so we can do photolithography or e-beam lithography. Photolithography is cool (technical term) because you can pretty easily (seriously: with a UV flashlight and a home printer; I’ll probably write that up at some point) pattern the film over a wide area. It’s straightforward and easy enough that machines can do it. However, its resolution is relatively limited, down to about 1 micron (human hair thickness: 25-100 micron). I should be careful saying this because you can get better resolution through various methods (like using a smaller wavelength of light), and for industrial applications they can do a lot smaller. However, for research purposes, ~1-10 micron is usually the figure people say (and this depends on definition too; do you mean the smallest linewidth, distance between lines, or precision for a given spot?).