×

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: 1119
  • Thank you received: 182
From your previous post I understand that the FITS header shows 2750x2200. But in the PI console upon importing the image PixInsight reads 1 px less in each dimension. That is also the dimension listed on the ATIK website.
If the ACTUAL pixel COUNT (not FITS header) shows 2750x2200 then the information on the ATIK website must either be 1) wrong, or 2) the resolution was rounded up to the next number that was divisible by 2, or 3) the driver that PI reads out states the wrong value in the console (as does the website), or 4) PI entered the value provided to it by ATIK into the database it uses for its calculations and disregards the FITS header AND the actual pixel count.
Looks like that cannot be solved without input from ATIK. You need confirmation of what the actual pixel count of the sensor really is.
5 years 3 days ago #36956

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

  • Posts: 106
  • Thank you received: 7

I know this Pixinsight error. To calibrate images Pixinsight needs, that all images (LIGHT, BIAS, ....) have the same image geometry (width and height in pixels). Your image may have different sizes.
This can possible origin from this bug, which came back in my INDI installation:
indilib.org/forum/general/4889-false-ima...gain-please-fix.html

Thomas
5 years 2 days ago #36975

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

  • Posts: 983
  • Thank you received: 375
This is NOT PixInsight error. It has been discussed on PixInsight forum and the issue is for sure related to actual geometry written to a FITS.
There is full consistency between actual image geometry and FITS header, however there is no consistency at all between actual image geometry and CCD specs on ATIK site.
Does anybody here use ATIK's windows software so we can confirm image geometry using native application? I don't even have a windows machine to try it on.
5 years 2 days ago #36983

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

  • Posts: 1185
  • Thank you received: 370
Hi Marco,
the calibration error is not related to the warning. I guess in your calibration setup geometries of lights, masterdark and flats do not match.
Wolfgang
5 years 2 days ago #36988

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

  • Posts: 48
  • Thank you received: 3
To all, this issue has been resolved some weeks ago.
It was actually a bug in the ASI camera driver which would leave out some rows of pixels when switching between binning levels.

It was not a Pixinsight issue.
5 years 2 days ago #36990

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

  • Posts: 106
  • Thank you received: 7
Hello Fusis,
I am on Jasems PPA and got updates regulary. Are you sure that this bug is gone. It is still there in my installation.
5 years 2 days ago #36997

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

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

I have not experienced it on my last session last Sunday. I'm on the nightly builds, although I have not updated in the last 10 days or so. I only update when I come across serious know issues. This prevents me from running into new issues.

I also keep a backup image available so I can always go back if I run into issues.

Cheers,

Marco
5 years 2 days ago #36999

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

  • Posts: 210
  • Thank you received: 104
Hi Thomas,
I look at Marco issue, but it was very different than your issue:
www.indilib.org/forum/general/4707-asi29...sue-3x3-and-4x4.html

This is probably the fix for this issue that is the cause for your problem.
In the solution Jasem say:
What changed in the driver is that it now strictly obeys that width % 8 must be zero

If I take the number for your camera:
- it start with a size of 5496, corresponding to width max.
- you ask for bin 4x4 : 5496/4 = 1374
- but 1374/8 = 171.75 , to respect the condition "width % 8 must be zero" it set the width to 171*8 = 1368
- Indi size are always unbinned so it is set to 1368*4 = 5472
- when you return to bin 1x1 it keep this size of 5472 making your new images not compatible with the first series.
The following user(s) said Thank You: Thomas Jäger
5 years 1 day ago #37008

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

  • Posts: 106
  • Thank you received: 7
You may be absolutely right. You can close my issue in mantis, I had to wait if Jasem fixes this driver.
By the way, this binning issue does not happen with EKOS as client. EKOS seems to handle it different.
Thomas
5 years 1 day ago #37012

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

  • Posts: 210
  • Thank you received: 104
Maybe Ekos do a CCD_FRAME_RESET to return to bin 1x1.
I not do that because one may want to change from bin 4x4 to 1x1 without changing the ROI that is set. If this cause the issue I can reconsider that.
5 years 1 day ago #37013

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

Time to create page: 0.542 seconds