Showing posts with label engineering. Show all posts
Showing posts with label engineering. Show all posts

27 April 2019

Reading Program

I'm doing something unusual today, and taking a book off my Goodread's to-read shelf. Almost invariably, I add books and leave them there till I finally get around to reading them. Removing them is so exceptional I feel the need to write a blog post justifying myself!

The specific story is pretty simple here: when I put John Anderson's Hypersonic and High-Temperature Gas Dynamics on my reading list last summer, I was more interested in bookmarking it for future reading rather than giving it a particular priority in my independent study plan. However, since then, I've started giving much more weight to reading the books that are already on my to-read list (and don't want to overpopulate it with the hundreds of titles which have, at least briefly, caught my attention over the years).

Hypersonic aerodynamics is an advanced topic, and Anderson recommends Fundamentals of Aerodynamics and Modern Compressible Flow as pre-requisite texts. At this point, I'm not going to forget about his hypersonics book, so when and if I get to the point where it's appropriate to study high-speed flow, I'll know where to look. In the meantime, however, I'm better served prioritizing more foundational engineering texts and the other types of books on my list (history of science, philosophy, fiction).

I'll probably use the newly-vacated slot for Spacecraft Mission Design by Charles D. Brown, which strikes me as a more appropriately challenging textbook at this point in my reading program.

30 May 2018

Some Things I Didn't Learn in Undergrad (And Really Wanted To)

Since graduating earlier this month1, several people have mentioned to me that you should never stop learning. I don't object to this statement, but I find it somewhat puzzling. I went into aerospace engineering because I enjoy astronautics, and this field moves fast enough that the only alternative to maintaining technical competency is sliding into obsolescence. Naturally, that does not appeal to me.

But this biggest issue is that I don't think I really learned enough in college. I mentioned this in passing to one of my professors, who assured me that most students from our department pursue graduate studies. That helps, but not a lot, because there's more that a few areas that I want to learn more about. To better structure my thoughts on the subject, let's discuss some of the areas which we didn't really cover, but I had really hoped we would.

Nucleonics. Technically, this one is my own fault. I started at a school which offered a nuclear engineering minor, and I had the credit hours (thanks to AP) to pursue it. Unfortunately, I didn't really understand how the college course system worked, and blew those slots on entrepreneurship classes freshman year.2 Trying to work ahead in my science coursework would have probably been a better use of my time.

Heat Transfer, on the other hand, strikes me as a widely-applicable subject for aerospace engineers in general. It does not appear to be standard in undergraduate plans of study. You can probably take it as a technical elective, but those slots are limited, and instead you're more likely to push it to graduate school. Letting M.E.'s have all the fun seems a bit strange, but whatever, there's a lot of ground to cover and plenty of heat transfer books out there.

Launch Vehicle Dynamics is a little more specialized but still something would would expect to discuss. Aside from a few problems with extremely unrealistic assumptions, we didn't cover this in any real detail, not even in astronautics classes. This is probably an artifact of KU's program being particularly airplane-focused, and other schools may handle it differently.

Manned Spaceflight. Pretty much everything we covered was unmanned, though "everything" at my school consists of two (2) space systems classes. Manned spaceflight builds on unmanned spaceflight, but there's a lot of material there which we simply did not discuss. Last year's class got some of it because their AIAA design competition involved a crewed mission, but mine didn't. I'm hoping to get my hands on a relevant textbook in the near future.

Advanced Propulsion—specifically, nuclear-thermal propulsion, which motivated my desire to study nucleonics. In retrospect, this was probably a touch optimistic and is a much more common subject to find graduate students learning, but a more flexible plan-of-study might have made undergraduates taking additional rocket classes plausible.3

Computational fluid dynamics and compressible aerodynamics represent the latest additions to this list, and were ultimately my own decision. Both are offered in most curricula, but undergraduates usually don't have room in their schedules unless that is the particular area they intend to specialize in. Taking these classes would have necessarily entailed giving up other electives. I cannot help but wonder, though, whether their stripped-down components could have been included in a more versatile plan-of-study.

If I were to offer any overall theme to this post, it would probably be that underclassmen generally have insufficient information to make intelligent decisions about their education. All too many students end up in the wrong major for their interests, or in the right major at the wrong school, or even at the right school yet mess up their plans-of-study in the first few semesters.

I don't see any easy solution to this problem beyond better advising to underclassmen and prospective students. Perhaps the best we can do is better explain the challenges and minutiae of engineering education, and hope for the very best.


1That's three of my 2018 predictions satisfied, incidentally.

2To be clear, entrepreneurship was interesting and will probably still prove valuable, but nuclear engineering strikes me as a much better subject to study in a formal context.

3Note that whether additional classes are available depends on the school. It's worth looking into course listings and developing a preliminary plan of study before Decision Day.

22 August 2017

Senior Design

Yesterday, I was camping to watch the solar eclipse. Today, I'm back at school, diving into the material for senior year. My space-focused classes haven't met yet (updates on that front possibly tomorrow), but already the workload shaping up to be just as tough as last year's graduates warned us it would be.

The aerospace senior design classes focus on the AIAA Design Competitions. This year, the undergraduate individual aircraft request is to propose a Close Air Support (CAS) vehicle to replace the A-10. It's a shame Alex had to push back 521 a year, because this sounds right up his alley.

Our first assignment is Block 1 of a combined report, which will be due on Monday, September 11. By that point in time, we will have needed to have derived a mission profile from the specifications, reviewed the history of similar aircraft, and extrapolated from that data to perform the weight, wing, and powerplant sizing. All of it will naturally need to be summarized, formatted, and referenced.

On the subject of formatting, we've been given a few options for producing our reports. The standard approach is to use Microsoft Word, which has an unfortunate tendency to completely obliterate carefully-tweaked documents. Alternatively, we can use Adobe InDesign, which few of us know but allows for more meticulous curation. Because the design curve on InDesign is so steep, Dr. Barrett is offering some extra-credit for its use. LaTeX is also permitted, but will not garner any extra credit. I specifically taught myself LaTeX this summer to avoid the hassle of using MS Word this fall, so LaTeX it will probably be.

What we don't have a choice about is submitting our designs to competition. Knowing that these proposals will actually be judged may provide additional motivation to produce something decent. Or maybe adding pressure will only cause more problems. We'll just have to wait and see!

In either case, I should probably start reading. There's an awful lot to learn.

09 December 2016

Forms and Structure

A problem which I've complained about mightily is the gap between my desired level of course material integration and what professors actually provide. Indeed, I still believe that this has been among my greatest hurdles in learning mathematics. It would seem, however, my preference for structure is at the rightmost end of the bell curve. Unfortunate.

As such, it would seem that divining the conceptual structure of a given subject is perhaps the utmost task for increasing my academic achievement. The problem with this, of course, is that I won't know where everything goes until the semester is almost over. By that time my grade will have suffered needlessly and I may even have lost all interest in trying to decipher the inchoate mess of equations and trivia that all too many classes top-out at.

The only strategy may, perhaps, be to stay ahead of the syllabus. This is hard. Very hard. When I don't understand the material, doubly so.

I maintain that engineering has not yet been hard. Badly presented, yes. Botched, even. But not hard.

What mystifies me is that no one else thinks this way. In other fields the value of good form for communication is patently obvious. Nothing about STEM screams any difference. So why the resistance to clarity I deal with day-in and day-out?

A mystery, but probably a stupid one.

06 December 2014

Notes on Spaceflight Economics

[ICYMI: First Flight Test Is Successful for NASA’s Orion Spacecraft]

Since NASA decided to retire the space shuttle, it seems the trend in spacecraft design has been more intimidating rockets, with more intimidating price tags, for single use missions. I'm pretty much alone over in my corner says "smaller, simpler, reusable."

(If you follow space news, they you probably realize I'm not quite alone in advocating reusable launch vehicles, and there's exciting progress on that front. Yet most NASA fans haven't quite gotten the memo.)

After today's Orion test flight, I discussed frustrations about the dominant approach with my friend Ben. Once finals are over I'll follow up this post with a more detailed explanation, but I want to record the main insights--along with my own thoughts--before they're buried in the chat logs.
  • Getting materiel out of the gravity well is most important.
  • One large rocket is less efficient (with regard to fuel) than many small rockets.
  • Launching one large rocket is less efficient (with regard to materials) than launching many small rockets provided the smaller rockets can be easily reused.
  • Smaller payloads would be financially viable if they can be easily assembled in orbit.
  • My aerospace aesthetic is "design with an emphasis on 'nothing that explodes and flies away'"
That's all for the time being

26 November 2014

The Marble Sorter

Outdated logo? Yes.
My shortlist of Things I am Still Not Over reads something like this:
  1. All the arguments I've ever lost
  2. The 2012 Republican Presidential Primary
  3. The Marble Sorter
For those blessedly unaware, the marble sorter is an assignment in the Project Lead The Way pre-engineering program. Small teams of students are tasked with designing, building, and testing a system to sort marbles based on color. The project format has changed a number of times, including the materials (we used fischertechniks, I believe Vex is now standard), plus the many tweaks teachers make to fit their resources. But that's inconsequential.

What matters is how badly my partner and I failed, and why.

In the end, we never did get a decent performance. The criteria specified that all the marbles would be dropped into the machine at once, and then sorted by color into three categories. (Marbles came in blue, black, and clear. Extra credit was available if it could distinguish between dark blue and black marbles.) In the end, ours could distinguish between clear and opaque marbles, under the right conditions, if they were loaded one by one. On a project worth a huge percentage of the semester grade, we got around fifty percent.

And we had to fight for that. We came in early, and stayed late. Principles of Engineering was right before lunch, and I missed a few meals for that project. It inhabited my dreams (I know, I was keeping a journal for Psychology). I fantasized about tearing it apart and starting afresh, and over four years later I'm still thinking about it.

But that wouldn't have made a difference, because Nathan and I weren't using good engineering practice.

There's a programming proverb: "resist the urge to code." In engineering, this applies to both the software and the hardware. It strikes me as odd the Principles of Engineering curriculum didn't mention it. Maybe it did and the lesson just didn't stick. Regardless, we ignored any cautionary impulse, and began building with only an excuse for a plan. We drop the marbles into a hopper, they roll down a chute, a door lets one out, the photosensor tells us its color, put the bins on a track that moves back and forth, and another door opens to drop the marble into the appropriate bin. What could go wrong?

Quite a lot, it turns out.

I could go into many, many details, but (fortunately for you, readers) I've forgotten most of them. I still have my notebooks lying around somewhere, but our slack documentation would have gotten us fired from any worthwhile company. This itself was another bad practice, which hamstrung our ability to replicate more successful approaches and identify what wasn't working.

One of those things was our approach to the materials. I'd experienced fischertechniks in middle school at a PTLW-sponsored summer program, and really should have understood just how stubborn they are. Yet we blundered ahead as if they were modelling clay, and burnt through huge chunks of our limited time trying to make them bend to our will.

A particular instance that sticks out in my memory: the mess we made trying to build and secure one of the doors. What's worse, though, was trying to reconstruct it after taking it apart. In retrospect, the situation was ridiculous. The whole system was elevated for no good reason. We had to build ridiculous struts and cantilevers, when we could have just attached the motor cleanly if we'd had the sense to set the system on a lower platform.

Unnecessary elevation brings us to our next point: ignoring basic scientific principles.

For a system driven largely by gravity, you would think doing some physics would occur to us. Then again, I'd only had the briefest introduction.

In the final days of the project (when we'd already missed the deadline and were fighting for completion points) we had several recurring frustrations. First, our chute, hopper, and bin systems didn't work very well at containing the marbles. They had an annoying tendency to bounce right out of the marble sorter altogether. The reason for this was very simple: elevating the system gave the marbles too much potential energy.

Potential energy was also the root cause of our second problem. No matter how much time we spent tweaking, we never could figure out the precise time the doors needed to open and close. We'd run several tests with an individual marble, then find all our measurements useless when we dumped the whole load in.

We had some clue at the time that it was the marbles' collective weight pushing on the marble, which usually resulted in two or three getting through. With my current knowledge of physics, I realize it's an application of weight and Newton's Third Law.

Weight  = mass * gravitational acceleration
Force = mass * acceleration

In the first equation, mass refers to that of the marbles altogether. In the second, it's the mass of an individual marble. Stated symbolically:

mload * accelgrav = massmarble * accelmarble

For the non-STEM people out there, this means the accelerationspeed a marble goes through the gate is related to the number that have already gone through. Later marbles go through slower than earlier ones.

We spent hours trying to find the right gate time, instead of taking a more sophisticated approach--either varying the gate time, or redesigning the hopper and chute to eliminate the gravitational effect.

Our final problem was more technical than scientific, because we knew the principle at play here. How do you measure slight differences in pigment when the ambient light is so variable? The obvious answer is to fully enclose, to the greatest degree possible, the area where pigment measurements are taken. We did this, but only with considerable reluctance and didn't do a very good job of it, because we still had some trouble.

The already flawed design, which we waited too late to modify, had a lot to do with it. We didn't know about sunk costs--yet another reason engineers need to learn economics. We had this problem in the first place, because we didn't consider external factors in developing our design.

At the time, the marble sorter almost drove me to a mental breakdown. Failure after failure had me seriously doubting the validity of reason (the unstated assumption was that I was operating rationally). I think it should now be clear this was not the case. After five years, the lessons are sinking in, and I'm finally get some closure. If only the other two items on the list were so easy.