Category: Galaxies

What a difference two years makes

What a difference two years makes

I am writing to affirm that progress is inevitable but only with heaps of patience and experimentation.

Two years ago I had the same telescope as today. So what’s the difference? The camera, but not what you think. It was how I was using it.

The top image, the one in color, was taken with the Atik 314E CCD, and the bottom image with the Altair 290M CMOS camera.

Don’t get me wrong. I’m not making a pitch for CCD over CMOS. I am saying that the exposure you choose makes all the difference in the world.

The bottom image used the subframe exposure of 4.7 seconds. Total integration time was 60 minutes. It may not be clear in this small image but it suffered from a severe case of “raining noise”. This was a common ailment of my early images. Without going into a lengthy explanation the cure was to increase the exposure.

The question is always “How far do I increase the exposure?” You can always experiment. A good test is to keep the total integration time the same, in my case 60 minutes, but you can choose 30 minutes if you want to test a greater range of exposures in one evening.

For the Altair 290M and my Bortle 5 skies it turns out that 30 seconds is optimal. You can increase it farther but image quality, signal-to-noise (SNR), won’t improve that much. You can decrease the exposure but then you will see a dramatic drop-off in SNR. If you decrease exposure too far then “raining noise” will rear its ugly head.

Of course the “optimal” exposure is completely dependent on your skies, your telescope, and camera.

The top image was taken with the Atik 314E using a 90-second exposure over 11.6 hours and LRGB filters. The signal-to-noise ratio is high due to the long integration time so comparing it to the bottom image is not entirely fair. The important point is that “raining noise” was never a problem. I chose a 90-second exposure because a CCD has higher Read Noise than a CMOS camera. I could have gone down to 60 seconds but below that the image would have suffered.

M81 Bode’s Galaxy in 11.6 hours

M81 Bode’s Galaxy in 11.6 hours

Telescope: William Optics ZenithStar 71mm f/5.9
Camera: Atik 314E CCD (Read Noise 5.3e-, Full Well Depth 13400e-)
Filters: Optolong LRGB
Mount: Unitron Model 152
Tracking: Self-designed R.A. stepper motor with PPEC on Raspberry Pi 3B
Image Acquisition: Astroberry INDI/Ekos on Raspberry Pi 3B+
Remote Guiding Assistance and Polar Alignment: SharpCap 3.1
Image Processing: AstroPixelProcessor (APP) version 1.076

Over five sessions:
L: 250x90s bin1, 6.25 hours, SNR 17.78
R: 90×85.8s bin2, 2.13 hours, SNR 10.74
G: 90×50.2s bin2, 1.26 hours, SNR 10.66
B: 90×77.8s bin2, 1.95 hours, SNR 10.63
Total Integration time: 11.59 hours
Total target SNR: 25.65

A quick survey of AstroBin reveals a startling variation of colors from members’ images of M81. One would think that there should be consensus. Top Picks did converge on a color scheme where the core is yellow and the arms are blue. I was keen on duplicating that result with little post-processing since I meticulously white balance my RGB filters. (This explains the strange looking exposure times that I use.)

I chose this Top Pick image at AstroBin as an accurate depiction of the galaxy’s color https://www.astrobin.com/385501/0/ . Notice he invested 30 hours to capture it. My method reduced the time to about 12 hours but I forfeited detail to achieve it.

Thankfully my equipment worked flawlessly but I did have to cope with a user error (me) on the last night from which I was able to recover.

Problems began during post-processing. The color balance was off. The galaxy was predominantly yellow with just a hint of blue in the outer arms. Here is that initial image:

The initial image was too yellow, not enough blue.

It took a day to solve but first let me explain that unlike a lot of astrophotographers I do not like to rely on software to perform color balancing. I prefer to get it right at the telescope.

A key component of my color balancing strategy is to white balance my filters against a Sun-like star. What I failed to realize is that there needs to be another component that accounts for atmospheric extinction. Atmospheric Extinction is an estimate of the amount of atmosphere between you and the galaxy. It is a function of the galaxy’s altitude above the horizon. The brightness diminishes the closer to the horizon, and grows as it reaches overhead.

