×

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: 535
  • Thank you received: 109

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

@rlancaste @knro

Hi Rob, the latest merge to master is not playing well with the copr build. Realizing you may still be working on this, here is a link to the output if it helps: download.copr.fedorainfracloud.org/resul.../builder-live.log.gz

Jim
3 years 6 months ago #61969

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

I pulled the changes at 18:30 (UTC+2) from github.

I was not able to install stellarsolver by using the installStellarSolverLibrary.sh script because <QtConcurrent> was not found, which was introduced into the source code two days ago.
Instead I had to follow Ron's build-instructions found on his github page:

cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTER=ON ../stellarsolver/
make -j $(expr $(nproc) + 2)
sudo make install

My files are solved blazingly fast.
Kstars still crashes if I try to solve M65 with downsampling.

By the way: what is the purpose of kstars new extractor branch?
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 6 months ago #61974

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

  • Posts: 2877
  • Thank you received: 812

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

"For the focalmm parameter, I thought that it was something you were using to convert from one range to the others. It seems that it's an astrometry parameter (with a very odd reference to full frame cameras), so I'll not use it for now"

It works just like the other scale units. Astrometry supports scales in several units degree width, arc minute width, arc seconds per pixel, and focal mm. KStars doesn't support the focal MM option, but astrometry does, so I thought stellarsolver should as well. I have yet to see any images though that have a scale in those units recorded in them, so I can't really test it to see if it works. The others. I can test easily because KStars and other programs use them all the time. Maybe someday someone will tell us if it works. Or maybe it is really falling into disuse so it doesn't matter anyway.
3 years 6 months ago #61975

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

  • Posts: 2877
  • Thank you received: 812

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

Cerro Torre,

Glad to hear that Jasem's updates to the SEP code sped up your solves and star extraction. He made it possible for us to run the star extraction in different threads simultaneously. I will have to update the install script because Jasem's changes rely on Qt concurrent.

I think I have your M65 image, correct? Was this on a Pi or some other computer? I can see if I get a crash. I don't get crashes when using my main computer, but it has much better resources than the PI does.

Jasem put his changes to both KStars and StellarSolver into a branch so that we could test things out before applying it. I tested it last night, found a few issues and corrected them before I merged his changes. If there are still crashes we can check it out.

Thanks!
3 years 6 months ago #61976

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

  • Posts: 2877
  • Thank you received: 812

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

Hi Jim, we will check it out. Thanks!
3 years 6 months ago #61977

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

  • Posts: 2877
  • Thank you received: 812

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

Cerro Torre

"My files are solved blazingly fast."

--That is exactly what we are aiming toward

"Kstars still crashes if I try to solve M65 with downsampling."

--That is what we are trying to um. . . aim away from. :-)

I think Jasem's improvement to SEP should really help with this and as we clean some things up, hopefully there will be no more issues.
3 years 6 months ago #61980

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

  • Posts: 1309
  • Thank you received: 226

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

The new solver really can solve fast! But I'm not exactly sure how fast as I did not see a time to solve stat in the output. That would be useful for determining optimal profile or custom settings.
I have managed to crash it on occasion with the simulator, but it's not very repeatable.
3 years 6 months ago #61987

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

  • Posts: 1009
  • Thank you received: 133

Replied by Peter Sütterlin on topic New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

