Yes, this one. I've never succeeded on it with a blind solve. I've tried again today with the same parameters that I can see on your screenshot and a fresh compilation from master

Only 8 and 16 bits bayered images supported.
FITS header: cannot find OBJCTRA (keyword not found in header).
FITS header: cannot find FOCALLEN: (keyword not found in header).
Automatically downsampling the image by 4
Evaluating Installed RAM for inParallel Option. Total Size of Index files: 0.609186 GB, Installed RAM: 3.6884 GB, Free RAM: 2.95144 GB
There should be enough RAM to load the indexes in parallel.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Sextractor. . .
Stars Found before Filtering: 5496
Removing the stars with a/b ratios greater than 1.5
Keeping just the 50 brightest stars
Stars Found after Filtering: 50
Starting 4 threads to solve on multiple scales
Solver # 1, Low 0.1, High 0.71875 arcminwidth
Solver # 2, Low 0.71875, High 2.575 arcminwidth
Solver # 3, Low 2.575, High 5.66875 arcminwidth
Solver # 4, Low 5.66875, High 10 arcminwidth
Scale range: 0.71875 to 2.575 degrees wide
Scale range: 0.1 to 0.71875 degrees wide
Image width: 3888 pixels, Downsampled Image width: 972 pixels; arcsec per pixel range: 0.37037 to 2.66204
Image width: 3888 pixels, Downsampled Image width: 972 pixels; arcsec per pixel range: 2.66204 to 9.53704
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine. . .
Starting Internal StellarSolver Astrometry.net based Engine. . .
Scale range: 5.66875 to 10 degrees wide
Scale range: 2.575 to 5.66875 degrees wide
Image width: 3888 pixels, Downsampled Image width: 972 pixels; arcsec per pixel range: 9.53704 to 20.9954
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine. . .
Image width: 3888 pixels, Downsampled Image width: 972 pixels; arcsec per pixel range: 20.9954 to 37.037
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine. . .
Child solver: 1 did not solve or was aborted
Child solver: 2 did not solve or was aborted
Child solver: 3 did not solve or was aborted
Child solver: 4 did not solve or was aborted
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Internal Sextractor w/ StellarSolver failed after 201.521 second(s).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


For the focalmm parameter, I think that was something you where using to convert from one type of limits with the others. I see that it looks like an astrometry parameter (with a very odd reference to full frame cameras), so I'll not use it.

Read More...

Hi Rob,

I've tried again the focalmm scale mode with the stacked image I've sent some days ago. It doesn't crash now, but it can't solve yet the image

Only 8 and 16 bits bayered images supported.
FITS header: cannot find OBJCTRA (keyword not found in header).
FITS header: cannot find FOCALLEN: (keyword not found in header).
Automatically downsampling the image by 4
Evaluating Installed RAM for inParallel Option. Total Size of Index files: 0.609186 GB, Installed RAM: 3.6884 GB, Free RAM: 2.79109 GB
There should be enough RAM to load the indexes in parallel.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Sextractor. . .
Stars Found before Filtering: 2913
Removing the stars with a/b ratios greater than 1.5
Keeping just the 50 brightest stars
Stars Found after Filtering: 50
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Configuring StellarSolver
Scale range: 580 to 620 mm focal length
Image width: 3888 pixels, Downsampled Image width: 972 pixels; arcsec per pixel range: 6.15911 to 6.58361
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine. . .
Solver was aborted, timed out, or failed, so no solution was found
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Internal Sextractor w/ StellarSolver failed after 24.222 second(s).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


The value for the arcsec/pixel seems wrong to me. For the 600mm focal length on my telescope and 5.70 microns per pixel, the image scale is 1.975 arcsec/pixel well outside the searched range

Read More...

No with the capture or the guide module. I was talking about the align module, the one where we perform the platesolving. Here I’ve been changing between FL and when done, sometimes the FL is mixed up on the final images generated by the capture module.

Read More...

Did you update to the latest stellarsolver first?


I've pulled down three hours ago, but nothing new was on the repo.

Read More...

I think that the problem reported by Jo it's a real one. I've seen it before. Some times I use the align module with the guide scope and then, when I change to the main telescope to generate accurate WCS entries on the main image, so I can fine tunning the framing of a target. When I latter select again the guider, sometimes the FL on the final images is from the guidescope,

Jo, do you remember if you have been changing between guidescope and main telescope?

