Console message 'Po...
 
Share:
Notifications
Clear all

MAY 4 2026: APP 2.0.0-beta44 has been released !

New improved internal memory controls should now work on all computers

May 1 2026: APP 2.0.0-beta43 has been released !

Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.

Apr 29 2026 APP 2.0.0-beta42 has been released !

New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

Console message 'Possible sensor offset issue'

4 Posts
3 Users
2 Reactions
1,448 Views
(@kevin-lewis)
Main Sequence Star
Joined: 7 years ago
Posts: 17
Topic starter  

Good morning,

I'm using APP 1.075 beta4 to calibrate and integrate images taken on a Canon 5D MkIV DSLR and see this message during integration.

09:54:18 - 6) INTEGRATE: integrate light frames: wrote frame: 8 to file mapper
09:54:20 - GENERAL IMAGE LOADER: loading frame D:\Temp_workspace\200919 Veil Nebula\Lights\L__21B9042_ISO800_240s__24C.CR2
09:54:20 - 6) INTEGRATE: integrate light frames: loaded frame 9 of 36 frames
09:54:20 - GENERAL IMAGE LOADER: frame D:\Temp_workspace\200919 Veil Nebula\Lights\L__21B9041_ISO800_240s__24C.CR2 was loaded successfully
09:54:21 - 6) INTEGRATE: integrate light frames: LNC: got center coordinates and area of frame 9 in integration composition
09:54:22 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
09:54:22 - 2) CALIBRATE: Adaptive Data Pedestal set at: 9.761E-03
09:54:22 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
09:54:22 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 3.125E-02 for channel 1
09:54:22 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.112E-02 for channel 1
09:54:22 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
09:54:22 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
09:54:22 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.

Details of the DSLR raw files are:

40 x 240 second Lights, 20 x Flats, 20 x  Darks, 50 x Bias. Everything was shot at iso800 and same sensor temperature

Anything I should be doing different during the calibration or is this message fairly typical?

best regards

Kev


This topic was modified 7 years ago 2 times by Kevin Lewis

   
ReplyQuote
(@mariusz)
Brown Dwarf
Joined: 8 years ago
Posts: 6
 

Hello.

 

I have the same console message. 

 

MBP, OS Mojave

APP 1.075 beta4

Canon 60d, ISO 800

Lights 17x 360s

Darks 26x 360s

Bias 40x 1/125s

Flats 40x 1/13s

DarkFlats 40x 1/13s

 

What is wrong?

 

Best regards

Mariusz

 

 



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Nothing, it is a warning, however the values are the same or very close to being the same. It shouldn't impact the result.



   
mariusz and Kevin Lewis reacted
ReplyQuote
(@kevin-lewis)
Main Sequence Star
Joined: 7 years ago
Posts: 17
Topic starter  
Posted by: @vincent-mod

Nothing, it is a warning, however the values are the same or very close to being the same. It shouldn't impact the result.

Thank you Vincent. I'll continue to ignore it 🙂



   
ReplyQuote
Share: