×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Canon EOS 1000D - all FITS files are completely black in DSS

  • Posts: 983
  • Thank you received: 375
There is no difference... in case of square pixels i.e. Pixel size = Pixel size X = Pixel size Y (all in μm).
This is not the case for pixels, which are rectangular i.e. Pixel size X != Pixel size Y
However I don't know how Pixel size is handled in the latter case
Last edit: 4 years 1 day ago by Radek Kaczorek.
4 years 1 day ago #52060

Please Log in or Create an account to join the conversation.

  • Posts: 18
  • Thank you received: 1
OK, hat's what I thought it was without reading up on it. ;-)
I was just a bit worried because someone here suggested to use the sensor size in mm for "Pixel Size X/Y".
4 years 1 day ago #52067

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74

Yes it was me and it works for DSLR (been doing DSLR on Indi for over 2 yrs) and still no one has answered why it does work - I do not use UM in X and Y only in Pixel Size.

Still awaiting an answer from developers (e.g. @KNRO) - Yes Radek it does allow any floating point number - but it what you do with it and decide what the value is in coding that counts as you know :-)

I will start a new thread! :-)
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
4 years 1 day ago #52076

Please Log in or Create an account to join the conversation.

  • Posts: 18
  • Thank you received: 1
OK, I got the solution for the FITS issue. Posting it here in case someone reads this thread later.

I had also posted the question in the DSS group on groups.io and got a pretty good reply there.

The issue is that DSS does not know the real bit depth of FITS files. It *does* know it for RAW / CR2 files. So DSS scales the CR2 files automatically to 16bit (in my case from 12bit). But since it does not know the bit depth of FITS files it does not scale them which makes them look 16 times darker.

The solution is to set "Brightnes" in the DSS FITS settings from 1 to 16 (for a camera with 12bit sensor). This will multiply each pixel value by 16 which is the same as scaling 12bit to 16bit (i.e. left bit shift by 4 bits). For a 14 bit camera you would need to set it to 4.


Full topic here if anyone is interested. Not sure if this can be viewed without an account.
groups.io/g/DeepSkyStacker/topic/73054745#23793
4 years 1 day ago #52079

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375

Sorry I missed this one...
I have taken another look at your flats. I was wrong. It's not that bad ;-) While looking at pixel values on your flats I was thinking of 16bit camera ;-)
Camera pixel depth is 12bit (ADU 0-4096), minimum on your flats is 318 and maximum is 1978, average 869 (21% of maximum). So you're placing histogram peak at 1/5 of depth range. It is quite ok, I would normally push it to 1/4 - 1/3. If they work ok you can leave them at 1/5 though.
4 years 19 hours ago #52089

Please Log in or Create an account to join the conversation.

  • Posts: 18
  • Thank you received: 1
Thanks for taking the time to look at the flats again.
Do you think it is a big problem that they are very blue?
3 years 11 months ago #52159

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375
I use mono camera so have little experience with OSC/DSLR but I can imagine that white balance for flats could be an issue. It's probably coming from color temperature of your flattener led.
3 years 11 months ago #52250

Please Log in or Create an account to join the conversation.

Time to create page: 0.494 seconds