WHAT WE DO


JOINRENEWJOIN

Give a Gift Membership
 

The Planetary Society Weblog

By Emily Lakdawalla


Welcome to The Planetary Society's Weblog, a guide to interesting stuff going on in space science, space exploration, and space advocacy. Have any comments?

JavaScript required to view email.

portrait

Aug. 21, 2008 | 14:17 PDT | 21:17 UTC

Tweet Tweet Tweet


As Phoenix approached Mars, it suddenly acquired a voice and began broadcasting status updates to Earth via an Internet service called Twitter. For those of you not in the know (a group that, admittedly, included me, before I was forced to figure it out as a result of Phoenix' activity), Twitter is a service that allows people to write to, and read, a blog, using the sorts of devices from which you might send text messages. It is sometimes referred to as a "micro-blogging" service because each post is limited to 140 characters. (FYI, a Twitter post is called a "tweet.") For those of you who do know what Twitter is, skip the next couple of paragraphs.

People not using text-messaging devices have also found Twitter handy for rapidly changing events, for which the blog format is unwieldy. For instance, it would have been really great if I had had my act together to use Twitter to blog the Phoenix landing. Such comments as "PHOENIX HAS LANDED!" (19 characters) and "Just got a press release that told me the landing time was 23:53:44, as received on Earth." (90 characters) and "PICTURES!! We got solar panels, footpad, and the postcard!!! It is super duper duper flat, just slightly tilted, as they said." (126 characters) are perfect Twitter fodder.

Twitter can also be used to ask and answer questions. When you see a tweet that has an "@" sign in it, that indicates that another Twitterer is being addressed directly. So, for instance, Twitter user "bayol" asked Phoenix a question by tweeting: "@MarsPhoenix If perchlorate is found in rocket fuel, Isn't it pretty obvious that it probably came from your soft landing procedure?" And Phoenix replied: "@bayol The retro rockets for landing used hydrazine fuel, not perchlorate."

The Phoenix Twitter feed is remarkably successful, with more than 32,000 signed-up followers, which undercounts the actual number of readers. By comparison, television personality Stephen Colbert, whose devotees are mostly very Internet-savvy, has (as of the time I wrote this) only 13,800 Twitter followers. Seeing the success of the Phoenix Twitter feed, a ton of other spacecraft suddenly jumped on the bandwagon and also started Twittering away. Here's a few examples of tweeting spacecraft (there are more):Some of these use the medium more successfully than others. From the outset, Phoenix' has been awesome. That's due in large part to the voice behind "MarsPhoenix," JPL public information officer Veronica McGregor, who has been comfortable with the medium from the get-go. I am amazed by the amount of personality and the quantity of factual detail that she's able to squeeze into the narrow limitation of 140 characters per post. A couple of other recent tweets: "A new pinch of soil, named Rosy Red 3, is in TEGA oven #5. Baking starts today to analyze chemical properties. This is my 3rd bake test :-)" and, useful for me, "Reports claiming there was a White House briefing are also untrue and incorrect" and, one of my recent favorites, "@nantel I'm doing what a guy with a shovel could do in 10 seconds? True, but I'm here a couple decades before that guy. :)"

Lunar Reconnaissance Orbiter and LCROSS started out a bit bumpy, with lots of tweets simply pointing to content on the mission websites. That wasn't very useful. But as the spacecraft are getting ready for launch, there have been frequent updates on each tiny step that both have to go through to get integrated, tested, and buttoned up. This is more useful, but still lacking in detail compared to MarsPhoenix. LRO tweets less-than-informative things like "I'm being tested today." and "I'm happy that my HGAS pop and catch was successfully completed." A Google search doesn't turn up what the heck the latter one is talking about. If they're going to try to communicate with the public, it would probably good to try to do it in a way that, well, communicates something! Hopefully they'll improve with time.

New Horizons, too, has lately joined in, and is beginning to establish a voice for the spacecraft. But it's struggling to make good use of the medium as well. There's simply not much for New Horizons to talk about these days that would demand the use of the fast-response medium of Twitter. I think this entry sums up the problem: "Ahhhh, another day, another million miles on the road to Pluto!"

I think it's a good idea for missions to use all the media out there to reach out to the public, and to evolve with the changing media environment. However, it's clear that missions need to find the right people to do the outreach, people who figure out how to use the medium to their advantage. I haven't used Twitter yet myself because I don't think I'd do any better with it than, say, LRO_NASA does. And until I'm sure I can do it well, I'm not going to do it at all. Ditto with Facebook; I've joined and have a slowly growing list of friends and well-wishers but am not real sure I can use it well to actually teach people anything, and it doesn't help that I am often too busy to visit the page for weeks at a time. (For those of you who have recently requested friendhood, I'm not snubbing you, I just haven't had time.) Maybe one of these days I'll get more comfortable with all these newfangled media! For now I'll stick with this old-fashioned blog medium, and continue to feel out streaming video.

If you are really in to all this social networking stuff, you might check out all the space missions that are on Facebook. Thanks to Keri Bean, originator of the first space mission Facebook identity (Mars Rovers) for this list (sorry I didn't have time to plug them in as links): Phoenix Mars Lander, Mars Rovers, Lunar Reconaissance Orbiter, Lcross Lunar Impactor, Hubble Telescope, Webb Telescope, Glast Satellite, Snap Satellite, Swift Satellite, Xmm-Newton Satellite, Glory Mission, Kepler Mission, and Aura Spacecraft. And the International Year of Astronomy has a Facebook identity, "Iya Cosmos."

I asked Keri why she thought this was valuable and she said: "I think it's a great way to reach out informally. I got tons of people asking questions after Phoenix announced the water ice, so I made a blog explaining how the scientists determined it was water ice, which got a lot of comments, including the most memorable "Now *this* is the kind of communication I like to see from NASA!" I see Facebook as a great outreach tool, especially for the younger crowd/Gen Y who would normally not keep up with NASA missions."



Aug. 21, 2008 | 08:21 PDT | 15:21 UTC

Watching the clouds drift by


Last week in my "what's up" roundup I noted that that in the previous week's Mars weather update the MARCI camera team on Mars Reconnaissance Orbiter had reported more water-ice clouds appearing in the equatorial regions of Mars, that is, in the skies of the rovers. It seems that the rover team noticed the news too, because Opportunity looked up to watch those clouds drift overhead:
Clouds drift over Opportunity
Clouds drift over Opportunity
Periodically, Opportunity gazes skyward to watch water-ice clouds drifting overhead, as in this four-image sequence , spanning about 90 seconds, from sol 1,614. There have not been many clouds to look at until recently, but Mars Reconnaissance Orbiter's MARCI camera has lately noticed more water-ice clouds over the rovers' equatorial positions. Credit: NASA / JPL / Cornell / Tman
Actually I am quite sure that the rover team receives regular updates from the MARCI team on what Mars' weather has in store -- that's one of the reasons MARCI is up there, after all!

When you next go outside, look up. Are there clouds in your sky? Do they move quickly or slowly? Are they puffy, white, and full of water, or do they look like the clouds over Opportunity -- wispy and dry with ice crystals? Spend a moment looking at your clouds, and wondering what it would be like to watch them from the surface of an alien world.



Aug. 20, 2008 | 16:39 PDT | 23:39 UTC

Things that probably won't ever be called planets, but maybe they should


The longer I listened to the "great planet debate" last week, the more strongly I felt that if it were up to me, I would define "planet" to mean "everything in the universe that's smaller than a star." The fact of the matter is, every time I speak about any object visited by a spacecraft, I make frequent slips of the tongue. I call Titan a planet. I call Enceladus a planet. I've even called Tempel 1 a planet. They're all wanderers, all places to visit. Subdivide it however you like -- it makes sense to speak of giant (or Jovian) planets, ice giant planets, major planets, terrestrial planets, minor planets, dwarf planets, binary planets, whatever. But just look around at the people who call themselves "planetary scientists" and see what they study. It's all of the above.

In that spirit, I went around the Internet to locate all of the really tiny Sun-orbiting worlds that have been visited by spacecraft, the ones too lumpy and common to fit into nearly anybody's definition of "planet." Yet, by virtue of having been visited by a spacecraft, they have been elevated to special status. Here's the gallery. Many thanks to Ted Stryk for rummaging through his archives and sending me his versions of many of these images.

The first of these minor planets to have been visited by spacecraft was, fittingly, the first comet that was recognized to be a periodic one: Halley's comet. A flotilla of spacecraft was launched to visit Halley when it last visited the inner solar system in 1986, including ICE (USA, NASA), Vega 1 and 2 (Soviet Academy of Sciences, USSR), Sakigake and Suisei (ISAS, Japan), and Giotto (ESA). Of these, Vega 1, Vega 2, and Giotto returned photos of Halley's nucleus, finding it to be good-sized for a comet at 16 by 8 kilometers across, but incredibly dark and also extremely low-density (if you're curious, the density was 0.1 grams per cubic centimeter). Here's a photo from Vega 2:
The nucleus of Halley's comet
The nucleus of Halley's comet
The Vega 2 spacecraft returned many images of the nucleus of Halley's comet on March 9, 1986. The nucleus is an irregular object about 16 x 8 x 8 kilometers and very dark, with an albedo of about 0.03. The next time Halley will approach the inner solar system is in 2062. Credit: Russian Academy of Sciences / Ted Stryk
After Halley, the next tiny object we visited came in 1991, when Galileo flew past Gaspra. The Galileo flybys of Gaspra, and later, in 1993, Ida, were wonderful, and not just because Gaspra was the first spacecraft encounter with an asteroid. They also allowed Galileo to take full advantage of its capabilities. Galileo's high-gain antenna never deployed. But for the Gaspra encounter they were able to return data at a high rate anyway, because after Gaspra Galileo returned to Earth for another gravity assist, in November of 1992. They waited until then to return all the data.
Asteroid 951 Gaspra
Asteroid 951 Gaspra
Galileo flew by Gaspra on October 29, 1991. Gaspra is an S-type asteroid about 19 x 12 x 11 kilometers in size. Gaspra is reminiscent of Mars' moon Phobos, having many craters and occasional grooves. Credit: NASA / JPL / Ted Stryk
Next, Galileo flew by Ida. During this flyby, Galileo serendipitously discovered Ida to have a tiny little companion satellite, later named Dactyl.
Ida and Dactyl in enhanced color
Ida and Dactyl in enhanced color
Galileo captured this image of asteroid Ida and its moon Dactyl about 14 minutes before its closest approach on August 28, 1993. The range from the spacecraft was about 10,500 kilometers (6,500 miles). This was from the imaging sequence that produced the discovery of Dactyl. The color is based on violet and infrared filters; it represents actual variations on the surface of Ida, but has little relationship to the colors that human eyes would see. Ida is an S-type asteroid, about 58 by 23 kilometers in size. Credit: NASA / JPL
Here's a zoom on little Dactyl.
Dactyl
Dactyl
Also known as (243) Ida I, Dactyl is a satellite of the asteroid Ida. Dactyl was discovered by the Galileo spacecraft in images taken as it sped past Ida in an encounter on August 28, 1993. It is about 1.6 by 1.2 kilometers in size, orbiting Ida at a distance of 90 kilometers. Credit: NASA / JPL / Ted Stryk
Next was NEAR. On its way to its destination of 433 Eros, it flew past asteroid 253 Mathilde:
Asteroid Mathilde
Asteroid Mathilde
Asteroid 253 Mathilde was visited by the NEAR spacecraft on June 27, 1997, on its way to Eros. The encounter was the first fast flyby of an asteroid; for the images to be captured, the spacecraft's targeting had to be updated less than 12 hours before the encounter, based upon the orbital information provided by pre-encounter images. Mathilde is a C-type main-belt asteroid, 59 x 47 kilometers in size. Credit: NASA / JPL / Ted Stryk
After Mathilde, NEAR became the first spacecraft to enter orbit around an asteroid on February 14, 2000; a year later, it became the first to land on an asteroid, and functioned there for two weeks before being shut down. It visited 433 Eros, which is not huge, but it's one of the biggest near-Earth asteroids.
Eros rotation animation
Eros rotation animation
One full rotation of the asteroid Eros as seen by the NEAR spacecraft on February 16, 2000, two days after its arrival. Eros is an S-type asteroid, about 33 by 13 kilometers in size.Source Credit: NASA / JHU APL
Next up is Deep Space 1, which flew by asteroid 9969 Braille (named in a Planetary-Society-run contest) on July 29, 1999. For an encore, they picked up a comet, 19P/Borrelly, on September 22, 2001, performing the highest-quality imaging yet of a comet nucleus.
Asteroid Braille
Asteroid Braille
Deep Space 1 flew by asteroid 9969 Braille (formerly known as 1992 KD) on July 28, 1999, at an altitude of only 26 kilometers. However, the only images of Braille were captured from much farther away, about 14,000 kilometers. Braille proved to be an irregularly shaped body about 2.2 kilometers long by 0.6 kilometers across. It is probably a Q-type asteroid, dominated by olivine and pyroxene. It is also unusually bright for an asteroid, with an albedo of about 0.34. Credit: NASA / JPL / Ted Stryk
Comet 19P/Borrelly, target of Deep Space 1
Comet 19P/Borrelly, target of Deep Space 1
Deep Space 1 flew by comet 19P/Borrelly on September 22, 2001. It flew within 2,171 km of the nucleus at 22:29:33 UT. The nucleus is about 4 by 8 kilometers in size and incredibly dark, with an albedo varying from 0.01 to 0.03. Credit: NASA / JPL / Ted Stryk
The next thing to do was to try to bring something back from one of these objects. That's what Stardust set out to do, flying through the coma of comet Wild 2 to collect samples. The flyby happened on January 2, 2004. On the way, though, it picked up an opportunistic encounter with an asteroid named Annefrank.
Asteroid Annefrank
Asteroid Annefrank
The Stardust spacecraft flew within 3,300 kilometers of asteroid Annefrank on November 2, 2002. Prior to the encounter, little was known about the asteroid except how much light it reflected. It turned out that the brightness of Annefrank had been interpreted incorrectly, leading mission planners to expect a smaller and brighter asteroid. Its size is 6.6 by 5.0 by 3.4 kilometers. Credit: NASA / JPL / Ted Stryk
Animation of Stardust's flyby of Wild 2
Animation of Stardust's flyby of Wild 2
This animation is composed of 24 frames captured by Stardust as it flew by Wild 2 on January 2, 2004. Credit: NASA / JPL / Emily Lakdawalla
On July 4, 2005, Deep Impact took a more direct approach to studying the makeup of a comet, smashing an autonomous spacecraft into the nucleus of Tempel 1 and flying through the debris cloud. This image was taken on the way in.
Mosaic of Tempel 1
Mosaic of Tempel 1
This view of the nucleus of comet Tempel 1 is composed of many frames captured from different ranges by Deep Impact as it approached for its July 4, 2005 encounter. Images of the whole comet nucleus were taken from a greater distance and so are blurrier; highest resolution images were captured of the bottom half of the nucleus. Credit: NASA / JPL / UMD
Finally, we have, I think, my favorite minor planet of the bunch. This is Itokawa, the second asteroid to be orbited by a spacecraft, and the second on which a spacecraft has landed, but the first from which we are attempting to return a sample, and by far the smallest body ever visited by a spacecraft. It's so very weird and different -- looking at pictures of Itokawa tells me that there are untold wonders remaining to be discovered among the very smallest denizens of our solar system. Itokawa was studied by Hayabusa in November 2005.
Itokawa rotates under Hyabusa
Itokawa rotates under Hyabusa
This animation consists of 57 separate images captured by the Hayabusa spacecraft as the tiny asteroid Itokawa (535 by 294 by 209 meters in size) rotated underneath it. The images are actually from three separate rotations; they were sorted and lined up into this animation by Øyvind Guldbrandsen of the Norwegian Astronautical Society. Click here for a full-resolution movie containing 169 frames (AVI format, 3.8 MB) Credit: ISAS / JAXA / Øyvind Guldbrandsen
The next tiny place to look forward to is Steins, which will be encountered by Rosetta very soon. There's a page on this website on the entire history and near future of asteroid and comet exploration, if you want to read more about these missions.

One thing I always wonder when I look at such photos is: how big are they? In particular, how do their sizes relate to each other? Here you go, all of the minor planets pictured above at the same resolution, 200 meters per pixel. Itokawa really is there, it's just a nearly invisible 2-by-1-pixel speck.

Mathilde at a scale of 200 meters per pixel

Eros at a scale of 200 meters per pixel
Eros
33 x 13 km

 

Annefrank at a scale of 200 meters per pixel

Annefrank
6.6 x 5.0 x 3.4 km

Gaspra at a scale of 200 meters per pixel

Gaspra
19 x 12 x 11 km

 

Dactyl at a scale of 200 meters per pixel

Dactyl
1.6 x 1.2 km

Itokawa at a scale of 200 meters per pixel

Itokawa
0.5 x 0.3 x 0.2 km

Braille at a scale of 200 meters per pixel

Braille
2.2 x 0.6 km

Asteroids above and left;
comet nuclei below

Halley at a scale of 200 meters per pixel
Halley
16 x 8 x 8 km

Tempel 1 at a scale of 200 meters per pixel

Tempel 1
7.6 x 4.9 km

Wild 2 at a scale of 200 meters per pixel

Wild 2
5.5 x 4.0 x 3.3 km

Borrelly at a scale of 200 meters per pixel

Borrelly
8 x 4 km

Mathilde
59 x 47 km

 

Ida at a scale of 200 meters per pixel
Ida
58 x 23 km




Aug. 19, 2008 | 08:06 PDT | 15:06 UTC

Beautiful mosaic from the Enceladus encounter


In an amazingly quick piece of work, the imaging team has already assembled the 8-frame mosaic captured by Cassini as it receded from its close encounter with Enceladus last week. This is a really difficult piece of work. There are 32 separate camera images in this mosaic -- 8 high-resolution images taken through a clear filter to get the detail, and 24 taken at half the resolution through ultraviolet, green, and infrared filters to get the color.
Mosaic of Enceladus' southern hemisphere
Mosaic of Enceladus' southern hemisphere
As Cassini receded from its August 11, 2008 flyby of Enceladus, it captured an 8-frame mosaic of the terrain of the southern hemisphere through five different camera filters. Those data have been combined to create this huge mosaic. The south pole is at the right, near the day-night boundary. All four of Enceladus' south polar sulci (or "tiger stripes") are visible: from top to bottom, they are Damascus, Baghdad, Cairo, and Alexandria. Circling around them is a scalloped annulus of deformed material, whose ridges and furrows are thrown into stark relief by the low-angle of the late-summer sun on the southern hemisphere. The sulci and that scalloped annulus are noticeably bluer than the rest of Enceladus in this enhanced-color image, indicating that they are made of solid or coarsely crystalline (and likely fresher) ice. In some places, there are rainbow colors -- these are imaging artifacts. Toward the equator (at the left side of this mosaic), the heavily tectonized terrain gives way to a cratered and therefore much older surface. Credit: NASA / JPL / SSI

Now, the rovers take mosaics of many more images than this all the time; in that context, 32 images doesn't seem like all that much data. But when the rovers take 32 images for a panorama, they're usually doing it from what amounts to a tripod with a pan-and-tilt mount with very accurately known geometrical properties. Take one set of pictures, pan by N degrees, take the next set, tilt by N degrees, take the next set, and so on. Each multi-filter set taken at one "pointing" overlaps perfectly, without any notable registration error.

Cassini, on the other hand, was flying quickly away from Enceladus while Enceladus was moving in its own orbit around Saturn. So, to begin with, all of those multi-filter sets of images aren't correctly registered. For example, the imaging sequence started with a clear-filter photo taken when Cassini was 4,742 kilometers from Enceladus. Then it rotated the ultraviolet filter into place and snapped the next picture, but by then it was 5,800 kilometers from Enceladus. The different distance means that the ultraviolet image is about 35 kilometers across, while the clear image covers much less area, less than 29 kilometers across. To build each color frame, the component color images had to be resized and coaligned. Then that low-resolution color data had to be overlaid on each clear-filter image.

When it came time to assemble the eight color images into a single mosaic, the rotation of Enceladus also had to be taken into account. To do that, it wasn't enough just to stretch the images; the geometric distortion caused by the rotation of the moon during imaging would really create a warped image. So each of the eight frames had to be tagged with geometric information about where each of its corners were, and where the spacecraft was when it captured the images. Then all the images were stretched -- the official terminology is "transformed" or "reprojected" -- to how they would appear to a viewer located a very long distance above Enceladus at 63.0 degrees south latitude, 281.3 degrees west longitude. (Technically, this is called an "orthographic projection" -- it assumes the point of view of a viewer at infinity.) Once they were transformed to a common map projection, they could finally be assembled into a finished mosaic.

It's difficult work and amazing it was done so quickly! Kudos to Jason Perry.

If you'd like to mess about with the images, I've completed updating my Enceladus flyby raw images page. There was an error in the original map showing the footprint locations for this eight-frame mosaic, which I've now fixed.

One last comment about this mosaic: it is in enhanced color, which helps you see the true color differences from place to place, but doesn't accurately show how Enceladus would appear to the human eye. Here is one amateur's attempt to show how Enceladus would appear if you were there.
Enceladus in natural color
Enceladus in natural color
This is a wide-angle shot taken during the July 14, 2005 close encounter with Enceladus through red, green, and blue filters. Gordan Ugarkovic has attempted to process the data so that it appears approximately as it would to the human eye. The tiger stripes or sulci are darker and bluer than surrounding terrain, but the difference in color is much more subtle than it appears in most Cassini color images, which are typically made with ultraviolet, green, and infrared filters (a broader range of the electromagnetic spectrum) and are stretched to enhance color differences. Credit: NASA / JPL / SSI / Gordan Ugarkovic





Browse the Weblog Archive »

Sign up for email updates!
Email address:
(optional) Your name: