Supersonic Man

May 10, 2017

no Apollo

Filed under: Hobbyism and Nerdry,thoughtful handwaving — Supersonic Man @ 9:21 am

If NASA had not been hurried into building the Apollo mission by the “space race” against the USSR, how might we have arrived at the Moon?  Space development might have proceeded a good deal more slowly and less expensively, building on the X-15 rocket plane experiments.  I think that program would eventually have arrived at something fairly close to the Space Shuttle.  If you solve all the problems of the X-15 one by one to make it orbit-worthy, it would have had to be much larger and blunter, because any adequate heat shield is going to be around four inches thick, and that doesn’t scale down for something skinny or pointy.  That sounds a lot like the shuttle to me.

So let’s say we were trying to send a mission to the moon using space shuttles.  The shuttle itself can’t go there even in you fill the cargo bay with fuel, and that would be wasteful anyway, as you don’t need most of its bulk.  So I think the bits that actually go to the moon would be much as they historically were in Apollo: a lunar module, command module, and service module.  Why not just stick those into a shuttle bay?

The shuttle’s cargo bay is 60 feet long and 15 feet across, though for a cylindrical cargo the cross section needs to be a bit smaller, as the space isn’t fully round.  The mass limit for a flight to low orbit is a hair over 30 English tons, or 27.5 metric tons.  (I don’t think any real flight ever exceeded 83% of that capacity.)  What can we work out based on these limits?

You can’t fit all three modules into one shuttle-load, but they’ll go in two loads, if you make the lander a bit less broad and gangly.  One would be the command module and lunar module, and the service module would be the other.  And we might have to trim a bit of weight from the service module.  This means the service module would have to be mounted to the command module by shuttle astronauts in space suits, which would be inconvenient, but doable.  Alternately, you might cram the three modules into one flight all preassembled, if their fuel were in another.  This would mean at least six operations of astronauts pumping dangerous fluids into various tanks spread throughout the modules.  It might also mean assembling the lander’s legs from some inconveniently compact from.

Now you need a rocket to send the set toward the moon — one very like the third stage of Apollo, which used most of its fuel to lift the three modules out of low orbit and fling them toward the moon.  This rocket is a bit too large to fit into a shuttle bay, but it’s not too implausible that there could be a way to make it fit.  Its weight is no problem, if it’s empty.  But the fuel would take at least four shuttle loads!  Historically this rocket weighed 10 metric tons empty, and pushed a 40 ton payload.  The required delta-V is 3.1 km/s.  It burned nearly 100 tons of hydrogen and oxygen to accomplish this.  It used a bit more to circularize Apollo’s Earth orbit, which would not be needed in this case.

So the mission would require seven shuttle launches, starting with one to put up the booster with the first splash of fuel in it, and four more to fill it up.  Then the service module would be brought up, and attached to the booster.  The command and lunar modules would come up last, along with the astronauts who will ride in them.  That last shuttle could stay in orbit to await their return.

Since the empty “third” stage might not fit easily, and since it’s probably better to bring the fuel up in the tanks that will be used instead of needing to pump it from one tank to another, maybe the booster would just be a framework that fuel tanks would be bolted into.  Such a framework could be folded smaller for transport.  This would require additional assembly in space, possibly employing double digit numbers of shuttle astronauts over several flights.  But if everything were prepared well on the ground, the task should not be difficult or dangerous.  And if the orbits were well planned, the booster stage could be recovered into Earth orbit, and either refueled for another mission, or if necessary flown back down for refurbishment.  As SpaceX has demonstrated with their Falcon landings, once a booster is detached from its payload and has mostly empty tanks, a small amount of remaining fuel can accomplish quite a lot of maneuvering, so I don’t think it’s implausible that its engine could return to low orbit, especially if it discards some empty tanks or scaffolding.

The command module might not need to splash down into the ocean.  But it might still need a heat shield, just to brake in Earth’s atmosphere enough to slow down into an Earth orbit, so a shuttle can pick it up.  Or, this somewhat risky air-braking could be avoided by giving the service module more fuel.  (Perhaps it also could use bolt-in tanks.  Add one more fuel-hauling flight to the schedule in this case.)  An ocean splashdown might be the emergency backup option if the rendezvous fails.  But if it succeeds, they could even have the option of recovering the upper stage of the lunar module, and flying both modules down with the astronauts in one shuttle landing.

I’m sure this sounds a lot more awkward and inconvenient than the Apollo’s simple process of just launching one big rocket, but it would have been vastly less expensive.  Most of the parts would be reusable instead of disposable.  The only part that absolutely could not be reused is the bottom stage of the lunar module.  Apollo cost us at least $20 billion per landing, in today’s money; this would cost perhaps a quarter of that — and I’m sure if we made this a continuing operation, we would have found ways to lower the costs further.  Instead of just six trips to the moon, we might have continued doing dozens.  We might never have stopped.

However, I do worry that this process might have exposed astronauts to greater risks.  Lots of opportunities for something to go wrong up in orbit, and lots more shuttle flights.  As we have seen, those shuttles were not the safest things to fly in.

May 5, 2017

makes it easy!

Filed under: Hobbyism and Nerdry,life — Supersonic Man @ 3:08 pm

Whenever someone introduces me to a new software framework which is designed to make things easier, especially one to make visual layout easier, I usually end up wishing they’d left things difficult.  Because the thing about these frameworks is that they impose assumptions and expectations.  As long as you work within those assumptions and expectations, the framework saves a lot of labor.  But as soon as a requirement comes along which makes you step outside of those expectations, the framework stops working with you and starts fighting against you.  You end up expending as much work getting around the framework as on solving the problem.

This is especially relevant when the framework is for visual layout.  Because then, they only keep things easy when you adhere to certain limitations of visual styling, and the only people who understand those limitations are the developers.  Which means you’re fine as long as you’re willing to live with a programmer’s sense of visual style.  These frameworks seem terrific in demos, because the examples always take advantage of their strengths and avoid their weaknesses.  But as soon as you bring in a designer or marketer who understands design but doesn’t know the quirks of the framework, their ideas will immediately push you into fighting the built-in assumptions, and all the benefits of having a simplified labor-saving technology wave goodbye, going out for a beer while you’re stuck with a job which is now more difficult than it would have been with no help.

This has been true since the early days of graphical interfaces, from Visual Basic to Twitter Bootstrap.  The latter is my particular bete-noir at the moment, as we adopted it at my job, had to retrofit parts of our old design to not be broken by it, then started to develop new stuff which used it but also had the retrofitting in place, and of course were immediately hit with design change requests which don’t get along with it.  Even before those requests, we were already in a situation where our own CSS was in a fight with itself, half of it saying “don’t be Bootstrap” and the other half saying “you gotta be Bootstrap”.

In the nonvisual realm, it isn’t necessarily so bad.  Some frameworks actually do make things easier without making you fight them.  It helps if their use is purely for code, so it’s designed by programmers for programmers, with no end users involved.  One good example nowadays is jQuery.  It makes many things easier and almost nothing harder.

And we’ve been using it at work but now the word is we’re going to switch to Angular.  We shall see how that turns out.

Create a free website or blog at