How to Photograph the Milky Way

This summer I’ve been making quite a few wide-angle astronomical photos, especially of the Milky Way. Here are links to a collection of photos taken in June in the San Rafael Swell, and some other miscellaneous astronomical photos.

When I show these photos to people, they often ask how to make similar photos themselves. Here’s a summary of what I’ve figured out so far. For much more advice on astrophotography, I highly recommend Jerry Lodriguss’s site.

To photograph the Milky Way, you need the following:

• A camera. I use Canon’s cheapest digital SLR, the Rebel XS (street price $500). Any other DSLR will probably work fine, except perhaps some of the earliest models which have higher noise levels. There may now be some high-end point-and-shoot cameras that will give acceptable results, but I’m not sure of this; most point-and-shoot cameras can’t take long enough exposures, and even if they could, the noise levels would be unacceptable. Film cameras don’t work well because even the fastest readily available films aren’t as sensitive to dim light as the sensor in a DSLR.
• A wide-angle lens. I’ve invested in a Sigma 20mm f1.8 lens ($520), although the inexpensive 18-55mm zoom lens that came with my camera was good enough to get started. If money is no object, get the Canon 24mm f1.4 ($1700), along with a full-frame Canon 5D ($2500); that’s what the pros seem to use, as far as I can tell.
• A tripod. I got a perfectly usable one at a discount store for $29.
• A dark site. This is the most difficult part for many people. You cannot make decent photos of the Milky Way from a light-polluted city. But here in Utah, there are some very dark sites within a one-hour drive of my urban home. Depending on where you live, you may need to travel farther.

Of course, you also need a clear sky with a view of the Milky Way. From the northern hemisphere, the best views of the Milky Way are in the summer, with the brightest parts in the southern sky.

Before heading out on a dark night, practice with the settings on your camera. Put it in fully manual mode, including manual focus. Set it for a 30-second exposure at ISO 1600, with the lens at its widest aperture (perhaps f3.5 on a zoom lens). Practice turning the display on and off, and turn its brightness down. Set the camera to store images in “raw” format, rather than jpeg. Most importantly, figure out how to manually focus the lens at infinity. Some lenses are conveniently labeled for focusing, but my zoom lens isn’t, so I had to mark the infinity setting (when zoomed out to 18mm) with white tape.

With this preparation, taking the photos should be pretty easy. Turn the display off when you’re pointing the camera (so it doesn’t ruin your eyes’ dark adaptation), then turn it back on to check the settings (30 seconds, ISO 1600, widest aperture) and fire away. It’s hard to compose a photo in the dark, but you can review the composition on the LCD and try again as needed.

After downloading the photos to your computer, use the software that came with the camera to adjust the brightness, contrast, and color balance. With “raw” images you can make some pretty dramatic adjustments without losing quality.

Speaking of quality, there are three factors that limit the amount of detail in a photo of this type:

1. Digital noise, which gets worse at higher ISO settings;
2. Lens aberrations, which blur and dim the edges of the image, and which get worse when the lens is opened to a wide aperture (low focal ratio);
3. The earth’s spinning motion, which turns star images into trails and blurs the Milky Way over time. (In 30 seconds the earth turns by 1/8 of a degree.)

To lessen any one of these problems, you generally need to worsen one of the others. The trick is to make sure that no one of them is much worse than the other two. By all means, experiment with different ISO settings, apertures, and exposure times. I always stop-down my Sigma lens to about f2.8 to reduce aberrations, but stopping-down may not be an option if you’re using a relatively slow zoom lens. I’m happy with ISO 1600, which is the highest setting on my camera. Most of the digital noise disappears when I reduce the photos to screen size, but in long exposures there are always some “hot pixels” which can be manually fixed in Photoshop if necessary.

Even with the most expensive equipment, photos made in this way will not be sharp enough to withstand poster-size enlargements. For example, I’m a big fan of Wally Pacholka’s photos, and I have a framed 36-inch panorama of his in my living room, but it doesn’t show much more detail at that size than in the screen version on his web site.

It’s a nice touch to include foreground scenery in your photos, but if you want more than silhouettes, you’ll need to plan carefully. A small amount of artificial light, from ambient light pollution or even a flashlight, can sometimes illuminate the scenery without ruining the Milky Way. Moonlight is another option, but anything bigger than a crescent moon will brighten the sky too much for a good Milky Way photo, and there are only a few nights each month, and a few hours each of these nights, when the crescent moon is above the horizon after dark. Even then, the moonlight won’t always be shining in the direction you want.

