Shallow Thoughts

Making "Citizen Science" compelling

I had the opportunity to participate in a focus group on NASA's new "citizen science" project, called Moon Zoo, with a bunch of other fellow lunatics, amateur astronomers and lunar enthusiasts.

Moon Zoo sounds really interesting. Ordinary people will analyze high-resolution photos of the lunar surface: find out how many boulders and craters are there. I hope it will also include more details like crater type and size, rilles and so forth, though that wasn't mentioned. These are all tasks that are easy for a human and hard for a computer: perfect for crowdsourcing. Think Galaxy Zoo for the moon. The resulting data will be used for planning future lunar missions as well as for general lunar science.

It sounds like a great project and I'm excited about it. But I'm not going to write about Moon Zoo today -- it doesn't exist yet (current estimate is mid-March), though there is a preliminary PDF. Instead, I want to talk about some of the great ideas that came out of the focus group.

The primary question: How do we get people -- both amateur astronomers and the general public, people of all ages -- interested in contributing to a citizen science project like Moon Zoo?

Here are some of the key ideas:

Make the data public

This was the most important point, echoed by a lot of participants. Some people felt that many of the existing "citizen science" projects project the attitude "We want something from you, but we're not going to give you anything in return." If you use crowdsourcing to create a dataset, make it available to the crowd.

Opening the data has a lot of advantages:

• People can make "mashups", useful sites that display your data in useful ways or combine it with other data. This can generate more interest in your project and more contributors.
• School groups can work on class projects or science fair projects, probably contributing more data along the way.
• It might help the next generation of scientist get started.
• It shows openness and good faith: witness the recent blow-up over the leaked IPCC emails and the debate over how much climate data has been kept private.

Projects like Wikipedia and Open Street Map, as well as Linux and the rest of the open source movement, show how much an open data model can inspire contributions.

Give credit to individuals and teams

People cited the example of SETI@Home, where teams of contributors can compete to see who's contributed the most. Show rankings for both individuals and groups, so they can track their progress and maybe get a bit competitive with other groups. Highlight groups and individuals who contribute a lot -- maybe even make it a formal competition and offer inexpensive prizes like T-shirts or mugs.

A teenaged panel member had the great suggestion of making buttons that said "I'm a Moon Zookeeper." Little rewards like that don't cost much but can really motivate people.

Offer an offline version

They wanted to hear ideas for publicizing Moon Zoo to groups like our local astronomy clubs.

I mentioned that I've often wanted to spread the word about Galaxy Zoo, but it's entirely a web-based application and when I give talks to clubs or school groups, web access is never an option. (Ironically, the person leading the focus group had planned to demonstrate Galaxy Zoo to us but couldn't get connected to the wi-fi at the Lawrence Hall of Science.)

Projects are so much easier to evangelize if you can download an offline demo.

And not just a demo, either. There should be a way to download a real version, including a small data set. Imagine if you could grab a Moon Zoo pack and do a little classifying whenever you got a few spare minutes -- on the airplane or train, or in a hotel room while traveling.

Important note: this does not mean you should write a separate Windows app for people to download. Keep it HTML, Javascript and cross platform so everyone can run it. Then let people download a local copy of the same web app they run on your site.

Make sure it works on phones and game consoles

Lots of people use smartphones more than they use a desktop computer these days. Make sure the app runs on all the popular smartphones. And lots of kids have access to handheld web-enabled game consoles: you can reach a whole new set of kids by supporting these platforms.

Offer levels of accomplishment, like a game

Lots of people are competitive by nature, and like to feel they're getting better at what they're doing. Play to that: let users advance as they get more experienced, and give them the option of doing harder projects. "I'm up to level 7 in Moon Zoo!"

Use social networking

Facebook. Twitter. Nuff said.

Don't keep results a secret

Quite a few scientific publications have arisen out of Galaxy Zoo -- yet although most of us were familiar with Galaxy Zoo, few of us knew that. Why so secretive? They should be trumpeting achievements like that.

How many times have you volunteered for a survey or study, then wondered for years afterward how the results came out? Researchers never contact the volunteers when the paper is finally published. It's frustrating and demotivating; it makes you not want to volunteer again. Lots of us sign up because we're curious about the science -- but that means we're also curious about the results.

With citizen science projects, this is particularly easy. Set up a mailing list or forum (or both) to discuss results and announce when papers are published. Set up a Twitter account and a Facebook group to announce new papers to anyone who wants to follow. This is the age of Web 2.0, folks -- there's no excuse for not communicating.

I don't know if NASA will listen to our ideas. But I hope they do. Moon Zoo promises to be a terrific project ... and the more of these principles they follow, the more dedicated volunteers they'll get and that will make the project even better.

Tags: science, astronomy, open source, crowdsourcing
[ 19:25 Feb 06, 2010    More science/astro | permalink to this entry ]

A new theory of orbital dynamics

This PG&E billboard just went up down the street from where I live.

"Solar Power: Making planets orbit and bagels toast."

And here all this time I'd been under the impression that orbits had mostly to do with gravity. Somehow I'd missed the influence of light pressure when writing my orbital software.

Or is the sun's gravitational influence considered a part of "solar power"? Can we look forward to the upcoming generation of gravitovoltaic solar cells?

Tags: humor, astronomy
[ 19:13 Sep 18, 2009    More humor | permalink to this entry ]

JS Jup: now, with variable animation speed

I wrote last week about the sorts of programmer compulsions that lead to silly apps like my animated Javascript Jupiter. I got it working well enough and stopped, knowing there were more features that would be easy to add but trying to ignore them.

My mom, immediately upon seeing it, unerringly zeroed in on the biggest missing feature I'd been trying to ignore. "Can you make it go faster or slower?"

I put it off for a while, but of course I had to do it -- so now there are Faster and Slower buttons. It still goes by hour jumps, so the fastest you can go is an hour per millisecond. Fun to watch. Or you can slow it down to 1 hour per 3600000 milliseconds if you want to see it animate in real time. :-)

Tags: programming, astronomy, javascript
[ 10:42 May 31, 2009    More programming | permalink to this entry ]

Javascript Jupiter

It's a sickness, I tell you.

It's not like I needed another Jupiter's moons application. I've already written more or less the same app for four platforms.

I don't use the Java web version, Juplet, very much any more, because I often have Java disabled or missing. And I don't use my Zaurus any more so Juplet for Zaurus isn't very relevant. But I can always call up my Xlib or PalmOS Jupiter's moons app if I need to check on those Galilean moons. They work fine. Another version would be really pointless. A waste of time.

So it should have been no big deal when, during the course of explaining to someone the difference between Java and Javascript, it suddenly occurred to me that it would be awfully easy to re-implement that Java Juplet web page using Javascript, HTML and CSS. I mean, a rational person would just say "oh, yeah, I suppose that's true" and go on with life.

But what I'm trying to say is that programming isn't a career path, or a hobby, or a field of academic study. It's a disease. It's a compulsion, where, sometimes, just realizing that something could be done renders you unable to think about anything else until you just ... try ... just a few minutes ... see how well it works ... oh, wow, that really looks a lot better than the Java version, wouldn't it look even nicer if you just added in this one other little tweak ... but wait, now it's so close to working, I bet it wouldn't be all that hard to take the Java class and turn it into ...

... and before you know it, it's tomorrow and you have something that's almost a working app, and it's just really a shame to get that far and not finish it at least to the point where you can share it.

But then, Javascript and web pages are so easy to work on that it really isn't that much extra work to add in some features that the old version didn't have, like an animate button ...

... and your Saturday morning is gone forever, and there's not much you can do about that, but at least you have a nice animated Jupiter's moons (and shadows) page when the sickness passes and you can finally think about other things.

Tags: programming, astronomy, javascript
[ 20:10 May 23, 2009    More programming | permalink to this entry ]

Pluto Visits the States

This is a reprinting of an article I wrote for my monthly planet column in the SJAA Ephemeris:

Is Pluto a planet, or not? Maybe you caught the news last month that Illinois, birthplace of Clyde Tombaugh, has declared Pluto a planet. It joins New Mexico, Tombaugh's longtime home, which made a similar declaration two years ago.

When I first heard about the New Mexico resolution, I was told that they had declared that Pluto would be a planet within the state's boundaries. That made me a bit curious: would Pluto even fit inside New Mexico? I looked it up: Pluto has a diameter of 2300km, while New Mexico is about 550km in longitude and a bit more in latitude. Not even close (see Figure 1). Too bad -- I liked the image of Pluto and Charon coming to visit and hang out with friends. Though at Pluto's orbital velocity (it takes it just under 248 years to complete its 18 billion kilometer orbit, meaning an average speed of 23 million km/year or 63,000 km/day) and its current distance of about 32 AU (4.8 billion km), it whould take it about 207 years to get here.

But it turns out that's not what the resolution said anyway. Both states' resolutions said roughly the same thing:

BE IT RESOLVED BY THE LEGISLATURE OF THE STATE OF NEW MEXICO that, as Pluto passes overhead through New Mexico's excellent night skies, it be declared a planet and that March 13, 2007 be declared "Pluto Planet Day" at the legislature.

RESOLVED, BY THE SENATE OF THE NINETY-SIXTH GENERAL ASSEMBLY OF THE STATE OF ILLINOIS, that as Pluto passes overhead through Illinois' night skies, that it be reestablished with full planetary status, and that March 13, 2009 be declared "Pluto Day" in the State of Illinois in honor of the date its discovery was announced in 1930.

