×

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

Bi-monthly release with minor bug fixes and improvements

Can not calibrate Images captured with EKOS (stellarmate) in Pixinsight?

  • Posts: 969
  • Thank you received: 94
Hi
Are you certain that PI is not trying to debayer the light frames; a default setting perhaps? The lights you have are to create only a monochrome image? I ask because the 294 produces superb colour images; it would be a pity to create only mono from it.
Last edit: 5 years 1 month ago by alacant.
5 years 1 month ago #34396

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

  • Posts: 48
  • Thank you received: 3
I set the images to be taken in RAW16. That's how I always do it, also in SharpCap. Debayering is done after calibration, I'm sure of that. If I compare the Fits data from an image taken in sharpcap the Geometry data is exactly the same. EKOS just adds a lot more information, which is great, but probably some info that is ambiguous...

This is what PI tells me when loading an image taken with EKOS:

open "C:/****/StellarMateCaptures/M81/M 81_Light_30_secs_001.fits"
Reading 1 file(s):
C:/****/StellarMateCaptures/M81/M 81_Light_30_secs_001.fits
** Warning: Deprecated format: FITS
52 FITS keywords extracted.
Reading FITS image: 16-bit integers, 1 channel(s), 4144x2816 pixels: done
* Loaded astrometric solution:
Reference matrix (world[ra,dec] = matrix * image[x,y]):
+3.19292082e-04 -5.45096074e-04 +1.06354272e-01
-5.45096074e-04 -3.19292082e-04 +1.57888942e+00
WCS transformation ...... linear
Projection .............. Gnomonic
Projection origin ....... [2071.500000 1408.500000]px -> [RA: 9 55 34.162 Dec: +69 08 41.16]
Resolution .............. 2.274 arcsec/px
Rotation ................ -59.640 deg (flipped)
Transformation errors ... ex=4.55e-13 ey=2.5e-12 px
Observation date ........ 2019-01-28 19:46:36
Focal distance .......... 419.93 mm
Pixel size .............. 4.63 um
Field of view ........... 2d 37' 4.3" x 1d 46' 44.2"
Image center ............ RA: 9 55 34.454 Dec: +69 08 40.75
Image bounds:
top-left ............. RA: 9 56 51.450 Dec: +70 43 22.71
top-right ............ RA: 10 11 07.300 Dec: +68 25 10.89
bottom-left .......... RA: 9 39 01.828 Dec: +69 46 33.99
bottom-right ......... RA: 9 54 27.845 Dec: +67 33 56.94

** Warning: The FITS format does not define an unambiguous orientation of pixel data. The coordinates read on the image may be wrong.

This is what it tells me on an image taken in Sharpcap:

Reading 1 image(s):
C:/****/M81/03_11_57/rawframes/frame_0.fits
** Warning: Deprecated format: FITS
24 FITS keywords extracted.
Reading FITS image: 16-bit integers, 1 channel(s), 4144x2822 pixels: done

Maybe if I could take out the astrometric solution data it will not give me the message.
5 years 1 month ago #34397

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

  • Posts: 983
  • Thank you received: 375
Guys, I have just opened a single light and single flat frame in the latest PixInsight.
I would ignore these warnings:
** Warning: The FITS format does not define an unambiguous orientation of pixel data. The coordinates read on the image may be wrong
** Warning: Deprecated format: FIT
They do not (or should not) impact calibration process whatsoever.

BUT

When you take a look at FITS header of both files you will find the answer why you cannot calibrate frames.
Light frame: 4144px x 2816px
Flat frame: 4144px x 2822px

The geometry of the files does not match in axis2 (NAXIS2). This is the actual reason why you cannot calibrate.
However, I cannot point out a root cause. Driver issue?

Could you capture just 1 light and 1 flat frame with Ekos with debug option enabled? One by one. Exposure and object does not matter.
Check the FITS Header pixels and post the logs for us.
The following user(s) said Thank You: Marco de Keizer
5 years 1 month ago #34398

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

  • Posts: 48
  • Thank you received: 3
Well that's weird. Only the first image has, all other do have 2822px.
I checked out the other captures from IC1805. And there is also 1 image with 2816px (the second image in the sequence).

I did immediately check if could calibrate, leaving out the first image. And YES the image gets calibrated just fine!
I was so focused on the ambiguity message that I did not notice this discrepancy.

Sorry for the inconvenience caused!

I will now do as you asked and try to get you some logs and sample data.
5 years 1 month ago #34400

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

  • Posts: 983
  • Thank you received: 375
OK then, so now we know that some images miss 4 vertical lines. We don't know why but we're closer to a solution anyway ;-)
Let's debug. Maybe we'll find it out. Good luck!
5 years 1 month ago #34401

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

  • Posts: 985
  • Thank you received: 160
That reminds me of my most recent session. I had to delete the first light image taken in order to have Regim calibrate and stack them. I didn't examine what the cause was but I guess I know what it was now. I used an ASI 294, too.
5 years 1 month ago #34403

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

  • Posts: 48
  • Thank you received: 3
Hi,

I just added the files you requested to the Onedrive I shared earlier.

I Examined some of the other test capture sequences I did and some of them have the same issue. The first image in the sequence is missing a few rows of pixels.

Earlier I mentioned, there was also a second image in a sequence that had this, but it turns out it was also the first of a sequence.

I have tried to reproduce the issue, but of course all tests do not have this untill now.
5 years 1 month ago #34412

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

  • Posts: 985
  • Thank you received: 160
I also did a few tests and just like you, I could not reproduce the problem (yet). However, at least 3 ppl have experienced the same issue repeatedly, all 3 using an ASI camera.
Last edit: 5 years 1 month ago by Alfred.
5 years 1 month ago #34416

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

  • Posts: 1119
  • Thank you received: 182
The problem I described in a different thread does in fact seem to be similar:

www.indilib.org/forum/general/4521-wrong...d-in-ekos.html#34418

Fusis and Alfred diagnosed that correctly.

HOWEVER: I get the same warnings when I open a FITS image that has the CORRECT dimensions, i.e. 3520 pixels in the y-dimension.

So the stacking problem I get in DeepSky stacker and the FITS problem in PixInsight still are not exactly the same. The faulty dimension is a different issue.
Last edit: 5 years 1 month ago by Jose Corazon.
5 years 1 month ago #34419

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

  • Posts: 125
  • Thank you received: 24
If I may add, had this issue last week with ZWO 071 . Only one file out of 240 image had this issue . Just tossed that file out.
Last edit: 5 years 1 month ago by Tarun.
5 years 1 month ago #34421

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

  • Posts: 983
  • Thank you received: 375
I think it's a PixInsight issue.
I have just tried to calibrate my frames collected recently and... very strange thing happen. I cannot calibrate because PI reports "Incompatible image geometry" even though the files are just fine.
FITS files are <strong>2750 x 2200 px</strong>, and FITS header confirms this size. However when I try to calibrate the frames PI reads them as <strong>2749 x 2199 px</strong>. 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.
Have you seen anything like this?



UPDATE: Siril has no problem with calibrating the images whatsoever.
Last edit: 5 years 1 month ago by Radek Kaczorek.
5 years 1 month ago #34782
Attachments:

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

I believe there is another problem with PixInsight in opening INDI Bayered images as well. Need to file a bug report about this.
5 years 1 month ago #34823

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

Time to create page: 0.719 seconds