I’ve known of atmospheric extinction and its effects for quite some time. I’ve chosen to mitigate its effects by selecting the red filter first, followed by green then blue. This is for objects east of the meridian. This strategy worked well up until this galaxy M81.

The essential difference between a galaxy like M81, Bode’s Galaxy, and M31, the Andromeda Galaxy, is that M31 faces east and M81 is circumpolar. Circumpolar means that it never sets since it is so close to Polaris. This also means that M81 never gets very high in the sky. It reaches 62 degrees above the horizon whereas M31 almost reaches 90 degrees. M31 becomes much brighter in the telescope when it is close to overhead. M81 never reaches those heights. The end result is that M81’s blue filtered images are less bright than M31’s.

I performed a mathematical analysis and discovered that M81’s blue stack of images is less bright than its red stack. This explains why the initial print of M81 is so weak in blue.

One solution is to go back to the telescope and capture more blue images. A second solution is to delete some of the 90 red images but keep all 90 blues. A third solution is to leave the images alone and to use the controls in AstroPixelProcesssor (APP) to attenuate the red stack. I chose to do the latter.

To get the color balance right I needed to attenuate the red stack by 17% and the green stack by 10% while keeping the blue stack at 100%. Here is the final processed image:

The final image is just right!

I have since developed a spreadsheet to assist me in capturing the proper number of images per filter. I’ll use that going forward.

Andromeda Galaxy (M31) The Saga Continues: Siril + APP.

Andromeda Galaxy (M31) The Saga Continues: Siril + APP.

This is only half of the galaxy. The core is at the lower-left and the arms stretch outwards to the upper-right. To visualize how large it really is, imagine the Full Moon. My camera can just about fit the Full Moon in its frame!

UPDATE: I want to thank Mabula Haverkamp, author of Astro Pixel Processor (APP). Beginning with version 1.075 APP successfully processes this image. The original story was written using version 1.074. As you read you can see that I had to fallback to using Siril which is no longer the case. The image shown above is part of the original story which used Siril for star alignment and stacking. While it was successful the alignment was not perfect. If interested you can see the high-quality APP image here: https://u235.herokuapp.com/#lrgb-exposure and scroll two-thirds of the way down.

Original story:

The night of this shot I was blessed with excellent seeing conditions, a rarity in this part of the country. The atmosphere was calm. Stars were stable. On most nights however the atmosphere is quite turbulent, causing starlight to rapidly twist and turn.

Sounds idyllic, right? Well, yes and no. On the one hand I can capture some very fine detail which normally would be lost to poor seeing conditions. On the other hand however the small size of the stars on the camera’s sensor can lead to a condition called “under-sampling”.

Ideally you want the average brightness star to cover a 3×3 area of pixels. With average to poor seeing conditions this is no problem but with excellent seeing conditions the star may only cover a 2×2 area.

After capturing the image at the telescope I began processing with Astro Pixel Processor (APP). Almost immediately it complained that it could not find enough stars in the color frames! I was shocked but not surprised.

When I purchased this CCD camera I knew that it had a tendency to under-sample (see notes at the end of the article.) This condition is exacerbated when capturing color frames using bin2 mode. Bin2 can dramatically reduce the exposure time of color frames but there is a downside. It cuts image resolution in half because it reduces each 2×2 matrix of pixels to one pixel.

This isn’t as terrible as it sounds. I think it was Trevor Jones at AstroBackyard who made the analogy of a child and his coloring book. The child provides the crayons and the publisher provides the detail in the form of the outline. If the child draws a little outside the outline the picture still looks good. If he gets sloppy it gets worse but is still acceptable especially if seen from a distance. This is the analogy that Trevor made with binning: bin2 is like the child drawing a little outside the outline, and bin3 is sloppy but acceptable. Remember that the outline is the job of the luminance filter running at bin1 and since the sensor sees three times more photons than with a color filter the exposure time is short.

