old FIT file year 2014

Somewhere to ask questions about the best way to use SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Post Reply
User avatar
carlomuccini
Posts: 260
Joined: Mon Apr 27, 2020 12:42 pm
Location: Montecatini Terme (PT), Italy
Contact:

old FIT file year 2014

#1

Post by carlomuccini »

I wanted to open an old FIT file from 2014 in deepsky camera. I click on browse, select the file but it doesn't load it, it doesn't do anything, it doesn't even give an error message.
It's not a serious problem ...

I attach the "incriminated" file, one of a series of 30 FITs but none of them opens

https://drive.google.com/file/d/1LRGdn8 ... sp=sharing


Carlo
User avatar
Menno555
Posts: 1186
Joined: Mon Apr 20, 2020 2:19 pm
Location: The Netherlands
Contact:

Re: old FIT file year 2014

#2

Post by Menno555 »

FITS Liberator recognises it and gives all the details. I also can open it in SiriL and Deep Sky Stacker.
The SC log shows: No support for loading image with -32 bits per pixel.
I presume the minus-symbol is the culprit but Robin for sure knows what that means :)

Menno
Meade LX200 8" f/10 ACF OTA / Ioptron CEM25EC / Zwo ASI071MC Pro / Zwo ASI482MC
User avatar
turfpit
Posts: 2257
Joined: Mon Feb 13, 2017 8:13 pm
Location: UK
Contact:

Re: old FIT file year 2014

#3

Post by turfpit »

Opens in Astro Pixel Processor 2.00 beta29
Opens in Pixinsight latest version
Opens in FITS Liberator 4
Fails in FITS Liberator 3 with 'could not load file, the selected file is not supported'

As Menno says it looks like the BITPIX=-32 is the culprit.

Dave
User avatar
admin
Site Admin
Posts: 17464
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: old FIT file year 2014

#4

Post by admin »

Hi,

BITPIX=-32 is valid for fits and indicates that the file contains 32 bit *floating point* data, rather than 32 bit integer data.

However, SharpCap doesn't currently support reading 32 bit floating point fits files (and only has partial support for 32 bit integer fits file reading). The main problem is that SharpCap largely works internally with either 8 or 16 bit depths, with only some areas coping with 32 bit data. Loading a 32 bit FITS would therefore meant that detail would be thrown away as the file is loaded, which isn't ideal.

cheers,

Robin
Post Reply