Read More...

Hi Rob

Some updates. I'm unable to solve the result.fits file that I sent yesterday with M27. But if I use one of the frames, as captured by KStars two months ago, it was solved on les that 2 sec. Same for other individual frames from other sessions. So, perhaps the stretching that I have applied to the result is invalidating the photometry, and confuses the matching algorithm. What is important for me, is that It works with individual frames as taken from the telescope, so it's seems reliable enough for my needs.

Rafa

Read More...

Jo, thanks for your help. I was aware on how to go back on git, this was the reason I've told Rob that perhaps, this kind of changes will be best applied as a squashed commit. Because as its currently merged, if you go back in time, you will not recover exactly the same repo. I hope, that as you have found in your compilation, the leftovers doesn't interfere too much with the rest.

But I'm starting to put my feet on thin ice, because I that I'm not working actively on the project, should not be talking about its dynamics... sorry, it's a professional deformation :)

Ok, let's go to help stabilising the product. Rob if you need any other test, or do you think that I can try something, please, don't hesitate to ask me

Rafa

Read More...

Nobody is being hard with nobody. At least not me. I'm aware that I've put myself on this problem not Jasem or you, Rob, don't worry.

In my case I've get a perfect storm scenario: a bug on OnStep driver that don't let me use the official build, a new platform (I've recently changed from macOS to RP4) and my insane curiosity about code :dry:

Rafa

Read More...

Hi Rob,

Sorry for my delay, I live on Europe (Spain), and I can not expend too much time during working day. I'll test it throughly latter today.

Yes, yes, I'm testing exclusively with StellarSolverTester. I've opened the file and press start without any other change. Latter I've found that it was trying yo use the profile 5 (I've stopped it after waiting for 10min). Then I've tried with profile 5 and I've seen different process end without finding a match. I've stoped it after 4 minutes. Then I've tried to put limits on focalmm (550 to 650 for a 600mm real focal length) and it crashed very quick.

About the first problem, the crash when I press the solve button, yes, it now solved.

Thank you very much for all your effort!

Rafa

Read More...

Hi Rob,

Now, it didn't crash, but it didn't works. I've stoped it after more that 10 minutes trying a blind solve. Then I tried to guide it adding limits to the focal length and then crashed. Also, as you have merged this branch (instead of squashing the changes into a single commit) it's almost imposible to revert the app to a point before the change. I've trapped my self into a corner :): I can't revert to the oficial 3.4.3 because there is a problem with the OnStep driver and I can't go to the current nightly because the Solver is not working on the RP4 build.

Read More...

Can you share this file you tried to solve?


Yes, of course!. Is a stack generated with the last version of SiriL You can download it from my drive crash on RP4

Read More...

Downloaded and compiled on RPi4 the master branch of StellarSolver. Running StellarSolverTester and opening a FITS file, shows the next warnings

Only 8 and 16 bits bayered images supported.
FITS header: cannot find OBJCTRA (keyword not found in header).
FITS header: cannot find FOCALLEN: (keyword not found in header).


When I press START it crashed. In the terminal I can read:

pi@raspberrypi:~ $ StellarSolverTester
libEGL warning: DRI2: failed to authenticate
qt5ct: using qt5ct plugin
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

FITSIO status = 202: keyword not found in header

FITSIO status = 202: keyword not found in header
Segmentation fault



Read More...

I've tried to compile the current master branch of KStars on a Raspberry PI4 running Raspbian buster and I was unable because there is no libstellarsolver-dev version available. Are there any spacial procedure to try the new internal solver on RP4?

Read More...

rbarberac replied to the topic 'RPI4 GPS dongle' in the forum. 1 week ago

Yep, after restarting KStars multiple times it's working. Now my next doubt with this setup. I'm using a OnStep mount, so I need to set time and location to the mount on each boot, so I've KStars configured as:



But as soon as I add the GPS aux it changes automatically to:



So, now my Raspberry / KStars has the correct time / location, but my OnStep mount is not updated. Any solution? Or should I boot KStars first to fix location/date and then change the configuration to update the mount?

Read More...

rbarberac replied to the topic 'RPI4 GPS dongle' in the forum. 1 week ago

The Set button on the GPS NEMA driver's Connection page is not working. As I press it, nothing happens. Are there any solution to this annoying bug? I have suffered it on macOS before, but I thought that it was a macOS related thing, but now it's happening again on the raspi



Read More...