×

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: 1119
  • Thank you received: 182


If the Stellar Solver Tester works, it should be properly installed, right? See the build date on top.

3 years 5 months ago #62138
Attachments:

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

  • Posts: 1009
  • Thank you received: 133
The stellarsolver 'issues' are only warnings about unused stuff, the error is from the fits viewer:
/home/ubuntu/Projects/kstars/kstars/kstars/fitsviewer/fitsdata.h:162:33: error: ‘const struct FITSImage::Statistic’ has no member named ‘channels’

Not sure what's wrong though - compiled w/o errors here.

Can only test it with the simulator, and it has problems solving those, maybe because of the small field? Two of my load&slew objects (Cocoon, Helix) loaded&solved fast.

Somewhat nasty: If the solver fails on the captured frame, the 'load&slew' button stays disabled until I do another slew...
3 years 5 months ago #62139

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

  • Posts: 1119
  • Thank you received: 182

Odd. I deleted my kstars and build folder, then recompiled Stellar Solver (only compiled and installed a few hours ago) and reinstalled it again. Then recompiled kstars from source. Now it installed fine.

Looks like the Stellar Solver was out of date by a couple of hours and that's why the kstars build failed?

3 years 5 months ago #62141
Attachments:

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

  • Posts: 1119
  • Thank you received: 182


You can solve any fits image you have acquired in the past, using the simulator in the solver and the 'Load and Slew' option to see if it in fact slews to the correct position. Works fine at my end.
3 years 5 months ago #62143

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

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

Time to create page: 0.566 seconds