×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Kstars 3.5.0 final help needed. solver not working

  • Posts: 33
  • Thank you received: 7
the solver wasnt working because the file ownership was set to root instead of me. Once I changed the ownership back to me, the solver started working.
3 years 3 months ago #64310

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

  • Posts: 2876
  • Thank you received: 809
good to know, was it the index files, the folder, or both?
3 years 3 months ago #64318

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

  • Posts: 333
  • Thank you received: 23
Sorry byt I was unable to solve nothing using Shoot and Goto ì. I tried all th options, I am going back to the 3.4.3

[2020-12-13T23:48:02.293 CET INFO ][ org.kde.kstars.fits] - Loading file "/home/pi/CONDIVISA/test_vari/M_42/Light/Luminanza/L_M42_60_secs_2020-12-07T00-58-12_003.fits"
[2020-12-13T23:48:03.503 CET INFO ][ org.kde.kstars.ekos.align] - "Automatically downsampling the image by 3"
[2020-12-13T23:48:03.666 CET INFO ][ org.kde.kstars.ekos.align] - "Evaluating Installed RAM for inParallel Option. Total Size of Index files: 1.18568 GB, Installed RAM: 3.56449 GB, Free RAM: 0.924511 GB"
[2020-12-13T23:48:03.669 CET INFO ][ org.kde.kstars.ekos.align] - "Not enough RAM is available on this system for loading the index files you have in parallel"
[2020-12-13T23:48:03.671 CET INFO ][ org.kde.kstars.ekos.align] - "Disabling the inParallel option."
[2020-12-13T23:48:03.691 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2020-12-13T23:48:03.693 CET INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Sextractor with the 1-Default profile . . ."
[2020-12-13T23:48:04.620 CET INFO ][ org.kde.kstars.ekos.align] - "Stars Found before Filtering: 290"
[2020-12-13T23:48:04.622 CET INFO ][ org.kde.kstars.ekos.align] - "Stars Found after Filtering: 290"
[2020-12-13T23:48:04.625 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2020-12-13T23:48:04.628 CET INFO ][ org.kde.kstars.ekos.align] - "Configuring StellarSolver"
[2020-12-13T23:48:04.798 CET INFO ][ org.kde.kstars.ekos.align] - "Scale range: 5.94144 to 8.91216 arcsec/pixel"
[2020-12-13T23:48:04.801 CET INFO ][ org.kde.kstars.ekos.align] - "Downsampling is multiplying the pixel scale by: 3"
[2020-12-13T23:48:04.803 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2020-12-13T23:48:04.811 CET INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . ."
[2020-12-13T23:48:16.096 CET INFO ][ org.kde.kstars.ekos.align] - "Solver was aborted, timed out, or failed, so no solution was found"
[2020-12-13T23:48:16.098 CET INFO ][ org.kde.kstars.ekos.align] - "Solver Failed"
3 years 3 months ago #64438

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

  • Posts: 333
  • Thank you received: 23
How is possible that the system was unable to solve a stupid image of M42 or M27???

we.tl/t-PC64GJzQP7
3 years 3 months ago #64440

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

  • Posts: 2876
  • Thank you received: 809
Can you share the image you had trouble with solving so that we can see why it might not have succeeded?

Also, you can try the other StellarSolver options, such as using ASTAP, local Astrometry.net, etc.
3 years 3 months ago #64441

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

  • Posts: 2876
  • Thank you received: 809
I can't answer why it did not solve the image until I have more information.
3 years 3 months ago #64442

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

  • Posts: 333
  • Thank you received: 23
i tried all the option possible. When I use Local astrometry RAM grows to the maximum, never happened with previous version 3.4.3
3 years 3 months ago #64443

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

  • Posts: 333
  • Thank you received: 23
Here you can get 2 FIT of my M42 and M27

we.tl/t-PC64GJzQP7
3 years 3 months ago #64444

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

  • Posts: 2876
  • Thank you received: 809
I just ran a test on your M27 image in the Stellar Solver tester. It did not solve as you said with the information in the file. When I disable the "scale" setting, it solves in 0.88 seconds and it revealed the problem.

Field size: 40.5873 x 26.9722 arcminutes
Pixel Scale: 0.439275" per pixel

That was not the pixel scale information saved in your image. In the fits header, your scale is 2.475", which is clearly too big. Was this information set in KStars?
3 years 3 months ago #64446

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

  • Posts: 2876
  • Thank you received: 809
I just tried your other image, M42, it had the same issue. The solver failed, but disabling scale allowed it to solve.

The results:

Field size: 40.7144 x 27.0481 arcminutes
Pixel Scale: 0.440581"

The pixel scale in your fits header again said 2.475 arcseconds per pixel.
3 years 3 months ago #64447

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

  • Posts: 333
  • Thank you received: 23
The Use scale is eabled in my configuration.
Where I have to see for the pixel scale in your fits header???

Other images of M42 or M27 has been solved
3 years 3 months ago #64449

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

  • Posts: 2876
  • Thank you received: 809
I just opened the image in PixInsight to see the pixel scale value that was saved in the file. But you could also open it in KStars and view the fits header in the side of the fits viewer
3 years 3 months ago #64450

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

Time to create page: 1.280 seconds