×

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

Bi-monthly release with minor bug fixes and improvements

New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

  • Posts: 1009
  • Thank you received: 133
I'd rather think there was something left in your kstars/build folder. I always build out-of-tree in a new created folder to make sure cmake doesn't use old cached info...

As for slewing: Yes, it solves (fast!), then slews (to the correct target :) ), but then runs the simulator CCD, and tries to verify - which fails. Then the 'Load & Slew' button stays disabled. So I first have to click some other location in the star map, 'goto' there, and only then I can try another image for solving....
Gets tiring after a while :ohmy:
3 years 5 months ago #62144

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

  • Posts: 1119
  • Thank you received: 182

There was nothing left in my kstars/build folder when it failed, because I had deleted them before. Still, it threw the same error on three attempts to build kstars again. Only AFTER I reinstalled Stellar Solver would kstars compile again. Weird. I'll see what happens next time.

As for the loading and slewing: Works fine here and the simulator then correctly solves the target as well at my end:

3 years 5 months ago #62145
Attachments:

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

  • Posts: 2876
  • Thank you received: 809
So based on what I am hearing, different options might be working better for the "load and slew" type function vs the "capture and solve" function?

Maybe it would be good to have two different sets of combo boxes in the Align options, a set of selections on which ones to use for "load and slew" vs a set of selections to use for "capture and solve"?

I ran some tests on some Images Jasem sent me that were taken with "capture and solve" and I found that they solved better on the default profile, however, for blind solves and load and slew, the Small Scale solving profile worked better.
3 years 5 months ago #62147

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

  • Posts: 152
  • Thank you received: 20
Possibly a factor is the load and slew images might be longer exposures compared to relatively short captures for alignment?
3 years 5 months ago #62148

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

  • Posts: 2876
  • Thank you received: 809
Yes, I was thinking that, and the fact that the "load and slew" images could be JPEGs, PNGs, GIFs, and other images that don't have scale or position. They could also come from different equipment. The capture and solve should have the same info most of the time.
3 years 5 months ago #62149

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

  • Posts: 535
  • Thank you received: 109
Maybe just 2 sets of solver configs that are tried before failing? It is fast after all, what would it hurt? With luck, this could remove the need to manual tune much, and the system could make the configuration that worked the first configuration for the next solve.

All the tuning could still be in an advanced tab, of course, but it would be nice to not have to worry about it if possible.

$.02

Jim
3 years 5 months ago #62152

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

  • Posts: 1119
  • Thank you received: 182
That's a great idea, Jim!
I presume more than two configurations could be specified, to be worked down consecutively until one succeeds.
That would be especially useful when using the scheduler unattended with a series of targets, where the schedule would start to hang if solving fails.
Jo
3 years 5 months ago #62155

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

  • Posts: 2876
  • Thank you received: 809
Now that's what I call a good idea!! Let's think about this one.
3 years 5 months ago #62158

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

  • Posts: 106
  • Thank you received: 4
I get a build error:

CMake Error at CMakeLists.txt:212 (find_package):
By not providing "FindStellarSolver.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"StellarSolver", but CMake did not find one.

Could not find a package configuration file provided by "StellarSolver"
with any of the following names:

StellarSolverConfig.cmake
stellarsolver-config.cmake

Add the installation prefix of "StellarSolver" to CMAKE_PREFIX_PATH or set
"StellarSolver_DIR" to a directory containing one of the above files. If
"StellarSolver" provides a separate development package or SDK, be sure it
has been installed.


-- Configuring incomplete, errors occurred!
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 5 months ago #62184

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

  • Posts: 459
  • Thank you received: 69
3 years 5 months ago #62190

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

  • Posts: 106
  • Thank you received: 4
Jasem, thank you.
The update to stellarsolver's CMakeLists.txt works on Kubuntu 20.04 and I'am able to build KStars again.
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 5 months ago #62191

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

  • Posts: 2876
  • Thank you received: 809
Yes, he changed both KStars and sent me a pull request for Stellarsolver today to change the way the package is installed and found. Apparently this change will fix a windows build issue.
The following user(s) said Thank You: Jerry Black
3 years 5 months ago #62192

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

Time to create page: 0.635 seconds