×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

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

  • Posts: 5
  • Thank you received: 0

Replied by Justin on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

But I am definitely hoping to make good progress on it this week.
3 years 5 months ago #62335

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

Replied by Jasem Mutlaq on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

I actually found the issue on another image and then fixed it accordingly in master, so that's why.
3 years 5 months ago #62338

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

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Load and Slew is crashing to the desktop for me. It loads an image, solves, slews the scope, lands on the object, captures, solves, and crashes.

I need to load more debuginfo files, and will do so, but here is what I have so far:

ekosdebugger:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe3143640 (LWP 70834)]
[New Thread 0x7fffe18ac640 (LWP 70835)]
[New Thread 0x7fffe10ab640 (LWP 70836)]
[New Thread 0x7fffe08aa640 (LWP 70837)]
[New Thread 0x7fffd3f9d640 (LWP 70838)]
[New Thread 0x7fffd358e640 (LWP 70840)]
[New Thread 0x7fffc7fff640 (LWP 70841)]
[New Thread 0x7fffbffff640 (LWP 70842)]
[New Thread 0x7fffb7fff640 (LWP 70843)]
[New Thread 0x7fffaffff640 (LWP 70844)]
[New Thread 0x7fffa7fff640 (LWP 70845)]
[New Thread 0x7fff9ffff640 (LWP 70846)]
[New Thread 0x7fff97fff640 (LWP 70847)]
[New Thread 0x7fff8ffff640 (LWP 70848)]
[New Thread 0x7fff7ffff640 (LWP 70849)]
[New Thread 0x7fffc55ee640 (LWP 70850)]
[New Thread 0x7fff7bc6a640 (LWP 70851)]
[New Thread 0x7fff73fff640 (LWP 70852)]
[New Thread 0x7fff6bfff640 (LWP 70853)]
[New Thread 0x7fff63fff640 (LWP 70854)]
[New Thread 0x7fff5bfff640 (LWP 70855)]
[New Thread 0x7fff53fff640 (LWP 70856)]
[New Thread 0x7fffbd24a640 (LWP 70857)]
[New Thread 0x7fffbca49640 (LWP 70858)]
[New Thread 0x7fffb5ffe640 (LWP 70859)]
[New Thread 0x7fffb57fd640 (LWP 70860)]
[Thread 0x7fffbd24a640 (LWP 70857) exited]
[Thread 0x7fffbca49640 (LWP 70858) exited]
[New Thread 0x7ffff0a76300 (LWP 70865)]
process 70828 is executing new program: /usr/bin/ps
[LWP 70865 exited]
[New LWP 70866]
process 70828 is executing new program: /usr/bin/indiserver
[New LWP 70875]
[New LWP 70880]
[New LWP 70881]
[New LWP 70882]
[New LWP 70883]
[New LWP 70828]
[New LWP 70889]
[New LWP 70890]
[New LWP 70891]
[New LWP 70892]
[New LWP 70893]
[LWP 70891 exited]
[LWP 70889 exited]
[LWP 70892 exited]
[LWP 70890 exited]
[New LWP 70896]
[LWP 70893 exited]
[New LWP 70897]
[LWP 70897 exited]
[New LWP 70900]
[LWP 70896 exited]
[New LWP 70903]
[LWP 70903 exited]
[New LWP 70906]
process 70828 is executing new program: /usr/bin/gawk
[LWP 70906 exited]
[New LWP 70907]
process 70828 is executing new program: /usr/bin/gawk
[LWP 70907 exited]
[New LWP 70908]
[LWP 70908 exited]
[New LWP 70916]
process 70828 is executing new program: /usr/bin/gawk
[LWP 70916 exited]
[New LWP 70917]
process 70828 is executing new program: /usr/bin/gawk
[LWP 70917 exited]
[New LWP 70918]
Thread 50 "SextractorSolve" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 70918]
0x00007ffff470c645 in ?? ()
#0  0x00007ffff470c645 in ?? ()
#1  0x00007ffff6bbe4dc in ?? ()
#2  0x00007fff00000040 in ?? ()
#3  0x0000003000000000 in ?? ()
#4  0x00007fffb5ffd380 in ?? ()
#5  0x00007ffff6bc28db in ?? ()
#6  0x00007fffb5ffcd31 in ?? ()
#7  0x00007ffff633f180 in ?? ()
#8  0x00007fffb5ffd1b0 in ?? ()
#9  0x00007fff00000000 in ?? ()
#10 0x0000000000000002 in ?? ()
#11 0x00007ffff633f180 in ?? ()
#12 0x0000000000000000 in ?? ()