So the law applies to anyone (though it's probably not enforceable outside state boundaries) -- but only when Pluto is overhead in New Mexico or Illinois.

But wait -- does Pluto ever actually pass overhead in those states?

New Mexico stretches from 31.2 to about 37 degrees latitude, while Illinois spans 36.9 to 42.4. Right now Pluto is in Sagittarius, with a declination of -17° 41'; there's no way anyone in the US is going to see it directly overhead this year. Worse, it's on its way even farther south. It won't cross into the northern hemisphere until the beginning of 2111. But how far north will it go?

My first thought was to add Pluto's inclination -- 17.15 degrees, very high compared to other planets -- to the 23 degrees of the ecliptic to get 40.4°. Way far north -- no problem in either state! But unfortunately it's not as simple as that.

It turns out that when Pluto gets to its maximum north inclination, it's in Bootes (bet you didn't know Bootes was a constellation of the zodiac, did you? It's that 17° inclination that puts Pluto just past the Virgo border). That'll happen in February of 2228.

But in the Virgo/Bootes region, the ecliptic is 8° south of the equator, not 23° north. So we don't get to add 23 and 17; in fact, Pluto's declination will only be about 7.3° north. That's no help!

To find the time when Pluto gets as far north as it's going to get, you have to combine the declination of the ecliptic and the angle of Pluto above the ecliptic. The online JPL HORIZONS simulator is very helpful for running data like that over long periods -- much easier than plugging dates into a planetarium program. HORIZONS told me that Pluto's maximum northern declination, 23.5°, will happen in spring of 2193.

Unfortunately, 23.5° isn't far enough north to be overhead even from Las Cruces, NM. So Pluto, sadly, will never be overhead from either New Mexico or Illinois, and thus by the text of the two measures, it will never be a planet.

With that in mind, I'm asking you to support my campaign to persuade the governments of Ecuador and Hawaii to pass resolutions similar to the New Mexico and Illinois ones. Please give generously -- and hurry, because we need your support before April 1!

Tags: science, astronomy, pluto, humor, writing
[ 19:09 Apr 01, 2009    More science/astro | permalink to this entry ]

For Ada Lovelace Day: Vera Rubin

For Ada Lovelace Day I'm honoring Vera Rubin.

In 1948, when she applied to Princeton as an aspiring astronomy grad student, they wouldn't let her in because women weren't allowed. (They finally started admitting women in 1975.) Fortunately, Cornell was more accommodating.

For her thesis, she worked on a project that seemed useful and uncontroversial. She took other people's data on the redshifts of galaxies, and catalogued them to see how fast they were all moving away from us.

Except something unexpected happened. She found that galaxies in one direction weren't moving away as fast as galaxies in the other directions. The universe was supposed to be expanding evenly in all directions -- but that's not what her data showed.

In 1950 she presented her results to a conference of the American Astronomical Society. The results were not promising. Famous astronomers she'd read about but never met stood up in the audience to ridicule her paper and say it couldn't be true. No one would publish her master's thesis. It wasn't a good start to her career. She decided to try to find something less controversial to study.

Her husband finished at Cornell and moved to Washington, D.C.. Rubin and her new baby moved with him, and she enrolled as a PhD student at Georgetown. They had two children by now; her parents watched the kids while she took night classes.

She hooked up with George Gamow at Georgetown. He called her to ask her about her research -- but said they'd have to talk in the lobby, not in his office, because women weren't allowed in the office area of the building.

After Rubin finished her PhD with Gamow in 1954, Her experience trying to present her 1950 paper made her leery of confrontation. She's said, "I wanted a problem that no one would bother me about." Working with Kent Ford at the Carnegie Institute in Washington, she helped design a super-sensitive digital spectrograph, and they set out to make a huge catalog of data on boring "normal" galaxies no one else was looking at. They started with the Andromeda galaxy, M31, the closest large galaxy to us (and the easiest one to see with the naked eye, if you go somewhere away from city lights).

And right away they found something weird. Normally, you'd expect the outer parts of the galaxy to be rotating a lot slower than the inner parts. Think of our solar system: Mercury goes around the sun really fast (a Mercury year is only 88 days), Earth goes not quite as fast, and when you get all the way out to Pluto, it takes 247 years to go around the sun once. It's not just that it has farther to go to make a circuit around the sun; it's that the sun's influence is so weak way out there that Pluto goes a lot slower in its orbit than we do.

Galaxies should be the same way: stars in the center should just whiz around in no time, while stars at the outer edge take forever.

But Rubin and Ford found that Andromeda wasn't like that. When they started looking at the stars farther out, they were all going about the same speed. If anything, the stars at the edge were going a little faster than the stars in the center.

That made no sense. It didn't follow any normal model of gravity or galaxy formation. They published their results in 1970, but no one took them seriously. They decided that maybe something was wrong, or their equipment was faulty. They decided to try studying a simpler problem: just measure the redshift of some faint galaxies and make a catalog of those.

That went well for a while -- except that pretty soon, they ran into the same thing Rubin had discovered as a graduate student back at Cornell. Galaxies in the direction of Pegasus were moving away from us at a different speed from galaxies in other parts of the sky. She and Ford tried again to present that, but the reaction wasn't any more positive this time.

Discouraged, they went back to trying to measure galaxy rotation, hoping Andromeda had just been a fluke. But every galaxy they studied looked the same as Andromeda, with the stars far out near the edge of the galaxy rotating as fast, or faster, than the stars near the hub.

There were only two possible explanations. Either the law of gravity doesn't work the way we think it does ... or there's a lot more matter inside a galaxy than what we see with a telescope.

When they tried to present this result, no one believed it, so they kept measuring more galaxies, always with the same result.

By 1985, they had enough evidence that people finally started paying attention. As their results got talked about more and taken more seriously, they came up with a name for the extra mass that makes the galaxy rotation flat: "dark matter". Yes, the dark matter you hear about that apparently makes up more than 90% of all matter in the universe. Not a bad discovery for someone who was just trying to lay low and catalogue a lot of data that might be useful to other people! (Rubin's first graduate project, on the rotation of the universe, has also since been vindicated.)

Vera Rubin is still working at the Department of Terrestrial Magnetism. Her intellect, hard work and perseverance are an inspiration, and I salute her on Ada Lovelace Day. (You can read other people's Ada Lovelace Day posts in the Ada Lovelace Day Collection.)

Tags: AdaLovelaceDay09, chix, astronomy
[ 19:12 Mar 24, 2009    More science/astro | permalink to this entry ]

LCA 2009 Tuesday

I missed a lot of the miniconf talks on Tuesday because I wanted to make some last-minute changes to my talk. But I do want to comment on one: Simon Greener's talk on "A Review of Australian Geodata Providers." Of course, I'm not in Australia, but it was quite interesting to hear how similar Australia's problematic geodata siguation is to the situation in the US. His presentation was entertaining, animated and I learned some interesting facts about GPS and geodata in general.

And Dave and I got another good astronomy opportunity with the dark skies at Peppermint Bay at the Speakers' Dinner. Despite occasional intrusive clouds we managed to get a great view of the Large Magellanic Cloud and a decent view of the small one, as well as eta Carinae and the star clouds between Crux and Carina. Pity I'd forgotten to bring my thumpin' travel optics that I'd been using the previous evening: a 6x20 monocular.

Tags: lca2009, linux.conf.au, astronomy, mapping
[ 16:15 Jan 20, 2009    More conferences/lca2009 | permalink to this entry ]

LCA 2009 Monday

On day one of LCA 2009, I divided my time between the LinuxChix and Kernel miniconfs.

In the morning, Paul McKenney, in "Why is parallel Programming Hard?", discussed some of the background of parallel programming research, then gave an entertaining demonstration of instruction overhead using a roll of toilet paper. Each square represented one clock cycle -- he estimated there were a few hundred clock cycles in the full roll -- and he had audience members unroll the roll carefully, passing it from one person to the next. It took a long time.

Over at the LinuxChix miniconf, Jacinta Richardson gave a wonderfully entertaining (and useful) talk "On Speaking". She explained how to hack audience members' brains, particularly the corpus callosum and the hippcampus, by using emotion, visual images and suspenseful stories to give your audience whole-brain entertainment.

After Jacinta's talk we spent some time going around the room introducing ourselves, and speakers got a chance to plug their upcoming talks.

I skipped the panel on Geek Parenting (not being a parent) to go back to the kernel miniconf's "Problem Solving Hour". Questions involved network performance, solid state disk performance, how to debug crashes, tracing (the moderator commented that if you're thinking of getting involved in the kernel effort but aren't quite sure what to do, there's a huge need for better tracing and performance analysis tools), solid-state disks (someone plugged the talk on that subject on Friday) and similar interesting topics.

I asked about an overheating problem I've been having with my laptop. I mentioned that even in single-user mode, the CPU temperature keeps going up, so I was pretty sure it was a kernel and not userspace issue. Matthew Garrett said that a lot of drivers are optimized for a normal use case -- meaning X -- and may work very poorly in text mode. You can have something that's overheating in single-user mode, then you start X and a bunch of power management systems kick in and the temperature actually goes down. So how do you figure out what's causing a temperature problem? Open up the laptop when it's hot, poke around then figure out what's hot. Then debug that component.

Lunch was a lovely BBQ provided by Google.

After lunch, Matthew Garrett, in "How I learned to stop worrying and love ACPI", was entertaining, as all his talks are. I'm not sure I actually learned much in the way of practical advice for helping ACPI work better on my machines, but at least I learned lots of new ways in which ACPI sucks more than I ever realized.

Then it was back to LinuxChix for a workshop on getting schoolgirls more interested in IT. We saw short presentations from the four workshop leaders, then split into groups -- our group went outside and sat in the hazy sunshine and talked about how to get girls, teachers, parents and school IT staff on board.

After tea, all the LinuxChix groups reported back on the discussions and there was a full-room discussion on how to get involved with educational programs like that. Then we ended with lightning talks; I got roped into giving one, so I didn't take notes on the rest, but they were all fun and interesting.

Then in the evening, after dinner, we found a spot somewhat sheltered from the lights of the hotel for some quick astronomy before bed. The sky was hazy and picking up lots of sky glow from a light beam shining from the hotel, but fortunately the sky around the Southern Cross was clear. We found both the Large and Small Magellanic clouds, as well as Eta Carina and some other clusters around the Southern Cross. A lovely view, unmatched by anything I saw from around Sydney or Melbourne. Tasmania definitely wins for stargazing!

Tags: lca2009, linux.conf.au, astronomy
[ 04:17 Jan 19, 2009    More conferences/lca2009 | permalink to this entry ]

Upheaval Dome: New research confirms impact theory

Kurt Fisher wrote to draw my attention to the latest Lunar Photo Of the Day (LPOD), a lovely shot he made of one of my favorite places anywhere, Upheaval Dome in Utah's Canyonlands National Park.

Upheaval Dome has long been strongly suspected to be a massive, eroded impact crater, but the LPOD highlights a study that finally puts this (non-)controversy to rest, Elmar Buchner and Thomas Kenkmann's Upheaval Dome, Utah, USA: Impact origin confirmed, documenting shocked quartz grains in the Kayenta sandstone of Upheaval's outer ring.

It's about time -- it's been pretty clear for many years that this structure was an impact formation, not a collapsed salt dome (the relative lack of salt in the core might have been a clue) but the park service doesn't seem to have gotten the message, giving equal weight to the salt-dome theory in all its Canyonlands literature and signs. Perhaps the Buchner and Kenkmann paper will finally convince them.

Reading about this gave me the push I needed to update my own Upheaval Dome page, adding links to the latest research and to the excellent Upheaval Dome Bibliography Kurt has put together. My page also badly needed a bigger view of the crater itself, so I stitched together a quick panorama of the view from the rim that I'd shot on a trip several years ago but never assembled.

Tags: geology, astronomy, trails, impact crater
[ 12:15 Nov 29, 2008    More science/geology | permalink to this entry ]

Cleaning up the edges of Moonroot's transparent images

I wrote moonroot more to figure out how to do it than to run it myself. But on the new monitor I have so much screen real estate that I've started using it -- but the quality of the images was such an embarrassment that I couldn't stand it. So I took a few minutes and cleaned up the images and made a moonroot 0.6 release.

Turned out there was a trick I'd missed when I originally made the images, years ago. XPM apparently only allows 1-bit transparency. When I was editing the RGB image and removing the outside edge of the circle, some of the pixels ended up semi-transparent, and when I saved the file as .xpm, they ended up looking very different (much darker) from what I had edited.

Here are two ways to solve that in GIMP:

1. Use the "Hard edge" option on the eraser tool (and a hard-edged brush, of course, not a fuzzy one).
2. Convert the image to indexed, in which case GIMP will only allow one bit's worth of transparency. (That doesn't help for full-color images, but for a greyscale image like the moon, there's no loss of color since even RGB images can only have 8 bits per channel.)

Either way, the way to edit a transparent image where you're trying to make the edges look clean is to add a solid-color background layer (I usually use white, but of course it depends on how you're going to use the image) underneath the layer you're trying to edit. (In the layers dialog, click the New button, chose White for the new layer, click the down-arrow button to move it below the original layer, then click on the original layer so your editing will all happen there.)

Once you're editing a circle with sharp edges, you'll probably need to adjust the colors for some of the edge pixels too. Unfortunately the Smudge tool doesn't seem to work on indexed images, so you'll probably spend a lot of time alternating between the Color Picker and the Pencil tool, picking pixel colors then dabbing them onto other pixels. Key bindings are the best way to do that: o activates the Color Picker, N the Pencil, P the Paintbrush. Even if you don't normally use those shortcuts it's worth learning them for the duration of this sort of operation.

Or use the Clone tool, where the only keyboard shortcut you have to remember is Ctrl to pick a new source pixel. (I didn't think of that until I was already finished, but it works fine.)

Tags: programming, astronomy, gimp
[ 14:48 Nov 16, 2008    More gimp | permalink to this entry ]

Requesting no window decorations (and moonroot 0.4)

Someone on #openbox this morning wanted help in bringing up a window without decorations -- no titlebar or window borders.

Afterward, Mikael commented that the app should really be coded not to have borders in the first place.

Me: You can do that?

Turns out it's not a standard ICCCM request, but one that mwm introduced, MWM_HINTS_DECORATIONS. Mikael pointed me to the urxvt source as an example of an app that uses it.

My own need was more modest: my little moonroot Xlib program that draws the moon at approximately its current phase. Since the code is a lot simpler than urxvt, perhaps the new version, moonroot 0.4, will be useful as an example for someone (it's also an example of how to use the X Shape extension for making non-rectangular windows).

Tags: programming, xlib, astronomy, window managers
[ 11:06 Oct 20, 2008    More programming | permalink to this entry ]

Linux Planet: Linux Astronomy part III: Stellarium and Celestia

Part III in the Linux Astronomy series on Linux Planet covers two 3-D apps, Stellarium and Celestia.

Writing this one was somewhat tricky because the current Ubuntu, "Hardy", has a bug in its Radeon handling and both these apps lock my machine up pretty quickly, so I went through a lot of reboot cycles getting the screenshots. (I found lots of bug reports and comments on the web, so I know it's not just me.) Fortunately I was able to test both apps and grab a few screenshots on Fedora 8 and Ubuntu "Feisty" without encountering crashes. (Ubuntu sure has been having a lot of trouble with their X support lately! I'm going to start keeping current Fedora and Suse installs around for times like this.)

Tags: writing, astronomy, linux, ubuntu, bugs
[ 21:10 Sep 22, 2008    More writing | permalink to this entry ]

Linux Planet: Linux Astronomy part II: XEphem

I have a new article on XEphem on Linux Planet, following up to the KStars article two weeks ago: Viewing the Night Sky with Linux, Part II: Visit the Planets With XEphem.

Tags: writing, astronomy, linux
[ 10:50 Sep 12, 2008    More writing | permalink to this entry ]

Writing for Linux Planet: Stargazing with KStars

I have an article on Linux Planet! The first of many, I hope. At least the first of a short series on Linux astronomy programs, starting with the one that's easiest to use: KStars. It's oriented toward binocular observing, with suggestions for good targets for beginners.

Viewing the Night Sky with Linux, Part I: KStars

Tags: writing, astronomy, linux
[ 21:46 Aug 28, 2008    More writing | permalink to this entry ]

Setting app name and class in Xlib

I was looking at Dave's little phase-of-the-moon Mac application, and got the urge to play with moonroot, the little xlib ditty I wrote several years ago to put a moon (showing the right phase) on the desktop.

I fired it up, and got the nice moon-shaped window ... but with a titlebar. I didn't want that! Figuring out how to get rid of the titlebar in openbox was easy, just

<application name="moonroot">
    <decor>no</decor>
    <desktop>all</desktop>
</application>

... but it didn't work! A poke with xwininfo showed the likely cause: instead of "moonroot", the window was listed as "Unnamed window". Whoops!

A little poking around revealed three different ways to set "name" for a window: XStoreName, XSetClassHint (which sets both class name and app name), and XSetWMName. Available online documentation on these functions was not very helpful in explaining the differences; fortunately someone hanging out on the openbox channel knew the difference (thanks, Crazy_Hopper). Thus:

• XSetWMName sets a property called XA_NAME which is primarily used to update the window's titlebar. Note that this may be more than the app name (for instance, Firefox puts the title of the current page in the titlebar). To use XSetWMName, you have to set up and populate an XTextProperty structure, which first requires that you set up a string list then run XStringListToTextProperty -- not difficult but it's several annoying steps.
• XStoreName is a shortcut to XSetWMName, a way to set the XA_NAME (titlebar name) in one step.
• XSetClassHint sets two properties at once: a name hint and a class hint. This is the name and class that the window manager uses for directives like suppressing the titlebar.

I didn't see much in the way of example code for what an app ought to do with these, so I'll post mine here:

    char* appname;
    XClassHint* classHint;
[ ... ]
    if (argv && argc > 1)
        appname = basename(argv[0]);
    else
        appname = "moonroot";

    /* set the titlebar name */
    XStoreName(dpy, win, appname);

    /* set the name and class hints for the window manager to use */
    classHint = XAllocClassHint();
    if (classHint) {
        classHint->res_name = appname;
        classHint->res_class = "MoonRoot";
    }
    XSetClassHint(dpy, win, classHint);
    XFree(classHint);

And if anyone is interested in my silly moon program, it's at moonroot-0.3.tar.gz. moonroot gives you a large moon, moonroot -s gives a smaller one. I'm not terribly happy with its accuracy and wasted too much time today fiddling with it and verifying that it's doing the right time conversions. All I can figure is that the approximation in Meeus' Astronomical Algorithms is way too approximate (it's sometimes off by more than a day) and I should just rewrite all my moon programs to calculate moon phase the hard (and slow) way.

Tags: programming, xlib, astronomy
[ 20:15 Mar 18, 2008    More programming | permalink to this entry ]

Bright naked-eye comet: 17/P Holmes

I finally got a chance to take a look at Comet 17/P Holmes. I'd been hearing about this bright comet for a couple of days, since it unexpectedly broke up and flared from about 17th magnitude (fainter than most amateur telescopes can pick up even in dark skies) to 2nd magnitude (easily visible to the naked eye from light-polluted cities). It's in Perseus, so only visible from the northern hemisphere, pretty much any time after dark (but it's higher a little later in the evening).

And it's just as bright as advertised. I grabbed my binoculars, used a finder chart posted by one of our local SJAA members, and there it was, bright and obviously fuzzy. Without the binoculars it was still easy to see, and still noticably fuzzy.

So I dragged out the trusty 6" dobsonian, and although it has no visible tail, it has lots of structure. It looked like this:
It has a stellar nucleus, a bright inner area (the coma?) and a much larger, fainter outer halo. There's also a faint star just outside the coma, so it'll be fun (if we continue to get holes in the clouds) to see how fast it moves relative to that star. (Not much motion in the past hour.)

It's nice to have a bright comet in the sky again! Anyone interested in astronomy should check this one out in the next few days -- since it may be in the process of breaking up, there's no telling how long it'll last or what will happen next. Grab some binoculars, or a 'scope if you have one, and take a look.

Tags: science, astronomy
[ 21:51 Oct 28, 2007    More science/astro | permalink to this entry ]

Mercury Transits and Titan Occultations

Mercury transited the sun today. The weather forecast predicted rain, and indeed, I awoke this morning to a thick overcast which soon turned to drizzle. But miraculously, ten minutes before the start of the transit the sky cleared, and we were able to see the whole thing, all five hours of it (well, we weren't watching for the whole five hours -- the most interesting parts are the beginning and end).

I had plenty of practice with solar observing yesterday, showing the sun to a group of middle school girls as part of an astronomy workshop. This is organized by the AAUW, the same group that runs the annual Tech Trek summer science girls' camps. (The Stanford Tech Trek has a star party, which is how I got involved with this group.) It's the second year I've done the astronomy workshop for them; this year went pretty smoothly and everybody seemed to have a good time observing the sun, simulating moon phases, learning about the Doppler effect and plotting relative distances of the planets on a road map.

But what I really wanted to write about was the amazing video shown by last weekend's SJAA speaker, Dr. Ivan Linscott of Stanford. As one of the team members on the New Horizons mission to Pluto, he was telling us about Pluto's tenuous atmosphere. There isn't a lot of information on Pluto's atmosphere yet, but one of the goals of New Horizons is to take readings as Pluto occults the sun to see how sunlight is refracted through Pluto's atmosphere.

But that's no problem: it turns out we've already done more challenging occultation studies than that. Back in December 2001, Titan occulted a binary star, and researchers using Palomar's Adaptive Optics setup got a spectacular video of the stars being refracted through Titan's atmosphere as the occultation progresses.

This is old news, of course, but most of us hadn't seen it before and everyone was blown away. Remember, this is a video from Earth, of the atmosphere of a moon of Saturn, something most Earth-based telescopes would have trouble even resolving as a disk. Watch the Titan occultation video here.

Tags: science, astronomy
[ 22:38 Nov 08, 2006    More science/astro | permalink to this entry ]

Pluto is too a planet

The BBC had a good article today about the International Astronomical Union vote that demoted Pluto from planet status.

It was fairly obvious that the previous proposal, last week, that defined "planet" as anything big enough that its gravity made it round, was obviously a red herring that nobody was going to take very serious. Fercryinoutloud, it made the asteroid Ceres a planet, as well as Earth's moon (in a few billion years when it gets a bit farther away from us and ceases to be considered a moon).

But apparently there were several other dirty tricks played by the anti-Pluto faction, and IAU members who weren't able to be in the room at the time of the vote are not happy and are spoiling for a rematch. The new definition doesn't make much more sense than the previous one, anyway: it's based on gravitationally sweeping out objects from an orbit, but that also rules out Earth, Mars, Jupiter and Neptune, all of which have non-satellite objects along their orbits.

And of course the public is pretty upset about it for sentimental, non-scientific reasons. Try searching for Pluto or "Save Pluto" on Cafe Press to see the amazing selection of pro-Pluto merchandise you can buy barely a day after the IAU decision. (Personally, I want a Honk if Pluto is still a planet bumper sticker.)

It'll be interesting to see if the decision sticks.

So do I have a viable definition of "planet" which includes Pluto but not Ceres or the various other Kuiper belt objects which are continually being discovered?

Why, no, I don't. But the discussion is purely semantic anyway. Whether we call Pluto a planet doesn't make any difference to planetary science. But it does make a difference to an enormous collection of textbooks, museum exhibits, and other science-for-the-public displays.

Pluto is big enough to have been discovered in 1930, back in the days before computerized robotic telescopes and satellite imaging; it's been considered a planet for 76 years. There's no scientific benefit to changing that, and a lot of social and political reason not to -- especially now with New Horizons headed there to give us our first up-close look at what Pluto actually looks like.

There are two possible bright notes to the Pluto decision. First, Mark Taylor pointed out that it has become much easier to observe all the planets in one night, even with a very small telescope or binoculars.

And second, maybe Christine Lavin will make a new updated version of her song Planet X and go on tour with it.

Tags: science, astronomy
[ 21:56 Aug 25, 2006    More science/astro | permalink to this entry ]

Dark Side of the Moon; M51 Supernova

Yesterday was the annual Fremont Peak Star-b-q. This year the weather managed to be fairly perfect for observing afterward: the fog came in for a while, making for fairly dark skies, and it wasn't too cold though it was a bit breezy. It was even reasonably steady.

I had my homebuilt 8" dob, while Dave brought his homebuilt 12.5". Incredibly, we were all alone in the southwest lot: the most Star-b-q was fairly lightly attended, and most of the handful who stayed to observe afterward set up at Coulter row.

The interesting sight of the evening was the supernova in M51 (the Whirlpool galaxy). It was fairly easy in the 12.5" once we knew where to look (Mike Koop came over to visit after looking at it in the 30"), and once we found it there all three of us could see it in the 8" as well.

We had excellent views of Jupiter in the 8", with detail in the red spot, the thin equatorial band easily visible, and long splits in both the northern and southern equatorial bands. I didn't make any sketches since a family wandered by about then so I let them look instead.

We also had lovely low-power views of Venus and crescent Mercury, and we spent some time traversing detail on the dark side of the slim crescent moon due to the excellent earthshine. All the major maria were visible, and of course Aristarchus, but we could also see Plato, Sinus Iridum, Kepler, Copernicus and its ray system, Tycho (only in the 12" -- the 8" was having glare problems that close to the lit part of the moon) and one long ray from Tycho that extended across Mare Nubium and out to near Copernicus. Pretty good for observing the "dark" side!

Neither of us was able to find Comet Tempel-1 (the Deep Impact comet), even with the 12.5". But after moonset I picked up the Veil and North American in the 8" unfiltered (having left my filters at home), and we got some outstanding views of the nebulae in Sagittarius, particularly the Trifid, which was showing more dust-lane detail without a filter than I've ever seen even filtered.

It was a good night for carnivores, too. We saw one little grey fox cub trotting up the road to the observatory during dinner, and there was another by the side of the road on the way home. Then, farther down the road, I had to stop for three baby raccoons playing in the street. (Very cute!) They eventually got the idea that maybe they should get off the road and watch from the shoulder. The parents were nowhere to be seen: probably much more car-wise than their children (I don't often see raccoon roadkill). I hope the kids got a scolding afterward about finding safer places to play.

Tags: science, astronomy
[ 22:31 Jul 10, 2005    More science/astro | permalink to this entry ]

The Game of Telephone

Remember the game of "Telephone" when you were a kid? Everybody gets in a big circle. One kid whispers a message in the ear of the kid next to them. That kid repeats the message to the next kid, and so on around the circle. By the time the message gets back to the originator, it has usually changed beyond recognition.

Sometimes the Internet is like that.

Background: a year and a half ago, in August 2003, there was an unusually favorable Mars opposition. Mars has a year roughly double ours, so Mars "oppositions" happen about every two years (plus a few months). An opposition is when we and Mars are both on the same side of the sun (so the sun is opposite Mars in our sky, and Mars is at its highest at midnight). We're much closer to Mars at opposition than at other times, and that makes a big difference on a planet as small as Mars, so for people who like to observe Mars with a telescope, oppositions are the best time to do it.

The August 2003 opposition was the closest opposition in thousands of years, because Mars was near its perihelion (the point where it's closest to earth) at the time of the opposition. Much was made of this in the press (the press loves events where they can say "best in 10,000 years") to the point where lots of people who aren't normally interested in astronomy decided they wanted to see Mars and came to star parties to look through telescopes.

That's always nice, and we tried to show them Mars, though Mars is very small, even during an opposition. The 2003 opposition wasn't actually all that favorable for those of us in northern hemisphere. because Mars was near the southernmost part of its orbit. That means it was very low in the sky, which is never good for seeing detail through a telescope. Down near the horizon you're looking through a lot more of Earth's atmosphere, and you're down near all the heat waves coming off houses and streets and even rocks. That disturbs the view quite a bit, like trying to see detail on a penny at the bottom of a swimming pool.

This year's opposition, around Halloween, will not be as close as the 2003 opposition, but it's still fairly close as oppositions go. Plus, this year, Mars will be much farther north. So we're expecting a good opposition -- weather permitting, both on Earth, which is sometimes cloudy in November, and on Mars, where you never know when a freak dust storm might appear.

Which brings me back to the game of Telephone.

A few weeks ago I got the first of them. An email from someone quoting a message someone had forwarded, asking whether it was true. The message began:

The Red Planet is about to be spectacular! This month and next, Earth is catching up with Mars in an encounter that will culminate in the closest approach between the two planets in recorded history.

and it ended:

Share this with your children and grandchildren. NO ONE ALIVE TODAY WILL EVER SEE THIS AGAIN

(sic on the caps and the lack of a period at the end).

I sent a reply saying the email was two years out of date, and giving information on this year's Mars opposition and the fact that it may actually be better for observing Mars than 2003 was. But the next day I got a similar inquiry from someone else. So I updated my Mars FAQ to mention the misleading internet message, and the inquiries slowed down.

But today, I got a new variant.

Subject: IS MARS GOING TO BE AS BIG AS THE MOON IN AUGUST?

As big as the moon! That would be a very close opposition!

(Dave, always succinct, said I should reply and say simply, "Bigger." Mars is, of course, always bigger than the moon, even if its apparent size as viewed from earth is small.)

It looks like the story is growing in the telling, in a way it somehow didn't two years ago.

I can't wait to see what the story will have become by August. Mars is going to hit us?

Tags: science, astronomy
[ 10:48 Jun 17, 2005    More science/astro | permalink to this entry ]

Open Source Scientific Image Processing

Anthony Liekens has a wonderful page on open-source Cassini-Huygens image analysis.

A group of people from a space IRC channel took the raw images from the descent of the Huygens probe onto Titan's surface, and applied image processing: they stitched panoramas, created animations, created stereograms, added sharpening and color. The results are very impressive!

I hope NASA takes notice of this. There's a lot of interest, energy and talent in the community, which could be very helpful in analysis of astronomical data. Astronomy has a long history of amateur involvement in scientific research, perhaps more so than any other science; extending that to space-based research seems only a small step.

Tags: science, astronomy
[ 18:30 Jan 17, 2005    More science/astro | permalink to this entry ]

FPOA Star-b-q

Hiking up to the top of Fremont Peak before the FPOA Star-b-q started, we saw the Ghost and the Darkness, squirrel style. A couple of ground squirrels hidden in the tall grass startled as we walked by, and whisked off through the grass, occasionally twitching a tail-tip up above the tops of the grasses but otherwise mostly invisible.

Down in the parking lots, there were some interesting ant or wasp-like insects: furry scarlet head, black thorax, furry scarlet abdomen. The wings were black, too, and they could fly at least a little. No idea what they were.

Learned a new word reading scoops on the way down: Anecdotage, that advanced age where all one does is relate stories about "the good, old days."

Turned out Jeff Moore was the speaker at FPOA. He always gives good talks, but this one was especially good: interpretation of the Mars Rover geologic results so far. Some of his slides showed terrestrial scenes (mostly Death Valley) for comparison with the Martian geologic features, and he mentioned that the terrestrial slides were easy to tell because they were the ones with the pocketknife showing (for scale). So the following morning, I got inspired to whip up a few counterexamples.

Tags: science, astronomy
[ 09:00 Jul 18, 2004    More science/astro | permalink to this entry ]