1) I suspect that you had a different profile selected than you intended to solve with. I added separate combo boxes for solving and sextracting and if you want to use the settings in the left panel now you need to click unsaved options.

2). It should give a warning when you try to sextract with it. I will check. I moved the warnings I got the library

3) do you mean aborting when using the parallel options, the internal solvers, or external ones?

I tried your image. I had a couple of issues with my ParallelSmallScale profile, which I think is the right one for this, but once I tweaked the settings a little, I got it to solve in 1.3 seconds. However, these issues were important. One of them was the saturation limit setting. It prevented key stars from getting included. Another one was that I seemed to have accidentally not included downsample in that profile, although the effect of that one was very minor. The big issue was the Saturation Limit on this image, it prevented it from solving! Based on that, I think I will remove the saturation limit from the solving profiles and keep them in the ones aimed getting good HFR.

Also I think I may make it so that if you change a setting on the left, it automatically selects unsaved options in the other combo boxes. That way it will alleviate some confusion. I will think about it and see what is less confusing.

Here is your image

Rob,

FYI

I've done a git pull and erased the directory and a git clone this morning. I build and install using the installLinux.sh script on Debian Buster (10). My header on SexySolver says 0.9, build: 2020-04-29T20:28:32Z. The CMakeLists.txt shows version 1.1.

Please make sure you are running the correct version. I did change the name of the Application. It is SexySolverTester not SexySolver anymore. I changed it because I merged all of the separate libraries into one library and didn't want a name conflict. So when you run it, it is not SexySolver, but SexySolverTester.

Maybe the install script for Linux could remove the previous version, and maybe a simlink from SexySolver to SexySolverTester would be good?

I missed the rename. I ran /usr/bin/SexySolverTester from the command line and got the correct version. I'll fix my desktop icon to point to the correct executable.

I plan to work on some blind solves with jpegs for input. I'll post those results later today.

Thank you very much, please note what I said in the post before yours. The Combo Box for the Selector and Solver are now separate from the options on the left. If you want to use the options on the left, you need to select "Unsaved Options" for the Sextracting or Solving options profile as appropriate. Or you can edit a profile, save it, and select to use your new profile for Sextracting or Solving

Also, we found a couple of issues with a couple of the profiles' settings in solving one of Han's images that had many stars near the saturation limit. I will revise these profiles later today, but I haven't done so yet. The main issue was SaturationLimit. It isn't really needed for solving (I don't think?), and it removed too many good stars.

Rob,

I thought I had run the Internal Solver with the ParallelSolving option several times, but the last couple of times it crashed. For what it's worth, I have attached the crash report.


Richard

I just updated the options profiles with the downsampling and saturation limit on GIT. You might want to git pull and build again to get a better solve.

I can't replicate your crash. It looks like it happened due to a logging issue. Maybe try changing the log setting to log none or maybe log verb and see if either have an effect on the crash?

I just fixed a bug with star positions when one profile is used for sextracting and a different one is used for solving. I also added some edit buttons so hopefully the profile lists are less confusing. And I made an automatic option for the parallel algorithms and put it in the FastSolving profiles

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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