If you don’t want to include foreground scenery in your photos, then life becomes much easier. You can try using a tracking mount to compensate for the earth’s rotation, allowing much longer exposure times. Then you can use a smaller aperture and/or lower ISO setting to reduce problems 1 and 2 above. You can even use a film camera, which is far less expensive but requires additional skills and patience.

Detecting Bad Data

Political numbers geeks learned yesterday that Research 2000, one of the most prolific national political pollsters in recent years, may have been manipulating or even fabricating much of its data. This news comes less than a year after another national pollster, Strategic Vision, was exposed for probable fraud.

The evidence against these pollsters has come mainly from statistical scrutiny of their published results, performed by heroes like Nate Silver and Michael Weissman. But in most cases, you don’t have to be an accomplished sports statistician or a PhD physicist to detect bad data. You just have to care about numbers, and spend some time with them, and use a lot of common sense.

The sad thing is that in America today, hardly anybody cares about numbers except professional scientists and sports enthusiasts. Journalists, in particular, seem to think that their only job is to report both sides of the story--as if there’s no such thing as a fact. Except sports reporters, of course, who have to be extremely careful with facts and figures.

The good news, at the national level, is that the traditional media usually pick up the fraud stories after the bloggers do the actual work. The New York Times wasted no time reporting the Research 2000 accusations on its Caucus blog. If the accusations hold up, we’ll undoubtedly hear more. (Nate Silver will soon be assimilated into the New York Times. Let’s hope these kinds of stories don’t get suppressed in the process.)

Also, at the national level, there’s often enough honest fact-gathering that the frauds don’t make much difference. No single pollster had much impact on Silver’s bottom-line prediction of the outcome of the 2008 presidential election. The danger arises when everyone is relying on a single primary source, like the military or the White House.

At the local level, relying on a single authority is the rule rather than the exception. The Ogden Standard-Examiner almost always prints the word of local government officials as if it were fact, with no questions asked. Despite the detailed exposés on Weber County Forum, the Standard-Examiner has yet to report that the Ogden government manipulated its crime statistics, or that the government’s revenue projections for the Junction development were fraudulently overblown.

In science, fabricating data is the most serious of all crimes. I’ve given failing grades to astronomy students for fabricating their observations (which is usually easy to detect). There are continual allegations of fraud in medical research, where the financial stakes are incredibly high. Fortunately, the list of significant and documented cases of fraud in the physical sciences is extremely short. Although we physical scientists are just as human as everyone else, we know that our peers will tear our work apart if it doesn’t hold up to scrutiny.

APOD Celebrates 15 Years

Astronomy Picture of the Day, one of the very best sites on the Web, is celebrating its 15th anniversary today. My heartfelt thanks go to its devoted authors and editors, Robert Nemiroff and Jerry Bonnell--and to NASA for hosting the site.

APOD’s diversity is remarkable. The pictures include straight photographs, highly processed digital images, graphs, and even paintings. They come from professional astronomers, NASA, dedicated amateurs, scientifically inclined artists, and historical archives. The subjects go beyond pure astronomy to include the space program, earth science, and physics. Each picture comes with a short lesson, written by the editors, full of hyperlinks for those who want to learn more.

Although APOD is pitched to the general public, it’s also extremely useful to those of us who teach introductory astronomy, and to any scientist who needs a daily dose of breadth in this era of hyper-specialization.

Among Web sites, APOD is also remarkable for its simplicity: No banners, no sidebars, no drop-down menus, no fancy fonts. This is the Web as it was originally meant to be, where content takes precedence over presentation, and the hyperlinks are inserted by real human beings. The most noticeable change since 1995 is that the pictures have gotten bigger. They’ve also added Javascript rollovers to annotate some photos, and even an occasional video. And there’s now a linked forum where you can discuss the pictures. But simplicity still prevails.

Collected Works from Weber County Forum, Volume 2

About a year ago I posted a list of my Weber County Forum articles (loosely defined) over the previous three years. Since then the list has approximately doubled in length, so it's time for an update. Here, then, are my contributions since the middle of last June, in reverse chronological order:

• New Developments On and Around Malan's Basin Property (8 June 2010)
• Powder Mountain MOU Hearing Live Blogging (1 June 2010)
• Roosters Celebrates 15 Anniversary (14 May 2010)
• A Sunday Tour of Downtown Ogden (10 May 2010)
• Ogden City Miscellany (9 May 2010)
• 100 Ride in Damp Tour de Drome (1 May 2010)
• Mayor Vetoes Searchlight Ordinance (23 April 2010)
• Ogden's Transit Choices (6 April 2010)
• RAMP Funds Dog Park and Adventure Park, Not Velodrome (27 March 2010)
• Standard-Examiner: 36th Street Tank Closer to Reality (15 February 2010)
  
