×

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
Todays version (*) is also crashing for me, on the file that last time (2 days ago) was solved, though only after very long time.
Tried a gdb backtrace - not sure if it's useful

(*) kstars-3.5.0-1537_ga8b786e88.x86_64 libstellarsolver-1.4-113_g0c587a6.x86_64

Edit: Sorry. So this is when loading a saved image from a previous obseration via 'Align->Load and Slew'
Last edit: 3 years 5 months ago by Peter Sütterlin.
3 years 5 months ago #61413
Attachments:

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

  • Posts: 106
  • Thank you received: 4
I pulled the changes for kstars at 16:30 (UTC+2) and the plate solving is more stable.
M57 is fine.
The Iris Nebula was not solved using the Internal SEP | StellarSolver | 4-ParallelSmallScale settings.
I switched to 1-Fast and external astronomy solver but kstars crashes and there is the error message "double free or corruption (out)".
CLion reports: Process finished with exit code 255
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
Last edit: 3 years 5 months ago by Heiko.
3 years 5 months ago #61421

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

  • Posts: 535
  • Thank you received: 109

Confirmed. I can now use Load & Slew... again.

Jim
3 years 5 months ago #61422

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

  • Posts: 2876
  • Thank you received: 809
Cerro Torre, if you are using the "Built in Sextractor" with "External Astrometry.net Solver" in the Fast Solving profile, that set up should solve in the same way that astrometry.net works in the currently released KStars program. Do you get crashes when you select these options?
3 years 5 months ago #61424

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

  • Posts: 106
  • Thank you received: 4
Rob, no crash yet no solved image.

Therefore I pulled astrometry from github and installed it, adjusted the paths accordingly -- and had no luck.
I switched to 4-Parallel and kstars crashed on me
Found one coordinate representation.
Found one coordinate representation.
double free or corruption (out)
[2]- Exit 253
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 5 months ago #61427

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

  • Posts: 106
  • Thank you received: 4
1st try

gdb /../..kstars
r
Starting program: (...)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef0fc700 (LWP 80001)]
[New Thread 0x7fffee018700 (LWP 80002)]
[New Thread 0x7fffe7dfa700 (LWP 80003)]
[New Thread 0x7fffdffff700 (LWP 80004)]
[New Thread 0x7fffd7fff700 (LWP 80005)]
[New Thread 0x7fffcffff700 (LWP 80006)]
[New Thread 0x7fffc7fff700 (LWP 80007)]
[New Thread 0x7fffbffff700 (LWP 80008)]
[New Thread 0x7fffb7fff700 (LWP 80009)]
[New Thread 0x7fffaffff700 (LWP 80010)]
[New Thread 0x7fffddffe700 (LWP 80011)]
[New Thread 0x7fffdd7fd700 (LWP 80012)]
[New Thread 0x7fffdcffc700 (LWP 80013)]
[New Thread 0x7fffd5ffe700 (LWP 80014)]
[New Thread 0x7fffd57fd700 (LWP 80019)]
[New Thread 0x7fffd4847700 (LWP 80020)]
[New Thread 0x7fffcdffe700 (LWP 80021)]
[New Thread 0x7fffc5ffe700 (LWP 80022)]
[New Thread 0x7fffccfac700 (LWP 80023)]
[Thread 0x7fffccfac700 (LWP 80023) exited]
[Thread 0x7fffd4847700 (LWP 80020) exited]
[Detaching after vfork from child process 80024]
[Detaching after vfork from child process 80025]
[New Thread 0x7fffd4847700 (LWP 80029)]
[New Thread 0x7fffccfac700 (LWP 80031)]
[New Thread 0x7fffbdffe700 (LWP 80032)]
[New Thread 0x7fffbd7fd700 (LWP 80033)]
[Thread 0x7fffcdffe700 (LWP 80021) exited]
Found one coordinate representation.
Found one coordinate representation.
[Detaching after vfork from child process 80070]
[New Thread 0x7fffcdffe700 (LWP 80071)]
free(): invalid pointer
--Type <RET> for more, q to quit, c to continue without paging--

Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) c
Continuing.
[Thread 0x7fffaffff700 (LWP 80010) exited]
[Thread 0x7fffb7fff700 (LWP 80009) exited]
[Thread 0x7fffbffff700 (LWP 80008) exited]
[Thread 0x7fffcffff700 (LWP 80006) exited]
[Thread 0x7fffd7fff700 (LWP 80005) exited]
[Thread 0x7fffdffff700 (LWP 80004) exited]
[Thread 0x7fffe7dfa700 (LWP 80003) exited]
[Thread 0x7fffef0fc700 (LWP 80001) exited]
KCrash: crashing... crashRecursionCounter = 2

2nd try

[New Thread 0x7fffb5ffc700 (LWP 80287)]
Found one coordinate representation.
Found one coordinate representation.
corrupted size vs. prev_size
--Type <RET> for more, q to quit, c to continue without paging--

Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) c
Continuing.
[Thread 0x7fffef0fc700 (LWP 80172) exited]
INDI server localhost/7624 disconnected.
INDI server localhost/7624 disconnected.
[Thread 0x7fffd4847700 (LWP 80285) exited]
INDI server localhost/7624 disconnected.
[Thread 0x7fffccfac700 (LWP 80286) exited]
KCrash: crashing... crashRecursionCounter = 2
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 5 months ago #61431

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

  • Posts: 2876
  • Thank you received: 809
Right, so I am trying to see exactly what is causing your crash:
A. Is it something with the internal build of astrometry.net that you can select by selecting "stellarsolver" as the solver type.
B. Is it an issue with your computer and solving in multiple threads at the same time, which you select by selecting one of the parallel profiles instead of one like fast solving which always uses a single thread.

So I think you changed both variables at the same time. If you can try the "fast solving" profile with the Internal Stellarsolver and then with the External Astrometry.net solver, we can see if there is a crash either time and whether it solves either time. And then after that, if you select one of the parallel profiles with the Internal Stellarsovler and then the External Astrometry.net solver we can see the same thing.

Also I am wondering what you are trying to solve, is this a FITS Image with Position and Scale information (and do you have UseScale and UsePosition selected in the options, or is this a non-FITS image which wouldn't have any of that info? Based on what you said, I assume it is either a FITS image without position and scale or it is a non-FITS image. Because if it had position and scale info, no matter which method you use to solve it should be done very fast and wouldn't try multi-threading in the first place.

And can you post this image that is giving trouble?
3 years 5 months ago #61433

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

  • Posts: 61
  • Thank you received: 10
I´m using openSUSE Tumbleweed. Kstars, indi and astrometry.net are self-compiled and intalled to /usr/local. All is fine so far.

Today I updated my system (git pull) for using it with StellarSolver. Kstars didn´t compile anymore but compiling stellarsolver prior to kstars solved this issue (in Tumbleweed I have no stellarsolver-devel). Testing went fine, solving was very fast. Great!


Same OS, other computer.

I installed a brand new opensuse Tumbleweed on my testing-system and compiled and installed the whole stuff. But now the solver didn´t work anymore. It told me:

"Die Einstellungsdatei für „Astrometry“ ist beschädigt oder fehlt: /home/ich/.local/kstars/astrometry/astrometry.cfg
Bitte stellen Sie den vollständigen Pfad zur Einrichtungsdatei in den INDI-Einstellungen ein."

It looks like kstars is looking for astrometry.cfg but cannot find this file, because it dosen´t exist.


So I did another test on the first computer, thisone, which worked with stellarsolver. I renamed the solve-field command from the installed astrometry.net to be shure, that the new internal solver is used. All pictures I tried, are solved without any problems. So the new internal solver is used.
Now I renamed the existing astrometry.cfg-file. And now kstars didn´t solve anymore. It asks for the path to astrometry.cfg.


I thougt, stellarsolver should work without astrometry.cfg?

Edgar
3 years 5 months ago #61434

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

  • Posts: 2876
  • Thank you received: 809
You are certainly right, there is no longer a need for astrometry.cfg. But we might not be finished removing all references to it. I will do a search for astrometry.cfg. There is probably a check somewhere to make sure you have it on your system . .. but of course its not needed.
3 years 5 months ago #61436

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

  • Posts: 61
  • Thank you received: 10
So I have to add astrometry.cfg because without this file it does not solve. Will try this tomorrow evening.
3 years 5 months ago #61437

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

  • Posts: 2876
  • Thank you received: 809
Hopefully by then you shouldn't need it because we hopefully have it fixed by then so you don't need it, but just in case, sure
3 years 5 months ago #61438

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

  • Posts: 61
  • Thank you received: 10
3 years 5 months ago #61439

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

Time to create page: 0.586 seconds