wrog: (rockets)

So,... picking up where we left off, I, the intrepid hero, am sailing off to your right into the sunset, with my incredibly reliable gerbil keeping time for me. You, the diligent historian, will eventually reconstruct everything I'm seeing from all of the reports you'll get — from the cloud of NSA bugs that I'm flying through — into a big, happy space-time diagram in which:

  • My time axis, everything that is happening "Here" according to me, is — as everyone would reasonably expect because I'm moving — slanted away to the right from your own natural, obvious, and vertical notion of "Here",

  • My space axis, everything that is happening "Now" in my direction of motion, according to me, is, — as nobody expected prior to 1905, — slanted up from your own natural, obvious, and horizontal notion of "Now" and by the same angle,

that second item being what makes all the difference, ruins Galactic Empire stories, and happens to be the only thing you really have to remember about Relativity because it's enough to derive all of the other wacky effects you hear about.

Here's how:

Introduce a 3rd player, call her Alice, moving away from you to the left at exactly the same speed that I'm moving to the right.

Let's also give Alice a gerbil clock that is identical to mine. Same laws of physics applying to an incredibly reliable identical-twin gerbil running on its own identical gerbil-wheel. Thus far, everything Alice does mirrors what I'm doing, as far as you're concerned. Therefore she's got the same tilt to her time axis, her space axis, same spacing on all of her ticks, etc.

Rewind everything to when Alice and I were in the same place. Call that moment "here" and "now" for both of us. And then we zoom in on what happens in that first tick afterwards:

Look at all the events I consider simultaneous with my first tick. One of them is on Alice's ship, and it's somewhat before when she gets to her first tick. Meaning her first tick isn't happening fast enough, as far as I'm concerned. Which means I'm "seeing" her clock running slow — and a quick look at that grayed right triangle shows that it's by a factor of √1−v² — or, if you're one of those weirdos who insists on using stupid units that entail the speed of light being some c≠1, then it's √1−(v²/c²), whatever.

For you, this should be no mystery:  my definition of "simultaneous" is fucked up in not being horizontal. And if we flipped things around and look at where Alice thinks my first tick should be, she can just as easily conclude that it's my clock that's running slow.

And if I tell you that second gray triangle to the right is just the first one rotated by 90°, then it's not too hard to see that the distances Alice and I are measuring in the direction of motion will likewise have to be fucked up and by exactly the same factor.

If you're getting the idea that my deciding that a bunch of events are all happening "now" is a pretty arbitrary thing, you wouldn't be far wrong. Apart from the moment we meet, I'm not actually there on Alice's ship, so one might reasonably conclude it doesn't actually matter what I think about her clock. In fact, we're never really going to be able to compare notes because if we stay on our ships and never fire our engines, we never see each other again.

It's also a fair bet that other observers will have yet other ideas as to which event on Alice's ship is one tick from now according to them. And then we're stuck in this rhetorical black hole where all opinions are equally valid as to where "one tick from now" actually is, leading us to conclude that the notion of "one tick from now" must actually be nonsense, therefore time doesn't exist, and everything decays into this heap of moral relativism, Satan wins, etc.

We can still salvage something. There may not be a universally agreed, absolute notion of when "one tick from now" is. But, everyone still has to agree on which event on Alice's ship Alice thinks is one tick from now and that Alice and all of her passengers, just like her gerbil, must be experiencing one tick's worth of physics in that whole time.

And if we arrange for one of her passengers, Dave, to jump ship at the point that I think of as being one tick from now, everyone (including me) can and must still agree that Dave could only have experienced one √1−v²th of a tick while aboard Alice's ship.

If we then have Dave immediately catch a ride with Bob, who is coming towards me with the same velocity as Alice is moving away, so that Dave can arrive back where I am just in time for my second tick, we can all similarly calculate that Dave only experiences another √1−v²th a tick, thus arriving back at my place somewhat younger than expected,…

…and that is what rubs it in our faces that time is not this Absolute Thing, i.e., the way Newton and Gallileo thought it was.

Einstein probably figured he was done at this point, but I'm sure he hadn't reckoned with the tenacity of 20th century SF writers, so I'm going to go a bit further with this and extend the diagram to the left (a whole lot).

Let's suppose for the sake of argument everything thus far is all happening out in space 500 light-years from Earth, and let's suppose there exists some magical Tachyon or Subspace Transmitter Ansible Thing that allows communicating with Earth in real time. Remember, Sinclair was able to talk to Geneva on Gold Channel and get immediate responses.

Do we need the super-genius Vulcan working out the Intermix Formula that's likely to make the ship go up in the biggest fireball since the last sun in these parts exploded, which is why nobody'd ever thought to try it before? Do we need freak sunspot activity interfering in just the right way with the unobtanium-powered stargate? Or do we need Mysterious Tech from the ancient, dead civilization that takes up the inside of an entire planet and can only be used for the one episode?

Or… maybe,… just maybe,… we can look at where Bob's and Alice's Now axes are.

If we know how to make a subspace transmitter, we could make two of them: One for Bob, one for Alice. The physics of it, whatever it is, should work just as well on their ships as on mine, so all I have to do is give my message ("Kill Dave.") to Bob when we meet, Bob sends it to Earth, Earth relays it to Alice and voilà: trivially easy time loop.

For extra fun, let's see just how incredibly fast Bob and Alice have to be going in order to send a message back in time, say, one whole day. That ought to be enough to wreak havok, right?

Stretch the diagram so that the Earth⟷Me distance is 500 light-years, and then we make each of the ticks 12 hours. 500 years to 12 hours is a ratio of 365,000 to 1. Which gives you an idea of just how thin all of those triangles really are. Which means it's enough if Alice and Bob are going 1/365,000th of the speed of light, which is,… wait for it,…

900 meters per second.

This is so ridiculously easy we don't even need spaceships. Earth Alliance pulls a couple of SR-71 Blackbirds out of cold storage and it's game over right there.

You say, "Fine, so we don't do real-time communication. But surely, we could still have something where the message to Star Fleet Command takes 2 weeks to get there?" This changes nothing. Rerun the previous problem and ask how fast Alice and Bob have to be going to get a message back in time 4 weeks plus one day. The answer comes out to around 24,000 m/s. Yes, that's a bit harder. It's roughly how fast the Earth moves in its orbit around the sun. I think we'll be able to manage that.

If the communication delay is anything less than 500 years (minus 12 hours), Alice and Bob can go fast enough to make up for it and get the message delivered in time (a day ago).

The problem with "Meanwhile, back on Earth,…" is this:  If you are 500 light-years away from Earth, then "meanwhile" can, depending on how fast you're going and in what direction, refer to anything between the cord-cutting ceremony for a shiny, new Star Fleet Academy building in Marin City, California, and the first Spanish Explorers landing at Point Reyez 1,000 years earlier.

That much is not a problem so long as you and the Meanwhiles cannot actually talk to each other. But if you're relying on a Meanwhile for story purposes, then, chances are, you are assuming that they can. Why else would you be bothering with the happenings on Earth if it weren't going to affect your characters less than 500 years in their future?. And that's where you're going wrong.

Because once there's any kind of conversation along the "Now" lines, that means they all can talk to each other. Easily. And then the rogue Star Fleet cadets are teaching the Ohlone tribes how to make phasers, and would-be conquering Spaniards and causality all get toasted extra crispy.

Note that this is not an argument for FTL travel/communication being impossible. Just that if it were possible, in the sort of arbitrary and ubiquitous way that you would need for most Galactic Empire stories, then we're in Bill and Ted Land. Which we could actually be, for all we know, though, if so, I'd like to think we'd have noticed this by now. In any case, all of your stories then end up being unintentional time-travel stories, which will then consequently officially suck, because with two (2) pairs of stargates, a couple of non-FTL-but-really-fast ships, and a big enough fuel supply, you can fix anything…

…and then we spend the rest of the movie chasing down Biff's Sports Almanac.

wrog: (rockets)
(Yes, more Space! Part 1 is here but you don't need to go back that far to follow this)

Having at least covered (see Part 8) the question of why the speed of light is constant, the next order of business is the weird and wacky consequences. I'll skip straight to the one that nobody seems to get:

If you're writing your Galactic Empire story and you find yourself needing to say, "Meanwhile, back on Earth,…" that, right there, means you are doing it all wrong.

This can be explained, but first, we need some building blocks:

A Digression on Events and Light-Rays

An event is some instantaneous thing that happens somewhere.

  • On April 11, 1945, just off Okinawa,
    the USS Enterprise gets hit by a kamikaze.

  • On 287 พשּׁ₽ủ⿓, 389284th Year of the BL🐡R🐢G,
    somewhere near Gamma Leporis (~30 light-years from Earth)
    construction is completed on The Giant Commemorative Mirror.

  • On June ▒, 200▒, in a particular hospital room in Bellevue,
    my son is born.

I could do this all day. The entire history of the universe is basically one huge grab-bag of events.

We typically identify events by saying when and where they happened, but that is perhaps a bit misleading since actual numbers for time and place turn out to be negotiable given that observers are free to set up their own coordinate systems. Surveying your back yard, you can calculate latitude and longitude for all of your fence posts, but a prequisite and key piece of that puzzle is the direction you decided to call "North" (South Pole Station inhabitants can have particular fun with this). Change that and the latitude/longitude numbers all change,… but that doesn't cause the fence posts to move.

There's a similar choice with time. If you, sitting in your spaceship observing things, fire your engines, then you're changing the direction that you're calling "The Future". A series of events that were originally all going to take place near your ship is instead going to occur at progressively farther distances from you. But, again, despite that, the events themselves, The Things That Happen, our fence posts, remain wherever/whenever they are.

In particular, if the Things That Happen send messages to each other, then everyone observing them has to agree on who's sending what to whom. Because light rays carry information, whatever happens at the source has consequences at the destination, and no switching of viewpoints should be able to affect that.

So if the kamikaze blowing up on the deck of the Enterprise sends light out into space, which travels for 30 light-years, then encounters the Gamma Leporis mirror, and bounces back to the aforementioned hospital room, where yours truly had the foresight to set up a telescope pointed in exactly the right direction, then we can be in the birthing room watching/experiencing the battle of Okinawa in real time, with all that implies

(..."Oh cool! Enterprise control tower just got blown up. Okay, hon, time for another push…" and I'm pretty sure this would have had consequences if I'd actually done this.)

Building a Map

What you might not have expected is that just this much, i.e., having the universe be a grab-bag of events tied together by light-rays, is, by itself, enough for any single observer to map out everything in his/her vicinity.

Here's one way to do it:

  • We have bugs everywhere, helpfully planted by the NSA. I suppose if we want to be slightly more realistic, it'll suffice that there be a bug present at just the events where we need them, and they just get there somehow (and exactly how, we probably don't want to know).

  • I have a clock — a device based on some well-understood physical process, e.g., an incredibly reliable gerbil running on his little gerbilwheel specially contrived to make a "tick" every so often in a uniform way and sufficiently quickly that I can get whatever timing accuracy I need.

  • I have a transmitter that the bugs are all tuned to listen to. Every time my clock ticks, my current timestamp (= number of ticks since I started my clock) heads out into the universe at the speed of light.

  • The bugs have two jobs:
    1. Remembering what time it is, or, rather, what timestamp they most recently received from me. Since I'm constantly sending these out, they'll constantly be getting new ones. That way, they don't need clocks of their own.
    2. Reporting back to mommy. Every time a bug notices Something Interesting in its immediate vicinity, it compiles a (brief) report ("ship go boom" or "baby born") with my latest timestamp, and then broadcasts it in all directions.

  • Finally, I can have a very sensitive and very directional receiver.

So I sit there for a while collecting bug reports. The trumpet sounds and Time comes to an End, or maybe I just get bored and decide I'm done with all this. And then I can compile all of the reports I've received from everywhere and plot when and where all events occur onto one big, happy space-time diagram:

The way you read this is Time goes bottom to top. The black vertical axis in the middle is me and all of my clock ticks, evenly spaced because my gerbil is so incredibly reliable. Easy.

The horizontal axis is one of the spatial dimensions, call it "X", and there's some choice here about which way to point it. For the sake of argument I'll use some event that I care about and point it that way, meaning when the event finally occurs, it'll be on that line somewhere.

The speed of light being constant, once we send a signal, we know exactly how far away it'll be at any given time. So we can draw, in blue, lines representing all of the timestamp signals heading outwards, and they all have to have the same slope (because the slope is how fast they're going and that number is always the same).

I've taken the liberty of bolding one of the lines. All of the events where there are bugs receiving that particular timestamp have to be on that particular blue line.

Similarly, in red, I've drawn the possible paths of incoming signals from the bugs, and, again, helpfully bolded one of them. If I receive a signal at a particular time from a particular direction, then it had to have come from some event along that red line.

Once I receive a report and extract the timestamp, that, along with the time direction of receipt is enough to nail down exactly where the event is on this diagram.

(… It is a bit unfortunate that this 2-dimensional picture can only represent happenings in a 1-dimensional universe, but that's really all we need for now. If you want, you can imagine a Y axis pointing straight into the page/screen. The bent blue line becomes a blue cone, while the red line remains a single ray intersecting it at exactly one point, so this all still works. If you're totally insane, you can try putting back the Z axis as well, coming orthogonally out of reality, though if you were already able to do that you probably didn't need me to be explaining this stuff…)

What's interesting here is where the left-right axis comes from. Since I'm not moving — yeah, I know, hold that thought,— light rays will cover the same distance going out to an event and back. Even if the event is happening on some moving object, or perhaps the bug doing the report is itself moving around, or both, we simply don't care, because the bug receiving the timestamp, the event itself, and the bug's reporting of it, is all over and done with in such a short span of time that any errors resulting from the relative movements will be teentsy.

Therefore if the timestamp received at event E was 1006 and the corresponding report came back at 1026, then, obviously, the event E
  • happens midway between the two times, at 1016, and

  • at a distance of 10 ticks away from me, because if the signal is taking 20 ticks to get back to me, it must have taken 10 ticks to go out and another 10 ticks to come back.

Yes, I'm using "tick" as a unit of distance:  it's how far light travels in a clock tick. The speed of light is then 1, i.e., one tick per tick, and that's one less multiplication we have to do, so yay. This is also why we have the blue and red lnes being sloped 45°, in case you were wondering; life is so much more convenient when you use the right units.

We can also have other events happening at the same time (1016) at different distances away. But in order to infer that something happened at time 1016, the timestamp has to be just as much earlier as the receipt time is afterwards. Which then dictates that all of those events are on the same horizontal line as you'd expect.

Notice how I'm using my clock to measure distance. This is in fact the only good way to measure distance; actual, physical rulers are far too prone to being stretched, bent, or broken. Yes, things can happen to light beams, too, but we'll generally know what's happening and be able to compensate for it.

But the real point is so that we can do all of our measurements without having to go anywhere. All measurements come to us if we live long enough.

Now for the fun part…

Another Point of View

… in which Somebody Else, say, you, tries to reconstruct what I've done.

In what follows, you are somewhere off the screen, with your own clock built in its own peculiar way (you have an extraordinarily dependable hamster) ticking away at whatever rate along a vertical line, broadcasting your own timestamps, none of which I'll be bothering to show.

Your own "tick" is whatever it is, but for for the sake of clarity I'll assume your distance unit likewise matches up with your time unit so that you, too, can have light rays sloped at 45°.

What remains is to modify the bugs ever-so-slightly so that they're smart enough to distinguish your timestamp signals from mine and nice enough to include both timestamps in whatever reports they send. And then I ignore your timestamps, you ignore mine, and all proceeds as before.

At some point the trumpet sounds, or you get bored, and now it's your turn to reassemble the puzzle pieces.

There being NSA bugs in my clock, that's as good a place as any to start and you'll have all the information you need to plot where and when all of my clock ticks are taking place. You thus discover that I'm moving at some particular velocity (because different people can have different velocities and my future will be in a different place from yours; who knew?)

The velocity is constant because we're all just coasting along with engines turned off, nobody is spinning, and we're out in deep space where there's no gravity to worry about. And whatever direction it is I'm moving, we'll take that to be your X direction so that everything can stay on the page.

Once that's done, given that we have to agree on which events are joined by light rays, then for any other event, like E, no matter what place time numbers you assign to it, it remains the case that a (blue) timestamp message travels from me to E and a (red) bug report gets sent back; you have to have those light-rays linking E to the same ticks on my clock as I do. Which means once you've nailed down all of my clock ticks, E is nailed down as well.

The same goes for all of the other events I know about, including all of the ones on that now-not-so-horizontal line where I have t=1016.

Recall that the only assumption that went into this is that I have a constant nonzero velocity in your X direction, which necessarily tilts my time axis from your vertical. The rest of my grid of light-rays and events folds up sideways like an empty wine-bottle carton being stepped on, and there's only one way it can fold once you know how fast I'm going. Which means there's no way around concluding that my X axis, i.e., all of the events I consider to be simultaneous with my own here now, must be tilted from your own horizontal one…

and, it's not too hard to show, by the same angle. Meaning if, according to your grid, my 1026 clock tick is 500 light-years away from my 1016 clock tick — the sort of scale you need for a Galactic Empire story, — then, for you, E is happening 500 years later than my 1016 clock tick (rather than simultaneously, as it is for me).

It also turns out to be fairly simple to find an observer for whom E is happening 500 years earlier than my 1016 clock tick.

We don't even need to know exactly where you are or how fast your clock is ticking; which is why I haven't bothered to plot any of that.

Everything thus far is an unavoidable consequence of events being connected by light-rays and the speed of light being constant…

…and this much is enough to screw the pooch for any kind of Faster Than Light travel/communication.

(though exactly how will need to wait for Part 10)

Exodus

May. 8th, 2017 10:15 pm
wrog: (wmthumb)
So, wow, it's been 15 years. And yours truly is Not Actually Illegal in the Russian Federation (at least, not so far as I know and not yet).

But I'm still joining the Exodus to Dreamwidth because, well, fuck every last bit of that noise (also, fuck the ads, and maybe also fuck brad, while I'm at it...).

In other news, I learned enough of the API to fix the cross references in my journal to all point to Dreamwidth so that you can painlessly follow my various n-part series which might possibly be continuing; we'll see. (I may be sufficiently annoyed to change all of cross references on the LJ side as well, whee...)

Now I just need to turn off commenting on the LJ side (just c'mon over — or if you don't want to do the wholesale move, just create an account and claim your LJ OpenID (note that some of you who've already moved here still need to do that...)

wrog: (rockets)

(Still waffling on whether this should be Space Travel part 8 or Relativity part 1; we'll see...
If you want to go back to part 1, that's here though none of the prior material really matters for this one.)

It's weird to me how everybody knows there's a problem.

How, if you are, say, Issac Asimov or George Lucas or Gene Roddenberry trying to write your Galactic Empire/Federation/Whatever story, you've got to do some kind of handwave about Relativity. We know this because we were taught at some early age that trying to go faster than lightspeed is Somehow Bad, even if nobody ever explains the details.

It's particularly annoying to me because many of the details actually could be explained without going beyond 6th grade math. If you get how right triangles work, that's pretty much all you really need for Special Relativity, except nobody seems to bother trying.

I suppose part of the problem here is the mystique of General Relativity. True story:

Arthur Eddington is at a meeting of Royal Society in 1919 where Sir J.J. Thomson (President) concludes a talk saying nobody's ever really stated in clear language what Relativity is about. The meeting disperses, Ludwig Silberstein (the author of one of the early books on relativity) comes up to Eddington and essentially says, "So you must one of three people in the world who actually get this stuff." Eddington demurs, but Silberstein pushes further, "C'mon, don't be modest," at which point Eddington replies, "Actually, I'm trying to think who #3 is..."

Then again, given the sheer number of people I've encountered who have Misner, Thorne, and Wheeler's Gravitation sitting on their bookshelves, that's clearly not the case anymore.

But if even Albert Fucking Einstein had to take five years off to get up to speed on Differential Geometry — which to some extent is just the Partial Differentiation Chain Rule on Steroids and working through all of the various consequences, but if you didn't get past high school calculus, even that much is going to be a bit hard to take — what hope is there for the rest of us ordinary mortals?

But it so happens that, for Special Relativity, you don't need differential geometry. So let's get started:

Why is the speed of light constant?

How did they even get this idea that the speed of light is always the same? That's the part They never explain. They figure there's no way anybody's going to get that without having the full-ass physics course, so they don't bother trying.

The short answer is that they've done the experiments and that's the way it actually is. Since that's unsatisfying, I'm going to try giving you the half-assed physics course instead:

Read more... )
wrog: (party politics)
(... The curse of being a math geek living in a state where they have caucuses instead of primaries (not to mention having spent some time observing party rules committees) is I end up thinking about this stuff...)

So here's a fun issue with caucuses:

First, a quick review of the basic rule for awarding delegates at caucuses.

Your precinct is allocated some number of delegates, D, to elect. Some number of people attend your caucus and each declares a preference for a particular candidate. Twenty minutes later, once the blood has been mopped off of the floor, the battle lines have hardened, and everyone who might have been inclined to change his/her mind has been talked to death, you then compute for each candidate the following number
(# of votes for that candidate)
——————————————————  × D
(# attendees)
I'll note first of all that every attendee will in fact be included here, because if you don't ever actually declare a preference, that's treated as equivalent to declaring a preference for "Uncommitted," this extra fake candidate that's always added to the mix. So it's guaranteed that all of these "delegate-share" numbers will indeed add up to D.

The next step is to split each delegate-share into a whole number plus a fractional part. For each candidate, the whole number gets awarded directly, and, if those numbers by themselves don't sum to all of the available delegates, you then rank the fractional parts and distribute any remaining delegates, one each, to the highest candidates in that fractional ranking.

(...And yes, for those of you who know about this, I'm skipping the 15% threshold rule, which some states apply at the precinct level. Thankfully, in Washington, we got rid of that 8 years ago, since it's a complete waste of time at the precinct level [also has any number of bad effects, but that's a whole 'nother discussion].)

So first, I'll present Survival Trick Number One, so that you can survive in a chaotic caucus environment without having to do long division in your head. It goes like this: we rewrite the formula above as follows:
(# of votes for that candidate)
————————————————————
((# attendees)/D)
i.e., just divide numerator and denominator by D, which works because multiplication is commutative (...except that the DNC stupidly ruins the commutativity by including a 3-decimal rounding rule in the process, but, as it happens, this doesn't affect things very often at the precinct level, and in any case this still works fine as a rule of thumb so that you can wrap your head around what's going on...)

Bottom line is there's a certain magic number of votes ((# attendees)/D) that you need to get a "whole delgate".

Meaning you can take your caucus, divide it up into blocs of that many people who are all voting for the same candidate. For each such bloc, that candidate gets a "whole delegate", and then whatever votes you have left over, you rank those, and the candidates that are highest on that ranking get the remaining delegates. The advantage of doing things this way is that you're just counting votes without having to do any long division in your head.

Concrete example:

You're in a precinct that's been allocated two delegates.
Twenty people show up.
14 are Kerry supporters.
6 are Dean supporters.
If you follow the worksheet, then it's (14/20)*2 = 1.4 vs. (6/20)*2 = 0.6.
Kerry gets 1 whole delegate and then, because 0.6 beats 0.4, Dean gets the other one.

Or you can do it my way, seeing that (20 attendees)/(2 delegates) = 10 votes needed to get a whole delegate. Thus, Kerry's 14 votes produce one whole delegate (10 votes) with 4 left over that then lose to Dean's 6 leftovers, and so Dean gets the other delegate out of the "fractional ranking", never mind that we're not having to rank fractions any more.

Now for the problem.
It turns out that the number of votes that you need to get a whole delegate is NOT the same as the number of votes you need to win a delegate out of the fractional ranking.
In fact, if your candidate is getting awarded any whole delegates at all, there's a fair argument that some of your votes are being wasted.

What do I mean by this?

Back to our example: Thus far, it's 14 to 6 with each candidate ending up with one delegate. But then the Kerry folks wonder if they can do better. And it turns out, they can!

After a brief strategy session, 7 of the Kerry voters change their preference to Uncommitted. Which now means the totals are 7 Kerry, 7 Uncommitted, and 6 Dean. Since you need 10 to get a whole delegate, there are now zero whole delegates, the fractional ranking then has to award two and they go to Kerry and Uncommitted.

Except,... since the "Uncommitted" folks are really all Kerry supporters, it's a good bet that "Uncommitted" delegate will be signing in for Kerry at the next caucus level.

Which means Kerry has just effectively cleaned up and claimed both delegates.

WTFF? How did that happen?

On the other hand, he did have more than 2/3 of the vote in that precinct, so there's some argument that this isn't actually a totally unfair outcome and perhaps the real question is why should the Kerry supporters have to jump through this extra hoop to get the delegates that are rightfully theirs?

The problem is that, while the number of votes you need to get a whole delegate is
(# attendees)/D,
the number you need to guarantee one out of the fractional ranking is actually
(# attendees)/(D+1),
which, in our example is 20/3 = 6+2/3.

... or, more precisely, if your candidate has at least (# attendees)/(D+1) and there is at least one candidate with strictly more than (# attendees)/(D+1) (even if it's only the slightest ε more), then you are guaranteed a delegate out of the fractional ranking (since in that case there cannot be more than D groups with (# attendees)/(D+1) votes, and you're one of them, so you win)

Dean with 6 votes isn't quite there, and that makes all the difference in the world.

Meanwhile back in the first scenario, where the Kerry supporters are spending 10 votes to get a "whole delegate", this can now be seen as a ripoff, spending 10 when they only needed to spend 6+2/3, thus wasting 3+1/3 of their votes, which costs them a delegate.

More generally, (# attendees)/(D+1) will always be less than (# attendees)/D and, if you're in a close race, chances are you're going to care about that difference.

And apparently, they've even thought about this in Iowa, or, rather, it's the only way I can account for Iowa's version of the threshold rule which not only makes things way more complicated, but also introduces the nastier features of thresholds into the lower-delegate caucuses where they weren't originally a problem.

My fix, which will most likely never be adopted, is much simpler:

Instead of multiplying by D, multiply by (D+1).

That is, for each candidate you instead compute
(# of votes for that candidate)
————————————————————  × (D+1)
(# total number of voters)
and then proceed as before, awarding the whole numbers, and again if the total number of delegates awarded in this way is different from D, use the ranking of the fractions to fix it. The only difference now is the (remote) possibility that there will be too many (i.e., D+1) delegates awarded via the whole numbers, in which case, instead of giving out delegates to whoever is at the top of the ranking, we're taking a delegate away from whoever is at the bottom (except that if all of the whole numbers are indeed adding up to (D+1), that means all of the fractional parts will necessarily be zero, so we don't even have to look at any ranking; you just pick somebody at random to lose one).

So in our example, for Kerry the magic number is 14*3/20 = 42/20 = 2.1 and for Dean it's 6*3/20 = 18/20 = 0.9, Kerry gets 2 and we are done; we don't even need to consult the fractional ranking at all.

Or, calculating things my preferred way, you need 20/3 = 6+2/3 votes to get a whole delegate, Kerry has 2 such blocs, Dean doesn't have any, and again we're done. At which point it should be blindingly obvious that there's absolutely no advantage to be had by splitting your voters up over multiple fake candidates; you'll get the same result either way.

Which is the way caucus rules should be (i.e., they just give you an answer and no amount of gameplaying changes it).

But, even though they're never going to adopt this rule, you can still use it, the point of it being that if you're ever in a situation where the Multiply By (D+1) rule is giving you a different answer than the actual Multiply By D rule, that's where you have to watch out.

This effect is most pronounced in the 2 delegate caucuses but it can show up in higher-delegate caucuses as well.

Example 2

4 delegate caucus
20 people show up
17 for Kerry
3 for LaRouche

So now it takes 20/4 = 5 votes to get a whole delegate. Thus, Kerry supporters can spend 15 to get 3 of the 4 delegates. Unfortunately, that means they only have 2 votes left over, which lose to LaRouche's 3 in the fractional ranking and so we get one LaRouche delegate.

What does the Multiply By (D+1) rule say? In this case (D+1)=5, meaning you only need 20/5 = 4 votes to get a delegate out of the fractional ranking, and, with 17 votes, Kerry supporters can produce four such blocs which will all beat LaRouche's 3 votes.

... the only problem being that those blocs need to be for four different candidates. But this is actually doable:

5 for Kerry
4 for Uncommitted (actually Kerry)
4 for Sharpton (actually Kerry)
4 for Kucinich (actually Kerry)
3 for LaRouche

Now Kerry only gets 1 whole delegate while the fractional ranking awards the rest to Uncommitted, Sharpton, and Kucinich, who all change their votes to Kerry at the next caucus, and thus Kerry cleans up all four delegates.
wrog: (toyz)
William has learned about Rock, Paper, Scissors. In honor of that, a puzzle:

Same game: Rock breaks Scissors, Paper covers Rock, Scissors cut Paper. So far so good. Now we add a couple twists:
  • I do research and find myself a Better Rock, a chunk of pure New England granite that rules, absolutely crushes all lesser Rocks. Even though it still loses to Paper I'm happy with it.
  • Meanwhile you've been doing your own research; being of a technological bent you know there are better ways to do Scissors; carbon steel with a diamond edge; not only cuts Paper but completely destroys other Scissors as well. Granted, even a diamond edge is no match for an any actual Rock, let alone mine, but you still win against everything else, so you're happy.
So... my Rock beats your Rock, your Scissors beat my Scissors, and Paper vs. Paper is the only draw possibility left.

What's my strategy? What's your strategy?

And how does this change if I go out and get really good, battle-ready Paper as well, e.g., some of that Tyvek stuff that they use to insulate houses; something that will entirely shred your Paper, even if your high-tech Scissors will still make short work of it. Meaning that not only is there no longer any possibility of a draw, but out of the 9 possible scenarios, I'm winning in five of them.

Unfair, right?

Discuss.
wrog: (rockets)

(This is Part 7. There are previous installments; this one is a digression from something I said in Part 6, though you can also start from the beginning at Part 1)

In Part 6, I said:

The theoretical absolute best we can do with rockets is if we can get the exhaust velocity up to the speed of light. This means our exhaust will be pure radiation, that we are somehow powering a huge-ass laser with 100% efficiency, since that's the only way we get all of the exhaust going the same direction. And, boy howdy, do you not want to be following along directly behind,…

Which leads rather directly to this:

The best possible rocket engine and the best possible directed energy weapon are exactly the same thing.

Remember this the next time you're watching Star Wars, Babylon 5, Battlestar Galactica, etc. All of those little fighter ships where the engine is distinct from the guns? Those scenes where they're accelerating forward, closing with the enemy, firing forward with everything they've got?

Wrong. Wrong. Wrong. No military contractor worth its salt is going to waste resources mounting a second gun on a ship when there's already this totally effective and somewhat expensive first gun.

Conversely, if you've got a phaser/laser/gamma-ray-laser that can do real damage from a distance, then most likely that is your engine. If you're in a universe where rockets are your only form of propulsion, you are definitely not going to be wasting resources on a 2nd engine. It's going to be correspondingly expensive to fire, too. Nor will you get off that many shots before you're hurtling away.

What you need to do is arrange to be headed towards your target with as much velocity as you can manage. Then, when you're really close, you flip around and shove the throttle to maximum. It'll look exactly like you're landing on your target (modulo the small matter that you'll want to not be too predictable about it, see below). Best if, once you've killed all of your relative velocity, you can whip out some (really strong) tethers to attach yourself with before continuing to fire, so that you can be expending as much energy as possible on your target vs. propelling yourself away.

Of course, if you actually can get that close you're probably still better off with a burrowing torpedo that can blow up your target from the inside.

In fact, I'm rather having trouble shaking the conclusion that directed energy weapons aren't at least as stupid as rockets. On the other hand, if you're stuck in a universe where rockets are all you have, then so be it. Swords, planted bombs, and bioweapons are all very nice if you can get close enough to use them, but sometimes you just can't.

Also, to be sure, planet and asteroid-based gamma-ray-laser cannons will be a different story. They'll have room for arbitrarily huge reserves of antimatter compared with what you'll have available in your fighter ship, and the momentum consequences of firing off huge blasts will be negligible for them.

Suffice it to say, you'll want to stay well out of range of those. Except for the small problems that,

  1. being lasers, they'll have lots and lots of range, and
  2. the moment you stop firing your own engine for any length of time, your trajectory becomes immediately predictable; figure by the time we have practical antimatter distilleries, we'll have the software for this worked out just fine, too
  3. given the stupidity of rockets, you won't be able to be constantly firing your engine for any length of time before running out of fuel
So, good luck with that.

Granted, if I were going up against an entire planet, I'd probably want to arrange for a dinosaur-killing asteroid to do the dirty work for me. Hide an armada behind it to take out anyone who tries to come near to divert it.

Which then means that any sensible planet is going to have an entire inventory of asteroids of various sizes lined up at its Lagrange points to be able to deal with any such threat, at which point I'd then concentrate my efforts on subverting the folks in charge of the asteroid inventory.

Or maybe just taking a trip down to the planet itself, sneaking in, and detonating the huge antimatter reserve where the phaser cannon is located.

Of course, if everybody has sufficient resources to be distilling out the insane quantities of antimatter needed to be fighting these battles, I'd have to wonder what the hell they're fighting over. Not that this would be the first time in human history where a war got started for completely stupid reasons (cf. WWI)

And round and round we go.

(and there's a Part 8 now, where we move on to Something Completely Different)

wrog: (rockets)

(This is Part 6. There are previous installments, though if you only made it as far as Part 3: Rockets Are Stupid, that's good enough for this one.)

Rockets are Even More Stupid Than You Thought

Meanwhile, back on the launch pad, staring at the 2500 tons of Saturn V that I've just told you how to make smaller, we can ponder what's going to be possible once our technology gets Really Good.

The theoretical absolute best we can do with rockets is if we can get the exhaust velocity up to the speed of light. This means our exhaust will be pure radiation, that we are somehow powering a huge-ass laser with 100% efficiency, since that's the only way we get all of the exhaust going the same direction.

And, boy howdy, do you not want to be following along directly behind,…
… which inspires an observation about fighting space battles, which I'm going to defer to Part 7.

Anyway, this Best Possible Rocket brings the fuel cost for getting your Winnebago-sized Command Module to the moon and back again down to a mere 327 grams.

The catch is that half of that 327 grams will need to be antimatter. This also assumes you've solved the problem of storing it in a reasonable way — and if so, the Fusion Power People would really like to hear from you; and no, they won't necessarily be obsolete, because antimatter is merely a storage medium; you still have to extract the energy from somewhere. It should be noted that the amount of energy needed to make that amount of antimatter — and what you get back when you let it recombine — is roughly that of an 8 megaton bomb.

So, if you're imagining this to be the family car, where you can just hop in and fly to the moon for a week when the kids are off school, guess again. Unless you like the idea of each of your neighbors having an 8 megaton bomb in the garage and DUI being about much more than just the occasional lamp post or pedestrian. Hell, let's just have every auto repair garage, bus station, and airport be a terrorist candy shop, where the stakes in question are not just single office buildings but whole continents and planetary habitability.

Suffice it to say, there's a whole range of social and political problems we're going to need to have completely solved before we get to any kind of ubiquitous space travel regime.

Never mind that said problems will have bitten us in the ass long before we have practical antimatter distilleries. No matter how many countries we can get to sign the nuclear non-proliferation treaty, if you're Joe Sixpack sitting at L1 with a 6 ton rock and the right software, that's an 8 megaton bomb you can drop anywhere on earth, no nuclear tech needed.

To The Stars?

And all of that insane energy expense is just to get to the fucking moon. You want to go to the stars?

Using this theoretically perfect rocket which will never actually exist, accelerating at one g (earth gravity) for a day costs you 0.3% of your ship. That may not sound like a lot but you'll need to keep that up continuously for a year to get to 3/4 the speed of light. At which point 2/3 of your ship is now gone (which means at least 1/3 of it was antimatter to start with).

That may be good enough to reach Alpha Centauri, but to get anywhere real, you need to keep this up. Four more years (proper time) of accelerating at 1g — meaning you'll have to spend 242/243 of your original ship; picture launching one third of a Saturn V half-filled with antimatter — puts you 75 light-years out from earth, with finally enough time dilation (100 to 1) so that you can coast across some reasonable fraction of the galaxy (thousands of light-years) in a single lifetime.

Confined to a Winnebago.

And you thought space exploration was going to be fun and exciting.

Also, you better hope you picked a good destination, because, unless you happen to have a perfectly placed neutron star or black hole in your path — at which point you will then also be needing enough shielding to cope with all of the crap likely to be in the vicinity of any such object, because going at any significant fraction of light-speed means you'll need to get really, really close to make any kind of tight turn (also, good luck with the tides) — course changes will be essentially impossible once you get going fast enough.

Nor will you be able to stop anywhere along the way or even slow down at the end of the trip, unless you've arranged to be able to spend another 242/243 of your ship and allowed for another 5 years (proper time) to do it. Meaning we're now launching something 73 times the size of the Saturn V, half-filled with antimatter, and stuck in the Winnebago for a minimum of ten years, in order to be able to do any kind of interstellar travel beyond 150 light-years.

Rockets just suck.

Why I Shouldn't be Allowed to Write for SF Television

This, by the way, is something else that Star Trek and similar shows get wrong.

((Update: It seems I've done Roddenbury an injustice; he apparently did make a pronouncement about impulse engines early on. So you'll have to read this as, "What Star Trek would have been like if impulse engines were rockets." In any case, it doesn't let any of the other shows off the hook: BSG, I'm lookin' at you.))

It's not that I'm going to fault them for postulating the existence of something like Warp Drive, which you just need if you're going to do Galactic Empire stories. Nor am I going to fault them for not dealing with Relativity properly, because the sad fact is that most SF authors only understand Newtonian Universes anyway, and I'd just as soon they stay in their comfort zone and tell stories that make sense on their own terms, rather than attempt to include Relativity and make an utter, complete hash of it. The other fun thing is that if you try to have Warp Drive and Relativity in the same story, then that generally means you have a time travel story even if you don't realize it, at which point JWZ's Law probably applies.

No, where Star Trek — along with everybody elseactually screws up is with the impulse engines, whether they're called that or "thrusters" or "reaction engines" as on some other shows, they are clearly intended to be rockets of some sort. And then they get used in every episode as a completely routine means of puttering around a planetary system.

To which I say, "Wrong." Firing a rocket is cannibalizing your spacecraft; it uses exponential amounts of fuel; you never want to do it if you have any alternative available. Rockets are the propulsion method of last resort.

Meaning if you actually had anything at all like Warp Drive, you would contrive a way to use it for everything you possibly could. You'd use it in-system, you'd install it on the shuttlecraft, you'd use it in the space dock, you'd use it for going to the grocery store. You would use it everywhere that you didn't have some other reasonable alternative (like space elevators, solar sails, tethers, whatever).

WHY? BECAUSE THAT IS HOW MUCH ROCKETS SUCK.

The only proper scene in which the impulse engines would even be brought up would be something like the Battle Aftermath Scene. In which the ship has been wrecked by Commodore Decker's planet killer or some such. They've barely eked out a victory, but half the crew is dead. Bodies are scattered everywhere. Shit is on fire. You can hardly see through the smoke. Sulu and Chekov have big nasty burns. Kirk has his shirt ripped off and is bleeding in a dozen places. McCoy and Chapel are buzzing around doing triage. Warp drive is trashed. Dilithium crystals are hopelessly fused, etc.

And now it transpires that they're spinning out of control into a planet or something. At which point we have a dramatic pause and musical cue as Kirk calls down to Engineering.

"Scotty," he says, "Ready the impulse engines."

Some of the younger bridge crew startle at this. It comes up in the training sessions but you never imagine that you'll hear it for real. Because if you do, it usually means you're about to die.

And then we have the long anguished close-up on Scotty. He looks around at the debris in the engine room and realizes the captain is probably making the right call. And finally...

"Aye, captain."

His children are about to be murdered and there's nothing he can do about it. He motions two of his surviving lieutenants over and together they remove the cover and break the seal on the impulse controls. There's a huge lever there that takes three men to move.

Back on the bridge, Kirk flicks a switch on his armrest, "All hands! Jettison Stations! Level Three Emergency! Unnecessary mass into the tubes! Repeat! Level Three Jettison Emergency! Unnecessary mass into the tubes!"

Cut to scenes around the ship of surviving crew members, rummaging through every room, grabbing everything not nailed down — wreckage, equipment, random belongings — and stuffing it all into chutes specifically designed for this purpose.

"Sulu, what's our time factor?"

"We need 5000 ΔV in the next 30 minutes or we're dead."

Flick. "Engineering?"

"Impulse engines ready, Captain. You'll have 195 seconds of burn time."

"Thank you, Scotty. We'll make it count. Spock, how's our mass situation?"

"Down 23% We need to lose another 5. Another 10 minutes, 42 seconds if we can keep the jettison rate up."

"That's cutting it too close." Flick. "All hands! Level TWO Jettison Emergency! Repeat! Level TWO!" Cut to more scenes around the ship. Now they're gathering the dead bodies and stuffing them into the tubes. Cut to exterior view of the ship with expanding cloud of debris and bodies and crap.

… and so on.

Really. Rockets just suck.

Up next, Part 7: Space Battles

wrog: (rockets)

(This is Part 5. The previous installments are Part 1: Another Anniversary, Part 2: Climbing the Wall, Part 3: Rockets Are Stupid, Part 4: L1 Rendezvous )

Sisyphus Revisited

So, before I get on with confessing my sins and explain what I've been lying about, I'm realizing I need to say a bit more about instabilities and why that horribly weird spiral trajectory — which I'm going to guess would have been especially horrifying for those Mercury and Gemini astronauts who all got their start as experimental aircraft test pilots; just mention "spiral dive" to any pilots you know and see what they have to say about it (hint: it's not something one usually lives to tell about) — and about why said trajectory is something to be embraced rather than feared.

Imagine a ball bearing rolling back and forth in a parabolic valley.

This scenario, the Simple Harmonic Oscillator, shows up all over the place, pendulum clock, weight on spring, child on a swing. It's like 90% of physics is about making as many situations as possible look like simple harmonic oscillators. Not suprising since this one of the easiest things to solve; we have this hammer; if we can make everything look like a nail, so much the better.

Qualitatively, there's only one solution:

x ∝ cos(ωt)

The ball just goes back and forth and back and forth and back and forth. Forever and ever; the epitome of stability. Once you know the frequency ω, you've got the whole story.

(I use the wonky "is proportional to" (∝) symbol so as not to have to be writing out lots of pointless constants. If, in what follows, you also want to imagine (t-t0) wherever you see t, feel free. So really what we're saying is x=x0cos(ω(t-t0)), the most general solution. Or you can just ignore the math altogether.)

And now we sneak in and make a little, teentsy sign change. What harm could it do?

The next morning, the security guards wake up and find that the parabolic valley has been turned upside-down/inside-out/whatever and we now have a parabolic hilltop (... along with Spock getting a goatee, Federation → Empire, Cat → Dog, etc...).

Whereas before, we had one simple solution, there are now nine (9) and they're all different qualitatively.

Instead of running away screaming, I'm going to make a table listing them all, so that you can get a sense of what we're up against. You may find it easiest to read them in a clockwise or counter-clockwise order.

x ∝ −e−ωt
The ball has always been rolling in from the left; someday it may reach the top but we won't live to see it.
x ∝ +sinh(ωt)
The ball approaches from the left,
makes it over the top,
and rolls down to the right
x ∝ +e+ωt
The ball has always been rolling away to the right; if it was ever at the top, long ago, nobody remembers that far back.
x ∝ −cosh(ωt)
The ball approaches from the left,
fails to get to the top,
rolls back to the left
x = 0
The ball was, is, and ever shall be perfectly balanced at the top of the hill. Amen.
x ∝ +cosh(ωt)
The ball approaches from the right,
fails to get to the top,
rolls back to the right
x ∝ −e+ωt
The ball has always been rolling away to the left; if it was ever at the top, long ago, nobody remembers that far back.
x ∝ −sinh(ωt)
The ball approaches from the right,
makes it over the top,
and rolls down to the left
x ∝ +e−ωt
The ball has always been rolling in from the right; someday it may reach the top but we won't live to see it.

Tell me where you are and how fast you're going, and I'll tell you which box you're in.

The colorings are energy levels. All of the gray boxes have the same energy. Meaning if, when you're at some particular place and you have just the right velocity, you'll be in one of the gray boxes. If you're going faster, then you're in one of the blue boxes; if you're going slower, you're in one of the red boxes.

The gray boxes are essentially boundaries, drawing the fine line between success (blue boxes) and failure to cross over (red boxes). And you can skirt as close to them as you dare, so if, say, you're in one of the blue boxes, by reducing your energy you can make your trajectory be arbitrarily close to the trajectory in the gray box on either side. The closer you get, the more time it takes, so if you're going over the hill, you can arrange to take exactly as much time as you want by picking the right velocity/energy level.

In the center is chaos. An infinitesimal change to an x=0 scenario has eight possible outcomes. Rounding errors will ruin your day if you're not sufficiently clever.

Now, as I mentioned earlier, L1 is actually a saddle point. That is, assuming we orient our axes the right way, it's a parabolic hilltop in the x direction but in both of the y and z directions it's a parabolic valley. Parabolic valleys are places where we can park arbitrary amounts of energy while we're passing through (well okay, there are limits). In other words, if we're going through L1 from the Earth to the Moon or vice versa, we can make the transit take however long we want by changing the size of the spiral.

And since the various frequencies/periods stay roughly the same if we don't go too far out, that means we can spiral around as many times as we want while going through. But also, since we can mess with the y and z directions independently, that gives us even more choices re what direction we're going once we're out of the neighborhood of L1.

What we need is to build a map. Essentially, you can think of there being a (4-dimensional but never mind that) sphere of possible ways to park energy in the y and z directions. Imagine that sphere as being the center box in the table above (i.e., what the orbits would be if we weren't moving at all in the x direction).

Then you have the upper-right and lower left "Rolling Away" boxes which are now (5-dimensional) tubes leading from the sphere to elsewhere, and then the pair of "Rolling in" boxes, which are tubes from elsewhere back to the sphere. These bound the set of possible useful transit trajectories (the blue stuff) that take us from the elsewheres on the left (in the big hole where Earth is) to the elsewheres on the right (the moon and everything outside), which are what we want out of this.

At which point our agenda is simple (hahahahaha): Solve for where the sphere is. Figure out where the tubes go. Once we know where the tubes go, we know what our choices are.

The Actual Lay of the Land

Something is indeed rotten in Denmark and the core of it is that we're not actually doing the happy two-body problem that Newton solved, where angular momentum is conserved, everything has to move on conic-section-shaped trajectories, and ellipses are forever. Counting on our fingers, we see that Earth is one, Moon is two, and spacecraft makes three (3) bodies there, at which point there are no closed-form solutions, Newton gave up, Lagrange figured out a few things and then gave up.

There are lots of weird nooks and crannies, and we're in the process of stumbling onto one of them. Indeed the very fact that we can even have saddle points where chaotic things are happening is all part of why there can't ever be a closed form solution.

But now we need the Big Picture.

L1 is at minus 170km but "the top" is not at 0km. Why? Because, this whole time, I've actually been using a rotating reference frame where the earth and moon are fixed. Which means, among other things, there's centrifugal force to contend with, which gets stronger the farther out you go.

Meaning that 6000 km deep hole where the Earth is is not in the middle of a plane, but rather at the center of this parabola-shaped hill (well okay, parabola-of-revolution-shaped hill), which turns out to be a volcano with a 6000-km deep crater at the top of it. The circular rim of the crater is where the moon's orbit is; everything slopes downwards in all directions outside of it.

Things are further messed up because the moon is sufficiently big to put the earth off-center. That is, since earth and moon actually revolve around their common center of mass, the earth is displaced somewhat (4600km) in the direction opposite to the moon. Which then tilts that aforementioned circular crater rim; rather than being a constant −160½km altitude, the point opposite the moon on the rim (the L3 Lagrange point) is a bit lower (−161km) because it's closer to the earth.

Now if L3 is the low point on the rim, you might be thinking the place opposite it, where the moon is, should be the high point, but

  1. the moon is there, and
  2. the moon has its own gravity, which we have to add back (450km deep hole, remember?)
So, no.

Where is the high point? Follow the rim 120° from L3 in the direction of the moon's orbit and you get to L5 and O'Neill's space colony. If you'd gone 120° the other way you'd have gotten to L4 instead. L5 and L4 are both at −160km and are the real (twin) hilltops. They are as high as you can go and there is no place that's 0km after all.

Things are actually further messed up because of the Coriolis force, which I haven't told you about, which happens to be crucial for understanding why L4 and L5 are stable even though they are hilltops which should otherwise be completely disastrous from a stability point of view. Fortunately, for L1 and L2, the Coriolis force only messes with the frequencies and tilts the various axes a bit; it doesn't change the overall qualitative picture, so I can skip that part.

(Nor was I never clear on why O'Neill preferred L5 to L4. Everything you can do with L5, trajectoriwise, you can do with L4; it's all symmetric, see. I'm also now wondering if the hilltop genuinely is the best place to be; it's actually the hardest place to get to in the Earth-moon system. There are so many tasks you need to do to maintain a space colony and keep everybody alive; station-keeping was never even remotely the biggest problem. Stability also means it's harder to leave, which will suck if you ever want to move the colony somewhere else. Though I suppose being at hilltop may reduce the probability that random rocks will arrive from infinity and ruin your day. That, to me, would be a much better selling point than stability — if it's actually true; haven't done the math on that one yet...)

So to get out from L1, instead of having to climb 170km as you might have originally thought, it's looking like, depending which direction we go, we only have to climb 10km at the most.

But it gets better.

The presence of the moon actually cuts a huge notch in the crater rim. If we continue our hike along the rim from L3 past the peak at L5 we'll find ourselves headed decisively downwards. Then the rim wall splits, going around either side of the big hole where the moon is. Directly across the moon from where they split, the walls rejoin on the far side and the rim continues around up to L4. L1 is the saddle point on the inner wall; L2 (you knew there had to be an L2) is the saddle point on the outer wall. And that is the last of the flat spots; Lagrange proved that there could only be five and this is where he left things 200 years ago.

L2, at −169km, is a measly one (1) kilometer higher than L1. As long as you have at least 140 m/s (313 mph) of velocity when you get to L1, you'll have enough energy to get to L2. And everything I've said about L1 (i.e., that it's a saddle point, that there are tubes, etc...) is true of L2 as well.

So if you're stationary at L1, you just need to put on 140 m/s of ΔV. But it's actually easier than that. The moon is right there. L1 has two outgoing tubes, one headed back towards Earth, the other outward. L2 likewise has two incoming tubes. See where the outward bound L1 tube intersects L2's from-inwards tube. Find the pair of intersecting orbits that comes closest to the moon. That is where you want to do your burn and chances are it'll be a lot smaller than 140 m/s (because the deeper you are, the faster you're moving and the faster you're moving, the less ΔV you need to achieve a particular energy change, i.e., to gain that last kilometer).

Once you are at L2, you are definitively outside the crater.

At which point we switch to the Earth-Sun rotating frame, where there is an entirely different set of Lagrange points. As it happens, the Earth-Sun L1 and L2 points are each about 1.5 million kilometers from Earth, your being at the Earth-Moon L2 point means you're now moving in a 444,000 km radius circle around the earth — exactly where depending on the time of the month — at something like 1200 m/s which is 300 m/s faster than what you'd ordinarily need to stay in circular orbit around Earth at that distance.

Which means, once you get sufficiently beyond L2 and away from the moon's influence, you're being flung away. Depending on how you timed things — and you can hang out in the halo orbits as long as you need to in order to time things just right — you can arrange to get flung away in any direction you want; and you'll be left with enough energy to both get away from the moon and get up another 63km worth of wall (this "wall" now being the wall around the solar crater whose rim is where the Earth's orbit is). Which is good because the Earth-Sun L1 and L2 points are both only about 50km higher from where you are now.

Or you can view everything from a completely non-rotating frame and see that the Moon just gave you a big gravitational assist. And when you get to Earth-Sun L2, the Earth is going to give you one, too, if you've played your cards right.

Except that, once you know where the tubes are, it's no longer a matter of chance. That is, you know where the outgoing tube from Earth-moon L2 is and where the incoming tube for Earth-sun L2 is and thus where they intersect. You then have a bunch of trajectories you can use.

And from Earth-sun L1 or L2, we can similarly go all sorts of other places, Sun-Mars L1, Sun-Mars L2, Sun-Jupiter L1, Jupiter-Ganymede L2, and on, and on. All pairs of co-orbiting bodies in the solar system, sun-planet, planet-moon, etc. each have their own L1 and L2 points guarding the entrances to their respective craters. Since everything is time-reversible in classical mechanics, you have trajectories going both ways, i.e., for every weird spiral trajectory that sends you away from L1 or L2 off to wherever, there's a corresponding one that brings you back in. You can string these trajectories together playing mix and match with them, giving you a way to visit any planet or moon that you like — admittedly, these low-fuel trajectories tend to be really slow, but if you're an unmanned satellite, you don't care.

This is the essence of the Interplanetary Transportation Network.

(which might seem to be a conclusion, but I actually have more to say about rockets in Part 6)

Random update:
I, of course, forgot to mention the really cool part of Farquhar's thesis, which was the proposal that Collins be put in a halo orbit at L2 behind the Moon — which, as noted above, is a measly 1km worth of additional energy/effort beyond my have-him-orbit-L1 plan.

It then so happens you can make the radius big enough so as to remain visible from Earth at all times.

And then we do Far Side landings with no gaps in communication.

wrog: (rockets)

(This is Part 4. The previous installments are Part 1: Another Anniversary, Part 2: Climbing the Wall, Part 3: Rockets Are Stupid )

Improving on Lunar Orbit Rendezvous

Sometimes all it takes is asking the right stupid question. LOR was the result of one such, i.e., "Why do we need to take all of this crap down to the lunar surface?"

Here back in 2013, with the benefit of 20-20 hindsight and 40+ years worth of bored grad students in physics, control theory, and aero-astro engineering picking away at the various issues, yours truly has another one:

Why are we bothering to go into lunar orbit at all?
Why not just leave Michael Collins and the heat shield at L1?

See, in the LOR plan which was ultimately adopted, when the Command/Service Module/LEM combination gets into the vicinity of the moon, the Service Module has to do this burn that puts both it and the LEM into a low lunar orbit about 110km up from the surface. This may not be going all the way to the "bottom" of the 450km well, but in energy terms it's just like going "down" a bit less than half-way to the bottom — just like low Earth orbit is like being half-way down Earth's gravity well — to −290km (recall that L1 is at −170km). We have to kill velocity in order to do that and so there'll be a cost.

On the other hand, leaving the Command Module behind at L1 means the LEM has to travel all the way from L1 down to the lunar surface and back by itself, which is an extra 60,000 kilometers in each direction, probably another day or two of travel time each way. Which, is a hell of a lot more than the few hours it takes to get down from a lunar orbit that's only 110km up. And, for every day you need a few kg of oxygen per person, and likewise for food and water. Clearly, since every last kilogram matters, this is obviously insane, right? Never mind the challenge of getting Armstrong and Aldrin to survive cramped in the LEM for a few days without the mediating influence of Collins; I'm sure they would have killed each other.

But then you notice that they're going to be spending at least that amount of time on the lunar surface anyway (and later missions were significantly longer), the extra food and life-support, in fact, turn out to be a trivial addition to a LEM ascent stage that's already 2½ tons. And, as is the typical pattern, everything pales in comparison to what the fuel cost is going to be.

Running the numbers, we find that the extra ΔV to get us that 60,000km from L1 to low lunar orbit turns out to be roughly a third of what we need to get us the rest of the way down to the surface. It seems that getting down that last 110km is, by far, the hardest part of the trip; recall that we spend 50% of the spacecraft doing it. When we add in the trip from L1 down to 110km, this cost increases to 60%. And, as noted before, the trip back is the same flight path time-reversed, thus with the same ΔVs needed, so it's another 60% getting tossed in order to get us back to L1. Putting that together with the 2 minute hover time at the bottom, and we find we need an extra 7½ tons of fuel for the LEM.

However, since the 30-ton Command/Service-Module is neither having to do a burn to drop into lunar orbit nor having to get back out again; that turns out to save 12 tons of fuel.

… which, doing the subtraction gives us a net of 4½ tons of fuel saved. Which means the overall LEM+CSM combination that we have to launch from earth to L1, originally 45 metric tons, is now reduced in size by 10%. Even if the LEM part of that needs to be quite a bit bigger than before, the Service Module is reduced even more so.

This shouldn't be that surprising since what we're doing is taking the LOR plan to its logical extreme:  Everything we need for the trip back to Earth stays perched in the saddle at L1. We expend zero effort/fuel taking any of it down into the lunar gravity well and back.

But the real bonus appears when we translate this savings back to the launch pad on Earth, where we find ourselves looking at (…drumroll…)

A Saturn V that's ten percent smaller.

This has got to be a win. The accumulated savings over 8 missions are just enough to fly an Apollo 18. Or maybe we could have saved Skylab. Who knows?

What's more, while Armstrong and Aldrin are puttering around on the surface, Collins remains at L1,… stationary between the moon and the Earth. Or we could put him in a halo orbit around L1, that's doable, too.

Which means he stays in contact with both Houston and Tranquility Base at all times. In fact, the only time anybody gets out of contact in this scenario is when the LEM zips behind the moon for its descent and ascent trajectories. This also has to be a win.

It's Unstable. We Are All Going to Die.

Now if Lunar Orbit Rendezvous was difficult to sell to NASA management in 1962, I'm sure my Collins-at-L1 Plan would have been that much harder. "Halo orbits? WTF? How the hell can he just be sitting there?"

It's a fair bet that referring them to Robert Farquhar's 1968 Ph.D thesis would have gotten me a quick trip to a padded cell. But even if I'd managed to avoid that, there'd probably still have been someone in the room who'd actually had the physics course:

"Um,…, isn't L1 unstable?"

Ruh roh.
(also an anachronism; Scooby Doo premiere wasn't until 1969)

Now that sounds like a real objection.

"Unstable". It's a scary word, no question. Evidently, any plan involving L1 means things are going to explode and people will die; that's what you get for using proto-matter (but at least we get Spock back — god, that movie was stupid).

Contrast with L5, which, being "stable", must therefore be a nice, safe place to raise your kids; perfect for a space colony. (Hey, it was good enough for O'Neill.)

And I'm sure this psychology has something to do with why what I'm about to tell you remained overlooked for so long, why L1-L3 were originally dismissed as useless curiosities, and why it took us another two to three decades after 1962 to figure out that this instability is a feature, not a bug.

So what do these words actually mean? Here's the deal:

At L1, all of the various forces cancel out. What you're left with are tides. Tides are weird.

To get a better sense of how tides work, let's consider another situation where gravity gets cancelled out: You're in an elevator and somebody cuts the cable. Elevator is falling freely, you and everything else in the elevator are falling freely, all at the same rate, which you can't actually see because you're inside the elevator. As far as you're concerned, it's as if somebody flipped a magic switch that turned the gravity off, and now you and everyone else in the elevator are just floating there. At some point you'll all go splat but let's not worry about that yet.

Now, as it happens the various hats and hairpieces floating at the top of the elevator are all slightly farther away from the center of the earth, thus aren't getting pulled quite as strongly, and thus, from your point of view will be accelerating (very slightly) upwards, away from you. Likewise, any random shoes at the bottom of the elevator will be closer to the center of the earth, getting pulled on more strongly and thus (again) will be accelerating away from you (downwards).

Similarly, the people to your sides are going to get pulled towards you, the problem this time being that, for them, the center of the earth is in a very slightly different angular direction from where it is for you.

If you need another example, consider the Actual Tides. Here, it's the Earth itself, which you now need to imagine being inside of a Very, Very, Very Extremely Large elevator falling around the sun. Nothing on Earth actually feels the sun's gravity, because we're all in the same orbit, falling together. And yet, the oceans at noon and midnight are getting pulled upwards (outwards, away from the center of the earth), while the oceans at 6am and 6pm getting pushed down (inwards, towards the center of the earth) — that these times tend not to corresponding with high and low tide is only because oceans are big and heavy and take A While to react, but it does explain why high and low tide are six hours apart rather than twelve as you might have expected.

Anyway, at L1, it's the same story, except that you don't even need the elevator anymore, because the gravity is cancelled out for real (sort of).

If you move in any of the "sideways" directions off of the earth-moon axis, the "low tide" force pushes you back towards L1 and then you end up oscillating back and forth through L1. And you can also combine oscillations in the different directions away from the axis any way you want. One such combination gives you a (vaguely) circular orbit in the plane perpendicular to the earth-moon axis, which, viewed from earth, will look like you're following a halo around the moon, hence "halo orbit", even though it's something of an optical illusion, i.e., you're circling L1, not the moon.

If, however, you move "up/down", i.e., towards the earth or the moon, then you get hit by the "high tide" force that not only pulls you farther away from L1, but gets stronger the farther away from L1 you are. Hence, "unstable". That is, if you don't start at exactly the right place, or even if you do, but then get bumped by a perturbation as will inevitably happen, you start moving further away and then pick up speed at an exponential rate.

And if you're off diagonally, then you're affected by both forces at the same time, and thus you will be headed away on this horribly weird spiral trajectory as the high-tide force pulls you farther away while the low-tide force keeps you circling the Earth-moon axis. Remember this, I'll get back to it.

Meaning, that the bad Star Trek dialogue ("Oh no, Riley's shut down the engines! Our orbit is going to decay!") actually applies to orbits around L1. If you care about staying there, you have to do active station keeping, firing your maneuvering thrusters every so often.

But so what? That "exponentially" may sound scary, but the flip side of it is when you're really close to L1 radially, it's exponentially small. Meaning, if you're sufficiently close to L1, it's a matter of remembering to sneeze in the right direction once every few days. The amount of fuel involved is utterly trivial.

To be sure, rockets can fail, just like any other piece of equipment. And I suppose it would have been slightly scary to the folks in 1962 that the orbits in the vicinity of L1 are, shall we say, a bit chaotic. Meaning when it comes time to leave, a slight change in how you leave can make a big difference in where you end up. One wild burn and now you're on a spiral trajectory headed basically anywhere.

Like Jupiter.

Or the Sun.

No, really.

When I say that aforementioned weird spiral can go anywhere, I really mean anywhere.

At this point, your bullshit detector is probably going off. "Um, what happened to conservation of energy? When did we ever get to (earth) escape velocity? In fact, you said that at L1, we're still 170 km down from 'the top', i.e., 170km from being out of the Earth's gravity well. So how the hell are we getting out to Jupiter?"

Fair questions, those. Something is indeed rotten in Denmark and I now have to reveal what I have been lying about glossing over.

The Three-Body Problem and other Danish Zombies a.k.a. The Magic of L1

(to be continued in Part 5)

wrog: (rockets)

(This is Part 3. The previous installments are Part 1: Another Anniversary and Part 2: Climbing the Wall)

The Stupid Thing About Rockets

There are so many tropes about rockets that the SF authors take for granted. You'd think a spaceship is just like your car: you put fuel in, you get so many miles to the gallon, multiply to figure out how far you can go, or equivalently, divide to see how many gallons you'll need.

Rockets don't work that way. At all.

Imagine being stuck in the middle of a perfectly smooth, flat ice pond, so slippery you can't even stand up. With no way to get traction, nothing to push off of, the only way you can actually get yourself moving somewhere is to throw something away in the opposite direction.

And, as luck would have it, the bastard who put you there also left you with a large suitcase filled with baseballs. And fortunately, while you might not be a major league pitcher, you still have a pretty good throwing arm. So you throw a baseball, and now you're moving; throw another one and you're moving faster.

This is what a rocket is. Firing your rocket always means throwing away part of your spacecraft. Never forget this. Physics doesn't care how big or bright the flame out the back is. What matters is how much junk you're throwing and how fast you're throwing it.

If this sounds like a completely absurd and stupid way to move around, that's because it is. Constantly cannibalizing your own ship is the absolute worst way to travel. We use rockets because, much of the time, there is no alternative, and, given the fundamental principles involved, there's reason to believe that, outside of various special situations, there never will be.

But if you're going to travel this way, there are things you need to know:

  • You want to be throwing each baseball as fast as you possibly can,
    because once it's thrown it's gone forever. You can't retrieve it, since turning around and going back to retrieve it defeats the very purpose of throwing it in the first place. So you have to make each ball count for everything it's worth. Once you run out of baseballs, you're screwed, unless you want to start throwing clothes, limbs, or vital organs, but I can pretty much guarantee that's not going to end well.

  • You can rest as much as you want between throws.
    The ice is perfectly smooth so once you're moving, you stay moving. You keep the velocity you've earned while you're resting up to throw the next baseball. In this case, Conservation of Momentum is your friend. And since space is really, really, really big, you'll generally have all the time in the world to perform your maneuvers. To be sure, timing is everything, but that just means you have to plan ahead, i.e., start throwing earlier.

  • In space, your destinations are not places but rather trajectories (orbits).
    Once you're on a particular trajectory, you stay there forever and it costs you nothing. It's only when you want to change trajectories that you have to do anything, at which point there will be a specific velocity change ΔV you need to achieve, and it really doesn't matter how you do it.

Putting all of this together, we find that, once you've tuned your rocket engine so that it's always throwing stuff as fast as it possibly can, a velocity change ΔV of any particular magnitude always costs you the same percentage of your ship — thank you, Konstantin Tsiolkovsky — no matter how many engines you have running, no matter what your throttle settings are, i.e., no matter how much you're resting between throws.

To put some numbers on it, imagine that your best fastball happens to be 30 meters per second — not quite Randy Johnson Territory but close enough — and you want to gain (or lose), say, 20 meters per second. Then you need to keep throwing until roughly half of your original mass remains (well, okay, e-20/30≈0.51 of it, if you must know). Or, equivalently, that suitcase of baseballs needed to be at least as big/massive as you are. If, after that, you want to pick up another 20 m/s, you need to be able to toss half of your mass again. And if you can manage it a third time, then you'll be going 60 m/s faster than when you started, but you'll only have 1/8 of your original mass left.

Which meant you had to have started with a suitcase of baseballs that's seven (7) times as massive as you are. And now it's gone. Let's hope you're headed in the right direction.

Notice the exponential growth in reverse.

Moreover, with each maneuver tossing all but some percentage of your ship, if you have multiple maneuvers, you have to multiply those percentages to figure out your total cost. It's not like you can just add the gasoline costs for each leg of the trip.

This is where Conservation of Momentum stops being your friend and how rocket travel is fundamentally different and will never be like driving your car.

Bottom line is, once you know your engine technology (fastball velocity) and your flight plan (sum of all of the ΔV's you need to do), you'll know your fuel cost and it'll be a multiplier that is exponential in the total ΔV you need to do. That is, you take your payload, multiply by this number, and that's how big a ship you need to start with, assuming you can manage it so that everything minus your payload is fuel.

And if that multiplier is very large, then a small change in your payload at the end of the trip can make a big difference in what you need at the start.

The only way to reduce the fraction of your ship you have to toss for a given ΔV is to get a better engine that has a higher exhaust velocity. But whatever engine you install, chances are that's what you'll be stuck with for the rest of your trip.

Nor does refueling work the way you think it would. If the new fuel isn't already travelling at the same velocity you are, then collecting it is going to change your course. To avoid that and get it matching your velocity, if it was launched from the same place you were —the only choice in 1969 and also for the forseeable future until we can, say, start harvesting comets or put a hydrazine refinery on Titan—it's going to have performed a set of maneuvers similar to what you've already done, which means it most likely expended the same percentage of itself catching up with you.

Which means you've saved nothing at all by not bringing that fuel with you in the first place.

Which means that Earth Orbit Rendezvous is completely pointless, at least as far as saving fuel is concerned; it just doesn't. In fact, chances are, it uses more because you have all of this duplicated engine+fuel-tank stuff getting boosted into low Earth orbit, whereas a single humongous rocket could have significant economies of scale once you figure out how to build it.

If you really care about saving fuel, what you need to do is either reduce your payload or come up with a better flight plan, or both.

How Lunar Orbit Rendezvous (LOR) Wins

What the LOR advocates noticed is that there's a heat shield, fuel, air, and other consumables needed for the trip back to Earth, that are not being used for the trip down to the lunar surface. If there were a way to just leave all of that crap behind in lunar orbit, i.e., take down a separate Lunar Excursion Module (LEM) that holds only what you're going to need on the surface, then bring back only what you need to bring back, and finally rejoin the stuff you left behind in orbit -- hence the name for this plan: Lunar Orbit Rendezvous (duh) -- you would save tons of fuel, literally.

How much? Well consider that in the actual Apollo 11 mission, the LEM was 15 metric tons (N.B., all tons are metric from now on).

  • Descent stage was 10 tons, 8 of it of fuel.
  • The ascent stage was 5 tons, half of it fuel.

They also wanted enough fuel to be able to hover for 2 minutes before landing; that was the safety margin. And for Apollo 11, they ended up using every last bit of it to get to a new landing site when the original site turned out, upon closer examination, to be hosting its Annual Large Irregular Boulder Convention that week and was thus slightly less than ideal.

So,... 7 tons hovering for 2 minutes in lunar gravity works out to 500kg of fuel, so the rest of the descent stage fuel, 7½ tons, was for getting down from orbit. Meaning whatever the total ΔV was for getting down from lunar orbit, it cost 50% of the ship (started out as 15 tons, remember). And getting back up evidently cost 50%, too. Actually this is what you'd expect, since one trajectory is a time-reversal of the other, so the ΔV's are all the same and therefore so is the total fuel cost, percentagewise.

How does this change if we try to bring everything down with us?

The Command/Service Module that stayed behind in lunar orbit starts out as 30 tons, but 18 of it is fuel, 13 of which gets spent getting us into lunar orbit. Which means we have 17 tons left, 5 of it fuel for getting back to Earth. And then we work backwards from there:

Lunar Orbit RendezvousDirect Flight
2½ ton empty LEM ascent stage
reaches lunar orbit;
astronauts with moonrocks
crawl back into 17 ton CSM
17 tons of CSM
returns to lunar orbit
÷ (1/2) mass reduction getting to lunar orbit from the surface
5 tons of LEM ascent stage lifts off34 tons of CSM lifts off
leaves behind 2 ton empty LEM descent stage
7 tons of LEM lands36 tons of CSM lands
÷ (14/15) mass reduction hovering for 2 minutes
7½ tons of LEM after descent38½ tons of CSM after descent
÷ (1/2) mass reduction descending from lunar orbit
15 tons of LEM separates from77 tons of CSM enters lunar orbit
17 tons of CSM
32 tons of LEM+CSM enters lunar orbit
÷ (32/45) mass reduction getting into lunar orbit
45 tons of LEM+CSM fully loaded108½ tons of CSM fully loaded

And everything from here on back to the launch pad on Earth is correspondingly bigger.

Which means that for Direct Flight we need a rocket more than twice the size of the Saturn V. And this was all being generous in assuming that, e.g., there was nothing in the LEM ascent stage that wasn't already duplicated in the Command Module and that the 2 ton empty LEM descent stage would not need to be correspondingly bigger.

And even if we split the Supersize-Saturn into two or three rockets as per the Earth-Orbit Rendezvous plan, it's still the same multiplier for each rocket to get into orbit and to get all of that material to the moon. That is, even if it's rockets we can actually build, we're still not saving any fuel. Ultimately, if the overall budget stays the same, instead of 8 moon missions (Apollos 10-17), we only get 3 at best. Meaning Apollo 12 is the last one and we wouldn't have been able to spare Apollo 10 for a dress rehearsal (with possibly disastrous results).

I suppose it's a measure of how much a bureaucracy NASA was even back then that it still took at least a year of lobbying by the LOR proponents to get NASA management to actually accept the math on this.

Never mind that there are better flight plans out there. Which brings us to…

How I Would Have Done It.

(to be continued in Part 4)

wrog: (rockets)

(continued from Part 1, introducing the 1961-62 NASA debate on how to get to the moon, which you might want to read first)

Climbing the Wall

I don't know who first got the idea to picture the Earth's gravity well as this huge funnel, with the Earth at the bottom and the moon and various other satellites as ball bearings rolling or sliding around the top. I'd draw it but you've seen it already in every science museum on the planet. For all I know, Newton may well have had it in his Principia even if they hadn't quite figured out how to make ball bearings at that point.

What's annoying is just how deep the hole in the middle is, and this number I first heard from either Arthur C. Clarke or Gerard O'Neill:

Getting out of the earth's gravity well takes the same amount of energy as climbing a wall 6,000 kilometers high (i.e., if you had to climb the whole way against earth's surface gravity).

O'Neill's point was pretty simple: Why would you ever want to live at the bottom of a hole? Let's build space colonies!

Unfortunately, my point is a little more subtle, so we need some more numbers.

The energy you need just to get to low earth orbit is like climbing the first 3000km, half way out. Even though you've only gained a few hundred kilometers in real altitude, it's a huge accomplishment to go from standing still on the surface to going fast enough to stay in orbit. And it's useful enough to get to a place outside most of the atmosphere, where you have time to think about what you want to do next. But you still have at least another 2000km of wall to climb before you can get anywhere useful…

Like, say, geosynchronous orbit, where most of the communication satellites live — which is already much farther away than people give it credit for. At this point you're a bit more than a tenth of the way to the moon and about 500km from "the top" of the wall, though by that point the funnel has flared out pretty far so that you're actually going 50km outward for every one that you're going "up" (yay inverse square law...). Meaning instead of climbing El Capitan, we're now doing the leisurely stroll from the house to the supermarket — in my case this happens to be a fifty foot elevation gain over half a mile that I'll hopefully still be able to do when I'm 70.

Now as it happens, since our goal is just to get to the moon, we don't need to get all of the way out of the hole. The moon itself isn't all the way out; it's still in orbit around the Earth, see. But it's most of the way out.

Continuing outward from geosynchronous orbit towards the moon, the "wall" continues to flatten out until finally, when you get about 5/6 of the way there, it flattens out completely. You're now just 170km from "the top", in this saddle point where, to either side of you, the wall continues to rise, but in front of you it drops off and you're staring at another big hole with the Moon at the bottom.

Welcome to L1, the first of the Lagrange Points, the five magical places in the Earth-moon neighborhood where moon gravity, earth gravity, and centrifugal force all cancel each other. Put a ball bearing here in exactly the right place and, if it could be undisturbed by perturbations from the sun and the other planets, it would just stay there forever, i.e., orbiting the earth once a month exactly in synch with the moon.

And I really do mean magical, here. Forget Stonehenge, the Bermuda Triangle, or even Disneyland; they've got nothing on L1, as we'll see.

So now we're staring down into this second hole. To be sure, it's not anywhere near as deep, only 450km down to get to the lunar surface, child's play after having come this far. But it's still deep enough to inspire the Lunar Orbit Rendezvous (LOR) people to ask this stupid question:

"Why the hell are we taking everything with us down this 450km hole and back out again?"

Keep in mind that not only do you have to reach the bottom, but you want to be standing still when you get there (so as not to make a fresh crater), which means burning off all of the velocity you accumulate as you fall into the hole.

Which you have to do with rockets because there's no atmosphere.

And then, of course, you have to add all of this velocity back in order to get yourself out of there.

Which gets us to

The Stupid Thing About Rockets

(to be continued in Part 3)
wrog: (rockets)

Another Anniversary

(... something that's been brewing over the past month; this is going to be Part 1 of n...)

Among other things, I've been reading up on the Interplanetary Transportation Network,

but I was also reminded that last month was the 45th anniversary of the Apollo 7 launch, which in itself wasn't much — fly a Saturn 1B and Command/Service Module into low earth orbit and splash down again just to make sure the basic system works. It was mainly notable for being the first manned flight after the Apollo 1 disaster killed Grissom, White, and Chaffee, which resulted in everything at NASA being grounded for a year while they figured out what they did wrong...

Which I knew nothing about at the time because I was seven years old, as old as William is now. For me, Apollo 7 was an introduction to whole idea that we even had a space program. It started as a stupid little "Hey look, we launched something!" article in the Weekly Reader that was maybe a paragraph long and had pictures of astronauts. Sometime later that year they showed the Disney "Man in Space" series in class, by which point I was vacuuming up all kinds of colorful books on space exploration.

By then we were maybe a year or two away from an actual moon landing. It was a big deal for everyone.

What amazes me now is how much we didn't know.

Take orbital mechanics, the study of how things move in space (or everywhere, really). As it's covered in the physics curriculum, you'd think it was a dead subject. Isaac Newton, Joseph-Louis Lagrange, and William Rowan Hamilton had everything we needed to know worked out by 150 years ago, and then Physics moved on to more exciting topics (electricity! magnetism! relativity! quantum mechanics! quantum electrodynamics! quantum chromodynamics! string theoryloop quantum gravity? hell if I know what's next …)?

Classical Mechanics? Been there, done that. Boring?

Guess again.

Granted, I'd already had some inkling of this, what with one of my friends in grad school being a Control Theory student who burst out laughing at the thought that there wasn't anything more to learn about mechanics. And to be fair, they didn't have computers 150 years ago, nor did they know what we know now about numerical analysis or non-linear differential equations. Never mind the general Playing Around With Numbers that you just couldn't do even 40 years ago. And now that people are actually shooting crap into space and needing it to go to particular places, there's a bit more than just abstract interest, now.

So, to take an example,…

Remember how in the late 1970s there was this serendipitous lineup of the outer planets -- Jupiter, Saturn, Uranus, Neptune, all in a nice row so that if we launched something Just Right, even with very little fuel it could go bing-bing-bing-bing, each planet doing a gravitational assist to boost the probe to the next, and so we get this really cheap odyssey that visits them all? Obviously this was a golden opportunity since it would be hundreds of years before we'd get that kind of lineup again. And so we launched Pioneer 10+11 and then Voyagers 1+2 and got back all of those nice pictures.

Turns out,… that "golden opportunity"? Total lie.

Not only can we can do this any time we want, but if we'd known about this back in the 1970s, we could not only have saved a bit of fuel but also done it in such a way that, instead of being stuck with single flyby for each planet, the probe could instead have been arranged to loop around each one as many times as we wanted before going on to the next.

But before I get into how the Interplanetary Transportation Network works, let's start with something much simpler that I'm pretty sure we'd have done differently had we known what we know now:

The Apollo Debate

In the early 1960s, shortly after John F. Kennedy issued his famous challenge, there was a huge debate about the best/cheapest way to actually get somebody to the moon.

Calculating what it takes to launch from Earth something big enough to hold a few astronauts, land it on the moon, and bring it back—this being the "Direct Flight" scenario—you find out that you need this insane, huge-ass rocket, something like two or three times the size of the Saturn V that was eventually built, something that maybe we'd be able to do by 1975 or 1980 (cue maniacal laughter from The Future), but if the goal is to get to the moon by 1970, we'd have to come up with Some Other Plan.

So they focused on what they could do, which is build smaller rockets. You put the astronauts on one of them, and have the rest carry spare fuel tanks, have them meet in low earth orbit, bolt everything together, and then send that to the moon (and back). Obvious, really. This, the "Earth-Orbit Rendezvous" (EOR) scenario, became NASA's game plan. Wernher von Braun gave his blessing and we were off to the races.

But then there was this annoying group that had this other, completely bizarre idea: "Lunar Orbit Rendezvous" (LOR), they called it.

Keep in mind that at this point, we hadn't rendezvoused anything yet in space, so nobody had any idea how hard EOR might be. Think about how you might go about catching up with a meteor. It's going thousands of meters per second and your job is to match it's velocity. And now we're supposed to be doing this in lunar orbit, instead? WTFF?

And they just would not shut up and get with the program.

It's weird to me now, remembering all of those colorful books with illustrations of all the possible ways to get to the moon. They actually mentioned this debate, even if they didn't do a very good job explaining well what the actual pros and cons were.

Or maybe they did, and it just whooshed over my head because I was seven years old and hadn't had any actual physics, yet, and anyway, hey, look, rockets!

But now that I have, it's bloody obvious. In fact, it's so obvious it's a bit appalling to me that NASA had to spend an entire year figuring this out:

Climbing the Wall

(to be continued in Part 2)

wrog: (toyz)
I guess he is president of the university now...

but woo, look! I get quoted! (it's about 2/3 of the way down) and I wasn't saying something completely stupid and embarrassing. There's hope for me yet.

I think the reporter was slightly annoyed that neither I nor anybody else could offer up any good skeletons. (Some people just don't have them, sorry...)


Oh, and that "freshman-year physics course" that he got a C in (that gets mentioned twice in the article)? I had to laugh because there's a somewhat important detail that got left out:

Physics 206 was the spring-term sophomore-year advanced track Classical Electrodynamics course...

...in which the Princeton Physics Department takes its last opportunity to ask prospective majors, "Are you sure you want to do this?", and then goes absolute balls-out dialing the fire-hose up to 11 to see who survives.

And the two of us took this class as freshmen. Insane much? Yeah.
(File under things you can do when you have the metric crapload of AP credit.)

It was brutal.

In other words, this is the kind of "C" that you take home, frame, and put on your wall, even if nobody viewing the transcript later on will ever have any clue about this.

(... well okay, in my case it was a B+, but you get the idea...)
wrog: (howitzer)
After Wm's swimming lesson today at the community Pool, when we were in the locker room getting him back into his clothes, I remembered [livejournal.com profile] emmacrew telling me about this wonderful little centrifuge device they had there, basically like a mini-washer that just does the spin cycle. You put bathing suit and towel in, and some small number of seconds later they're almost completely dry.

So here I was with sopping wet swimsuit and towel looking around for this thing and not finding it, so I ask.
Staffguy:  "Oh, um, we only have those in the women's locker room."

MeWTF?

Staffguy:  "If we put one in on the men's side, we're worried someone'll put a milkshake in it or something. You know how boys are."

Me:  "Because girls will never do that sort of thing."

Staffguy[shrug]
I think I need to learn how to speak with a more obvious verbal-irony font.

(Cue discussion on how this is exactly like being propositioned by creepy dude in the elevator at 3am at <pick-your-favorite-sfcon>)
wrog: (howitzer)
Ancient cultures didn't have cavalry as we know it. The stirrup, that stupid little strip of leather that hangs down from the saddle that you put your foot in, is a far more recent invention than you might have thought. And it makes a huge difference. Once you have it, your legs are no longer devoted to clinging to the horse, you have better control over the animal, and you can stand up and Do Stuff, like, say, carry a lance or fire a bow. It also took a long time to figure out the right way to do reins, too. Without any of that, it's a struggle just to stay on for any length of time and get the animal to move in the direction you want.

Which is why, if we're talking about any time prior to, say, 500 B.C., horses are for pulling things, period. But that's okay. If you can come up with something useful for them to pull, that, too, can have an impact.

All you need is the right idea at the right time and you change the world.

Somewhere around 2000 B.C., someone in central Asia gets such an idea: a spoked wheel. Among other things, this allows for construction of a small, lightweight chariot that fits two people. One guy drives, the other guy has a bow, leaving just enough room for a reasonable supply of arrows. Lightweight means it can move really fast if you need it to.

To the peoples of the Bronze Age, this is basically a humvee with machine gun mounted on it.

If you're on foot, having to fight this thing, you've got a problem. Maybe you can get close enough to it to get a spear thrust in, but then the driver fires up the horses, it moves, sets up shop fifty yards away, and continues shooting at you until you're dead.

Sucks to be you.

By 1700 BC, the idea works its way south through the mountains of the Caucuses and Persia. This takes a while since chariots don't work so well in mountains, so their utility isn't immediately obvious. But once it reaches the flat-lands of Mesopotamia and the eastern Mediterranean, it spreads like wildfire. The Hittites pick up the idea and run with it, building an empire that covers most of Anatolia (modern Turkey). Farther down the Euphrates, to keep from being overrun, the Assyrians have to learn it too, as do the Babylonians, the Egyptians, the Minoans that ruled Crete, and, basically, everybody else.

Because that's the way of military technology; you either learn it or you get conquered.

And for the next 500 years, chariots are the standard for how you fight wars. Maintain a small, elite chariot corps. You don't actually need that many: Egypt's army was the biggest and they got by with a few thousand. Most of the smaller city-states had numbers in the hundreds (we have the Linear-B archives from the palaces at Knossos, Mycenae, Pylos and a dozen other, archives strangely devoted to inventories of chariot parts and horses, because apparently that was what mattered).

Granted, every so often you'll have to deal with barbarians living in the hills where the chariots can't go. But that's no problem: You hire infantry mercenaries, generally Other Barbarians from Elsewhere, who you can send to deliver your local hill people a bloody nose so that they think twice about messing with you again any time soon -- and, of course, if said hill people dare to come out onto the plains, you can have chariots ready and waiting to deal with them more directly.

The neat thing about small, professional armies is they free up the rest of your civilization to do Other Stuff. Not having to expend huge resources on defense means civilization flourishes in the late Bronze Age. Yes, your ships are going to get attacked by pirates every so often, or maybe the big empires will occasionally come up with some reason to go at each other, but apart from that times are relatively peaceful. At Pylos (southern Greece) and Knossos (Crete) the palace people feel so secure, they don't even bother to build walls.

And then we get to 1200 BC. Otherwise known in archaeological circles as The Bronze Age Collapse, or more simply, The Catastrophe.

In the space of about 50 years, pretty much every city in southern Greece, Crete, Cyprus, Anatolia, and the Levant, is destroyed by fire.

The Hittite Empire is erased from the map and nothing replaces them. Anatolia doesn't again see that standard of living until the 2nd century A.D. when the Roman emperors finally get their act together and decide maybe they ought to try governing the provinces properly.

Mycenaean Greece likewise disappears; the citadels of Mycenae and Pylos themselves, the homes of Agamemnon and Nestor according to Homer's Iliad, are buried and don't see the light of day until 19th century archaeologists find them again.

Egypt gets lucky. A change of dynasty at just the right time produces a young, energetic pharoah, Ramesses III, who can think out of the box. And so they survive by the skin of their teeth.

For different reasons, Assyria also manages to survive, and thus the Catastrophe, whatever it was, doesn't reach beyond them to Babylon or India.

But everywhere else in the eastern Mediterranean, the lights go out and stay out for centuries. It's a dark age every bit as deep and as long as what happened in Western Europe after the collapse of the Western Roman Empire 1500 years later.

Except that for the post-Roman dark age in Europe, you still have the odd monastery here and there where, in between copyings of the Bible, some monk manages to jot down a sentence or two about what was happening around them in the present day, and occasionally those particular pages of his diary would manage to survive when the place later got torched by Vikings.

And so it is that, in the century or two after the Romans leave Britain, we can have the writings of Gildas and Nennius, containing tantalizing hints of a post-Roman duke who rallies the Roman and Celtic refugees of south Britain to take a stand against the invading Saxons. It's very unlikely that this man styled himself High King of all Britain. It's also a fair bet there was no Round Table in his castle, assuming he even had a castle, since this was Before Castles (though it's a fair bet he had a home base of some kind, since there was no shortage of abandoned Roman forts to occupy or steal building materials from). His name probably wasn't Arthur.

But you can get a sense of where the legend might have originated, even if the tale-spinners centuries later, be it Geoffrey of Monmouth or Thomas Malory, never let the facts get in the way of a good story -- never mind that they probably knew even less of the facts than we do now, given that archaeology hadn't been invented yet. And so they anachronistically imposed concepts from their own time (plate mail, castles, chivalry, and jousting tournaments) and adding other embellishments (e.g., everything having to do with Merlin) without even thinking about it.

For the Greek Dark age, 1500 years earlier, there is no Gildas. Whether the palace scribes trained in Linear-B (the written version of Mycenaean Greek) were killed immediately or sold off as slaves doesn't matter a whole lot. What matters is they didn't pass on their knowledge. There is nobody to keep records; the very idea of Writing Stuff Down just ENDS.

The last written records we have of the Catastrophe outside of Egypt are the tablets recovered from palace rubble whether in Linear-B or Hittite script. At the palace of Urgarit in Syria, tablets were still baking in the furnace at the time of the attack and never retrieved, various bits of correspondence that never made it out the door:
  • So, um, this place is getting kind of hard to defend,
    what with most of our chariots being away defending Hattusas.

  • Um, hello again.
    100 ships would be REALLY FUCKING USEFUL right about now.
    Just saying.
There are no clues as to who was attacking; they themselves apparently had no idea. And, suffice it to say, help never arrived.

Beyond that, we have only the oral tradition, the huge mass of Greek myths we learned about in grade school: The Trojan War, Jason and the Argonauts, Perseus and Andromeda, Theseus and the Minotaur playing tag in the Labyrinth underneath the palace of Minos, King of Crete.

Somewhere around 400 years after the Catastrophe, someone in Greece, inspired by the Phoenecians, comes up with a new 24-letter alphabet, and written history picks up again. Homer's Iliad is finally committed to papyrus, thence becoming THE oldest piece of Western literature we have. Over the next few hundred years we have the Greeks of the Classical period (Herodotus, Socrates, Plato, etc...) trying to piece some kind of history together out of all of the random scraps that have been handed down to them, undoubtedly having to do no small amount of Making Shit Up to fill in the gaps just as Geoffrey of Monmouth ended up doing for the early history of England 1500 years later (wherein we get Uther Pendragon and Arthur listed at the beginning of an unbroken line of English Kings).

And while we could dismiss all of the Greek myths as bullshit, there are random threads that appear to pan out, scraps of knowledge that really do seem to have been preserved from 1200 BC. The palace at Knossos on Crete really does have a Rather Complicated Basement. The city unearthed at Mycenae may not actually have been ruled by anyone named Agamemnon, but, if you squint, the gate does look kind of like it has a lion on it.

And on a site that the Romans called Ilium, there's a mound with evidence of a city destroyed by fire at about the right time. In Hittite correspondence, it's called Willusa and was evidently part of a confederation of allied cities, guarding the northwest frontier of their Empire, ruled by a prince named Alaksandu (Alexander/Paris being the son of Priam in the Iliad). It sat on the Bosporus, guarding the passage between the Aegean and the Black Sea; any ships passing between Egypt and Hattusas, the Hittite capital, would have to go through there.

There are any number of scenarios in which one could imagine the Mycenaean Greeks having a motive for taking it down.

In any case, this city, now widely believed to be Troy, was one of the first to burn, probably around 1225 BC.

As for the actual causes of the Catastrophe, there have been lots of theories and Robert Drewes in The End of the Bronze Age (yes, I read a book; try not to faint), demolishes them one by one in the course of advancing his own (that I'm vaguely regurgitating here, ... surprise), which historians and archaeologists are allowed to do:
  • Volcanic eruption (Thera is usually blamed), earthquakes, drought, or some other natural disaster, never mind that whole region is fairly geologically active and other civilizations always managed to survive the wiping of an odd city or two (Rome went on just fine after Pompeii was buried), never mind that whatever THIS natural disaster was, it somehow specifically targets every major settlement in the eastern Mediterranean and in nearly all cases left time for the inhabitants to get out leaving very few skeletons behind in the ruins (slightly unlike Pompeii). Natural disaster. Sure.

  • The advent of iron weapons was a popular explanation, until it was noticed that there weren't any to be found in the destruction layers and better dating revealed that iron didn't really come into use until a couple centuries later.

  • Mysterious "Sea Peoples" embarking on massive journeys turn out, under closer examination, to be fantasies of a 19th-century archeologist giving a really strange reading to Egyptian texts in order to get them to reconcile with accounts in Herodotus and the Bible (which, of course, HAD to be correct). Same goes for the "Dorian Invasion". The main problem is you'd expect migrating peoples to conquer and move in rather than just burn the place. And when you try to figure out where they came from and it turns out they're actually from fairly close by, perhaps none other than the barbarian hill people who'd already been there for hundreds of years, that the palace folks dismissed because they were never a threat...
... until they were.

Something changed, but what?

At this point you're probably guessing it has something to do with the chariots.

In short, somebody got Another Idea to change the world. But this idea was completely insane:
Chariots can be defeated.
Never mind that they've reigned supreme on the battlefield for the last 500 years. Never mind that nobody you know who's gone up against them lived to tell about it. Never mind that you'd have to be a complete idiot to send infantry against them. It can be done.

All you need is slightly better armor, so that the bowman doesn't get you right away. Something that protects your torso while leaving the legs free so that you can still run quickly.

That plus your very own lightweight round shield; doesn't have to be very big because you'll have two guys standing on either side of you and they'll ALSO have shields. Just stay in formation and you'll be fine.

And that stupid three-foot lance that you thought was only good for hunting rabbits actually makes a damn fine projectile weapon. Having a projectile weapon means you don't actually have to get that close to what you're fighting.

Granted, you certainly can't throw the lance as hard as a bow can fire an arrow. And it's small so it's not going to do anywhere near as much damage as a proper lance would. And it's also true that you'll only get one shot, at least until you can manage to retrieve it from wherever you threw it.

Well, all right, I'll admit, the short lance IS a pretty stupid weapon. But, if nothing else, it's at least easy to make, never mind that everybody in your tribe already has one. Give me that much.

And, here's the thing:
You're fighting a chariot. All you have to do is wound one of the horses and it's Game Over.
No, really. What happens to a chariot with a wounded, screaming horse? It just spins around in a circle for a bit and then falls over. At which point it's just Two Guys on the Ground, both wearing armor that's not very well designed for running away.

Sucks to be them, you might say.

Also?

If there are 10,000 of you and only 500 of them, I'm going to guess at least one of these stupid lances will get through. Call it a hunch.

Oh, and bonus! We've got a new kind of sword, too. It has an edge that cuts things, so that you can slash from side to side as well as thrust.

Somebody in northern Greece -- for lack of an actual name, we'll just call him "Odysseus" -- puts all of the pieces together:

"Hey, let's go knock over Troy."
"Are you fucking kidding me?"
"Seriously. I did a mercenary gig there a few years back. I've been inside the palace. Metric craploads of gold. And the women! They've got maybe 200 chariot crews, tops. We can take them."

And they did.

It's hard to imagine the Mycenaean Greeks in the south having much to contribute to this enterprise. If they'd known at the time, they'd probably have been VERY disturbed by the details of just how it was done.

But there was no Internet back then. Any survivors escaping from Troy would flee eastward to Hattusas. It was probably enough to the south-Greeks to know that Troy had fallen. They could still celebrate, even if details were sketchy as to who actually pulled it off and how. It would have been an easy assumption that one of the palaces, probably Mycenae itself, had their hand in it, even if nobody was talking.

Or maybe Agamemnon just outright took credit for it. (We *know* Ramesses III had no problem taking credit for stuff HE didn't do; historical integrity clearly takes a back seat to maintaining the prestige of your throne and kingdom). And he's believed because of course there's no fucking way those stupid hill people did this by themselves.

Fifty years later, after all of the palaces in south Greece have been destroyed and the older generation is pushing up daisies, the fall of Troy is remembered as the Last Great Victory, and, over time, all of Greece comes to identify with it. The aftermath is also remembered; the heroes don't make it home because their homes have been destroyed. The conclusion in the south that they'd all been cursed by the gods would have been inescapable.

Over the next 400 years, the story mutates. Unless Priam or Alaksandu kept a diary and we can find it, the details are likely gone forever. Homer tries to fill them in using what he knows of warfare in his day, where now everything is conducted on foot, massed infantry being the new standard of warfare.

But we'll throw in lots of duelling heroes from all parts of Greece, because the crowd eats that stuff up. Especially when one of the heroes is from their own town; they cheer when the troubador gets to that part. The more places you can tell the story and get cheers (and extra coins and extra wine and whatever else), the better. Hence the Iliad's all-important catalogue of ships naming practically every town in Greece.

There is a memory that chariots were involved, but no idea how they were actually used. Achilles leaves his tent, hops into the chariot, rides the half-mile to get to the front, hops out, and *then* picks up his sword. Almost like that scene in L.A. Story where Steve Martin gets into his car and drives 50 feet to get to the house next door. Makes no damn sense.

There is also a memory that the Trojans had a huge city wall, so obviously there must have been a siege. Over time, the wall gets bigger and the siege gets longer. It's telling that there are no stories from the first nine years of the war (the Iliad itself picks up partway into Year Ten); they're all just sitting there sieging, or something. Anyway, that part's boring, so who cares?

That Troy's only defense might have been a small chariot force that was eliminated in single afternoon would have seemed patently absurd. But the cleverness is remembered. They knew it wasn't simply about wearing them down in a siege. There was some trick involved. And it had something to do with horses.

With respect to how the legend developed, we'll probably never have any real information, so the possibilities for speculation are endless.

What we do know is that, sometime after the fall of Troy, Meryre, the king of Libya, sets his eye on some choice real-estate in the Nile delta. The great pharoah Ramesses II of Egypt is dead after ruling for 70-some-odd years, and his untried son Merenptah is in charge, and so it's time to invade.

One small problem: Meryre doesn't have very many chariots.

But somehow he has a sense that this isn't necessarily a problem. Somehow, he knows to recruit mercenaries from all over the Mediterranean: Sicily, Sardinia, south Italy, northern Greece. Somehow, he knows that if he assembles an army of barbarians who know how to use the hunting lance and the new swords, and makes it big enough, those chariots won't matter anymore.

It might have been a coincidence that fully half of Meryre's recruits were from northern Greece (we know this because we have the casualty figures from Merenptah's victory inscription).

Perhaps the Greeks who sacked Troy indeed took their time about going home, NOT because Poseidon hated them, but because there's not much point to going home when "home" is just a pile of rocks on a hillside in northern Greece and there's much bigger game to be had out there.

Why work for Pharoah for a few coins when you can take home Pharoah's entire treasury?

But whether or not Odysseus himself actually makes it to Libya to plant a bug in Meryre's ear doesn't matter. The idea gets there somehow. Once it's known to work, as was demonstrated at Troy, it spreads, and anybody can use it,
. . . there being nobody to enforce business-method patents in the Late Bronze Age.

Meryre's assault fails, whether because he doesn't hit on quite the right combination of tactics, or he doesn't listen fully to what his north-Greek friends were telling him, or his army just isn't quite big enough, who knows?

But he evidently comes awfully damn close, and the mercenaries who survive know it. Meaning when they finally do go home, it's with further experience that they can apply against much smaller, easier targets in southern Greece, and Anatolia, or wherever else they feel like going.

20 years later, once the rest of the eastern Mediterranean had been finished off, the Egyptians are the only ones left standing, the Libyans decide it's time to try again. Meanwhile over on their eastern front, the Caananite palaces at Hazor, etc... have all been burned by yet more annoying hill people, who themselves decide it's time to take down the Big Bad.

Fortunately for Egypt, Ramesses III is the start of a new dynasty. In other words, he's had to actually work his way up, probably leaving behind a long trail of bodies.

And he's been paying attention, or at least is awake enough to notice that all of Egypt's trading partners to the north have gone radio silent and that Egypt itself is likely to have a huge target painted on its back. And at least one of his advisors reads up on what happened with his predecessor Merenptah, so he knows he had better NOT rely on the chariots to save his ass this time.

Luckily, here in Egypt, we have lots and lots of people. So if it's a question of training foot-soldiers, we could actually think about doing just that. And even if the chariots are now useless, there are still lots of trained bowmen left over, there ought to be something we can use them for.

Hmm. Ships coming in. Hey, here's an idea: let's pump those bastards full of arrows BEFORE they can reach the shore; then we don't have to fight them on land. Genius.

Ultimately, Ramesses III wins two great victories, one in the east and one in the west. The Libyans don't bother them again for a very long time. Likewise for the Phillistines and the Israelite hill people to the east,...

... except that, for some reason, the eastern battle is followed by a strategic withdrawal. The royal road through Palestine, the key land route that used to link Egypt with the Hittites and Mesopotamia, an area that had been under Egyptian rule for centuries, is now abandoned and left to fend for itself, apparently now too hot to handle. Never again does Egypt reach this far. There's no further attempt to retaliate for, let alone take back, the palaces of Caanan and Syria that have burned.

It's almost as if those annoying Israelite hill people actually won this one and Ramesses just doesn't want to admit it.

Also interesting to me is how Exodus apparently gets things backwards. We have yet to find any evidence at all that the Israelites were ever in Egypt proper in that era, whereas the evidence that the Egyptians ruled Palestine in the centuries leading up to 1200 B.C. is pretty much irrefutable. Apparently, the Israelites didn't so much escape from Egypt as Egypt escaped from them.

As with the Iliad or the stories of King Arthur, trying to extract the actual history of that long ago from the Hebrew Tanakh — what the Christians call the Old Testament — is something of a fool's game. Oral tradition sucks, sometimes.

And yet, the earlier parts of the Hebrew Bible (Exodus, Joshua, etc.) are chock full of tales of Israelite bands massing and defeating chariot armies. Combined with the archeological evidence that, at least in this part of the world, chariots mostly fall out of military use once we get past 1200 B.C. — which, I suppose, shouldn't be much of a surprise at this point — you get a rather strong sense that these tales, which could not have been written down any earlier than the seventh century B.C are pretty damned old, and, like the Iliad, contain scraps of truth.

(... and for those of you who want to claim "literal" Biblical inerrancy, sorry, but you've got huge problems, long before you even get to Darwin. For starters, you can try explaining why the story of Abraham in Genesis includes domesticated camels….)

So, you might ask, what happened with the Assyrians? Good question.

The short version appears to be that the Assyrians were on the front lines dealing with all of the random crap coming out of central Asia -- that millions of square miles of steppe that's nothing but a huge tribal mixmaster, i.e., where nomads wander around, split up, recombine, and fight each other, until once every couple of centuries a new bad-ass group (e.g. the Celts, the Huns, the Mongols, the Turks) gets tossed out to plague the more civilized lands.

All during the period where the chariots reigned supreme, the Assyrians never actually got around to outsourcing their infantry; they didn't dare because they needed it. And it served them in good stead when they finally started getting invaded from the west.

A sensible historian would stop here and not try to derive some lame moral. History is what it is, and no situation will ever be repeated in exactly the same way, assuming we're even getting right what happened the first time around, which is no small stretch given that these are events of three thousand years ago.

But I still can't shake the image of the Mycenaean palace scribes on the eve of their destruction, diligently planning a re-fight of the previous war, assuming their technology will carry them through as it always has, having no inkling that the rules are about to change.

Or the idea that, in a world where less than 1% of the population sit in their palaces controlling an insane percentage of the resources, that the other 7 billion "hill people" won't eventually have something to say about that (if they aren't saying it already). Maybe this time they'll find a way to keep civilization going, if only so that they'll have a place to spend the gold that they're about to redistribute, but if their situation is sufficiently dire (or they're sufficiently pissed off), they may not have any reason to care about that.

I also have reason to suspect that firing drones at them is not going to improve their disposition.

Things are different now, of course. We have an internet. Both the 1% and the hill people could conceivably be reading this right now. (Hello, 1%! No regime lasts forever; please stop being idiots. Hello, Hill People! Please don't burn all of our stuff. kthnxbye.)

One might suppose that more knowledge will be preserved this time around, but then I think about how volatile our digital media is. It's something of a miracle that I can still read my email from 30 years ago; what's going to survive 3000 years from now?

And finally, there's remains the Small Matter of what the next big idea is going to be.
wrog: (me07)
My son's elementary school did a Beatles-themed musical presentation. Each class got up and sang a selection of songs from the Lennon/McCartney collected works. William (1st grade) was excited because he was one of the ones who got to do the dance as part of his class' rendition of When I'm 64.

I found this all incomparably weird, both generally weird and specific-to-me weird.

For one thing, it took me a while to catch on to something, and it wasn't until the parent sitting next to me remarked on how important it was to expose kids to this music. Although if she hadn't said anything, the Total Lack of Energy in the 5th grade class performance of All You Need is Love that ended the show would have nailed it:

For these kids, born in 2001-2007, it's just another random chapter out of the Big American Songbook. All You Need is Love may as well be In the Mood, Oklahoma, or I've Been Working on the Railroad, and the theme of the show may as well have been Glenn Miller or Rodgers & Hammerstein for all of the difference that it makes to them. For that matter the Beatles clearly predated a fair number of the teachers there as well.

In other words, this show was not, oddly enough, any kind of desperate, lame attempt on the part of the administration or teachers to be current, hip, or "groovy", to get the kids' attention by doing their music, or (in the more positive version) doing a daring presentation of edgy current music despite the possibility that it might upset a large fraction or even a majority of the parents.

Which is what I associate the Beatles, or more precisely, the Beatles songs with, and it's a measure of just how much I make that association that it took me so long to figure this out.

See, in the early 70s you simply could not get through a middle school band program without encountering at least one medley of Beatles tunes and often other currently-popular groups as well. Though there was always at least one Beatles medley.

In fact, I vividly remember doing an assembly in 4th grade (1970-71) where our class sang Raindrops Keep Falling on My Head and Three Dog Night's Joy to the World, both of which, if they weren't top-40 at the time had probably only recently dropped off.

To be sure, Raindrops is about as tame as it gets, but, now that I think about it, doing anything remotely hard-core rock like Three Dog Night must have been a pretty daring move on the part of my 4th grade teacher, given the community we lived in — the short version being that I grew up in the white Republican part of New Jersey; our town had THE best 4th of July Parade...

The previous year, we'd had the Earth Day assembly where a bunch of the cooler 8th graders (including my older brother) performed Peter Paul & Mary's Lemon Tree. Not quite Woodstock, but it probably still scared the shit out of some of the parents.

At which point you're probably saying, "Wait a minute… Raindrops…? Peter Paul & Mary? Three Dog Night? What does this have to do with the Beatles?"

At which point we get to the specific-to-me weirdness, which is that to me, at the time, there wasn't necessarily much of a distinction, except for one thing, but I'll get to that.

Time to rewind a bit:

My parents made a point of not having anything in their record collection that post-dated Stravinsky, Ravel, or Richard Strauss. (Well okay, they had Prokovief's Symphony #1, the "Classical" symphony, even if that's unlike everything else the guy ever did. And when my oldest brother came back from college with stuff by Poulenc and Messiaen, that got added; so it's not like they weren't open to new things.)

And the FM radio in our house basically only had two stations: WQXR 96.3 and WNCN 104.3 — yes, once upon a time, New York City was able to support two (2) commercial radio stations entirely devoted to classical music (true!).

My sole exposure to popular music in the media was
  1. whatever leaked in via the one AM station we listened to (WOR710 for its rush-hour news&traffic coverage) which was mainly confined to the safer 60s pop icons (e.g., 5th Dimension, Petula Clark, Simon & Garfunkle, Carpenters) and
  2. network TV, which in the early 70s was the variety shows that survived the 60s (Flip Wilson, Merv Griffin, Carol Burnett) and the wall-to-wall cop shows with fusion-jazz soundtracks that filled up the rest of the schedule.
When I started piano lessions in 2nd grade, my teacher was an Italian emigré, son of a baron who'd fled Mussolini in the 1930s, came to New York to try to continue his career as a concert pianist, had a performance at Carnegie Hall and then things kind of fizzled after that, as often happens; his career in Italy didn't mean squat here and sometimes you just don't get the break that you need. And so he settled down to teaching.

I got a marvelous education from him. Strictly old-school; you work your way up through the classics: Bach, Czerny, Haydn, Mozart, Beethoven, Chopin, Liszt.... By the time I got to 7th grade, aside from the piano technique, I knew a small crapload of music theory, had fairly intuitive understanding of sonata form, knew what all of the random mordants meant in Bach scores, and so on.

And to be fair to my parents, it's not like they forbid their kids from listening to other stuff. When my band director in 8th grade approached my mom about letting me play in the jazz band he was forming, worried that my parents wouldn't approve, they turned out to be fully supportive. (... At which point I had to learn a completely different music notation (chord changes instead of notes) and a whole new style of playing, a massive challenge given that there was so much I had to work out for myself — my teacher's knowledge of jazz didn't go much beyond Gershwin, and none of my directors were keyboard players, so there I was...). I suspect some of it was that my Mom was a closet Glenn Miller fan, but there were no complaints later on when things took a decidedly more modern direction.

Still my parents made no secret about wanting their kids to be classical music fans, and boy howdy did that work out for them. They didn't forbid; they were subtle; selective about their record collection; careful about finding a good piano teacher; if I wanted to listen to something there was no problem, but there was always a "Why would you want to?" attitude that seeped through.

Parents get to do that.

Thing is, I actually liked some of the stuff I heard on the AM radio, even if it wasn't necessarily Real Music™.

But I also knew that I hated the Beatles.
Even if I had no fucking clue who the Beatles actually were.

How does that work, you might ask?

Part of it is understanding how the Beatles were portrayed in the media, i.e., what you saw if your only experience of them is what you saw of them on network television in the late 60s and early 70s.

You'd see occasional documentaries or news items where there are clips of them performing. You know that they appeared on the Ed Sullivan Show in the early 60s. You'll see the standard shot of their first appearence in the US with millions of girls screaming at the top of their lungs and then swooning. Then an immediate cut to Helter Skelter and I am the Walrus, played through overloaded guitar pickups and badly distorted amplifiers (never mind the problems I already had with loud music in general, cf. autism spectrum sensory distortion issues for which I apparently share at least one or two genes with Philip)

That last part would go on for a while, interposed with cutaways to completely out-of-control crowds.

I didn't need my parents to tell me that this "music" was utter crap; that much was obvious.

It was also obvious that the Beatles were popular, for absolutely no reason that I could discern other than,
"Your parents hate this shit."

Which is not to say that I as a teenager didn't recognize the appeal of rebelling against my parents. But someone like me was far more inclined to rebel against my peers. You might say it was a natural consequence of the number of times I got beat up by my peers in elementary school. It's a small step from there to,

"Fuck that noise; sometimes parents actually do get stuff right the first time."

Of course, it didn't actually make a whole lot of sense to me that kids were going to these concerts solely and specifically to piss off their parents. That's an awful lot of trouble to go to.

Which left the other possibility, namely that the fans of the Beatles and the other hard rock groups were just insane, full stop.

This, of course, was borne out a few years later when Charles Manson's gang and the Symbionese Liberation Army went on their respective rampages.

Never mind that it was all part of a general trend. In the 1970s, crime rates spiraled out of control. Rampaging mobs shut down the city of Asbury Park -- an amusement park on the Jersey shore that we always used to go to every summer, that eventually became far too dangerous. Black Muslims were taking over the Newark public schools — my mom had a black college friend (see, we're not racist!) still living there, who had plenty of horror stories to relate. Orange and Montclair, where my mom had grown up and where she'd gone to college, were likewise getting overrun. There were so many places we couldn't go anymore.

Then there was that well-intentioned but stupid peace movement that shut down the Vietnam War, caused us to lose the entire country to the Soviets, put all of those millions of people in boats, and allowed Pol Pot to get in to kill half of Cambodia.

(...And, man, is it good that we were able to stop that shit dead in its tracks when they tried to do the same damn thing in Chile, where my father grew up and where my grandparents lived until they panicked and moved away after Allende's election...)

Or that well-intentioned but stupid "affirmative-action" reverse-discrimination bullshit that meant my dad, as the only white, Anglo, protestant guy in his department, stopped getting promotions. His career having stalled out meant that when the company got bought and the new board decided to close down the research division in New Jersey, he missed out on the department-head job that would have been an easy commute and instead had to take a department-head job that was 200 miles away, and so I only ever saw him on weekends after that.

And, finally, to top it all off, there was that Saturday morning TV show of theirs that was completely inane. I tried to watch a few episodes of it at one point but gave up in disgust. Could NOT see the appeal. Best I could come up with was Peter Tork possibly being handsome by some standard — something I, naturally, would know nothing about — but that, of course, could only explain the girl fans (no sexism here, either, nope!).

Suffice it to say, I had no shortage of completely objective reasons to hate the Beatles and all of that hippy 60s crap that they represented.

Suffice it to say, it's interesting how things can change when more facts become available or when one gets an additional 30 years to mull things over. This being long enough, I'll skip the details, except for one (if you care about the others, or otherwise want to draw too many conclusions about my current political views, you might want to look at this first (though I only ever really knew the Jerry Schwarz version)) …

…namely that Ob-La-Di, Ob-La-Da turns out to indeed be a Beatles song, which I only found out this morning. Yes I'd heard it before, but given its reggae style, I was sure it had to be by Herb Alpert or somesuch. (And I now feel less stupid finding out that Herb Alpert — along with a billion other people — indeed did a cover of it in 1969, mere months after the White Album came out.) It's still amazing how often this keeps happening to me, i.e., that some song I know from the 60s unexpectedly turns out to be by Lennon/McCartney, evidence of the considerable length and variation in their career prior to Helter Skelter.

The same, of course, happened with all of the aforementioned band medlies, i.e., I had no idea at the time that they were Beatles, only that they matched songs I heard on the AM radio, and that the school teachers were clearly attempting to "reach" the kids using "their" music. But I actually liked some of those tunes and so, in some cases at least, didn't mind so much.

I'd also be curious to know how many schools currently attempt what my school did in 1970, i.e., whether there are any Nirvana or REM or Spice-Girls-themed school productions happening now or whether we'll have to wait another decade for that.

Then again, I noticed that Helter Skelter was conspicuously absent from the program today.

geoguessr

May. 26th, 2013 11:48 am
wrog: (toyz)
I wonder if they've suddenly seen an upsurge in hits because of xkcd.

Anyway, I now know what most of southern Australia looks like (that one was basically impossible, but if you want to give it a try...)
or I could just give it away )
Update: It is possible to get over 32000 points. (hm, am I not supposed to be using Google search?)
wrog: (toyz)
So, I remember this demo.

It was something that, back in grade school, the engineer father of one of my best friends really liked to put on -- did it on several occasions that I remember. It was one of these Physics is Cool demos.

Start with a room about 40-50 feet long, almost exactly like this one, in fact if we can trust Google's scale marker, that's pretty much what it was (yes, the room takes up the whole length of the building; yes, the Internet is really scary these days...). I remember the ceiling as being really high, but since I was smaller back then, that recollection is suspect. I also distinctly recall someone accidentally sticking the end of a flagpole into the ceiling (we had our Boy Scout troop meetings in that room), so it couldn't have been that high. From the photo, 12 feet seems likely.
  • There's a stepladder right at the back wall of the room.

  • Somewhere towards the middle of the room, there's a hook in the ceiling.

  • A piece of twine is tied to the hook, long enough to almost reach the floor; at the other end of the twine, a Rather Heavy Object of some sort, ... shotput or bowling ball or somesuch, I forget.

  • Up at the front of the room is a chair with a 1-2 foot diameter basket on it.

  • He pulls two volunteers out of the audience. Volunteer #1 is somebody's little sister. He positions her near the middle of the room, between the basket and the hook, and hands her this big-ass butcher's knife. "This is extremely sharp. I want you to hold this right here, just like that." Blade is pointed towards the back of the room, angled downward.

  • Volunteer #2 takes the bowling ball up the stepladder. "Yeah, that's about high enough. Just let go of it."

  • Ball swings forward, right down to the floor and up again, reaches the knife, the twine parts pretty much instantaneously, the ball sails through the air, and lands right in the middle of the basket.
And there was much rejoicing.

What's a bit frustrating now is that, since I was in 6th or 7th grade at the time, this was all before I'd had any Actual Physics. Meaning "Physics is Cool" was pretty much all of the content that I got out of this. It was mentioned that the ball needed to be heavy and the knife needed to be sharp, but beyond that I had no idea which other details of the setup were crucial and which didn't matter at all. Nor was there really much of an explanation of why it worked, what principle was being demonstrated -- or maybe there was one, and I just didn't have the background to appreciate it and so it all just went kind of went whoosh.

Actually, now that I think about it, there may indeed have done some kind of brief "inertial foo gravitational mass mumble mumble", but I'm sure he knew up front that when you've got something that works mainly because it just drops out of the math and you've got an audience that doesn't know a whole lot of math, you're just going to lose them if you try to explain too much, so you just skip the boring part and get on with the show.

To be sure, it's fairly cool to be able to set up a scenario, calculate out in advance where things are going to go, then pull the trigger and have them Actually Go There. Which perhaps describes pretty much every classroom physics demo ever. And this may indeed be enough of a point for 7th & 8th graders (i.e., "Learn your math, kids. Keys to the universe!" or maybe just, "It works, bitches").

But still a bit frustrating, because, years later I learned some Actual Physics, and a few questions remain. Not that I'm particularly surprised that this worked, but,... what's the gimmick? Some particular sweet spot where to put the basket so that it doesn't matter quite so much where you put the knife or where you let the ball drop from? Or maybe it's a sweet spot in the knife placement or the original drop point? Was the scenario chosen the one that was easiest to calculate? Or the one that had the basket the furthest forward? Or the one had the longest flight time for the ball?

I suppose I could just call John up and ask, "Hey, that thing your dad did with the knife and the swinging shot put; what was the deal with that, anyway?" But this would be cheating. So I'm going to analyze this a bit. . .

bet you didn't see *this* coming... )
wrog: (toyz)
So I've arbitrarily decided that more people need to know about spherical trigonometry. (e.g., just in case the GPS gets destroyed and we're stuck having to do our own navigation again.)

It's really the same solving of triangles that you learned to do in high school geometry/trig, i.e., gimme side-angle-side or angle-side-angle to nail down what the triangle actually is, then use Law of Sines or Law of Cosines or some combination thereof to work out the previously unknown sides/angles that you care about.

It's just that some of the rules for spherical trig are a Little Bit Different.

So, jumping right into the deep end, here's an application inspired by recent events:
You, an observer stationed on planet Earth at some particular latitude, want to know where the sun is going to be in the sky at some particular time of day, some particular day of the year.
And, cutting to the chase, here's a triangle to solve:



If you know b, A, c (side, angle, side), you can solve for a (opposite side) using the Law of Cosines
cos a = cos b cos c + sin b sin c cos A
and then B (next angle) using the Law of Sines
sinB/sinb = sinA/sina = sinC/sinc
...math wanking continues... )
Page generated Oct. 20th, 2017 05:35 pm
Powered by Dreamwidth Studios