Made a quick tutorial on how to remove background gradient with GIMP
You need the GIMP Astronomy Plugin
Made a quick tutorial on how to remove background gradient with GIMP
You need the GIMP Astronomy Plugin
I’m sharing with you a photo I took of the recent Venus and Pleiades conjunction. The closest approach was on April 10th, but I had to wait until the 12th for a clear sky. It was a pretty sight to see the bright planet and the star cluster so close together in the night sky. I used my Canon 80D and a telephoto lens to capture this image. Here are some tips on how I did it:
I was hoping to capture a hint of the nebulosity within the star cluster, but I guess 5 seconds exposures, even when integrated to 6 minutes is not enough to capture that fainter detail. It was around 8:00pm when I took the photos, the sky was not fully dark, making the use of exposure above 5 seconds too bright. However I did manage to capture the colors of the stars down to magnitude 9.
I hope you enjoyed this post and learned something new. If you have any questions or comments, feel free to leave them below. Thanks for reading!
Canon 80D
135mm F4.5 telephoto lens
Individual photos: 5 seconds at ISO 1600
6 minutes total integration time
Vixen GP Equatorial Mount (untracked)
Registration and stacking with DSS
GIMP for final adjustment
Creating night-time images with star trails is the easiest and should be your first project when getting into astro photography.
Back in the day of film, you had to stomp down the diaphragm and use a shutter actuator to take one VERY long exposure. And if something happened during that long exposure (bird, plane, clouds, etc…) your photo was ruined. With digital, you can instead take LOTS of short exposures and digitally stitch them together, leaving out the ones that got ruined.
Setup your camera to take a series of short exposure photos, 10 seconds is good. For some tips on how to setup your camera, head over to my Astrophotography Cookbook page.
If you are starting out, or want to simply do this quickly, skip taking Bias, Dark and Flat photos. These are used to improve the final image processing and make more sense when you wish to do some deep sky stacking.
For this exercise I configured the intervalometer of the camera to take 10 second exposures with a 1 second pause between (i.e. the shutter is pressed every 11 seconds and each click is a 10 second exposure). I left the camera operating for a little more than one hour, with the result over 400 photos captured.
It’s important to review all the photos and note down the ones to exclude from the final image, things like camera movement because you knocked the tripod, a plane, clouds, etc. It’s possible that from the 438 photos taken, only the range 5 to 352 will be good to build the star trail image as clouds decided to roll into view on the 353rd photo.
The next step is to import the photos into Deep Sky Stacker. This is done by using the Open picture files… command. As I mentioned earlier, the dark, flat and bias can be skipped, these are not required. But if you have them, they will improve the quality of the final image. Don’t forget to select Check all before moving to the next step, and to uncheck any photos you want to exclude if you did a bulk import.
Once the photos are selected, go straight to Stack checked pictures… In the window that pops-up, hit the Stacking parameters… button and select the following:
The remaining tabs can remain with the default setting. Hit OK and the program will now start processing all the photos. Note that DSS will still register each image even if you selected No Alignment. If you know how to prevent this waste of time, please tell me in the comment below.
The end result is something like the image below. Base on your the quality of your sky, the camera setting, color balance, etc… various level of work will be required to make it look nice, but you now have something to import into your photo editor and correct all that.
In my Post-processing section of the Astrophotography Cookbook, I provide some tips on how to correct for things like sky gradient.
Clear dark skies!
What makes it possible to be able to generate a photo of the Milkyway from what appears to be just a faint trace in the original shot?
It all comes down to the signal vs noise. Whenever we record something, sound, motion, photons, etc… there is always the information you WANT to record (the signal) and various sources of noise.
Noise can have many sources:
This noise can be random or steady/periodic in nature. A steady or periodic noise is easy to filter out as it can be identified and isolated because it will be the same in all the photos. However a random noise is more difficult to eliminate due to the random nature. This is where he signal to noise ratio becomes important.
In astrophotography we take not only the photos of the sky, but also bias, darks and flat frames: this is to isolate the various sources of noise. A bias shot is a short exposure to capture the electronic read-out noise of the sensor and electronics. The darks is a long exposure at the same setting as the astronomy photo to capture noise that appears during long exposures due to the sensor characteristics such as hot pixels and amplifier glow. Cooling the sensor is one way to reduce this noise, but that is not always possible. Finally the flat photo is taken to identify the optical noise caused by the characteristics of the lens or mirror as well as any dust that happens to be in the way.
But what can be done about random noise? That is where increasing the number of samples has a large impact. For a random noise, increasing the number of sample points improves the signal to noise ratio by the square root of the number of samples. Hence averaging 4 images will be 2 times improvement than a single photo. Going to 9 will be 3 times better. Etc…
You might be thinking: “Yeah but you are averaging, so the signal is still the same strength.” That is correct, however because my signal to noise ratio is improved I can be much more aggressive on how the image is processed. I can boost the levels that much more before the noise becomes a distraction.
But can’t I just simply duplicate my image and add them together? No that won’t work because we want the noise to be random, and if you duplicate your image, the noise is identical in both.
So even if you are limited to just taking 30-second, even 5-second shots of the night sky and can barely make out what you want to photogram, don’t despair, just take LOTS of them and you’ll be surprised what can come out of your photos.
The simplest form of astrophotography is nothing more than a camera on a tripod shooting long exposures. However by the time you get around to stacking and stretching the levels of your photos to accentuate various elements, such as the Milky Way, the sky gradient will become more apparent. That gradient can come from city lights, the Moon up above and the thicker atmosphere causing light to disperse at low angles to horizon. Normally the wider the field of view, the greater the gradient.
Below is a RAW 20-second exposure of the Milky Way near the horizon taken with a Canon 80D equipped with a 17mm F4.0 lens. The background has a slight gradient; brighter at the bottom. No all that bad.
But once you stack multiple exposures and stretch the levels to get the Milky Way to pop out, the gradient only gets worse.
There are various astrophoto software that can remove the sky gradient. The one that I’m familiar with and have been using is IRIS. I know the software is old, but it does a great job. So after I’ve completed my registration and stacking of images with DeepSkyStacker (see my Astrophotography in the City article), the next step is to open the resulting image with IRIS.
Once the stacked image is loaded in IRIS, head over to the Processing menu and select Remove gradient (polynomial fit) … Actually to get the best results you need to have the background and color corrected as well as trimming the edge of your photo. Got that covered here.
The following menu will appear.
Normally the default settings (as above) will work well. But this image has some foreground content (trees) and that will cause the result to look a little odd. The algorithm is designed to avoid sampling stars, but not so good when there is foreground content like the trees at the bottom of the image.
To correct this you must use the gradient removal function with a mask. The quickest way to create a mask is using the bin_down <value> command. This will change to white all pixels with intensities below <value>, and make black all pixels above it. Areas in black will not be used for sampling, while those in the white areas will. A little trial-and-error is sometimes necessary to select the right value.
In this case, even with the right bin_down value, the trees that I want to mask are not black, hence I will use the fill2 0 command to create black boxes and roughly block out the trees.
Below is the result after using multiple fill rectangles to mask the trees. This does not need to be precise as the mask is simply used to exclude areas from sampling. It is not like a photo-editing mask.
The resulting mask is saved (I called it mask), and I load back the original image, this time using the gradient removal with the mask option selected.
The program generates a synthetic background sky gradient, based on thousands of sample points and an order 3 polynomial. The image below lets you see the synthetic sky gradient the algorithm generated. This is what will be subtracted from the image.
The final image below is much better and more uniform. There are no strange dark and bright zones like the attempt without the mask.
If we compare the original raw images with the new stacked, stretched and sky gradient removed photo the results are pretty impressive.
I have two telescopes, a Skywatcher 80ED (identical to the Orion 80ED – 600mm focal length at F7.5) and a Williams Optics Gran Turismo 71 APO with 420mm focal length at F5.9. Just looking at the numbers it’s easy to see that the GT71 is a smaller and faster telescope, and because of the shorter focal length it should have a larger field of view.
Now I’ve photographed the same part of the sky with both telescopes, and can now overlap the images to see exactly what is the difference between the field of view between these two telescopes.
First I need to say that that GT71 NEEDS a field flattener when imaging with DSLR. The distortions off-center are terrible. Don’t get me wrong, as a three objective lens telescope (including 1 fluorite for color correction), it has provided me with the best lunar photos, however it has issues when using the large DSLR sensor. The SW80ED provides a much flatter field of view for photography out of the box.
The flattener for GT71 is in the plans…
So how does both telescope compare? Below is a photo of open star cluster Messier 38 taken with my GT71 and I’ve overlapped as a brighter box an image taken with the SW80. For those wondering, I used IRIS to register and align both photos using the coregister command.
Messier 38 – Field of view with William Option GT71 and Skywatcher 80ED (brighter box)
Both telescopes deliver just about the same field of view with the GT71 providing 1 degree more of horizontal field. But the difference is much less on the vertical.
What did surprise me is how much light the GT71 gathers. Inspecting the photos showed me that even with the smaller setup, the GT71 has great light gathering capabilities. I got down into magnitude 12 with only 15 seconds of exposure, which is nearly similar to the SW80ED at 30 seconds.
In conclusion I would say the GT71 has good photographic potential, but requires a field flattener if it will be used with DSLR. Stay tuned…
Shooting wide angle long exposures of the sky is always fun, because you never quite know what you will get. On an August night I decided to take a few 20 seconds exposures of the constellation Perseus hoping to catch a few open clusters. However got surprised by the faint glow of Messier 33 (Triangulum Galaxy) in the photos. This is the furthest object that can be observed to the naked eye, located 2.7 million light years away, and part of the Local Group which includes Andromeda and our Milky Way.
4 x 20 seconds
ISO 6400
17mm F4.0
Canon 80D
August 30, 2019
Most people don’t plan to take photos of the Moon, they just happen. You are outside doing something else and then you spot it over the horizon or high in the sky: “Hey that’s a pretty Moon tonight Maybe I should take a photo!”
I find that normal camera lens, even telephoto don’t do it justice. The setting and focus can be very tricky. The multi-lens setup of telephoto can also cause internal reflections or chromatic aberrations making the resulting photo less appealing.
So just grab the telescope tube and leave the tripod behind. If you have a small APO refractor you can simply hold the tube, but for anything heavier you’ll need to prop yourself up on something like a railing or a car roof.
The photo below is a single shot at 1/250sec and ISO400 with Canon 80D and William Optics Gran Turismo 71 held on the end of my arms.
80% Illuminated Moon on August 31, 2018 [Benoit Guertin]
Nothing like leaving the city lights behind and heading to a rural camp ground to check up on our galaxy.
Every summer the galaxy presents itself across the sky in the norther hemisphere, an ideal time to enjoy the view and spot a few open cluster along the way.
Canon 80D 17mm F/4 ISO6400
Stack of 10 x 10 seconds
No tracking
Mark Bailey
Electronics plus software tips and tricks
A site dedicated to learning Astronomy One Step at a Time
Charles Bracken
one post at a time
Astronomy, space and space travel for the non scientist
My adventures with amateur astronomy
Discoveries, Journeys & Milestones in Space Exploration
Welcome to a journey into our Universe with Dr Dave, amateur astronomer and astrophotographer for over 40 years. Astro-imaging, image processing, space science, solar astronomy and public outreach are some of the stops in this journey!
Observations, mostly astronomical from Limavady, UK (55N, 6.9W).
Photography Blog of James Silvester
Astronomy and Amateur Radio
The latest news on WordPress.com and the WordPress community.