Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - RadekK

Pages: [1]
1
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 18 13:32:48 »
Juan, it is much appreciated! Thanks for your support and responsiveness.

2
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 17 15:08:17 »
An update on the issue, so anybody looking for the solution finds it also here.

So the problem is exactly opposite to what I have thought! I have been using this Atik 460EX for over 3 years and it always imaged at 2750px x 2200 px. This geometry was always like that in FITS header and actual FITS data. I haven't used any other software than KStars/Ekos & INDI ever since so I never compared it to any other source. Also PixInsight was my choice for post-processing.
Having said that I would bet Atik 460EX chip resolution was 2750px x 2200 px :silly:
Recently the atik driver maintained by Peter Polakovi? (CloudMakers) has been replaced by Jasem Mutlaq (INDI) and the new driver was included in regular updates as a 3rdparty driver. I have updated my systems and noticed that I cannot calibrate new light frames with dark and bias frames library, which I maintain for myself. I noticed that the resolution of the new images changed to 2749px x 2199 px. First I thought t is PixInsight that crops the images, then I took it as a bug in the new driver BUT the actual issue is that it is the old driver that was wrong with the image geometry!
The native resolution of Atik 460EX is 2749px x 2199 px. Period.
This solves the issue!

3
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 10 07:00:35 »
It looks like the BAYERPAT property is not read from the header. I have just tested it on the M42 file and manually forcing the CFA pattern (according to BAYERPAT property) debayers properly.

4
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 10 02:41:29 »
That's right! It looks like the issue is on image acquisition side. I was mislead with several sets of data collected in various dates.
Thanks a lot for directions. Need to discuss this on INDI forum then ;)

5
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 10 02:25:30 »
I have just noted that all the files processed with the latest PI version report geometry missing 1 px in both axis. Whereas files processed with the older version read proper geometry.
Masterdark and superbias have been processed with older PI version. If I use them with recent lights I cannot calibrate BUT if I recompile them with the latest PI version they can be used in calibration process. However, if I do it all the files' geometry is read as missing 1 px in both axis. Even though the physical geometry is fine.
I think that the latest PI somehow loses this 1 px in both axis when reading FITS. Isn't it 2-dimentional array indexing issue? ;-)

6
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 10 02:12:31 »
Right, I uploaded wrong light frame. Please redownload the files that allow for reproducing the issue.
Also, attached the screenshot with the exact files uploaded.

BTW. Note the image size 2749 x 2199, which is not correct. When you open the image directly in PixInsight it reads 2750 x 2200 px (as per FITS header).

8
Bug Reports / Re: Incompatible image geometry - FITS cropped?
« on: 2019 February 09 16:24:07 »
The files are perfectly fine. I can calibrate them in any other software e.g. siril. When viewed in other software they show proper size and geometry.
Moreover they show proper size and geometry when opened in PixInsight. It seems something wrong is happening in Image Calibration module only (also in BatchPreProcessing).
BTW. I've been using PixInsight for a few years and the issue seems related to the latest version only. I have not observed it before.

9
Bug Reports / Incompatible image geometry - FITS cropped?
« on: 2019 February 09 14:27:25 »
I have just tried to calibrate my frames collected recently and... I cannot calibrate because PI reports "Incompatible image geometry" even though the files are just fine.
FITS files are 2750 x 2200 px, and FITS header confirms this size. However when I try to calibrate the frames PI reads them as 2749 x 2199 px. 1 pixel missing in both axis!
I inspected the frames and they ARE correct size and this is PixInsight that is wrong. I'm using the latest PixInsight 01.08.06.1457 Ripley (x64) running on Ubuntu 18.04 x64.
See the attached screenshot.

Pages: [1]