Problem when removi...
 
Share:
Notifications
Clear all

31 July 2020 - Comet Registration video tutorial using APP 1.083-beta1 released.

30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.

9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp

2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!

Problem when removing light pollution  

  RSS

(@aljo)
Molecular Cloud Customer
Joined: 3 months ago
Posts: 3
September 24, 2020 11:38  

When I try to use the light pollution tool, it begins by neutralising the background of the image, so I can no longer see the light pollution! This is before I have drawn the boxes. What am I doing wrong? This did not use to happen for me.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 25, 2020 12:24  

Then you likely already have a very nice background. You probably can still get it to show up by stretching more, try a stretch preset (on the right under the DDP checkbox) for 30%.


ReplyQuote
(@aljo)
Molecular Cloud Customer
Joined: 3 months ago
Posts: 3
September 25, 2020 12:39  

You don't understand. Immediately after integration the pollution was clearly visible. When I selected the tool, without drawing any boxes or telling it to calculate, it was not visible, and nor were most stars. it looked like an unstretched image.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 25, 2020 13:29  

That seems like a data issue then. I may have to have a look at it, can you show a before and after screenshot?


ReplyQuote
(@aljo)
Molecular Cloud Customer
Joined: 3 months ago
Posts: 3
September 25, 2020 15:53  

Unfortunately I did not take screenshots. I was able to process the problem image by putting it back into APP. It was made from 30GB of input data, so processing used up most of the available storage.

I have run APP with different data and the problem did not occur again.

 


Share: