Adding Pedestal for...
 
Share:
Notifications
Clear all

2022-05-29: APP 2.0.0-beta2 has been released !

Release notes

Download links per platform:

windows 2.0.0-beta2

macOS x86_64 2.0.0-beta2

macOS arm64 M1 2.0.0-beta2

Linux DEB 2.0.0-beta2

Linux RPM 2.0.0-beta2

Adding Pedestal for Lights calibration


 Axel
(@axel)
White Dwarf Customer
Joined: 5 years ago
Posts: 19
Topic starter  

Hi Mabula,

I have an issue after light calibration (Ha 300sec shot with ASI 1600MMpro Gain 200 / offset50) in APP because the calibrated lights appear heavily black clipped. I get the same result in PI unless I add a 800DN pedestal where everything works fine.

All masters are calibrated in APP (dark master / flat master / BPM) - calibration masters look fine.

How can I get APP to work?

Best Regards

Axel

 


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3158
 

Dear Alex,

Are all masters created with APP 1.061 ?

First a direct solution in APP:

With the batch modify tool, you can simply add a pedestal to a batch light frames.

Just load your lights, enter the amount of ADU that you wish to add into the add field and click on add.

Automated Solution in next version called Adaptive Data Pedestal:

APP 1.062 will have an automated solution for that in the calirbation engine, which will also fix residual amp glow possibly with camera's that have strong Amp Glow.

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processir-1-062-preparing-next-release/

  • Improved, data calibration of severe Amp Glow, amp glow does not behave linearly so it's always important to not use dark scaling if your sensor has significant amp glow. You need to create darks of the same offset, gain/ISO, temperature and exposure time as your lights, to properly deal with amp glow. Now, in cases of strong amp glow, it can happen that the glow is so strong when compared to the real photon signal and noise in our data that a large part of these pixels will be calibrated to zero if we subtract a suitable dark frame. This will happen in each frame for different pixels and that will have a cumulative effect in image integration. The statistics of the pixelstacks will actually be skewed to the upside still showing residual amp glow in some cases. In 2) Calibrate, there is now a new option that will adaptively solve this for data were this happens. It's called Adaptive Data Pedestal. If you enable this, it will prevent severe clipping on the black point in calibration, and will therefore prevent skewed pixel statistics in image integration. It's an adaptive algorithm, so it takes a little bit more time in calibration. A case were you probably need to enable this is strong Amp Glow with camera's like the ZWO ASI183. For most camera's and datasets, this setting will have no effect, but in cases where severe black clipping in calibration does occur, for whatever reason, this setting will prevent it and will ensure precise calibration and no-skewed statistics in image integration.
Adaptive Data Pedestal

Example of an integration of ZWO ASI183mm-c Oxygen-III data provided by Warren Landis @orangemaze, with and without the setting enabled in calibration:

APP 1062 ampglow fix
APP 1061 ampglow asi183

In this case, the amp glow is not calibrated out with the Adaptive Data Pedestal disabled, because the amp glow simply overpowers the real OIII data on the location of the amp-glow. By enabling the Adaptive Data Pedestal, the amp glow is properly calibrated.

Let me know if the proposed solution works and if you have other questions 😉

Mabula


ReplyQuote
 Axel
(@axel)
White Dwarf Customer
Joined: 5 years ago
Posts: 19
Topic starter  

Hi Mabula,

Yes I use the latest version of APP.

In the Batch Modify tool should I add 800 in the field "add" and then click on "offsets ok"?

Thanks

Axel


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3158
 

Hi Axel @axel,

Yes, add 800 in the add field. But then click on add !

The offsets ok button, is to crop based on pixel offsets 😉

Mabula


ReplyQuote
 Axel
(@axel)
White Dwarf Customer
Joined: 5 years ago
Posts: 19
Topic starter  

Thanks for your help Mabula. I reprocessed the whole stack and it is now ok!!!!

Looking forward for the next release 😎 


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3158
 
Posted by: Axel

Thanks for your help Mabula. I reprocessed the whole stack and it is now ok!!!!

Looking forward for the next release 😎 

Excellent @Axel, that's great to hear 😉

I have released APP 1.062 today 😉

If you enable the Adaptive Pedestal in 2) calibrate, it will fix this problem automatically.

Cheers,

Mabula

 


ReplyQuote
(@schurig)
Main Sequence Star Customer
Joined: 5 years ago
Posts: 70
 

Hi Mabula,

Does this new option also affect the creation of Master Calibration Frames? I have the 183MMPro and I want to know whether I should click the checkbox when I create Bias Master, Dark Master and Flat Master (with loaded Bias Master).

Thanks, Stephan


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3158
 

Hi Stephan @schurig,

No it doesn't affect the creation of master calibration frames. I affects how the masterdark is applied to the light frame data.

So you can use masters created before APP 1.062 with this setting.

The Adaptive Data Pedestal is used when actually calibrating the light frames. So it can be disabled if you are only creating the master frames, it will have no influence.

Let me know if this answers your questions.

Kind regards,

Mabula


ReplyQuote
(@schurig)
Main Sequence Star Customer
Joined: 5 years ago
Posts: 70
 

Thanx, now it is clear to me.


ReplyQuote
(@lead_weight)
Main Sequence Star Customer
Joined: 5 years ago
Posts: 33
 

I tried adding a pedestal value in 1.83 beta, and it just adds 0.0 no matter what value I put in the add field for batch editing.


ReplyQuote
Share: