×

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: 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: 460
  • 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.

  • Posts: 460
  • Thank you received: 69
Thanks. Removing both kstars and stellarsolver and starting from scratch appears to fixed my stellarsolver cmake issue.
3 years 5 months ago #62193

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

  • Posts: 33
  • Thank you received: 7
I'm having definite stability issues with stellarsolver. Align seems to be working fine, but running a dummy sequence with the simulators is failing somewhere in the FITS processing post capture. This has been consistent over the last few days as I have been keeping up with the changes. The SEGV goes not always occur in the exact same place, but it always occurs when doing analysis. I turned off all of the HFR calculation options and WCS load options for FITS and Ekos, but it still seems some calls go out to stellarsolver.

I am also guiding (simulated) at the time with SEP multistar, so perhaps there is a race condition between SEP in guiding and SEP in FITS analysis. I'm not sure if any of the changes made it across to guiding yet. There are references to guiding in the backtrace, but I have no idea if that has any relevance or not.

The back trace from the core dump is attached.

J.
Last edit: 3 years 5 months ago by Jeremy Burton.
3 years 5 months ago #62198
Attachments:

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

  • Posts: 2876
  • Thank you received: 809
I might be reading this wrong, because it is fairly late in the evening for me, but it looks to me like this crash occurred in KStars during guiding, after StellarSolver returned the star list, but before the method to find the guide stars completed? Perhaps the list was still needed and it got deleted in KStars too soon? I will send this to Jasem and see if he agrees.
3 years 4 months ago #62212

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

Time to create page: 3.282 seconds