´╗┐
×

INDI Library v1.8.9 Released (01 Mar 2021)

INDI monthly update. In addition to driver improvements, major code refactoring is in progress by @pawel-soja to modernize and improve INDI aging code.

New forum users, please go here first: indilib.org/forum/new-forum-users.html

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

  • Posts: 127
  • Thank you received: 10
Hi,

i'm playing with the polar aligment routine (with indi simulator). Sometime that work, sometime not (kstars crash). I played with some configurations (essentially with 1-FastSolving and 7-MidSizedStars).

I attached the console capture (with the crash) and the separate astrometry log file.

I updated the stellarsolver lib this morning and kstars yesterday.


Thank.

File Attachment:

File Name: astrometry.log
File Size:180 KB
C8 lightbridge, Orion Atlas mount, EOS 1000D modified and ASI120MM for guiding.
6 months 1 week ago #61403
Attachments:

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

  • Posts: 106
  • Thank you received: 4
Ok, after updating stellarsolverlib and kstars the light is solved blazing fast.
But it ran out of memory:
2020-10-11T10:33:46 Child solver: 5 did not solve or was aborted
2020-10-11T10:33:40 Child solver: 8 did not solve or was aborted
2020-10-11T10:33:40 Child solver: 3 did not solve or was aborted
2020-10-11T10:33:39 Child solver: 7 did not solve or was aborted
2020-10-11T10:33:38 Child solver: 4 did not solve or was aborted
2020-10-11T10:33:37 Child solver: 6 did not solve or was aborted
2020-10-11T10:32:04 Child solver: 2 did not solve or was aborted
2020-10-11T10:32:02 Child solver: 1 did not solve or was aborted
2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 5.33312 6.94444

2020-10-11T10:32:01 Scale range: 7.67969 to 10 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 1.03624 1.78819

2020-10-11T10:32:01 Scale range: 1.49219 to 2.575 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 2.75499 3.93663

2020-10-11T10:32:01 Scale range: 3.96719 to 5.66875 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 0.176866 0.499132

2020-10-11T10:32:01 Scale range: 0.254688 to 0.71875 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 0.499132 1.03624

2020-10-11T10:32:01 Scale range: 0.71875 to 1.49219 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 1.78819 2.75499

2020-10-11T10:32:01 Scale range: 2.575 to 3.96719 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 0.0694444 0.176866

2020-10-11T10:32:01 Scale range: 0.1 to 0.254688 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:32:01 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-11T10:32:01 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:32:01 Image width 5184 pixels; arcsec per pixel range 3.93663 5.33312

2020-10-11T10:32:01 Scale range: 5.66875 to 7.67969 degrees wide

2020-10-11T10:32:01 Set odds ratio to solve to 1e+09 (log = 20.7233)

2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Configuring StellarSolver
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Solver # 8, Low 7.67969, High 10 arcminwidth
2020-10-11T10:31:17 Solver # 7, Low 5.66875, High 7.67969 arcminwidth
2020-10-11T10:31:17 Solver # 6, Low 3.96719, High 5.66875 arcminwidth
2020-10-11T10:31:17 Solver # 5, Low 2.575, High 3.96719 arcminwidth
2020-10-11T10:31:17 Solver # 4, Low 1.49219, High 2.575 arcminwidth
2020-10-11T10:31:17 Solver # 3, Low 0.71875, High 1.49219 arcminwidth
2020-10-11T10:31:17 Solver # 2, Low 0.254688, High 0.71875 arcminwidth
2020-10-11T10:31:17 Solver # 1, Low 0.1, High 0.254688 arcminwidth
2020-10-11T10:31:17 Starting 8 threads to solve on multiple scales
2020-10-11T10:31:17 Stars Found after Filtering: 50
2020-10-11T10:31:17 Keeping just the 50 brightest stars
2020-10-11T10:31:17 Removing the stars with a/b ratios greater than 1.5
2020-10-11T10:31:17 Stars Found before Filtering: 88735
2020-10-11T10:31:17 Starting Internal StellarSolver Sextractor. . .
2020-10-11T10:31:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-11T10:31:17 Disabling the inParallel option.
2020-10-11T10:31:17 Not enough RAM is available on this system for loading the index files you have in parallel
2020-10-11T10:31:17 Evaluating Installed RAM for inParallel Option. Total Size of Index files: 63.5812 GB, Installed RAM: 15.5138 GB
2020-10-11T10:31:09 Inaktiv.

Another issue: reloading the same light frame gives a nullpointer to an object in the temp folder and kstars crashes.
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
6 months 1 week ago #61406

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

  • Posts: 1902
  • Thank you received: 410

rlancaste wrote: wvreeven, I am not sure it can be related to the new solver, since your screenshots are not of the new version of kstars. If you were using the new build, they would not look like that, the options are all different.


Thanks, that indeed solved it. I guess I had bad luck and was using a build (as I wrote, it was the one from Thursday, October 8 ) that was "in between removing the old solver and adding the new one". Now I see that libstellarsolver gets installed. I tried to solve the image again and this time it worked like a charm.

Thanks very much for all the hard work on this Rob!!!


Wouter
Wouter van Reeven

ASI6200 and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chr├ętien on a SkyWatcher EQ6-R
6 months 1 week ago #61407

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

  • Posts: 106
  • Thank you received: 4
Don't get me wrong, it disabled the parallel mode but did not run out of memory while solving the light frame.
I tested this with another light frame of M57. --- 6,83 of 15.5. GB RAM were utilised.
This time kstars crashes with the error message in the console window: corrupted size vs prev_size and a crashRecursionCounter = 2
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
Last edit: 6 months 1 week ago by Cerro Torre.
6 months 1 week ago #61408

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

  • Posts: 106
  • Thank you received: 4
This is a weird behaviour:
M57 is solved correctly using the Internal SEP | StellarSolver | 4-ParallelSmallScale settings.
But four times out of five the same light frame crashes kstars with the error message reported above.
I cannot reproduce a stable and correct plate solving.
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
Last edit: 6 months 1 week ago by Cerro Torre.
6 months 1 week ago #61412

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

  • Posts: 685
  • Thank you received: 92
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'
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
Last edit: 6 months 1 week ago by DerPit.
6 months 1 week 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: 6 months 6 days ago by Cerro Torre.
6 months 6 days ago #61421

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

  • Posts: 481
  • Thank you received: 97

rlancaste wrote: Jim, I think I have fixed the issues you were dealing with.


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

Jim
12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT w/.8x for the light
Fedora Linux, 100% INDI
6 months 6 days ago #61422

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

  • Posts: 2453
  • Thank you received: 660
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?
6 months 6 days 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
6 months 6 days 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
6 months 6 days ago #61431

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

  • Posts: 2453
  • Thank you received: 660
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?
6 months 6 days ago #61433

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

Time to create page: 0.709 seconds