East Wind Photography said:jrista said:Comet Lovejoy C/2014 Q2
I don't get to do comets often. They aren't in the sky that much, and even when they are, they are often low to the horizon during sunrise. Terry Lovejoy, comet-finder extraordinaire, discovered another comet in August 2014. It finally drifted into the northern horizon skies on December 24th, and I've been wanting to get some comet photons ever since. Finally got a chance last night:
![]()
In my haste to get some data before the moon came up, I ended up underexposing my subs. That resulted in the heavy banding of the 5D III showing through. I managed to eliminate most of it, but some is still visible in the coma. This was my first tracked comet image, and I managed to get some detail on the tail, which I'm fairly happy about. Hoping I get another opportunity to image this again, and get some better data.
Really nice. And very nice you have dark skies! I'm going to try the 600 tonight but I'm not expecting much. What was your integration to get this?
Nice one jristajrista said:Comet Lovejoy C/2014 Q2
I don't get to do comets often. They aren't in the sky that much, and even when they are, they are often low to the horizon during sunrise. Terry Lovejoy, comet-finder extraordinaire, discovered another comet in August 2014. It finally drifted into the northern horizon skies on December 24th, and I've been wanting to get some comet photons ever since. Finally got a chance last night:
![]()
In my haste to get some data before the moon came up, I ended up underexposing my subs. That resulted in the heavy banding of the 5D III showing through. I managed to eliminate most of it, but some is still visible in the coma. This was my first tracked comet image, and I managed to get some detail on the tail, which I'm fairly happy about. Hoping I get another opportunity to image this again, and get some better data.
East Wind Photography said:Seems that no matter what I do with DSS and the post in PS, this is the best I can get. By the time I work through the repetative curve process, the background ends up looking like 16 shades of grey. I know there is nice data here to be had but it's not coming out with the old school tools.
So I just submitted my trial license for pixinsight before I get too discouraged and give up.
jrista said:East Wind Photography said:Seems that no matter what I do with DSS and the post in PS, this is the best I can get. By the time I work through the repetative curve process, the background ends up looking like 16 shades of grey. I know there is nice data here to be had but it's not coming out with the old school tools.
So I just submitted my trial license for pixinsight before I get too discouraged and give up.
PixInsights calibration, registration, and integration tools are far better than DSS. The registration is far superior, and it includes a CometRegistration tool. I recommend following this:
http://harrysastroshed.com/pixinsight/pixinsight%20video%20files/2013%20pix%20vids/cometstack2/cometstack2.mp4
jrista said:Yeah, I've been having a lot of problems with DSS comet stacking as well. I found a PDF recently that explained a specific imaging procedure. The guy was imaging with a mono CCD with color filters, so his sequencing was complex. The trick was to use 20-second gaps between frames to ensure that stars were fully separated from each other. That is the only way that DSS will be able to properly apply kappa sigma clipping to reject stars when it registers on the comet. Anything else, and you'll have problems.
I've been integrating with PixInsight, and have had largely the same problem as with DSS. I think the star-gap technique is the right way to image a comet. If I get another change, I'll be employing it.
East Wind Photography said:jrista said:Yeah, I've been having a lot of problems with DSS comet stacking as well. I found a PDF recently that explained a specific imaging procedure. The guy was imaging with a mono CCD with color filters, so his sequencing was complex. The trick was to use 20-second gaps between frames to ensure that stars were fully separated from each other. That is the only way that DSS will be able to properly apply kappa sigma clipping to reject stars when it registers on the comet. Anything else, and you'll have problems.
I've been integrating with PixInsight, and have had largely the same problem as with DSS. I think the star-gap technique is the right way to image a comet. If I get another change, I'll be employing it.
Ah interesting. Since I took 130x20sec subs, I can use every other one that passes a decent score and see how that works. That gives me a 21 second gap between subs. Surely I can get at least 40 subs still.
East Wind Photography said:East Wind Photography said:jrista said:Yeah, I've been having a lot of problems with DSS comet stacking as well. I found a PDF recently that explained a specific imaging procedure. The guy was imaging with a mono CCD with color filters, so his sequencing was complex. The trick was to use 20-second gaps between frames to ensure that stars were fully separated from each other. That is the only way that DSS will be able to properly apply kappa sigma clipping to reject stars when it registers on the comet. Anything else, and you'll have problems.
I've been integrating with PixInsight, and have had largely the same problem as with DSS. I think the star-gap technique is the right way to image a comet. If I get another change, I'll be employing it.
Ah interesting. Since I took 130x20sec subs, I can use every other one that passes a decent score and see how that works. That gives me a 21 second gap between subs. Surely I can get at least 40 subs still.
So one of the issues I a see with pixinsight comet integration is that it assumes all subs are taken without moving the field of view. That is you specify where the comet is on the first and last subs and it interpolates the position on every other sub. I guess you have to do a star align on every sub first to normalize the fov then do comet integration.
jrista said:East Wind Photography said:East Wind Photography said:jrista said:Yeah, I've been having a lot of problems with DSS comet stacking as well. I found a PDF recently that explained a specific imaging procedure. The guy was imaging with a mono CCD with color filters, so his sequencing was complex. The trick was to use 20-second gaps between frames to ensure that stars were fully separated from each other. That is the only way that DSS will be able to properly apply kappa sigma clipping to reject stars when it registers on the comet. Anything else, and you'll have problems.
I've been integrating with PixInsight, and have had largely the same problem as with DSS. I think the star-gap technique is the right way to image a comet. If I get another change, I'll be employing it.
Ah interesting. Since I took 130x20sec subs, I can use every other one that passes a decent score and see how that works. That gives me a 21 second gap between subs. Surely I can get at least 40 subs still.
So one of the issues I a see with pixinsight comet integration is that it assumes all subs are taken without moving the field of view. That is you specify where the comet is on the first and last subs and it interpolates the position on every other sub. I guess you have to do a star align on every sub first to normalize the fov then do comet integration.
Yes, generally that's how comet imaging works. Most things assume that (DSS does for it's default integration, where you only mark the comet in the first and last subs sorted by time index.) If you change the field between subs, then your on your own.![]()