×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Bias frames - No data/empty?

  • Posts: 111
  • Thank you received: 40
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 2 months ago #47337

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

  • Posts: 984
  • Thank you received: 160
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 2 months ago by Alfred.
4 years 2 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 2 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 2 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 2 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 2 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 2 months ago #47365

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

  • Posts: 984
  • Thank you received: 160

Replied by Alfred on topic Bias frames - No data/empty?

Since light, dark and flat frames work fine, camera and connection must be OK. I've been using the same camera, same exposure time, etc. but the result is different. The only difference I can think of is software version. I'm on nightlies, what version of Indi/Kstars do you use?
4 years 2 months ago #47366

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

  • Posts: 77
  • Thank you received: 1
I’m not home to check the version (but I’ve used the astropi3 script). I’ve so far used two or three different versions for my images since august. Some for Mac and some for the Raspberry Pi 4. They all (all bias frames from August till now) show the same “empty” files, but still with a 23.4 MB filesize.
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 2 months ago #47367

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

  • Posts: 984
  • Thank you received: 160
So it is highly unlikely that software version is responsible for the issue. If you take a bias frame with simulators, is it empty, too?
Last edit: 4 years 2 months ago by Alfred.
4 years 2 months ago #47368

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

  • Posts: 984
  • Thank you received: 160
I'm running out of ideas. The next thing I would test is what happens with a different camera, does it produce empty bias frames, too? Do you own any another camera that you could do bias frame tests with?
4 years 2 months ago #47369

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

  • Posts: 77
  • Thank you received: 1
I’ll test with the simulator when I get home. I’ll also try taking bias frames with my guide cam then.
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 2 months ago #47370

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

Time to create page: 0.319 seconds