• Herbert Can Get More Than $10,000 for Political Favors (11 February 2010); follow-up (19 February 2010)
• Live-Blogging the City Council Water Tank Decision (2 February 2010)
• Ogden City Council Report (15 December 2009)
• Standard-Examiner: Candidates' Final Reports Filed (11 December 2009)
• Standard-Examiner Letter: Many Ethical Breaches in Ogden (3 December 2009); follow-up (11 December 2009)
• Live-Blogging the Streetcar Stakeholder Meeting (19 November 2009)
• Standard-Examiner: City OKs Use of Eminent Domain (19 November 2009)
• Bits and Pieces from Last Night's Emerald City Council Meeting (18 November 2009)
• Lifties and Smarties (13 November 2009)
• Is Candidate Mark Hains in Violation of Finance Disclosure Ordinance? (30 October 2009)
• Standard-Examiner: Tax Increment District Extended (14 October 2009)
• Live-Blogging City Council Decision on Junction Tax Increment Extension (13 October 2009)
• Be Honest, Fair, and Conservative (12 October 2009)
• Brief Report on City Council Candidates Forum (6 October 2009)
• Standard-Examiner Editorial Board Afraid of Mayor (28 September 2009); follow-up (3 October 2009)
• Saturday Evening News Roundup (19 September 2009)
• Vision Meets Reality (25 August 2009)
• The Junction: What Next? (7 August 2009)
• Live-Blogging the Big Veto Override (4 August 2009)
• The Junction -- A Good Investment? (29 July 2009)
• Junction 101 (27 July 2009)
• Live-Blogging the Transit Management Committee Meeting (9 July 2009)
• Scott Schwebke Fleshes Out the Budget Veto Story (9 July 2009)
• Court Orders Ogden to Explain Status of Missing Records (7 July 2009)
• Live-Blogging from the Planning Commission Chamber (1 July 2009)
• The Ogden City Run-Around (27 June 2009)
• Live-Blogging from the Emerald City Planning Commission (17 June 2009)

Purge Your Myrtle Spurge

Today’s Salt Lake Tribune has an article about a plant that’s been invading Ogden’s foothills over the last few years. Now I finally know what it’s called: myrtle spurge, euphorbia myrsinites.

A native of southeastern Europe and Asia Minor, myrtle spurge has made its way into Utah’s gardens as an easy-to-grow xeriscape plant. But it is also extremely invasive, spreading into natural areas and crowding out native vegetation. Now that we know the danger, we need to get rid of this enemy before it propagates any further. (Colorado has already banned myrtle spurge; Utah is still a little behind the times.)

Fortunately, myrtle spurge is easy to recognize and to uproot. Look for the low-growing succulent plant with gray-green leaves and yellow flowers and bracts at the tips of the stems. Being sure to wear gloves, gather up the multiple stems in both hands and firmly pull the plant up by its root.

You need to wear gloves, because the sap of the plant can cause a severe allergic reaction in some people. Be sure to wash your hands after touching it, and avoid touching your eyes. A reaction is especially likely in people who are allergic to latex.

This morning I made a good first dent in the myrtle spurge infestation just above the top of 27th Street. If a few others help out and we keep following-up, I’m sure we can purge it from this location. I’ve also seen it growing along the Mt. Ogden Exercise Trail, and I’m told it’s widespread in Ogden Canyon. I don’t know if it’s still feasible to eradicate it from Weber County, but now is the time to try.

And whatever you do, don’t plant this noxious weed in your yard! 

Science and Nature Reading List

Now that school’s out, it’s time for summer reading! Here are a dozen of my favorite science and nature books, recommended to students, colleagues, and friends alike. None of them are especially recent, and in fact, many are books that I first read for fun during graduate school, when I should have been working on my thesis. They’re listed below in approximate order by difficulty, starting with the lightest reading and ending with books that require some effort. None, however, assume any specialized background. Of course there are hundreds of other good science and nature books out there, most of which I haven’t read. I can’t promise that you’ll like all of these as much as I do, but I can promise that each of them is of the very highest quality.

• Encounters with the Archdruid by John McPhee. In this classic from the golden era of environmentalism, McPhee arranges for Sierra Club hero David Brower to spend some quality time with three of his natural enemies: a mining geologist, a resort developer, and a dam builder.
• Desert Solitaire by Edward Abbey. Essays by a hard-nosed realist about the wonders of southern Utah: juniper trees, snakes, clouds, heat, quicksand, tourists, inhabitants, and the encroachment of industrial civilization.


