Author Topic: PixInsight no longer correctly reading FireCapture fits  (Read 1810 times)

Offline rkayakr

  • Newcomer
  • Posts: 4
PixInsight no longer correctly reading FireCapture fits
« on: 2017 January 06 13:41:09 »
In the past I have successfully used PI with FireCapture v2.5 fit files.
Over the last few days I captured many subs from my ASI1600mm-c in FireCapture in 16 bit fit format. When I open the images in PI they are all displayed as uniform gray and image statistics show all pixels at .5.
The images open and display correctly in other applications. Older FireCapture fit images also no longer open correctly.
Did an update break the capability to read FireCapture fit files?

Offline Alejandro Tombolini

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1267
    • Próxima Sur
Re: PixInsight no longer correctly reading FireCapture fits
« Reply #1 on: 2017 January 06 13:47:27 »
Hi kayak, maybe you can share one of the image and someone check it.
Saludos, Alejandro.

Offline rkayakr

  • Newcomer
  • Posts: 4
Re: PixInsight no longer correctly reading FireCapture fits
« Reply #2 on: 2017 January 06 17:55:36 »
Thanks for the reply
Here is a link to a bias sub and the FireCapture text file
https://www.dropbox.com/sh/vy4dqn3u9famiiw/AAAZRnzf7CVTwz6Oo3JDobMca?dl=0

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PixInsight no longer correctly reading FireCapture fits
« Reply #3 on: 2017 January 07 02:44:16 »
No bug here. This is a 32-bit signed integer FITS image:

lskwd
bias_0000:
SIMPLE   T                         Java FITS: Thu Jan 05 09:52:32 EST 2017
BITPIX   32                       
NAXIS    2                         Dimensionality
NAXIS1   4656                     
NAXIS2   3520


Raw CCD frames, including bias frames, should be encoded as 16-bit unsigned integers. Anything else is an error denoting a poor software design and/or a wrong software configuration.

You can load this file is you enable the "signed integer images store physical pixel data" option in FITS Preferences (from Format Explorer). Anyway, this FITS image does not seem to contain a valid bias frame. Some relevant statistics are (in 16-bit range):

median      0.000549
minimum     0.000549
maximum     0.015152
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline rkayakr

  • Newcomer
  • Posts: 4
Re: PixInsight no longer correctly reading FireCapture fits
« Reply #4 on: 2017 January 09 06:16:18 »
Thanks for the reply and the work around.
As a user I have no control over how the file is saved.
Looking back I see that FireCapture  ASI178mc subs were stored as 16 bit fits but FireCapture  ASI1600mm subs are stored as 32 bit fits.
Yes, about .0005 is the level ImagesPlus reports.

Offline rkayakr

  • Newcomer
  • Posts: 4
Re: PixInsight no longer correctly reading FireCapture fits
« Reply #5 on: 2017 January 10 07:03:57 »
Follow up for anyone that has this problem in the future. FireCapture 2.5.05 saved images as 32 bit fits by default with no choices that PixInsight didn't like. FireCapture 2.5.10 has a check box under capture/settings that can be checked to yield 32 bit fits. Use 2.2.10 and make sure that box isn't checked and PI will read the 16 bit image fits.