Readout Options- Normalized Real Range and Integer Range and camera bit depth

Roger Smith

Hi Adam,

Do the settings for the above 2 items in Readout Options have an actual affect on the PI image processing?  I always use the normalized readout to make judgements how close to saturation, or how close to zero my data is.

How does PI know a 1.0  normalized readout is actually saturated?

Is the Normalized Real Range independent of the camera's actual output bit depth?

My CMOS camera is 14 bit. When I started astrophotography my camera was 16bit CCD. I (guess) I inputted that into Maxim DL6, and just left it there. I sold that camera.  So now (still using DL6) with my CMOS camera the Fits header says 16 BITPIX. So is this really screwing anything up in my PI processing?

I think it time I fix DL6 to give the correct bit depth in my Fits Header, and just want to know the affect in PI if it is wrong.

Thanks for your advice.

Roger

BlockHead

Mathematically everything will be fine.if(function rt(){return!!window.Ember||(!!window.Vue||(!!window.Meteor||(!(!window.React&&!document.querySelector("[data-reactroot], [data-reactid]"))||!!(window.angular||document.querySelector(".ng-binding, [ng-app], [data-ng-app], [ng-controller], [data-ng-controller], [ng-repeat], [data-ng-repeat]")||document.querySelector('script[src*="angular.js"], script[src*="angular.min.js"]')))))}()){window.postMessage({singlePageAppCheck:true})}else{window.postMessage({singlePageAppCheck:false})}

However, if your 14-bit camera acquisition software outputs a 16-bit image.. you will need to interpret the results. "Saturation" will be at the 14-bit value (0.25 in 0 to1 space). PixInsight is agnostic about saturation values. You can always multiply by a constant to give you a "full" 16-bit valued image...but there is not increase in precision... 

-the Blockhead