Skip to main content

Loose potato?

It seems that Japan’s Hayabusa probe hit a snag during a practice landing recently, abending the landing when the probe saw “an anomalous signal”. Hayabusa now orbits at 3km; there’s a good collection of images of the asteroid in question, Itokawa, at SpaceRef.

Asteroid Itokawa

So what was the “anomalous signal”?

My random guess is that Itokawa’s material is a lot looser than expected (as in, heavier material but more loosely packed) — a great big bent-potato-shaped pile of gravel and bulldust — and that even the light thrusters used by Hayabusa were enough in the asteroid’s microgravity to kick up a little dust from a few km away — especially if the thruster exhaust is electrically charged — and change the probe’s view slightly.

This would be consistent with the “gentle impacts” explanation for the odd cratering seen on other small bodies, and with the observations of Deep Impact.

If Itokawa is indeed so loosely packed, deflecting an Itokawa-like asteroid from a collision course with Earth would present a unique problem.

Traditional proposals have relied upon either blasting an incoming asteroid with a nuke, or mounting thruster units on it and more gently steering it aside.

A pile of gravel and dust hit by a nuke would not respond as a unit; much more of the force of a blast would be consumed in heating up and rearranging the gravel than would be the case for the chunk of stone usually modelled, and a likely outcome would be to simply disrupt the asteroid so now Earth would be hit in pretty much the same place by the same mass as a large variable-density cloud of gravel rather than by a single lump. An asteroid so disrupted would be completely unmanageable (no second tries).

Similarly, mounting thrusters on a rocky “slush pile” would result in the thrusters pushing themselves under the surface and/or rapidly becoming misaligned unless they were very low thrust and had a correspondingly long lead time in which to nudge the asteroid onto a more Earth-friendly course.

Comments

Popular posts from this blog

every-application-is-part-of-a-toolkit at work

I have a LibreOffice Impress slideshow that I wish to turn into a narrated video. 1. export the slideshow as PNG images (if that is partially broken — as at now — at higher resolutions, Export Directly as PDF then use ‘pdftoppm’ (from the poppler-utils package) to do the same). 2. write a small C program (63 lines including comments) to display those images one at a time, writing a config file entry for Imagination (default transition: ‘cross fade’) based on when the image-viewer application (‘display,’ from the GraphicsMagick suite) is closed on each one; run that, read each image aloud, then close each image in turn. 3. run ‘Imagination’ over the config file to produce a silent MP4 video with the correct timings. 4. run ‘Audacity’ to record speech while using ‘SMPlayer’ to display the silent video, then export that recording as a WAV file. 4a. optionally, use ‘TiMIDIty’ to convert a non-copyright-encumbered MIDI tune to WAV, then import that and blend it with the speech (as a quiet b

boundaries

pushing the actual boundaries of the physical (not extremes, the boundaries themselves) can often remove barriers not otherwise perceived. one can then often resolve an issue itself, rather than merely stonewalling at the physical consequences of the issue.

new life for an old (FTX) PSU, improved life for one human

the LEDs on this 5m strip happen to emit light centred on a red that does unexpectedly helpful things to (and surprisingly deeply within) a human routinely exposed to it. it has been soldered to a Molex connector, plugged into a TFX power supply from a (retired: the MoBo is cactus) Small Form Factor PC, the assorted PSU connectors (and loose end from the strip) have been taped over. the LED strip cost $10.24 including postage, the rest cost $0, the PSU is running at 12½% of capacity, consumes less power than a laptop plug-pack despite running a fan. trial runs begin today.