To guide or not to guide? [Deep Sky] Acquisition techniques · Tomvp · ... · 14 · 447 · 0

Tomvp 0.00
...
· 
Hi all,

If the weather ever clears up I intend to have a go at the heart and soul nebulas again and similar really wide area objects. For this I want to hook up a 100mm lens to my QHY183C and mount it on my CEM26. According to astronomy tools I will get a resolution of 4.95”/pixel. With the QHY183 I never go above 180 sec exposure times. Question is: with this resolution, exposure time and mount, should I bother to set up guiding? If the drift becomes too big I can let NINA recenter every now and then so the subject would not slide out of view after a couple of hours. Your thoughts?
Like
rveregin 6.76
...
· 
·  3 likes
I image without guiding on a CEM60EC with a theoretical resolution of 0.5"  on my C925 (though seeing is the limiting factor, rarely better than average for me). I get an rms typically < 0.3" for 1 minute exposures, 0.5" if I went to 2 minute exposures. I use SharpCap to do a very good polar align. I do benefit from the fact that my mount is the ec version, which means it has encoders to keep its tracking steady. When I turn off encoders, I get something that is 2 or so times worse in tracking. And I do note that if it is windy tracking is more challenging. 

The other thing is periodic error. There is one article here on Cloudy Nights about the CEM26: https://www.cloudynights.com/topic/759169-cem26-first-cloudy-night/page-3   The poster says he gets 8" of periodic error over 600 seconds. The maximum shift will be a little more than 8"/300 or about 0.03 "/s. for 180 s that gives you 5.4", which is an rms of about 2.7". So that sounds to be probably ok. But you would do better to implement PEC if you can, it sounds as if it is available for your mount. Or limit your exposures to 1 or 2 minutes. Remember it all adds up tracking errors, PEC, wind and polar alignment errors, so you can't let PEC be right at the limit of your resolution. 

