Jasem, I don't know whether this is important or not: the M65 file has no CFA pattern because it was (as far as I remember) acquired as a colour pattern in a fits file (?).

Right I can't figure out what's going now here, I can see the crash when it downsamples. Sending it to Robert to check out.

"Something still missing is the ability to load a raw image for Load and Slew."

By this do you mean Canon raw or something like that?

If so, that would be reasonable to add certainly, but right now I'm focused on making sure that Focus and Guide work well. Maybe we can add this before the release. There is code in KStars to convert Raw to FITS I think. The other thing I think would be nice would be TIFF support, which should also be possible.

Apologies for going off topic. But yes, I was referring to Canon CR2/CR3, and Nikon NEF. I image in native format because it's an easier workflow as it is compatible with darks and bias captured in camera without ekos. Currently I have to make a point of saving a FITS image to use later as a realignment frame.

Yes, support for Canon CR2 would be fine, if this could be integrated sometime in the future.

About tiff-support. I can solve my tiff-pics without problems. The only thing is, that for opening the tiffs in the align-module in kstars, you must delete the Filter "images" in the opening dialog

btw. It looks like the astrometry.cfg is not needed anymore now. Thanks for fixing this.

For me, downsampling (from1 to 5) does not work at all, I will leave this unchecked.
The message "Solver Failed" came very fast each time.

But from my perspective, the new downsampling code is responsible for a crash when I try to solve M65. This was the fits file that previously caused no problem at all.

TheSkyX uses sextractor. In case this is helpful, these are the settings both of my rigs use, one is a cadiotrope, the other is a reflector refractor.

Very helpful, thank you!

Welcome!
Caught a typo - those TSX settings work with both my cadiotrope (corrected dall-kirkham) and refractor (FSQ106).

I corrected a couple of things today. I finally got rid of those pesky messages that were being printed out to the console by the internal astrometry. I also corrected an issue with scale if you aren't using arc seconds per pix for the units. I also improved the logic for what happens when the solvers complete, which might make it stabler when it is doing a lot of operations. Please let me know if these changes help.

I think this might solve some issues where it failed to solve due to the scale

I will next take a good look at the parameters that folks have shared recently as well as what was hard coded in kstars to see if we can improve the profiles more.

Rob,

Is it possible the system parameters can be discovered through training on a set of data from the optics/camera in use? Perhaps make a tool that consumes a set of data and establishes a custom profile?

- Greg