×

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

Bi-monthly release with minor bug fixes and improvements

FITS file size not a multiple of 2880 anymore

  • Posts: 80
  • Thank you received: 4
stacking pictures I took in June (EKOS/INDI May versions with toupcam driver) with pictures taken recently (EKOS/INDI July versions with toupcam driver) I got errors. Closer inspection showed that the June files conform to the FITS standard with HDU/file size being a multiple of 2880 bytes and the newer files do not conform.

Could this issue please be resolved in the next version?

Markus

fitsverify 4.20 (CFITSIO V3.490)


File: NGC_6781_Light_Halpha_300_secs_2022-09-12T21-26-48_006.fits

1 Header-Data Units in this file.

=================== HDU 1: Primary Array ===================

59 header keywords

16-bit integer pixels, 2 axes (3112 x 2084),

< End-of-File >
*** Error: File has extra byte(s) after last HDU at byte 12977280.

++++++++++++++++++++++ Error Summary ++++++++++++++++++++++

HDU# Name (version) Type Warnings Errors
1 Primary Array 0 0
End-of-file 0 1

**** Verification found 0 warning(s) and 1 error(s). ****
Last edit: 1 year 6 months ago by Markus Kempf.
1 year 6 months ago #86358

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

  • Posts: 333
  • Thank you received: 92
ASTAP crashed in these files when it tries to change a header keyword. But it is now avoided in ASTAP version 2022.09.16. But the Ekos/Indi files are still not conform the FITS standard.

I'm not familiar with Ekos/Indi bug/issue tracker but raised an issue here
github.com/indilib/indi/issues/1733

Han
1 year 6 months ago #86359

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

Please check master and see if that fixes the issue.
1 year 6 months ago #86360

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

  • Posts: 80
  • Thank you received: 4
Hi Jasem,

could you elaborate bit more on what exactly should be done. I have tested it with Kstars 3.6.0 Stable and
org.kde.kstars: Welcome to KStars 3.6.1 Beta
org.kde.kstars: Build: 2022-09-17T21:16:43Z
with no change, still the FITS files do not conform. Do I have to use a nightly build of indilib and 3rd party drivers on my remote PC?

Markus
1 year 6 months ago #86413

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

  • Posts: 80
  • Thank you received: 4
installed the latest nightly build, but get a crash loop after connecting.
org.kde.kstars.indi: INDI driver "indi_toupcam_ccd" crashed!

Markus
1 year 6 months ago #86424

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

  • Posts: 80
  • Thank you received: 4
all good with Kstars 3.6.1 Stable and Indilib v.1.9.8!
THANK YOU!

Markus
1 year 5 months ago #86929

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

  • Posts: 4
  • Thank you received: 0
This problem seems to still be in Mac OS X versions of 3.6.3. I tried the dmg downloaded from the KDE Education page, kstars-3.6.3-1637-macos-clang-x86_64.dmg downloaded from binary-factory.kde.org/job/KStars_Release_macos/ and the 3.6.4beta that Robert Lancaster posted a short while ago. All write FITS files that fail the Tester page in the same way as described in the original post on this topic. A lot of apps ignore it, but it seems AstroImageJ is more strict as it fails with an invalid header error. I'm using the SBIG CCD on MAC OS X 12.6.3

DanZ
1 year 1 month ago #90758

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

  • Posts: 4
  • Thank you received: 0
An update: I did a fresh install of Ubuntu 22.04 on a raspberry pi 4 and installed 3.6.3 stable and this format error was NOT in the fits files created with this setup. Seems like it could be Mac specific.
1 year 1 month ago #90768

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

Time to create page: 1.150 seconds