In which I summarize Joe Veverka's Kuiper Prize talk at the Division for Planetary Sciences meeting: "Small is NOT Dull: Unravelling the Complexity of Surface Processes on Asteroids, Comets and Small Satellites."
It's been a very full day at the DPS-EPSC 2011 joint meeting. My day was less full than it might have been, because I overslept and missed most of the morning's session. I really needed the rest though so I think it was probably for the best!
According to the Stardust website, the spacecraft has continued taking navigational camera images of Tempel 1 since last Monday's flyby. But "This will end with a Navcam calibration that will take place [today]. This will be the end of the official Tempel 1 encounter activities. Planning is under way for the decommissioning of the spacecraft."
Here's two more items from Tuesday's flyby of comet Tempel 1 by the Stardust spacecraft to add to my previous roundup of Tempel 1 data. The first represents data from a dust counting instrument, portrayed as sound, and the second is a terrific morph animation of the flyby produced by Daniel Macháček.
I really didn't expect these images to look so good! I'd prepared myself for blurry images and a lot of squinting to try to match up features in pictures between Deep Impact and Stardust views of Tempel 1, but in fact the resemblance is obvious and you can clearly see that they successfully imaged the area in which Deep Impact's Impactor craft collided with the comet.
Stardust is very close to the last major act of its mission: the flyby of Tempel 1, which will take place at 20:40 PST (04:40 UTC). Here's a summary of the recent and current status of the mission, and how to follow the events over the next 24 hours.
A press briefing was held at NASA Headquarters this morning to preview the planned February 14 encounter by Stardust with Tempel 1. There aren't often lots of questions from media after these "preview" briefings, but today there were zero. That's not good.
Stardust is healthy after performing a "cold boot" to clear a memory address problem (a "memory address latch-up") that occurred late last year and caused the spacecraft to go into safe mode three times.