Ghosts in the Machine: the Astro-Tech AT111EDT...
Jun 13 2015 11:23 AM by jrbarnett
My NexStar 5 Journey
Jun 13 2015 10:29 AM by orion61
Review of the William Optics 102 GT
May 25 2015 11:22 AM by Perseus_m45
Review- Printing Astro photos on Metal with Bay...
Apr 16 2015 02:36 PM by ScenicCityPhoto
Categories See All →
- CN Reports
- User Reviews
- How to . . .
- Observing Skills
- Astronomical History
- Optical Theory
- Vision and Related Experiments
- How to Gain the Support of your Family for your Astronomical Pursuits
- Evaluation Tips
- Special Events
- The Elements
- New Articles in [!monthname!]
- Telescope Articles
- Submit a Review / Article
- Monthly Guides
- Behind the Scenes
- About Us
- Copyright ©
- Terms & Conditions
- Tiny Eyes on the Skies
- From the Editor's Desk
- What's Up . . .
- The Light Cup Journals
- Who is this Super Light Cup?
- Cloudy Nights T-Shirts
- Imaging Contest
- Small Wonders
- Previous Imaging Contest Winners
- This Month's Skies
- Mike's Corner
- The Cloudy Nights Friends and Family Discount
- Uncle Rod's Astro Blog
- Fishing for Photons
- Binocular Universe
- Article Submissions
Introduction to Fishing For Photons
Voice your opinion about this subject in our forums
Before we dive into the meat of things here with the first real entry, it's probably worth spending a bit of time introducing myself and introducing this column. Â First up - who am I? Â Some of you may know me from the software I write. Â I'm the author of PHD Guiding, Nebulosity, DSLR Shutter, and a host of other programs designed to make astrophotography a bit less painful than it can be. Â Others may recognize the name from articles I've written in several astro-mags or talks I've given at various astro-events. Â One or two of you out there may even know me from my day job (which isn't writing software for Stark Labs). Â Of course, the rest have no clue who I am, so for them and for the curious, a bit of a brief history.
I got started in astronomy the way many of us have. Â I got a department-store 'scope (complete with a click-stop variable barlow) and had a look at Jupiter, seeing a few moons and making out two red bands. Â Things progressed from there a bit and when snooping around in my high school, I found an old Criterion 8â€ Newt in need of some love. Â So that I could use it (and cover up for the fact that I was snooping around school closets), I founded an Astronomy Club and we even built a 10â€ Dob there (the school's Head of Discipline was our sponsor; that worked out well!). Â While in high school, I did a â€œsenior projectâ€ on astrophotography back in the days of hand guiding and developing your own film. Â For that project, I bought my first real scope, a Meade MTS-SN8 (their first Schmidt-Newt). Â College just outside of Boston, MA put the kaibosh on the hobby for a bit and that scope stayed in its box for over a decade as I moved around the country from city to city during my Ph.D. and â€œpostdoctoralâ€ years. Â City lights were bright, options to get under dark skies were slim, and I was spending my time doing research, writing papers, and working to become a professor (by day, I try to figure out how memory works in the brain.)
Then, a momentous event happened. Â Folks like Steve Chambers, John Grove, and William Behrens started pushing out ways of modifying webcams or video cams to do long-exposure astrophotography. Â This was incredibly exciting for me and was the spark that re-ignited the hobby. Â I didn't have cash to spend on a â€œrealâ€ astro-cam, DSLRs didn't exist (and would have been too expensive as well), but $50 for a Philips Vesta Pro was something I could swing. Â Modifying the camera involved some soldering skills, but that let me tap into another part of my background.
I grew up around electronics and around testing electronics. Â One of my dad's many jobs was writing for Stereo Review magazine (another way you might have heard my name, as he was also Craig Stark). Â I held a soldering iron before I held a pencil and from a young age, I started helping him test every cassette deck that was reviewed there. Â I'd run many of the tests and be the â€œesteemed listening colleagueâ€ (my young ears could hear things his older ones couldn't) on scores of reviews and started building amplifiers and speakers. Â I also took a keen interest in our first computer, a Northstar Horizon CP/M machine (with 64k of RAM!) and started programming at 10 or 11, teaching myself first by entering in programs from the back of Byte magazine. Â At 14, I managed to convince a local computer shop to hire me as a technician to fix their Kaypro machines and the IBM PCs (we had an IBM PC XT at home by then and my dad had started to work for PC Magazine). Â I took over there as the Service Manager a few years later and continued to work there for several years, even if only when home on college breaks. Â I owe a lot to Reese, the owner there. Â He had faith in that kid, taught me a lot, and gave me room to grow and learn.
I started college thinking I was going to be an astrophysicist, but physics and I didn't get along too well. Â I got by, but it wasn't a match made in heaven by any means. Â I think a lot more like an engineer and I certainly gave electrical engineering and computer science a lot of consideration. Â I even took the â€œif you pass this you can actually make itâ€ programming course in college -- my one official programming course (I'd actually taught a few programming courses while in high school but hadn't taken any.) Â In the term, you learned LISP, 68000 assembly, and C with your final project to write your own version of LISP in C (the language you'd learned only a few weeks earlier). Â It was a brutal course, considered by many to be the toughest in the university, but it was also fun. Â There's something very satisfying about programming. Â It make take you ages to get something to work, but once it does, it just works. Â You can cross that off the list of things to do and can feel like you've actually accomplished something.
But, a career in CS was not to be. I'd discovered something else. Â I figured that if astrophysics wasn't going to work out, I could trade one impossibly complex, impossible to understand system for another and I set out on the path that has led to my career. Â I'm a â€œcognitive neuroscientistâ€, trying to understand how the 10 billion neurons in our brain with their 100 trillion connections give rise to us. Â Specifically, I study how memory works, usually by taking many noisy, moving pictures of peoples' brains (called â€œfMRI scansâ€) hoping to pull out some faint signals from that noise (sound familiar?).
Jump back now to that guy who unboxed his scope after over a decade, now holding a hacked up webcam in his hands. Â He's got the desire to see these faint fuzzies but heck, he's never really even seen M51. Â His background though led him to the point where he's setup in his backyard with a laptop, the scope, and what looks like a pretty poor excuse for a DSO cam. Â A few nights earlier it was a simple webcam and there was no way this could be mistaken for some high-end observatory-grade piece of imaging gear.
I still remember that night. Â Under the glow of the Baltimore City lights, I swung the SN8 over to M42 and found it in the eyepiece (one of, if not the only thing I could find at the time). Â The glow of the Triangulum area was there and not much else - typical of my urban stargazing and typical of why I'd not set things up before. Â I placed the modified webcam in the eyepiece barrel and focused things, seeing no more in these short exposures than I had through the eyepiece. Â Then, I dialed up a few second exposure, waited and the image appeared. Â â€œHoly @#$$@#!!!!!!â€ Â The neighbor's lights went on as they poked their heads out from behind the curtains wondering just what would cause their otherwise quiet neighbor to start shouting profanities in the dark of night. Â Confused though they were, I'm sure many of you have had similar experiences and know just what I felt that night. Â There it was, looking not much worse than film shots I'd seen in books. Â There, before my eyes, were details I'd never seen outside of the shots in magazines or on the posters that had adorned my walls as a kid. Â I could blow out the whole core and see the structure. Â This wasn't some observatory. Â This was me, with my 20 year-old 8â€ scope, in urban skies using a cheap webcam.
After that, I was hooked. Â Scopes changed, mounts changed, and cameras changed many times over. Â After awhile, I started writing software to process the images (I was actually quite close to using my fMRI image tools for this at one point) and that changed from a simple tool to a whole set of programs. Â The one thing that didn't change was the link to the community on the internet. Â Out there, I found people who understood this odd obsession and who were inflicted with the same strange desires (just why do we go out in the cold to loose sleep so we can take pictures in the dark?) Â Out there, I found people who not only understood this, but were willing to help and to teach others who weren't as far along the way as they. Â I owe a lot to these people and to this community.
Having gotten so much from others in the etherial â€œout thereâ€ is one of the main reasons why I am writing this column and it's why I make programs like PHD Guiding free. Â The most common question asked of me is why I don't charge for PHD. Â One real answer is because it's something I could give back to the community. Â This brings me to the one thing I want to make clear to the readers here. Â Yes, I sell one piece of software. Â Proceeds from it fund development of all of the other programs (and yes, let me buy some nice astro toys). Â But, the goal here isn't to sell my software or push it in any way. Â Heck, all but one of the programs are free and even that is fairly low-budget (it costs less than a lot of Plossl eyepieces out there). Â I may use my software from time to time as an example of how things work, but I promise pushing it isn't the goal and I will make every effort to note how it can be done in other programs. Â If it ever comes across as a sales pitch, call me on it. Â
That was a lot of history and background. Â Hopefully, some found it entertaining and I wanted to put it out there as it often helps to know where someone is coming from, especially in on-line communication. Â I'm a scientist and engineer and so I approach things from a different perspective than some. Â You'll at least now know my perspective as I write these columns.
The big question now is, â€œWhat's this column going to be about?â€ Â One big theme will be trying to understand how imaging works so that we can get the best possible pictures. Â I'll leave ideas of composition, framing, etc. to those like Warren Keller who understand these issues better and focus on some of the technical bits. Â The first few entries, for example, will cover the concept of signal to noise as it's fundamental to what we do. Â After that, I have a number of ideas in the queue, some of which are expanded versions of a blog I've been doing for awhile. Â Some entries will be technical, others practical, and we'll hit things like gear reviews as well.
What I'd really like, though, is to get ideas and feedback from the readers (assuming there are any!) Â This means both sending me thoughts and questions for future columns and participating in the forums here. Â One of the things I love about Cloudy Nights here is the collection of forums and the fact that there's one dedicated to discussing articles and reviews put up here. Â Find something I said confusing? Â Put a post up there! Â Think I totally botched something (and yes, at times I will)? Â Put up a post and set the record straight. Â
Cloudy Nights is a wonderful community and I'm incredibly happy to be here. Â I'd like to close by giving a heartfelt thanks to Mike Bieler and Mike Loffland for making all of this possible.