• The Cuckoo’s Egg by Cliff Stoll. My favorite mystery, and all true! A Berkeley hippie astronomer and computer geek discovers that a hacker is breaking into U.S. Government computers. Soon he’s teaching the FBI, CIA, and NSA all about internet security.
• Voodoo Science by Bob Park. An entertaining survey of perpetual motion machines, cold fusion, human space flight, and other things that look like science but aren’t. Written in the same spirit as Martin Gardner’s classic, Fads and Fallacies.
• Basin and Range by John McPhee. The best geology book ever written, which just happens to be about the place where I now live. Filled with clever juxtapositions of human and geologic time. The three sequels are also good: In Suspect Terrain, Rising From the Plains, and Assembling California.
• First Light by Richard Preston. Before the author became famous for writing The Hot Zone, he spent some time hanging out at Palomar Observatory and wrote this delightful book about the astronomers working there.
• 365 Starry Nights by Chet Raymo. Among the hundreds of guides to the night sky, this is by far my favorite. It offers a mini astronomy lesson for each night of the year, with lovingly hand-drawn illustrations. Its only deficiency is the lack of an index, so I created one years ago.
• The Character of Physical Law by Richard Feynman. A set of seven informal lectures by the great theoretical physicist, just as relevant and insightful today as when they were first delivered in the 1960s. If you like this, you’ll also enjoy Feynman’s QED: The Strange Theory of Light and Matter, which presents four more lectures on quantum physics.


• Guns, Germs, and Steel by Jared Diamond. The big picture of human history and prehistory.
• The First Three Minutes by Steven Weinberg. Still the best book on cosmology, written soon after our understanding of the hot early universe became firmly established.
• The Copernican Revolution by Thomas Kuhn. This well-crafted classic on the history of astronomy reminds us that a moving earth was once just as much a threat to some peoples’ belief systems as evolution and global warming are today.
• Gödel, Escher, Bach by Douglas Hofstadter. A weighty masterpiece that interweaves art, music, logic, puzzles, puns, language, molecular biology, and artificial intelligence.

Mobile Computing Growing Pains

The experts have been saying for years that the future of computing is in mobile devices. I ignored them until recently, but now the iPhone, iPad, Kindle, and similar gadgets have gotten my attention. I own an iPhone myself, and I’m beginning to see the potential of mobile platforms for some of my own creative projects. These projects might include textbooks, educational software, and perhaps a trail guide to the local area.

I’ve already written about some of the challenges in delivering a textbook or trail guide on a mobile device. But perhaps the biggest challenge facing any of these projects would be the diversity of competing mobile platforms, and the fact that only a minority of the potential audience owns any one of them.

The obvious solution is to create content in a cross-platform format. This is trivial for a book whose formatting doesn’t matter. But a versatile and attractive electronic format for physics textbooks doesn’t seem to exist, so some custom, platform-dependent coding would probably be required. A good, practical trail guide would require much more coding. And a decent interactive simulation of molecular dynamics or the night sky requires a thousand or more lines of user-interface code.

For several years I’ve been writing these kinds of simulations in Java, which makes them portable to virtually all of today’s desktop and laptop computers--and deliverable over the web. I can’t overstate what a huge advance this is compared to the bad old days when you had to write native code that would run on only one platform. (The native Mac simulations that I wrote between 1985 and 1992 were never widely used, and now they don’t even run on the new Macs.)

Unfortunately, mobile devices don’t run Java applets. Apple’s mobile devices don’t support Java at all. I’m not absolutely wedded to Java, but I’ve been hoping that some kind of usable cross-platform development environment for mobile devices would soon come along. Last week my hopes got a major setback.

Apple has now added the following sentence to its iPhone developer license agreement:

Applications must be originally written in Objective-C, C, C++ or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++ and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

The geek blogs are all abuzz over this new rule, and rightly so. It seems to prohibit virtually any sort of cross-platform development tools, and even restricts what programming languages you can use to develop iPhone apps. Bloggers are inferring that Apple isn’t merely trying to maintain the quality of apps; it’s literally trying to make life difficult for any developer who wishes to deploy an app on multiple mobile platforms.

For a part-time, half-assed developer like me, this move by Apple is devastating. I write software not to make money but to reach a target audience. I have no intention of writing software that can reach only the fraction of that audience that owns a particular device. And I don’t have the time or the resources to port software from one device to another.

Eventually, I suppose, the situation will improve--just like it improved for personal computers when Java came along. Until then, I’ll keep deploying physics simulations as Java applets for personal computers. And I’ll keep publishing books in the tried-and-true format that’s universally readable by all.