And I do do what you suggested, I let it drift (with my mount it varies through the night, back and forth, or some drift in one direction and then the other, due to polar alignment, where you are in the sky (atmospheric refraction), etc. So I do have to occassionally recenter. Personally I only let it drift maybe 30 px in any direction, so that I don't loose FOV at the edges. But this is also enough to give me a good dither, which is important to limit camera noises.

I do suggest you do some test exposures. What I do is just take short exposures every 10 s for say 5 minutes. Then I use DSS to stack the images. It provides the offsets in pixels so you can see how much drift you are getting. So measure the shift for 1 minutes of the stack, 2 minutes, 3 minutes, etc. That way you can see how much you can tolerate by carefully examining the stacked images, as well as looking at the shift in the offsets (rms error is close to 1/2 of the shift in offsets. Your optimal exposure is something less than the image that shows no tracking defects, non-round stars etc, so you have some leaway. Note you will want to try this in different parts of the sky, it will affect your tracking. You will find with experience in polar aligning, making sure the mount is on a stable base, etc, that you will get better at unguided imaging than what you can do first starting out. I do like it because it is one less thing to worry about, not having to guide. And knowing it would be hard for me to do better guiding anyway. I live in a high Bortle 8 area, so even NB filters do not need more than 1 minute exposures generally. So I have been very happy with this approach.
CS
Rick
Like
Eteocles 2.71
...
· 
·  1 like
At over 7"/px with my 105mm lens setup on my RST-135 I have to guide for 120s-180s.  Never tried anything shorter than that, but I wouldn't want to deal with that many files anyway.  My guess is you will find yourself having to guide.
Like
starpixels 1.20
...
· 
·  1 like
I have the 183 too (same sensor)... small pixels, 15k full well... I know well why you avoid long exposures. That being said, I'm on the side of reducing files because this camera will gladly use up a google-server worth of space when you try to collect enough light at lower exposures... the lesser of the evils for me has been to expose long for the target if needed, run a different set of rgb for stars or fix in post, and always guide... but I don't have the pixel scale you're talking about and there's no upside to not guiding for me so I can't speak to that part... only to suggest that if it's exposure motivated, I have examples of running longer exps with the 183 and it's not a terrible option.
Edited ...
Like
Tomvp 0.00
...
· 
·  1 like
I have the 183 too (same sensor)... small pixels, 15k full well... I know well why you avoid long exposures. That being said, I'm on the side of reducing files because this camera will gladly use up a google-server worth of space when you try to collect enough light at lower exposures... the lesser of the evils for me has been to expose long for the target if needed, run a different set of rgb for stars or fix in post, and always guide... but I don't have the pixel scale you're talking about and there's no upside to not guiding for me so I can't speak to that part... only to suggest that if it's exposure motivated, I have examples of running longer exps with the 183 and it's not a terrible option.

That full well capacity is indeed my major concern. On the other hand, I will be using an L-Enhance filter, so that should make it possible to use longer exposures, especially since there no really bright stars around heart & soul. But on the plus side: it's an F/2 lens! So maybe even 180 is already too much at this aperture. Bottom line: I just have to try it out....

Once again, if the weather clears up right now (very unlikely ) , I could have a period of around 10 hours to shoot. At 120 sec I would end up with 300 exposures of 41MB each. that would make 12GB. With 180 sec exposures I have 200 times 41MB which consumes 8GB. Not an entire Google server, but still a considerable amount of data.
Like
markus.selbach 1.20
...
· 
·  1 like
Clear nights are so rare. It‘s a pain to throw away 50% of your subs because of errors that sum up to become visible. If you can guide I would recommend to do it.
Like
Tomvp 0.00
...
· 
·  1 like
Rick Veregin:
I image without guiding on a CEM60EC with a theoretical resolution of 0.5"  on my C925 (though seeing is the limiting factor, rarely better than average for me). I get an rms typically < 0.3" for 1 minute exposures, 0.5" if I went to 2 minute exposures. I use SharpCap to do a very good polar align. I do benefit from the fact that my mount is the ec version, which means it has encoders to keep its tracking steady. When I turn off encoders, I get something that is 2 or so times worse in tracking. And I do note that if it is windy tracking is more challenging. 

The other thing is periodic error. There is one article here on Cloudy Nights about the CEM26: https://www.cloudynights.com/topic/759169-cem26-first-cloudy-night/page-3   The poster says he gets 8" of periodic error over 600 seconds. The maximum shift will be a little more than 8"/300 or about 0.03 "/s. for 180 s that gives you 5.4", which is an rms of about 2.7". So that sounds to be probably ok. But you would do better to implement PEC if you can, it sounds as if it is available for your mount. Or limit your exposures to 1 or 2 minutes. Remember it all adds up tracking errors, PEC, wind and polar alignment errors, so you can't let PEC be right at the limit of your resolution. 

And I do do what you suggested, I let it drift (with my mount it varies through the night, back and forth, or some drift in one direction and then the other, due to polar alignment, where you are in the sky (atmospheric refraction), etc. So I do have to occassionally recenter. Personally I only let it drift maybe 30 px in any direction, so that I don't loose FOV at the edges. But this is also enough to give me a good dither, which is important to limit camera noises.

I do suggest you do some test exposures. What I do is just take short exposures every 10 s for say 5 minutes. Then I use DSS to stack the images. It provides the offsets in pixels so you can see how much drift you are getting. So measure the shift for 1 minutes of the stack, 2 minutes, 3 minutes, etc. That way you can see how much you can tolerate by carefully examining the stacked images, as well as looking at the shift in the offsets (rms error is close to 1/2 of the shift in offsets. Your optimal exposure is something less than the image that shows no tracking defects, non-round stars etc, so you have some leaway. Note you will want to try this in different parts of the sky, it will affect your tracking. You will find with experience in polar aligning, making sure the mount is on a stable base, etc, that you will get better at unguided imaging than what you can do first starting out. I do like it because it is one less thing to worry about, not having to guide. And knowing it would be hard for me to do better guiding anyway. I live in a high Bortle 8 area, so even NB filters do not need more than 1 minute exposures generally. So I have been very happy with this approach.
CS
Rick

Thanks for the clear explanation Rick, much appreciated. I hadn't looked at PPEC yet, as I went almost straight to NINA (after struggling to get Stellarmate to work). I definitely need test exposures. But I see a small challenge with DSS as I do post on a Mac, and DSS is Windows only. I could try DSS on my NINA system, a Mele 3, but that might blow it up, as it is not the fastest processor around. Do you have alternatives for the kind of analysis you described?
Like
starpixels 1.20
...
· 
Yes, using an optolong filter here too and agree that will definitely help you. Your F2 lens is a game changer. 10 hrs of clear skies is a dream-come-true in NE where I am, wishing you lots of luck!
Like
Tomvp 0.00
...
· 
Markus Selbach:
Clear nights are so rare. It‘s a pain to throw away 50% of your subs because of errors that sum up to become visible. If you can guide I would recommend to do it.

I probably need then to dust off my iGuider and see if I can get that to work. The way it is normally connected to the CEM26 saddle makes it very awkward to work with, it is almost impossible to strap a dew heater to it and not get in the way of the main imager.
Like
Tomvp 0.00
...
· 
Dan:
At over 7"/px with my 105mm lens setup on my RST-135 I have to guide for 120s-180s.  Never tried anything shorter than that, but I wouldn't want to deal with that many files anyway.  My guess is you will find yourself having to guide.

Ok, I wasn't hoping for that answer, but it sure sounds like you have something similar to what I am intending to set up, so I will definitely keep this option in mind. Luckily my lens is F/2 so I maybe I can get away with shorter exposures.
Edited ...
Like
Tomvp 0.00
...
· 
Yes, using an optolong filter here too and agree that will definitely help you. Your F2 lens is a game changer. 10 hrs of clear skies is a dream-come-true in NE where I am, wishing you lots of luck!

Well, we had the first two clear nights since September last week here in The Netherlands. I screwed up the first one (loose bolt....), but in the second one I got 6 hours worth of data. I could have gone further but wasn't sure my battery would have lasted. It was the first time I had that much data, and boy what a difference that makes: Rosette Nebula.
Like
Eteocles 2.71
...
· 
·  1 like
Dan:
At over 7"/px with my 105mm lens setup on my RST-135 I have to guide for 120s-180s.  Never tried anything shorter than that, but I wouldn't want to deal with that many files anyway.  My guess is you will find yourself having to guide.

Ok, I wasn't hoping for that answer, but it sure sounds like you have something similar to what I am intending to set up, so I will definitely keep this option in mind. Luckily my lens is F/2 so I maybe I can get away with shorter exposures.

You certainly can, but it depends on your tolerance for volume of files and your computer's processing capabilities.  Not to mention storage space.  To me, guiding is a small price to pay to avoid these issues, but different people have different tolerances/capabilities.
Like
rveregin 6.76
...
· 
·  1 like
Rick Veregin:
I image without guiding on a CEM60EC with a theoretical resolution of 0.5"  on my C925 (though seeing is the limiting factor, rarely better than average for me). I get an rms typically < 0.3" for 1 minute exposures, 0.5" if I went to 2 minute exposures. I use SharpCap to do a very good polar align. I do benefit from the fact that my mount is the ec version, which means it has encoders to keep its tracking steady. When I turn off encoders, I get something that is 2 or so times worse in tracking. And I do note that if it is windy tracking is more challenging. 

The other thing is periodic error. There is one article here on Cloudy Nights about the CEM26: https://www.cloudynights.com/topic/759169-cem26-first-cloudy-night/page-3   The poster says he gets 8" of periodic error over 600 seconds. The maximum shift will be a little more than 8"/300 or about 0.03 "/s. for 180 s that gives you 5.4", which is an rms of about 2.7". So that sounds to be probably ok. But you would do better to implement PEC if you can, it sounds as if it is available for your mount. Or limit your exposures to 1 or 2 minutes. Remember it all adds up tracking errors, PEC, wind and polar alignment errors, so you can't let PEC be right at the limit of your resolution. 

And I do do what you suggested, I let it drift (with my mount it varies through the night, back and forth, or some drift in one direction and then the other, due to polar alignment, where you are in the sky (atmospheric refraction), etc. So I do have to occassionally recenter. Personally I only let it drift maybe 30 px in any direction, so that I don't loose FOV at the edges. But this is also enough to give me a good dither, which is important to limit camera noises.

I do suggest you do some test exposures. What I do is just take short exposures every 10 s for say 5 minutes. Then I use DSS to stack the images. It provides the offsets in pixels so you can see how much drift you are getting. So measure the shift for 1 minutes of the stack, 2 minutes, 3 minutes, etc. That way you can see how much you can tolerate by carefully examining the stacked images, as well as looking at the shift in the offsets (rms error is close to 1/2 of the shift in offsets. Your optimal exposure is something less than the image that shows no tracking defects, non-round stars etc, so you have some leaway. Note you will want to try this in different parts of the sky, it will affect your tracking. You will find with experience in polar aligning, making sure the mount is on a stable base, etc, that you will get better at unguided imaging than what you can do first starting out. I do like it because it is one less thing to worry about, not having to guide. And knowing it would be hard for me to do better guiding anyway. I live in a high Bortle 8 area, so even NB filters do not need more than 1 minute exposures generally. So I have been very happy with this approach.
CS
Rick

Thanks for the clear explanation Rick, much appreciated. I hadn't looked at PPEC yet, as I went almost straight to NINA (after struggling to get Stellarmate to work). I definitely need test exposures. But I see a small challenge with DSS as I do post on a Mac, and DSS is Windows only. I could try DSS on my NINA system, a Mele 3, but that might blow it up, as it is not the fastest processor around. Do you have alternatives for the kind of analysis you described?

Well, you can stack in any stacking software that runs on a Mac, then just look at the images up close visually, you can expand until you can see individual pixels.. Take 10 s, 30s, 1 m, 2m, 3m exposures on say an open cluster with reasonably bright stars and see when you start to see tracking errors on the stars. Ideally stack enough of each sub exposure time so the total time is the same for each set of sub exposures, for a fair comparison. In the end the rms error or offset shift is only a surrogate metric, but don't get wrapped up in a number. If you can't tell the difference in the image it doesn't matter what your rms is. For example I see some folks complain that they can't get <0.3" rms or something, without even thinking that it won't make a difference if you sky conditions give you only 2.5", on very few nights do many of us get that sort of seeing often.  But it depends on how well you can polar align and how good and stable your mount is. But it is worth trying, as you will see from many threads guiding can be complicated and has its own issues. This hobby is complicated enough without jumping in the deep end, my advice is to start simple, and then make changes that are needed as you master that. And anyway, no way to tell if your guiding is helping, if you go that route, unless you know what you can do without it. Here is one of my recent examples, 1 minute exposures, no guiding at FL=1480 mm, so it can be done reliably: 
https://www.astrobin.com/yzxzpf/

Good luck
Rick
Like
Tomvp 0.00
...
· 
·  1 like
Rick Veregin:
Rick Veregin:
I image without guiding on a CEM60EC with a theoretical resolution of 0.5"  on my C925 (though seeing is the limiting factor, rarely better than average for me). I get an rms typically < 0.3" for 1 minute exposures, 0.5" if I went to 2 minute exposures. I use SharpCap to do a very good polar align. I do benefit from the fact that my mount is the ec version, which means it has encoders to keep its tracking steady. When I turn off encoders, I get something that is 2 or so times worse in tracking. And I do note that if it is windy tracking is more challenging. 

The other thing is periodic error. There is one article here on Cloudy Nights about the CEM26: https://www.cloudynights.com/topic/759169-cem26-first-cloudy-night/page-3   The poster says he gets 8" of periodic error over 600 seconds. The maximum shift will be a little more than 8"/300 or about 0.03 "/s. for 180 s that gives you 5.4", which is an rms of about 2.7". So that sounds to be probably ok. But you would do better to implement PEC if you can, it sounds as if it is available for your mount. Or limit your exposures to 1 or 2 minutes. Remember it all adds up tracking errors, PEC, wind and polar alignment errors, so you can't let PEC be right at the limit of your resolution. 

And I do do what you suggested, I let it drift (with my mount it varies through the night, back and forth, or some drift in one direction and then the other, due to polar alignment, where you are in the sky (atmospheric refraction), etc. So I do have to occassionally recenter. Personally I only let it drift maybe 30 px in any direction, so that I don't loose FOV at the edges. But this is also enough to give me a good dither, which is important to limit camera noises.

I do suggest you do some test exposures. What I do is just take short exposures every 10 s for say 5 minutes. Then I use DSS to stack the images. It provides the offsets in pixels so you can see how much drift you are getting. So measure the shift for 1 minutes of the stack, 2 minutes, 3 minutes, etc. That way you can see how much you can tolerate by carefully examining the stacked images, as well as looking at the shift in the offsets (rms error is close to 1/2 of the shift in offsets. Your optimal exposure is something less than the image that shows no tracking defects, non-round stars etc, so you have some leaway. Note you will want to try this in different parts of the sky, it will affect your tracking. You will find with experience in polar aligning, making sure the mount is on a stable base, etc, that you will get better at unguided imaging than what you can do first starting out. I do like it because it is one less thing to worry about, not having to guide. And knowing it would be hard for me to do better guiding anyway. I live in a high Bortle 8 area, so even NB filters do not need more than 1 minute exposures generally. So I have been very happy with this approach.
CS
Rick

Thanks for the clear explanation Rick, much appreciated. I hadn't looked at PPEC yet, as I went almost straight to NINA (after struggling to get Stellarmate to work). I definitely need test exposures. But I see a small challenge with DSS as I do post on a Mac, and DSS is Windows only. I could try DSS on my NINA system, a Mele 3, but that might blow it up, as it is not the fastest processor around. Do you have alternatives for the kind of analysis you described?

Well, you can stack in any stacking software that runs on a Mac, then just look at the images up close visually, you can expand until you can see individual pixels.. Take 10 s, 30s, 1 m, 2m, 3m exposures on say an open cluster with reasonably bright stars and see when you start to see tracking errors on the stars. Ideally stack enough of each sub exposure time so the total time is the same for each set of sub exposures, for a fair comparison. In the end the rms error or offset shift is only a surrogate metric, but don't get wrapped up in a number. If you can't tell the difference in the image it doesn't matter what your rms is. For example I see some folks complain that they can't get <0.3" rms or something, without even thinking that it won't make a difference if you sky conditions give you only 2.5", on very few nights do many of us get that sort of seeing often.  But it depends on how well you can polar align and how good and stable your mount is. But it is worth trying, as you will see from many threads guiding can be complicated and has its own issues. This hobby is complicated enough without jumping in the deep end, my advice is to start simple, and then make changes that are needed as you master that. And anyway, no way to tell if your guiding is helping, if you go that route, unless you know what you can do without it. Here is one of my recent examples, 1 minute exposures, no guiding at FL=1480 mm, so it can be done reliably: 
https://www.astrobin.com/yzxzpf/

Good luck
Rick

WOW, more than 3300 exposures!! How long did stacking take?
Like
rveregin 6.76
...
· 
·  1 like
Rick Veregin:
Rick Veregin:
I image without guiding on a CEM60EC with a theoretical resolution of 0.5"  on my C925 (though seeing is the limiting factor, rarely better than average for me). I get an rms typically < 0.3" for 1 minute exposures, 0.5" if I went to 2 minute exposures. I use SharpCap to do a very good polar align. I do benefit from the fact that my mount is the ec version, which means it has encoders to keep its tracking steady. When I turn off encoders, I get something that is 2 or so times worse in tracking. And I do note that if it is windy tracking is more challenging. 

The other thing is periodic error. There is one article here on Cloudy Nights about the CEM26: https://www.cloudynights.com/topic/759169-cem26-first-cloudy-night/page-3   The poster says he gets 8" of periodic error over 600 seconds. The maximum shift will be a little more than 8"/300 or about 0.03 "/s. for 180 s that gives you 5.4", which is an rms of about 2.7". So that sounds to be probably ok. But you would do better to implement PEC if you can, it sounds as if it is available for your mount. Or limit your exposures to 1 or 2 minutes. Remember it all adds up tracking errors, PEC, wind and polar alignment errors, so you can't let PEC be right at the limit of your resolution. 

And I do do what you suggested, I let it drift (with my mount it varies through the night, back and forth, or some drift in one direction and then the other, due to polar alignment, where you are in the sky (atmospheric refraction), etc. So I do have to occassionally recenter. Personally I only let it drift maybe 30 px in any direction, so that I don't loose FOV at the edges. But this is also enough to give me a good dither, which is important to limit camera noises.

I do suggest you do some test exposures. What I do is just take short exposures every 10 s for say 5 minutes. Then I use DSS to stack the images. It provides the offsets in pixels so you can see how much drift you are getting. So measure the shift for 1 minutes of the stack, 2 minutes, 3 minutes, etc. That way you can see how much you can tolerate by carefully examining the stacked images, as well as looking at the shift in the offsets (rms error is close to 1/2 of the shift in offsets. Your optimal exposure is something less than the image that shows no tracking defects, non-round stars etc, so you have some leaway. Note you will want to try this in different parts of the sky, it will affect your tracking. You will find with experience in polar aligning, making sure the mount is on a stable base, etc, that you will get better at unguided imaging than what you can do first starting out. I do like it because it is one less thing to worry about, not having to guide. And knowing it would be hard for me to do better guiding anyway. I live in a high Bortle 8 area, so even NB filters do not need more than 1 minute exposures generally. So I have been very happy with this approach.
CS
Rick

Thanks for the clear explanation Rick, much appreciated. I hadn't looked at PPEC yet, as I went almost straight to NINA (after struggling to get Stellarmate to work). I definitely need test exposures. But I see a small challenge with DSS as I do post on a Mac, and DSS is Windows only. I could try DSS on my NINA system, a Mele 3, but that might blow it up, as it is not the fastest processor around. Do you have alternatives for the kind of analysis you described?

Well, you can stack in any stacking software that runs on a Mac, then just look at the images up close visually, you can expand until you can see individual pixels.. Take 10 s, 30s, 1 m, 2m, 3m exposures on say an open cluster with reasonably bright stars and see when you start to see tracking errors on the stars. Ideally stack enough of each sub exposure time so the total time is the same for each set of sub exposures, for a fair comparison. In the end the rms error or offset shift is only a surrogate metric, but don't get wrapped up in a number. If you can't tell the difference in the image it doesn't matter what your rms is. For example I see some folks complain that they can't get <0.3" rms or something, without even thinking that it won't make a difference if you sky conditions give you only 2.5", on very few nights do many of us get that sort of seeing often.  But it depends on how well you can polar align and how good and stable your mount is. But it is worth trying, as you will see from many threads guiding can be complicated and has its own issues. This hobby is complicated enough without jumping in the deep end, my advice is to start simple, and then make changes that are needed as you master that. And anyway, no way to tell if your guiding is helping, if you go that route, unless you know what you can do without it. Here is one of my recent examples, 1 minute exposures, no guiding at FL=1480 mm, so it can be done reliably: 
https://www.astrobin.com/yzxzpf/

Good luck
Rick

WOW, more than 3300 exposures!! How long did stacking take?

I stack each night, then stack the stacks in DSS. The new DSS version 5 is blazingly fast. Calibration, registering and stacking takes maybe 10-20 minutes for each night. I load everything and let it run. Final stack of stacks is 2 minutes. So this is not an issue. And a 4 tb hard drive is $100, so storage is cheap.

But in the end it doesn't really matter how slow the stacking is, as long as the stacking program can handle it. It is automated, so just let it run...
Rick
Like
 
Register or login to create to post a reply.