×

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: 2876
  • Thank you received: 809
So, to give an update: Now that the repo is mostly perfected and almost ready for integration into programs except for a couple of remaining issues, a friend of mine is helping me to do a code review. I am also working on how other programs will interface with it. He and I are playing with integrating it into KStars now. I also figured that before we get too far, I would attempt a renaming. The name sexysolver came naturally from blending the words Sextractor and Solver which is very descriptive of what the library does. However, several people expressed concern about the name, and not just for puritanical reasons. Recently another friend told me that some people's workplaces might filter or block anything that has the word sexy or sex in it, which could mean that they would be unable to work with the library due to the name. So I have thought about it for a couple of weeks and decided that the name StellarSolver is close enough and still pretty catchy.

I am not 100% sure that I have sorted out all the issues with renaming it yet, since it took me a few steps, but it seems to be mostly good now.

As for how you update, are you currently using Linux, Mac, or Windows? If it is Linux, you can first "git pull" and then use one of the two install scripts that I put in the linux-scripts folder. I did verify that this worked properly yesterday. If it is Mac or Windows, even though I code on my Mac, for distribution I have been releasing craft recipes and binary distributions of the tester. Before I do that, I need to do more testing today to make sure everything works and that I updated the craft recipes properly.

An interesting thing that I noticed: Even though I changed the name of the repo from sexysolver-tester to stellarsolver, the old links still work fine and if you already cloned the repo, you can just do a "git pull" since it is actually still the same repository.
The following user(s) said Thank You: Eric, Craig
3 years 9 months ago #55781

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

  • Posts: 333
  • Thank you received: 92
That's much better name. I'm glad you changed it!
The following user(s) said Thank You: Craig
3 years 9 months ago #55784

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

  • Posts: 447
  • Thank you received: 30
Thank you for your reply
It seems that I was able to update by the following procedure.

cd /home/xxxxx/sexysolver-tester

git pull

cd /home/xxxxx/sexysolver-tester/linux-scripts

./installStellarSolverLibrary.sh

./installStellarSolverTester.sh

xxxxx is the user directory

afterwards

sexysolver-tester → StellarSolver
Renamed to

/usr/bin/sexysolver-tester
Remove

Remove desktop icon

Was the procedure okay with this?

It seems that you can use this procedure.

It may be better to be listed on github as it requires some steps.
The following user(s) said Thank You: Craig
Last edit: 3 years 9 months ago by T-Studio.
3 years 9 months ago #55801

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

  • Posts: 2876
  • Thank you received: 809
Yes, it sounds like that would work pretty well. I am hoping that when I am done it won't be so many steps.
3 years 9 months ago #55804

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

  • Posts: 1009
  • Thank you received: 133
Hi Rob,
seems you've hardcoded the destination /usr/lib/libstellarsolver.a in the makefile. Shouldn't that use LIBDIR? On my system, 64bit stuff goes to /usr/lib64 :o
3 years 9 months ago #55808

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

  • Posts: 2876
  • Thank you received: 809
Hi, I think I have it going to both places actually. If you check, it should also be in the libdir. I had to put it in both places because I have had issues in the past on some systems not being able to find libraries in the libdir or libdir not properly being set. For example, I have been on some raspberry pi systems and all the INDI libraries got installed in the libdir, but then when another program tried to find them, it looked in /usr/lib and couldn't find them since they were in the libdir. So I think it might be good to install in both places just in case.

install(TARGETS stellarsolverstatic DESTINATION "${CMAKE_INSTALL_PREFIX}/lib/")
install(TARGETS stellarsolver DESTINATION "${CMAKE_INSTALL_PREFIX}/lib/")
install(TARGETS stellarsolverstatic DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(TARGETS stellarsolver DESTINATION ${CMAKE_INSTALL_LIBDIR})
The following user(s) said Thank You: Peter Sütterlin
3 years 9 months ago #55819

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

  • Posts: 1009
  • Thank you received: 133
Ah thanks. Yes, I realized too late that both get installed.. Somewhat nasty, as those two should separate 64 and 32 bit libs... But no huge issue indeed.
3 years 9 months ago #55840

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

  • Posts: 333
  • Thank you received: 92
Hello Robert,

What's next for the StellarSolver?

Han
3 years 7 months ago #58333

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

  • Posts: 2876
  • Thank you received: 809
So I was working on getting it working in KStars, having somebody do a code review, and making revisions based upon things I find during the integration process. I was working on that in June, but then I took a bit of a break from it because I would like to get some other things done and I was working almost exclusively on that as my non work related project for a couple of months. I had a bunch of other projects that were getting neglected. I will be hopefully getting back to it this week I hope. I made a lot of progress on the other projects. I need to probably better manage my time so that I can do more than one project at once. But I am definitely hoping to make good progress on it this week.
3 years 7 months ago #58335

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

  • Posts: 333
  • Thank you received: 92

For the record, ASTAP can still read and display these XYLS files but in the next ASTAP version 0.9.410, I will remove the possibility to use them as an input to the ASTAP solver. At the moment I don't think this option will be ever used. I like to clean up the ASTAP code and secondly the ASTAP source extractor is also improved making sextractor usage less desirable.

Han
3 years 7 months ago #58378

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

  • Posts: 535
  • Thank you received: 109
Greetings all, and thank you for all the work on stellarsolver @rlancaste.

Last night, I put a PR up to add the spec file to stellarsolver. This allows an RPM to be built for systems that use RPM packages. I successfully built the RPMs from the branch the PR is created from for all current (and future) Fedora versions and made them available. Once the PR is merged to master, I will update the docs here with how to add the repository. This branch build also allowed me to make new kstars packages available that include stellarsolver. From version `1:3.5.0.git-20201009051405.fc32` and newer, stellarsolver will be included with kstars in the RPM, and is listed as a required dependency in the package.

Jim
3 years 5 months ago #61298

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

  • Posts: 643
  • Thank you received: 62
Hi!

Trying to test this for the first time, I pulled down the code from git. Following the instructions on Github, I should then run
./installLinux.sh

However, I find no such script. Is it still the two install scripts in linux-scripts folder that are to be used?

Magnus
3 years 5 months ago #61299

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

Time to create page: 1.860 seconds