When I try to compile the current stellarsolver my compiler (GCC 10.0) complains about missing includes in stellarsolver/sep/extract.cpp (#include <cstdio>) and stellarsolver/sep/lutz.cpp (#include <cstdlib>), else sprintf and malloc are not declared....

As for kstars, should I use 'master' or 'extractor' for testing?
3 years 6 months ago #61991

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


I am using an Intel NUC with 4 physical cores (8 logical threads) and 16 GB of RAM.


Already added by the kstars team, thanks!
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 6 months ago #62004

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

Meant as feedback for the developers:
Internal SEP | Internal Solver | 4-ParallelSmallScale (no downscale)

M57 solves in 4.44 seconds
Iris Nebula solves in 3.50 seconds
M65 solves in 2.84 seconds

Good work!
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 6 months ago #62005

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

  • Posts: 152
  • Thank you received: 20

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

Hi Rob,

I finally had a chance to do some testing with StellarSolver. I'm running a build from kstars commit 15ba3c90a1ec4724a28b43cfa69fa1fb6693242a and SS commit b8ce7148a1bad6f9dd4f5d8b4c4ef95396db4a3c.

I had been using ASTAP. I switched the solving method to "Internal solver" and left all settings as-is. I then ran Load and Slew and it just worked out of the box - no problems, generally. However, I did find a failure case that I'll share here.

BTW - when testing with the simulators I left the Solver Action as "Nothing" but the slew still occurred. Also, after the unwanted slew, the Load and Slew button was now greyed out. To recover it I had to stop/start the indi services.

The following image solves with no problem, even though the image has some problems including mystery stars.

www.dropbox.com/s/20kh08zb0xhc1y5/ic63_L...-35-21_001.fits?dl=0

This one works as well, without the mystery stars:

www.dropbox.com/s/4lx6wqjxu40lll6/ic63_L...-52-38_002.fits?dl=0

However, this one of the same field does not solve. The main differences I can determine is the median signal of this frame is higher than the other two and the image is rotated 180deg from the others.

www.dropbox.com/s/cfxuw6xdln8qjc5/ic63_L...-10-04_040.fits?dl=0

I've attached the log file with Alignment logging turned on. Also, below is from the log window on the alignment tab. Interesting that it says it needs 19.7GB of RAM. Is that true?

The optics are a corrected Dall-Kirkham at focal length of ~1700mm. Pixel scale is 6um.

Greg
2020-10-22T09:40:09 Solver Failed
2020-10-22T09:40:09 internal pixel buffer full
2020-10-22T09:40:00 Starting Internal StellarSolver Sextractor. . .
2020-10-22T09:40:00 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:40:00 There should be enough RAM to load the indexes in parallel.
2020-10-22T09:40:00 Evaluating Installed RAM for inParallel Option.  Total Size of Index files: 19.7149 GB, Installed RAM: 31.2902 GB
2020-10-22T09:39:35 Solver Failed
2020-10-22T09:39:35 Solver was aborted, timed out, or failed, so no solution was found
2020-10-22T09:39:35 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-22T09:39:35 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:35 Image width 640 pixels; arcsec per pixel range 0.93949 1.76154
 
2020-10-22T09:39:35 Scale range: 10.0212 to 18.7898 arcmin wide
 
2020-10-22T09:39:35 Set odds ratio to solve to 1e+9 (log = 20.7233)
 
2020-10-22T09:39:34 Configuring StellarSolver
2020-10-22T09:39:34 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:34 Starting Internal StellarSolver Sextractor. . .
2020-10-22T09:39:34 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:34 There should be enough RAM to load the indexes in parallel.
2020-10-22T09:39:34 Evaluating Installed RAM for inParallel Option.  Total Size of Index files: 19.7149 GB, Installed RAM: 31.2902 GB
2020-10-22T09:39:34 Image received.
2020-10-22T09:39:29 Capturing image...
2020-10-22T09:39:23 Slewing to target coordinates: RA (00h 59m 30s) DEC ( 61° 05' 18").
2020-10-22T09:39:23 Solution coordinates: RA (00h 59m 30s) DEC ( 61° 05' 18") Telescope Coordinates: RA (12h 45m 39s) DEC ( 90° 00' 00")
2020-10-22T09:39:23 WCS information updated. Images captured from this point forward shall have valid WCS.
2020-10-22T09:39:23 Solver RA (14.55265) DEC (60.97575) Orientation (0.22974) Pixel Scale (0.73429)
2020-10-22T09:39:23 Field parity: pos
 
2020-10-22T09:39:23 Field rotation angle: up is 0.229738 degrees E of N
2020-10-22T09:39:23 Pixel Scale: 0.734292"
2020-10-22T09:39:23 Field size: 55.0635 x 44.0628 arcminutes
2020-10-22T09:39:23 Field is: (-196.752, 50.8996) deg from search coords.
2020-10-22T09:39:23 Field center: (RA H:M:S, Dec D:M:S) = (00:58:12.637, +60:58:32.700).
2020-10-22T09:39:23 Field center: (RA,Dec) = (14.5527, 60.9758) deg.
2020-10-22T09:39:23 Solved with index:  4109
2020-10-22T09:39:23 Number of Matches:  11
2020-10-22T09:39:23 Solve Log Odds:  72.9335
2020-10-22T09:39:23 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:22 Starting Internal StellarSolver Astrometry.net based Engine. . .
2020-10-22T09:39:22 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:22 Scale range: 0.582152 to 0.873228 arcsec/pixel
 
2020-10-22T09:39:22 Set odds ratio to solve to 1e+9 (log = 20.7233)
 
2020-10-22T09:39:22 Configuring StellarSolver
2020-10-22T09:39:22 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:22 Stars Found after Filtering: 50
2020-10-22T09:39:22 Keeping just the 50 brightest stars
2020-10-22T09:39:22 Removing the stars with a/b ratios greater than 1.5
2020-10-22T09:39:22 Stars Found before Filtering: 20397
2020-10-22T09:39:18 Starting Internal StellarSolver Sextractor. . .
2020-10-22T09:39:18 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-10-22T09:39:18 There should be enough RAM to load the indexes in parallel.
2020-10-22T09:39:18 Evaluating Installed RAM for inParallel Option.  Total Size of Index files: 19.7149 GB, Installed RAM: 31.2902 GB
2020-10-22T09:38:29 World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid.
2020-10-22T09:38:29 Idle.
Last edit: 3 years 6 months ago by Greg.
3 years 6 months ago #62007
Attachments:

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

  • Posts: 1309
  • Thank you received: 226

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

I removed a couple of the largest unnecessary indexes from my system hoping to get the total low enough for parallel loading into memory. I found it will work once. But after the first solve more ram in consumed and it states there is not enough on the next solve.
Disabling the inParallel option.
2020-10-23T23:33:37 Not enough RAM is available on this system for loading the index files you have in parallel
2020-10-23T23:33:37 Evaluating Installed RAM for inParallel Option.  Total Size of Index files: 1.53425 GB, Installed RAM: 3.56387 GB, Free RAM: 1.51933 GB

The thing is, I have 4Gb Pi4. My Conky widget (AstroPi3 script setup, Thanks Rob) is showing only about 650Mb is being used. So I should have enough RAM. Furthermore running a memory check command returns this:
free
            total        used       free          shared    buff/cache  available
Mem:        3736984      610880     1571604       70892     1554500     2912904
Swap:       3736976           0     3736976

It appears the value under free matches closely what Stellarsolver finds. However the memory check states nearly 3Gb is available. Which is closer to what Conky reports.

I hope that is the case and the available RAM can be correctly detected and used.
Thank you.
3 years 6 months ago #62036

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

Time to create page: 0.916 seconds