Ok, I think I successfully fixed the windows header issue. I have successfully build a new version

github.com/rlancaste/sexysolver-tester/releases/tag/1.4

Please test and let me know if I broke anything important. It was a big change, but one that should really help.

I just ran a bunch of the files that you guys have shared that have caused issues in the past to see if it can do all of them. I made sure to select 10 trials for each one to average out any error and get some decent results. I used the same profile for all of them except one as you can see. Note that on 3 images, I had to disable the scale or position or both because they were incorrect. In that case it was more of a blind solve. All solved in less than 5 seconds on my computer. So I think this version might be a little better.

The 3 that I had to disable the scale and/or position included the M13 image, the m-108 image, and the light-lumen image.

Yes multiple scales makes sense. Splitting the search areas will be tricky.

I'm still considering using threads but probably improving detection is more rewarding.

Hi!
For what its worth. I have tried sexysolver 1.4 out of the box on my new Macbook Pro on different pictures taken with my Canon on a SW MN190 and ASI1600 on a 152mm refracror and they all solve in between 0,4-1,1 seconds and havent failed once. It works superbly!
Erland

Hi!
For what its worth. I have tried sexysolver 1.4 out of the box on my new Macbook Pro on different pictures taken with my Canon on a SW MN190 and ASI1600 on a 152mm refracror and they all solve in between 0,4-1,1 seconds and havent failed once. It works superbly!
Erland

Thank you very much, it is good to know I didn't mess anything up too bad with such a big set of changes. But of course, as always, I already did find a little bug.

I found that the star filters that I created were only being applied for the internal sextractor, they were not being applied to the external sextractor. That made the Ext SextractorSolver method not work too well as well. I will push a change later today that will try to fix that. There are still some differences between the stars found with the internal and external sextractor though. I think that Han alluded to this earlier, it seems to pick up a lot more noise than the internal sextractor. I don't think the star filter settings were the whole story. I will see if I can work on that.

Other than that, keep testing everybody and let me know if there is anything else.

Rob,

This version 1.4 works well. The Min size for stars works well for filtering the M108 image of Ron (ufile.io/cqoibgcy) I noted the SExtractor pick up more blogs (some oval) in the image then ASTAP. So it works very well.

I have uploaded and test image:
ufile.io/2yy1vv9p
This is an very faint image. An 0.25 second exposure with some extra artificial noise added. Both Sexysolver and ASTAP can solve it. But for SExtrator I have to set in the star filter the minimum size at 0.8 or lower. The stars are real stars and should have a shape close to Gaussian and a HFD of maybe 2. They are spread out over a few pixels. I don't know what star size is reported by SExtractor but I assume the SExtractor is measuring/reporting the HFR, half flux radius?

Going back to M108 image. For the hot pixel filtering, I have set the Min size at 0.9 or higher. So what I see is that hot pixel filtering could in extreme cases filter out faint stars. The original image without noise is not a problem for SExysolver with a Min size=1.

So not problem, just an observation at extreme conditions.

For Ron, I have released ASTAP 0.9.365 for Windows, Mac and all Linux versions. This version has a new hot pixel filtering which will work much better with your images. f they don't solve in ASTAP, expose longer. There is less need now for darks.

Han

I downloaded and installed the new build of SexySolver-Tester. I tried running it with the smallscaleParallel option in the solver (IntSEPInteralSolver). Three of my 4 images solved in under a minute (26, 45, 57 seconds). The fourth image did not solve and after it failed the program closed/crashed?

I am using main option of scale but not position. if I just run the extractor, the AllStars option finds too many stars that are dark pixels. If I run parllelSmallScale it finds only 50 stars (assume that is a default because it does not show in the options.)

I am trying to repeat my first success (15 min ago) with this build, but now it is failing and closing? with just running the solve option of INtSEPInt Solve - parallelSMallScale.

Ron

Well it seems to depend on the order I run the images, because I just had 2 successful runs (just using solve as above) and the program is still on the screen and running. I will try the third image.

The third image just solved ok and no crash. The 4th image is Light_lumen...003 and now the 4th image solved in 10 seconds!? where it failed and crashed before? But right now it seems to working fine and this option is solving all four images with just 50 stars. It is disabling the inParallel option because I don't have enough RAM for all the index files, but it is running multiple child solvers.

Ron

Han,
I have upgraded to the latest version 80.9.365 of ASTAP.

thanks,
Ron