So Astro Pixel Processor did not like my bin2 color frames. I checked the log file. Initially it said it found 100 stars but ultimately decided that only 4 of them qualified as real stars. Apparently the software looks at the star’s profile. Since there were so few pixels it failed.

I contacted my friend David Richards in the UK. He suggested I try Siril. I dedicated several hours and took a crash course from the online tutorial guide. Soon thereafter I had a reasonable looking final image. Thanks to Dave he helped me with some of the finer points of using Siril and now I have this wonderful image that you see here.

The subtitle of this blog post is “The Saga Continues”. It never ends but with regards to this image there is much more to say. I’ll leave that to a later post.

Technical Details:

William Optics 71mm f/5.9
Atik 314E CCD
Optolong LRGB filters

Luminance: 38x120s bin1
Red: 18x90s bin2
Green: 10x90s bin2
Blue: 17x90s bin2

Bias: 100 each for bin1 and bin2
Darks: 50 each for 120s bin1 and 90s bin2
Flats: 50 each filter

Total Integration Time: 2.4 hours

Siril for calibration, stacking, and color balance.
APP for histogram stretch and sharpening.

Note: Before purchasing an astronomy camera, no matter if it is CCD or CMOS, you should make sure that you match the camera to your telescope. Astronomy Tools has an excellent resource called the CCD Suitability Calculator. Scroll to the bottom of the page. There are two boxes I want you to fill in. Focal Length: 418. CCD Pixel Size: 4.65. Notice the warning: “this combination leads to slight under-sampling.” Now change CCD Binning from 1×1 to 2×2. Notice it goes off into the red. Ideally for 1×1 binning you want the indicator to be at the lower end of the green region and for 2×2 binning at the higher end of green. For my telescope that would be a camera with a pixel size of about 2 microns.

Andromeda Galaxy Mosaic as of 2019-08-12

Andromeda Galaxy Mosaic as of 2019-08-12


Panels A, B, C, E, F, and G in Luminance 21x90s each.
Rotated 35 degrees CCW to restore north up.

Racing against the Moon, Sun, and the meridian, on two consecutive nights I captured Panel G in luminance, red, green, and blue. The mosaic seen above consists of all six panels in luminance only.

Panel G in Luminance 21x90s, Red 21×109.4s, Green 21×67.5s, and Blue 21×90.5s.
Total integration time 2.1 hours.

Now having all data in LRGB, I created Panel G in color. The image above shows accurate star color and also variations in the arms of the galaxy as expected.

Try as I might I could not get Astro Pixel Processor (APP) to create the grand mosaic consisting of five monochrome panels and one color panel. At the very end of the process it complained it could not create a mosaic consisting of just one panel.

In a couple weeks when the Moon recedes I will capture RGB data for Panel F on the first night. Hopefully that will satisfy APP. With luck I’ll get a string of clear nights as the Fall season approaches.

Andromeda Galaxy Mosaic – Panel Definitions

Andromeda Galaxy Mosaic – Panel Definitions

If you have been following the progress of the mosaic and you’ve wondered how I derived the panel naming scheme, this explains it:

Panel Definitions – H, F, G, B, A, E, C, D – reading top to bottom, left to right.

That screenshot came from a program called Computer Assisted Astronomy (C2A) by Philippe Deverchère. I highly recommend it. It offers the ability to create User Catalogs. I created a catalog named “M31 Mosaic” that contains 8 records. A record defines each of the eight rectangles (or panels) that you see. The size of each panel represents the field-of-view of my Atik 314E camera and William Optics ZenithStar 71 telescope. Furthermore, I adjusted the position and orientation of each panel so as to provide sufficient overlap to satisfy Astro Pixel Processor (APP).

The body of the galaxy is represented by the large ellipse. As I’ve come to learn, the perimeter of the ellipse captures the very outer edges of the galaxy which is not visible in my mosaic, so because of that I’ve decided not to capture panels H and D. Perhaps one day after I acquire more data I will go back and capture them.

