×

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

Bi-monthly release with minor bug fixes and improvements

KStars 3.5.0 Beta for Windows

Please test this version: binary-factory.kde.org/job/KStars_Nightly_win64/

Download the exe file and set it up. Please test the StellarSolver integration. You need to download index files if you don't have them already. Report any issues here.
3 years 4 months ago #62195

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

  • Posts: 64
  • Thank you received: 9

Replied by Ray on topic KStars 3.5.0 Beta for Windows

Did about 50 solves using simulators only and results were good. Seemed slower than astap but faster than astrometry (local).
The following user(s) said Thank You: Jasem Mutlaq
3 years 4 months ago #62215

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

  • Posts: 910
  • Thank you received: 86
For some reason it doesn't work for me.
Looks like it cannot find my astrometry.net installation.
Previous version (without the internal solver) worked with same paths.
Tried other solvers - nothing works. ASTAP, astrometry.net local, astrometry.net on-line, astrometry.net remote : (
2020-10-29T22:44:44 Solver Failed
2020-10-29T22:44:44 Solver was aborted, timed out, or failed, so no solution was found
2020-10-29T22:43:05 Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
2020-10-29T22:43:05 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-29T22:43:05 Image width: 1280 pixels, Downsampled Image width: 640 pixels; arcsec per pixel range: 1.52962 to 2.86807
2020-10-29T22:43:05 Scale range: 16.316 to 30.5928 arcmin wide
2020-10-29T22:43:05 Configuring StellarSolver
2020-10-29T22:43:05 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-29T22:43:05 Stars Found after Filtering: 91
2020-10-29T22:43:05 Stars Found before Filtering: 91
2020-10-29T22:43:05 Starting Internal StellarSolver Sextractor with the 1-Default profile . . .
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
3 years 4 months ago #62241

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

  • Posts: 910
  • Thank you received: 86
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
3 years 4 months ago #62242
Attachments:

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

  • Posts: 910
  • Thank you received: 86
Argh... I was using simulators (I am not very good with them). Those often fail to solve. Once I switched from Primary to Guider - it worked!
Also the Primary started to work once I increased the exposure time from 2 to 6 sec.
So it works after all and it's very fast! I'll play some more.
Thanks!
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
3 years 4 months ago #62243

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

  • Posts: 910
  • Thank you received: 86
It's so many options now. Overwhelming. I hope it's going to simplify eventually.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
3 years 4 months ago #62244

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

  • Posts: 910
  • Thank you received: 86
Now everything works except for astrometry.net at http://127.0.0.1:8080 (ansvr) which is OK as long as the other solvers works.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
Last edit: 3 years 4 months ago by maxthebuilder.
3 years 4 months ago #62245

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

  • Posts: 910
  • Thank you received: 86
here's my latest config

-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
3 years 4 months ago #62246
Attachments:

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

  • Posts: 2876
  • Thank you received: 809

So the “local astrometry” option in the new version will run the ANSVR astrometry solve-field program and control its configuration directly, instead of relying on the external api web interface you were forced to use before. This appears to work much faster, gives you the same configuration options and downloading index capabilities that Mac and Linux users have had for years, and avoids the need to start, stop, configure, and run the web interface ANSVR provides.

I am not sure that you would want to access ANSVR using the traditional method now that you have the new method for using it. It should still work using “online” since it works just like the online solver, but I think the new way of using ANSVR should be better.
3 years 4 months ago #62249

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

  • Posts: 2876
  • Thank you received: 809

Were these the default values on windows for the external programs??

I need to look at that to make sure the defaults on Windows for the local solver are the ANSVR paths!
3 years 4 months ago #62250

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

  • Posts: 76
  • Thank you received: 5

Replied by Kevin on topic KStars 3.5.0 Beta for Windows

I really like the star size that you’ve added with SEP auto focus routine. This has been a problem for me in the past. It was selecting noise and not real stars. This has been working with the simulator but hasn’t been tested underneath real conditions.

Solving has been working for me. I had to tinker with some of the settings as Max had done above. I was used to the remote option taking time. I have my indexes on the raspberry but use the Kstar Windows client. Should I be changing the ANSVR address to the IP address of the rpi? There are a ton of options under solving. Maybe too many! My only complaint is, solving is almost too fast! I’m used to waiting and building suspense! This is no fun at all!

Kevin
3 years 4 months ago #62253

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

  • Posts: 2876
  • Thank you received: 809

So for the "ANSVR Address" I assume you mean the API URL? You can change this to the IP address of whatever computer you are running ANSVR on if you are using that. However, the new version can access the ANSVR solve-field executable directly just like it does on Linux and Mac computers. (You just have to select to use "local astrometry" instead of online. There is no longer any need to start up and use ANSVR as you did before. So you can ignore the "online" options entirely and just use the local astrometry option. It will be faster and easier to do.

Yes there are a lot of options, but it actually is no more options than were technically there before. Most of the options were previously in various different places on the computer, in config files, in KStars etc, so it was very hard to diagnose and fix any issues you had with plate solving. Basically I collected all the options in one spot. And yes I know it is an overwhelming amount of options. That is why I have wrapped all the options up into "profiles." The goal is that we can develop a great set of profiles that work for most people and you can just use the profile that works best for you and completely ignore all the various options because the profile "just works".

One reason the solving is much faster is because it isn't sending it over the network for a PI to solve and or sending it over a web API to ANSVR. Another reason it is faster is the usage of SEP instead of astrometry.net's system to extract the stars. Another reason is because I tried to tweak and optimize the options a bit. And finally, for blind solves it is MUCH faster because I have built into StellarSolver the ability to solve using astrometry.net in parallel on today's multi core machines and greatly speed up solving.
3 years 4 months ago #62254

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

Time to create page: 0.670 seconds