×

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

Bi-monthly release with minor bug fixes and improvements

Bias frames - No data/empty?

  • Posts: 77
  • Thank you received: 1
Actually, Ekos selects that exposure time for me. I (by accident) sat the time to 3.725 seconds last time, but Ekos just exposed the bias frames as the lowest possible (the 0.00003 s that’s written in the header). The file was named with the 3.725 label though.
SkyWatcher ED80 Pro
Skywatcher HEQ5 Pro with Rowan Belt Mod with EQDIR cable
ZWO ASI294MC Pro imaging camera
QHY5L-II-C guide camera on 50mm guidescope
DeepSkyDad AF3 autofocuser
Raspberry Pi 4 4GB running Kstars/Ekos
4 years 3 months ago #47330

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

  • Posts: 1119
  • Thank you received: 182
Have you tried shooting them as light frames and progressively setting a shorter exposure time? Then you find out when your camera hardware becomes limiting.
4 years 3 months ago #47331

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

  • Posts: 77
  • Thank you received: 1
No, but I don’t think that’ll help since Ekos automatically sets the bias exposure time to 3.2E-5 s, no matter what I enter as exposure time.
SkyWatcher ED80 Pro
Skywatcher HEQ5 Pro with Rowan Belt Mod with EQDIR cable
ZWO ASI294MC Pro imaging camera
QHY5L-II-C guide camera on 50mm guidescope
DeepSkyDad AF3 autofocuser
Raspberry Pi 4 4GB running Kstars/Ekos
4 years 3 months ago #47334

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

  • Posts: 1119
  • Thank you received: 182
I understand.

That's when you set the tab for 'Bias'.

What I meant was that you should set the tab for 'Light' frames, then take images at the shortest exposure your camera will allow (Probably 1/1000s). Then use those as bias frames.
4 years 3 months ago #47335

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

  • Posts: 554
  • Thank you received: 138
Let's try Science.
There's a hypothesis that the camera collects no data if the exposure is too short.
Try taking dark frames at shorter times until you see that the data goes to all zeroes.
Or try lights with the camera covered, it's the same thing.

Maybe there's a point where if the exposure is too short the camera does nothing.
4 years 3 months ago #47336

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

  • Posts: 111
  • Thank you received: 41
There is an excellent book/tutorial CCD Data Reduction Guide
that explains in very great detail with Python (astropy) code how actually an astronomical CCD image is formed.
In chapter Understanding an astronomical CCD image
is written:

In sub chapter Construction of an artificial (but realistic) image
is explained in detail how a offset (bias) image is formed.
4 years 3 months ago #47337

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

  • Posts: 989
  • Thank you received: 161
My bias frame was (automatically) taken with 3.200000E-05 exposure time (pulldown menu set to BIAS in Ekos) too and it is NOT empty. So something different is not right with andefeldt's setup.

Last edit: 4 years 3 months ago by Alfred.
4 years 3 months ago #47351
Attachments:

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

  • Posts: 1957
  • Thank you received: 420
It is possible that nothing is wrong with the Bias subs but rather with the way they are processed with PixInsight. Perhaps this should be asked in the PixInsight forum first? Either this leads to a correct way of processing them or to the conclusion that indeed the bias subs are wrong. In my experience it is best to start debugging at the end of the chain rather than at the start.


Wouter
4 years 3 months ago #47352

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

  • Posts: 1119
  • Thank you received: 182
This may be a stupid question, but how can the value for image resolution (arcsec/pixel) be negative in the FITS header?

SCALE = -9.551690E+02 / arcsecs per pixel
4 years 3 months ago #47353

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

So I'm not sure about the bias frame values, but the scale could be to missing focal length value. I just added more checks in INDI::CCD to prevent against generating bogus scale values.
The following user(s) said Thank You: Alfred
4 years 3 months ago #47363

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

  • Posts: 77
  • Thank you received: 1
Wouter, all my Bias frames are produced in Kstars/Ekos and they show up as emtpy in all fits viewers. Values are 0 for min, max, std dev, median etc. Loading the fits files in KStars/Ekos doesn't give me a view as "Herrhausen" produces. My view is just completely white i Kstars (completely black in all other fits viewer programs) even after I've auto-stretched them. So I really don't think the problem is with PixInsight?
SkyWatcher ED80 Pro
Skywatcher HEQ5 Pro with Rowan Belt Mod with EQDIR cable
ZWO ASI294MC Pro imaging camera
QHY5L-II-C guide camera on 50mm guidescope
DeepSkyDad AF3 autofocuser
Raspberry Pi 4 4GB running Kstars/Ekos
4 years 3 months ago #47364

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

  • Posts: 77
  • Thank you received: 1
@knro, my focal length are written in Ekos, but maybe it's not transfered to the Bias info?
SkyWatcher ED80 Pro
Skywatcher HEQ5 Pro with Rowan Belt Mod with EQDIR cable
ZWO ASI294MC Pro imaging camera
QHY5L-II-C guide camera on 50mm guidescope
DeepSkyDad AF3 autofocuser
Raspberry Pi 4 4GB running Kstars/Ekos
4 years 3 months ago #47365

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

Time to create page: 0.413 seconds