NGC281 - The Pacman Nebula

John_Gill

Well-known member
Try this, start at the very beginning, with all the "raw" images and use Blink to discard any bad images. Because you have enuff data, you can be ruthless. Then ImageCalibration, CosmeticCorrection, SubframeSelector and again be ruthless. Now you will have the best of the best images and continue processing ... It might be a worthwhile project.
 
  • Like
Reactions: StuartT

StuartT

Well-known member
Mar 5, 2022
348
51
Try this, start at the very beginning, with all the "raw" images and use Blink to discard any bad images. Because you have enuff data, you can be ruthless. Then ImageCalibration, CosmeticCorrection, SubframeSelector and again be ruthless. Now you will have the best of the best images and continue processing ... It might be a worthwhile project.
thanks. I've never used SubframeSelector so I'll have to read up about that
 

scotty38

Well-known member
Apr 5, 2021
279
87
United Kingdom
Try this, start at the very beginning, with all the "raw" images and use Blink to discard any bad images. Because you have enuff data, you can be ruthless. Then ImageCalibration, CosmeticCorrection, SubframeSelector and again be ruthless. Now you will have the best of the best images and continue processing ... It might be a worthwhile project.
I realise this is not really the forum for it but given all the weighting WBPP now applies etc etc do we need to be ruthless with blink and/or subframe selector any longer? I genuinely understood it that the WBPP weighting takes care of that now. I get you can still do it if you wish of course so just interested in your thoughts.
 

John_Gill

Well-known member
I use the Blink in the beginning, to remove obvious faulty frames mostly due to bad guiding or cloud. If I am combining data from multiple nights then I tend to be a little more ruthless and toss anything under par. The new WBPP weighting works great, but I still reject any frames below a certain level.
 
  • Like
Reactions: scotty38