Andromeda Galaxy Mosaic as of 2019-08-05

Andromeda Galaxy Mosaic as of 2019-08-05

Panels A, B, C, E, and F in Luminance 21x90s each.
Rotated 35 degrees CCW to restore north up.

Captured three additional panels last night: C, E, and F. The plan was to also capture G but a cloud bank interfered with F. Waited for clouds to pass but by then G was not possible due to the meridian and dawn.

The weather forecast says that this coming Saturday may be favorable. It will be my last chance to capture G for two weeks due to the Moon.

Andromeda Galaxy Mosaic as of 2019-08-02

Andromeda Galaxy Mosaic as of 2019-08-02

Panels A and B in Luminance 21x90s each.
Rotated 35 degrees CCW to restore north up.

Six more panels to go in Luminance! And then to do eight panels in Red, eight panels in Green, and eight panels in Blue. Lot’s to do but the results are encouraging.

For perspective here is Panel A:

Panel A in Luminance 21x90s

and here is Panel B:

Panel B in Luminance 21x90s

Astro Pixel Processor (APP) for imaging processing and mosaic creation. INDI/Ekos used for image capture.

M101 – Pinwheel Galaxy – Ha

M101 – Pinwheel Galaxy – Ha

Acquisition Date: February 17, 2019

This is a work in progress with the goal being a color image. As more data becomes available I will post updates.

Spiral galaxies like M101 contain ionized hydrogen regions. This is where star formation occurs and it is mainly found in the arms of the galaxy. There is a type of narrowband filter which is designed to pass the Hydrogen Alpha (Ha) emission line. This photo was taken with an Ha filter.

One of the advantages of imaging in narrowband is that it can be performed during all phases of the Moon. In fact, the Moon was 91% illuminated when I acquired this image. The downside is that the required exposure is quite long: 3 minutes 20 seconds for each of the 32 frames in this case. Wideband imaging, by comparison, typically uses exposures in the range of 30 to 60 seconds but images will be washed out by the light of the Moon. Wideband filters are typically named Luminance, Red, Green, and Blue (i.e. LRGB).

As this project matures to color I will provide more detailed technical information. The image shown above is a screenshot of Astro Pixel Processor (APP).

NGC 4565 – Needle Galaxy

NGC 4565 – Needle Galaxy

Acquisition Date: February 10, 2019

I wanted to do more color with my monochrome camera but the number of steps involved with capturing calibration frames and light frames using four different filters was overwhelming to accomplish manually in a single evening. For a while I thought I would simply spread imaging over four nights: one night for luminance, the second for red, etc. But then I realized that clear nights are hard to come by. Sometimes it takes well over a month to accumulate four nights. So that’s when I decided that I needed to come up with an automated solution to get an entire LRGB sequence in one night.

I took a three month rest from imaging while I developed a “Flip-Flat” work-alike since I couldn’t get myself to part with the $500 cost for the original. I ended up spending more on development but the experience was worth it. I call mine The Flatinator. I will write more about it later.

Ordinarily I use SharpCap software for image acquisition but in this instance I chose INDI/Ekos due to its advanced automation. The next version of SharpCap promises better features.

Technical Details:

William Optics 71mm f/5.9
Altair 290M camera (uncooled)
Optolong LRGB Filters
Unitron Model 142 GEM
The Flatinator
Passive tracking with PEC
No active guiding

Gain 200 (1.74 e-/ADU, FWD: 7100e-, Read Noise: 1.55e-)
Offset: 25 ADU
Exposure: Multiple
Camera rotation: 5 deg E of N

Luminance: 72x 25s
Red: 30x 30s
Green: 30x 30s
Blue: 25x 36s

Flats: 100x per channel
Darks: 20x per channel
Bias: 100x all channels

Total integration time: 74 minutes
Total time at telescope: 122 minutes

SharpCap 3.1.5219 for Polar Alignment and Periodic Error Correction
INDI/Ekos for Image Acquisition
APP 1.071 for Stacking and Image Processing