Issue with Align with StellarSolver

[Giles Coochey]

By the way, I saw your commits, and so built and loaded a test image 
which failed before. This worked very well with the default settings:

Evaluating Installed RAM for inParallel Option.  Total Size of Index 
files: 31.7369 GB, Installed RAM: 7.64153 GB
Not enough RAM is available on this system for loading the index files 
you have in parallel
Disabling the inParallel option.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Sextractor. . .
Stars Found before Filtering: 3097
Removing the stars with a/b ratios greater than 1.5
Keeping just the 50 brightest stars
Stars Found after Filtering: 50
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Configuring StellarSolver
Set odds ratio to solve to 1e+09 (log = 20.7233)

Scale range: 2.35182 to 2.87444 arcsec/pixel

Downsampling is multiplying the scale by: 2
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine. . .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Solve Log Odds:  222.518
Number of Matches:  40
Solved with index:  4108
Field center: (RA,Dec) = (38.1603, 62.6568) deg.
Field center: (RA H:M:S, Dec D:M:S) = (02:32:38.463, +62:39:24.581).
Field is: (128.653, 115.819) deg from search coords.
Field size: 1.70109 x 1.28661 degrees
Pixel Scale: 1.31564"
Field rotation angle: up is -138.765 degrees E of N
Field parity: neg

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Internal Sextractor w/ StellarSolver  took a total of: 5.101 second(s).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On 15/10/2020 16:38, Robert Lancaster wrote:
> Sounds great, thank you very much.  Yeah for at least the next day, I 
> will have too much work to do to even look at it.  But I definitely 
> should be able to check it out on Friday Afternoon or Saturday.  It is 
> interesting that based on the forums and all the testing, its now 
> working great for everyone on all platforms except the Pi.  All the 
> issues in the last couple of days except this were related to 
> incorrect scale information in the image that they were trying to 
> solve. I am hoping that this is just something related to memory and 
> it is easy to clear up, but I will look into it.
>
>> On Oct 15, 2020, at 11:25 AM, Giles Coochey <giles at coochey.net 
>> <mailto:giles at coochey.net>> wrote:
>>
>>
>> On 15/10/2020 16:12, Robert Lancaster wrote:
>>> I will definitely check this out tomorrow.  That is not the correct 
>>> amount of memory obviously.  In this case, it should detect that 
>>> there is not enough memory and disable the option to load all the 
>>> indexes concurrently.
>>>
>>> The goal with the settings is to actually reduce the number of 
>>> settings by wrapping them up in the options profiles. Astrometry.net 
>>> <http://astrometry.net/>, sextractor, and kstars had huge amounts of 
>>> different settings that would make astrometry work or fail.  The 
>>> options are hidden and all in different places.  I’m trying to 
>>> consolidate that.  Once this is perfected, unless you have a special 
>>> case, you should just be able to select from several profiles and 
>>> not even have to look at all the settings like downsample, min 
>>> width, max width etc etc etc.  I’m trying to perfect a set of 
>>> settings that work well for most people, so that you can just select 
>>> that and go with it.
>>>
>>> I’m sorry that it is taking a while to perfect the integration, but 
>>> on my machine, due to the optimizations and parallelization that I 
>>> added, the stellarsolver library has reduced the solving time from 
>>> several minutes to several seconds for most images, and now it can 
>>> solve images that were not solvable before.  It can blind solve 
>>> images that have no information about them including Jpegs in 
>>> several seconds.   In addition, this new library makes it possible 
>>> for users on windows to solve just as quickly as on Linux without 
>>> installing all kinds of extra packages that must be installed in 
>>> compatibility layers.  It also resolves issues on Macs, where 
>>> people’s python installations make astrometry have all sorts of 
>>> problems.  And third, it will allow us to stop reading and writing 
>>> so many temporary files to the Pi’s file system, because that wears 
>>> it out.
>>>
>>> So yes, I know that astrometry was working before on your system and 
>>> this might not work perfectly yet, but please be patient while we 
>>> perfect it because I have been working hard on this project for many 
>>> months since February and I think it will really help for a lot of 
>>> users.  Again, it was not my plan to put it into KStars master 
>>> before we were ready, but please be patient.
>>>
>>>
>> Thanks Robert,
>>
>> I'm looking forward to being able to Solve directly on Windows, 
>> that's certainly a plus.
>>
>> Don't apologize, I just saw the talk about StellarSolver, some 
>> reports of issues, and discussion of features and so, out of 
>> curiosity, went out and built the test versions to give it a try, 
>> unfortunately, not yet stable on my Pi, so thought I'd send some 
>> feedback.
>>
>> Now I'm back at 3.4.3 from the Astroberry repo, but would love to be 
>> able to run the SEP Multistar guiding on Astroberry as well, so 
>> thought I'd take a look. Happy to give it another try once you've had 
>> a look.
>>
>> -- 
>> Giles Coochey
>
-- 
Giles Coochey

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201017/d5b6dd96/attachment.htm>