307 Wrap-Up
Well, it’s been one hell of a quarter, with structures, this class, and CPSS. First, I’ll wrap up the lab hack. As I said in the last post, construction is complete, and on Friday we were able to get the data as promised. 3 hours later than scheduled, but that was mostly the fault of a campus-wide power outage (The Scanivalve Gone Walkabout group was none too happy about it, though). I haven’t had the time to properly analyze the data yet, though, so I don’t yet know if our modifications made any difference. At a glance, though, our run did seem to have a higher dynamic pressure in the tunnel than before the modifications (1,360 over 1,260), which is at least promising (but inconclusive because of varying ambient conditions, etc). And hey, at the very least, it looks cool.
Course Reflection
As before, I’m not inspired enough to do a free-form reflection, so I’ll settle for answering some (summarized versions of) reflection questions that Dr. Doig has thoughtfully provided.
What was your experince with the more open-ended style of project presented in this class, where you were given only a goal and not a procedure?
It’s pretty interesting, actually. I’m no stranger to the idea of an open ended project. After all, I’m heavily involved with CPSS, and that’s 90% of what we do - set out a goal and figure out how to get there. I actually found it more difficult in the 307 environment, though, mostly because of the lack of hierarchy. For comparison: In CPSS, there’s a leadership structure. I dictate the design for the avionics systems, and then delegate labor to make them happen. The avionics are designed to meet the requirements laid out by the president, Adam, who has the final say in all matters. If there’s ever a design dispute, we discuss until it seems each side has made a complete argument, and if we hit an impasse, the president makes the decision. This setup is useful in a couple of ways. Most obviously, it provides an easy way to move design along - just ask Adam. But it also makes sure that everyone knows what they’re responsible for; I don’t sit around hoping someone will take care of the avionics, because I know it’s my job. In 307, though, none of this structure exists. This means that design discussions are more difficult to conclude, and can result result in some sneaky politics if you’re not careful (we avoided this, thankfully). Also, if the group isn’t careful to assign jobs, some tasks just get left floating around until someone realizes they’re in the best position to get them done. For example, Eric wasn’t assigned to be our shopper, he just decided that, since he was commuting from off-campus anyway, he might as well hit up the hardware store. Similarly, on the night before our last lab day, I realized that we hadn’t coordinated a way to cut our foam inserts, so I reached out to a friend in DBF, who was willing to give up a couple hours on the morning before lab to help Kyle and I cut foam (Thanks Kurt!). Something that did end up falling through the cracks was a second tuft test. I didn’t mention the first one until now because no one shared the video with me, but we missed doing the second one entirely because everyone either forgot or waited for someone else to do it. Despite all that, I don’t think there should be a hierarchy established for teams next year, like having the TA’s and Dr. Doig choose a project lead. It’s good for us to get practice in creating organization from nothing.
Other than time constraints, what was the most challenging portion of this class?
Time constraints. I know other students will have a lot to say here, so I’ll keep things brief. This is supposed to be a two unit class, and yet it easily took as much time as other four unit major classes. I’m actually ok with that, though. I don’t think there would have been a way for me to get as much out of this course in less time. I would suggest, however, attempting to stagger the different groups that require heavy tunnel usage. Maybe have groups like PROVE and the PIV people do more work early in the quarter before 307 starts the open-ended projects, or prioritize the other way, and have 307 do their open-ended projects when groups like PROVE and the PIV people aren’t going to be as active.
What was the most memorable moment of the course?
The sexy water tunnel videos. C’etait vraiment magnifique. (Et je n’savais pas que Dr. Doig parle francais. C’est cool, ca.)
One last thought
Several Aero professors have reminded us to fill out the online course evaluations, since if they continue to get low response rates, they’ll have to go back to paper evaluations. Instead, I’d suggest just giving us some time in a class period to do the online forms, just as was done with the paper ones. That’s why the response rate was so much higher on the scantrons - not because students prefer pencil and paper, but because there was time set aside specifically to do the reviews. I’m saying this here because, despite all the reminder emails, I still haven’t done any of the online evaluations. And even when I’m done here, though it’s already on my mind, I probably still won’t do them. I have a structures final tomorrow!