gdb backtrace:
Core was generated by `kstars'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f002f2b3645 in __vfprintf_internal () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7efffca49640 (LWP 71068))]
(gdb) bt
#0  0x00007f002f2b3645 in __vfprintf_internal () from /lib64/libc.so.6
#1  0x00007f002f356ae3 in __fprintf_chk () from /lib64/libc.so.6
#2  0x00007f003170e6bd in fprintf (__fmt=<optimized out>, __stream=<optimized out>, __stream=<optimized out>, __fmt=<optimized out>) at /usr/include/bits/stdio2.h:103
#3  error_reportv (e=0x7eff58bb6e00, module=module@entry=0x7f0031765c90 "/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/libkd/kdtree_internal.c", line=line@entry=2207, func=func@entry=0x7f0031767b60 <__func__.19.lto_priv.2> "kdtree_build_2_ddd", 
    fmt=fmt@entry=0x7f00317671d8 "Data, N, or D is zero", va=va@entry=0x7efffca481e0) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/util/errors.c:183
#4  0x00007f003170e812 in report_error (modfile=0x7f0031765c90 "/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/libkd/kdtree_internal.c", modline=2207, modfunc=0x7f0031767b60 <__func__.19.lto_priv.2> "kdtree_build_2_ddd", 
    fmt=0x7f00317671d8 "Data, N, or D is zero") at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/util/errors.c:139
#5  0x00007f003171a966 in kdtree_build_2_ddd (kd=<optimized out>, indata=<optimized out>, N=<optimized out>, D=<optimized out>, Nleaf=5, treetype=<optimized out>, options=<optimized out>, minval=<optimized out>, maxval=<optimized out>)
    at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/libkd/kdtree_internal.c:2207
#6  0x00007f0031743da2 in kdtree_build (kd=<optimized out>, data=<optimized out>, N=<optimized out>, D=<optimized out>, Nleaf=<optimized out>, treetype=<optimized out>, options=2) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/libkd/kdtree.c:24
#7  0x00007f00316d8d98 in verify_field_preprocess (fieldxy=0x7eff58007c60) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/blind/verify.c:92
#8  0x00007f00316d0aa4 in solver_preprocess_field (solver=solver@entry=0x562a1b71c8c8) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/blind/solver.c:644
#9  0x00007f00316d3a6b in solve_fields (bp=bp@entry=0x562a1b71c8c8, verify_wcs=verify_wcs@entry=0x0) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/blind/blind.c:1015
#10 0x00007f00316d4416 in blind_run (bp=bp@entry=0x562a1b71c8c8) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/blind/blind.c:473
#11 0x00007f00316d5021 in engine_run_job (engine=0x7eff58002b80, job=0x562a1b71c890) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/astrometry/blind/engine.c:530
#12 0x00007f0031697110 in InternalSextractorSolver::runInternalSolver (this=0x562a1b71c5a0) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/internalsextractorsolver.cpp:1183
#13 0x00007f003168ef58 in InternalSextractorSolver::run (this=0x562a1b71c5a0) at /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/internalsextractorsolver.cpp:152
#14 0x00007f002fe204bc in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#15 0x00007f0030edb3f9 in start_thread () from /lib64/libpthread.so.0
#16 0x00007f002f348b03 in clone () from /lib64/libc.so.6

This is reproducible every time. I am using a FITS file captured tonight that I can make available if it helps.

Jim
3 years 5 months ago #62379

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

  • Posts: 106
  • Thank you received: 4

Replied by Heiko on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

The actual version of kstars at 20:00 (UTC+1) crashes on startup right after the telescope icon.
Signal: SIGSEGV (Segmentatiion fault)
The debugger holds at line number 419 in the file atomic_base.h

_GLIBCXX_ALWAYS_INLINE __int_type
load(memory_order __m = memory_order_seq_cst) const noexcept
{
memory_order __b = __m & __memory_order_mask;
__glibcxx_assert(__b != memory_order_release);
__glibcxx_assert(__b != memory_order_acq_rel);

return __atomic_load_n(&_M_i, int(__m)); <<<--- here!
}
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 #62412

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

  • Posts: 106
  • Thank you received: 4

Replied by Heiko on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Screenshot:

Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 5 months ago #62414
Attachments:

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

  • Posts: 2882
  • Thank you received: 816

Replied by Rob Lancaster on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

I can forward this to Jasem
3 years 5 months ago #62417

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

  • Posts: 2882
  • Thank you received: 816

Replied by Rob Lancaster on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Jim if you can make the file available that would help.
3 years 5 months ago #62418

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

  • Posts: 2882
  • Thank you received: 816

Replied by Rob Lancaster on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Cerro Torre, Jasem said it is probably a build issue, you might try deleting your kstars build folder and just rebuild it and see if that helps
3 years 5 months ago #62420

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

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Sure thing. Please find attached. I don't think it is the initial file that is loaded that is the problem. That image is solved and the scope moves to the location of the solve. It is upon this next capture/solve to find out how close it is that things go sideways.

It can be reproduced with the simulator as well.

Jim

PS. @knro would it be possible to add .bz2 to the allowed file extensions? .tar.bz2 is there, but it rejects just .bz2. You could then replace .tar.bz2 if you want.
3 years 5 months ago #62421
Attachments:

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

  • Posts: 2882
  • Thank you received: 816

Replied by Rob Lancaster on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Hi Jim, I tried it both in KStars and in the tester program and it solved right away both times. It didn't have to use any parallelization either since it had the correct scale and position information. It solved and slewed right away. So I'm not sure?
3 years 5 months ago #62424

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

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Thanks for checking, Rob. It solves and slews for me as well. It is after the slew when it takes another image to compare that it seems to have the problem. Do you have auto-WCS turned on in the options? I opened another thread where when fitsviewer opens after capture, if auto-WCS is on, it crashes to the desktop in the same way. I think now, after looking at gdb, that they may be related. That thread is here: indilib.org/forum/development/8067-fitsv...rash-to-desktop.html
3 years 5 months ago #62426

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

  • Posts: 2882
  • Thank you received: 816

Replied by Rob Lancaster on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

Yep, I do have Auto - WCS turned on.
3 years 5 months ago #62433

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

Time to create page: 3.015 seconds