Hi folks,
I am experiencing some issues with my Pier 5 datasets and hope you have a solution for that ;-)
After the stacking process one of my first steps is the background extraction to remove the slight vignetting wihich is still left in the images.
No matter what tool (PixInsight, AffinityPhoto) or method (DBE, ABE, manually) I use, I always have those large ring artefacts afterwards. This is kind of annoying and takes me forever to manually remove. I am not having such issues with Pier 1 data for instance.
I am pretty sure I use the correct Dark and Flat files from the time the images were recorded.
The ring artefacts exists in almost every dataset I worked on lately, so this is just one example but looks pretty much the same on other images as well.
Any ideas? Do you face the same problems? How do you solve it?
Best regards,
Martin
The Master Flat is over/under compensating. I had similar problems a while ago.
I found this advice on the Pixinsight forum from the Pixinsight team:
Hi Martin,
As old_eyes says something is not right with your flats calibration. I use WBPP in Pixinsight and haven't had any issues. WBPP calibrates the flats with the master bias, and then the lights with the master flat and master dark.
Chris
That’s exactly the method I use, although I don’t use WBPP to create master calibration files (it just adds processing time as we don’t do nightly flats).
A lot of older books and online tutorials do not use the right methods for CMOS cameras.
Hi Martin,
Hopefully the suggestions have cured the problem for you and we will soon get to see the result.
If for any reason it doesn't then when using WBPP and before selecting to run it, is their a note saying that "No Master Flat will be used to calibrate the frames." I very much doubt it as I am sure you would have rectified the issue, however, the result you show can be closely replicated if a flat is not being used. Very strange.
Cheers,
Ray
Ray
Roboscopes Guinea Pig
Hi Martin,
Hopefully the suggestions have cured the problem for you and we will soon get to see the result.
If for any reason it doesn't then when using WBPP and before selecting to run it, is their a note saying that "No Master Flat will be used to calibrate the frames." I very much doubt it as I am sure you would have rectified the issue, however, the result you show can be closely replicated if a flat is not being used. Very strange.
Cheers,
Ray
OMG...
After months of calibration issues I finally found the - stupid - error. And I have to admit that Ray was on the right track...
I used to cactivate the "CFA images" checkmark for the lightframes in WBPP, select the correct Bayer Pattern (RGGB) and then click "apply to all lightframes".
What I did not recognize all the time: you have to do the same thing for the flat frames as well?! How stupid is that? While the frames obviously have to be produced by the same camera, I assumed the "sophisticated PixInsight" SW would also automatically apply those settings to all relevant calibration frames... Oh boy, this took me uncounted hours and ours to figure out.
I only recognized the warning in WBPP that the flat frames didn´t match the darkframe time. OK, I knew that, sure. But I didn´t recognize there was no Flat calibration whatsoever being performed.
Hopefully somebody else can learn from my stupidness (or is it a bad GUI programming in PixInsight?) and doesn´t have to troubleshoot forever as I did...
Now I can re-do all my work and see where I´m going with that.
As a little christmal´s teaser you´ll find the christmas tree cluster from job 1932 ;-)
Happy holidays everybody!
CS
Martin
PS: Waiting for the big discussion about the new BlurXTerminator :-)
Hi Martin,
Hopefully the suggestions have cured the problem for you and we will soon get to see the result.
If for any reason it doesn't then when using WBPP and before selecting to run it, is their a note saying that "No Master Flat will be used to calibrate the frames." I very much doubt it as I am sure you would have rectified the issue, however, the result you show can be closely replicated if a flat is not being used. Very strange.
Cheers,
Ray
OMG...
After months of calibration issues I finally found the - stupid - error. And I have to admit that Ray was on the right track...
I used to cactivate the "CFA images" checkmark for the lightframes in WBPP, select the correct Bayer Pattern (RGGB) and then click "apply to all lightframes".
What I did not recognize all the time: you have to do the same thing for the flat frames as well?! How stupid is that? While the frames obviously have to be produced by the same camera, I assumed the "sophisticated PixInsight" SW would also automatically apply those settings to all relevant calibration frames... Oh boy, this took me uncounted hours and ours to figure out.
I only recognized the warning in WBPP that the flat frames didn´t match the darkframe time. OK, I knew that, sure. But I didn´t recognize there was no Flat calibration whatsoever being performed.
Hopefully somebody else can learn from my stupidness (or is it a bad GUI programming in PixInsight?) and doesn´t have to troubleshoot forever as I did...
Now I can re-do all my work and see where I´m going with that.
As a little christmal´s teaser you´ll find the christmas tree cluster from job 1932 ;-)
Happy holidays everybody!
CS
Martin
PS: Waiting for the big discussion about the new BlurXTerminator :-)
Glad you got it sorted Martin. These little conceptual problems trip me up all the time and can be very difficult to trace where you went wrong.
I am trying out BlurExterminator and so far I like it. A nice subtle effect. More when I have finished the trial and decided yes or no.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
You have declined cookies. This decision can be reversed.
FLI
656 Imaging
10 Micron
Planewave
ZWO
Roboscopes
802 Kingsbury Road
Birmingham
B24 9PS
United Kingdom
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.