KStars v3.5.0 Release Date?

Tue Nov 10 18:43:59 GMT 2020

*2. WCS Polar Align: Can this be reproduced with simulators?*

I just tried on my Mac's Ubuntu VM, and no issues. The WCS processing was
very quick.
I then tried on my RPi with the simulator, and yes, the problem reproduces.

Here is the output. Note, 1st WCS processing took 27s, and the 2nd and 3rd
took about the same.
What is the WCS processing doing?

Hy

2020-11-10T10:39:08 Mount axis is to the Top Left of the celestial pole
2020-11-10T10:39:08 WCS data processing is complete.
2020-11-10T10:38:41 Please wait while WCS data is processed...
2020-11-10T10:38:41 Solution coordinates: RA (11h 43m 41s) DEC ( 89° 59'
43") Telescope Coordinates: RA (04h 29m 12s) DEC ( 90° 00' 00")
2020-11-10T10:38:41 Solver RA (359.94313) DEC (89.88647) Orientation
(-89.94295) Pixel Scale (1.19178)
2020-11-10T10:38:41 Solver completed after 0.73 seconds.
2020-11-10T10:38:41 Field parity: neg

2020-11-10T10:38:41 Field rotation angle: up is -89.9429 degrees E of N
2020-11-10T10:38:41 Pixel Scale: 1.19178"
2020-11-10T10:38:41 Field size: 1.65446 x 1.32383 degrees
2020-11-10T10:38:41 Field is: (-1.05351e+06, 408.692) deg from search
coords.
2020-11-10T10:38:41 Field center: (RA H:M:S, Dec D:M:S) = (23:59:46.352,
+89:53:11.308).
2020-11-10T10:38:41 Field center: (RA,Dec) = (359.943, 89.8865) deg.
2020-11-10T10:38:41 Solved with index:  4208
2020-11-10T10:38:41 Number of Matches:  32
2020-11-10T10:38:41 Solve Log Odds:  172.435
2020-11-10T10:38:41
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:38:41 Starting Internal StellarSolver Astrometry.net based
Engine with the 4-SmallScaleSolving profile. . .
2020-11-10T10:38:41
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:38:41 Image width: 4998 pixels, Downsampled Image width: 1666
pixels; arcsec per pixel range: 2.28946 to 4.29274
2020-11-10T10:38:41 Scale range: 63.5707 to 119.195 arcmin wide
2020-11-10T10:38:41 Configuring StellarSolver
2020-11-10T10:38:41
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:38:41 Stars Found after Filtering: 34
2020-11-10T10:38:41 Keeping just the 50 brightest stars
2020-11-10T10:38:41 Removing the stars with a/b ratios greater than 1.5
2020-11-10T10:38:41 Stars Found before Filtering: 34
2020-11-10T10:38:40 Starting Internal StellarSolver Sextractor with the
4-SmallScaleSolving profile . . .
2020-11-10T10:38:40
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:38:40 There should be enough RAM to load the indexes in
parallel.
2020-11-10T10:38:40 Evaluating Installed RAM for inParallel Option.  Total
Size of Index files: 0.303479 GB, Installed RAM: 3.81495 GB, Free RAM:
2.39693 GB
2020-11-10T10:38:40 Automatically downsampling the image by 3
2020-11-10T10:38:40 Image received.
2020-11-10T10:38:28 Capturing image...
2020-11-10T10:38:28 Mount second rotation is complete.
2020-11-10T10:38:17 Please wait until mount completes rotating to RA (04h
09m 25s) DE ( 90° 00' 00")
2020-11-10T10:38:17 WCS data processing is complete.
2020-11-10T10:37:51 Please wait while WCS data is processed...
2020-11-10T10:37:51 Solution coordinates: RA (00h 55m 17s) DEC ( 90° 00'
07") Telescope Coordinates: RA (06h 09m 25s) DEC ( 90° 00' 00")
2020-11-10T10:37:51 Solver RA (358.95642) DEC (89.88291) Orientation
(-89.95193) Pixel Scale (1.19172)
2020-11-10T10:37:51 Solver completed after 0.77 seconds.
2020-11-10T10:37:51 Field parity: neg

2020-11-10T10:37:51 Field rotation angle: up is -89.9519 degrees E of N
2020-11-10T10:37:51 Pixel Scale: 1.19172"
2020-11-10T10:37:51 Field size: 1.65444 x 1.3237 degrees
2020-11-10T10:37:51 Field is: (-959762, 421.536) deg from search coords.
2020-11-10T10:37:51 Field center: (RA H:M:S, Dec D:M:S) = (23:55:49.542,
+89:52:58.464).
2020-11-10T10:37:51 Field center: (RA,Dec) = (358.956, 89.8829) deg.
2020-11-10T10:37:51 Solved with index:  4209
2020-11-10T10:37:51 Number of Matches:  23
2020-11-10T10:37:51 Solve Log Odds:  137.271
2020-11-10T10:37:51
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:51 Starting Internal StellarSolver Astrometry.net based
Engine with the 4-SmallScaleSolving profile. . .
2020-11-10T10:37:51
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:51 Image width: 4998 pixels, Downsampled Image width: 1666
pixels; arcsec per pixel range: 2.28946 to 4.29274
2020-11-10T10:37:51 Scale range: 63.5707 to 119.195 arcmin wide
2020-11-10T10:37:50 Configuring StellarSolver
2020-11-10T10:37:50
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:50 Stars Found after Filtering: 32
2020-11-10T10:37:50 Keeping just the 50 brightest stars
2020-11-10T10:37:50 Removing the stars with a/b ratios greater than 1.5
2020-11-10T10:37:50 Stars Found before Filtering: 32
2020-11-10T10:37:49 Starting Internal StellarSolver Sextractor with the
4-SmallScaleSolving profile . . .
2020-11-10T10:37:49
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:49 There should be enough RAM to load the indexes in
parallel.
2020-11-10T10:37:49 Evaluating Installed RAM for inParallel Option.  Total
Size of Index files: 0.303479 GB, Installed RAM: 3.81495 GB, Free RAM:
2.40435 GB
2020-11-10T10:37:49 Automatically downsampling the image by 3
2020-11-10T10:37:49 Image received.
2020-11-10T10:37:37 Capturing image...
2020-11-10T10:37:37 Mount first rotation is complete.
2020-11-10T10:37:27 Please wait until mount completes rotating to RA (05h
49m 39s) DE ( 90° 00' 00")
2020-11-10T10:37:27 WCS data processing is complete.
2020-11-10T10:37:00 Please wait while WCS data is processed...
2020-11-10T10:37:00 Solution coordinates: RA (09h 09m 07s) DEC ( 89° 59'
29") Telescope Coordinates: RA (07h 49m 39s) DEC ( 90° 00' 00")
2020-11-10T10:37:00 WCS information updated. Images captured from this
point forward shall have valid WCS.
2020-11-10T10:37:00 Solver RA (359.80905) DEC (89.89045) Orientation
(-89.93621) Pixel Scale (1.19184)
2020-11-10T10:37:00 Solver completed after 0.84 seconds.
2020-11-10T10:37:00 Field parity: neg

2020-11-10T10:37:00 Field rotation angle: up is -89.9362 degrees E of N
2020-11-10T10:37:00 Pixel Scale: 1.19184"
2020-11-10T10:37:00 Field size: 1.65452 x 1.3239 degrees
2020-11-10T10:37:00 Field is: (-872634, 394.378) deg from search coords.
2020-11-10T10:37:00 Field center: (RA H:M:S, Dec D:M:S) = (23:59:14.171,
+89:53:25.622).
2020-11-10T10:37:00 Field center: (RA,Dec) = (359.809, 89.8905) deg.
2020-11-10T10:37:00 Solved with index:  4208
2020-11-10T10:37:00 Number of Matches:  32
2020-11-10T10:37:00 Solve Log Odds:  172.537
2020-11-10T10:37:00
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:00 Starting Internal StellarSolver Astrometry.net based
Engine with the 4-SmallScaleSolving profile. . .
2020-11-10T10:37:00
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:00 Image width: 4998 pixels, Downsampled Image width: 1666
pixels; arcsec per pixel range: 2.28946 to 4.29274
2020-11-10T10:37:00 Scale range: 63.5707 to 119.195 arcmin wide
2020-11-10T10:37:00 Configuring StellarSolver
2020-11-10T10:37:00
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:37:00 Stars Found after Filtering: 34
2020-11-10T10:37:00 Keeping just the 50 brightest stars
2020-11-10T10:37:00 Removing the stars with a/b ratios greater than 1.5
2020-11-10T10:37:00 Stars Found before Filtering: 34
2020-11-10T10:36:59 Starting Internal StellarSolver Sextractor with the
4-SmallScaleSolving profile . . .
2020-11-10T10:36:59
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-11-10T10:36:59 There should be enough RAM to load the indexes in
parallel.
2020-11-10T10:36:59 Evaluating Installed RAM for inParallel Option.  Total
Size of Index files: 0.303479 GB, Installed RAM: 3.81495 GB, Free RAM:
2.61315 GB
2020-11-10T10:36:59 Automatically downsampling the image by 3
2020-11-10T10:36:59 Image received.
2020-11-10T10:36:47 Capturing image...
2020-11-10T10:36:34 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-11-10T10:36:34 Idle.

On Tue, Nov 10, 2020 at 2:16 AM Jasem Mutlaq <mutlaqja at ikarustech.com>
wrote:

> Alright, let's look at this:
>
> 1. Parallel algorithm: This is related to SOLVER, not image partitioning.
> It should work fine on Rpi4 and the checks are more reliable now as Robert
> worked on that.
> 2. WCS Polar Align: Can this be reproduced with simulators?
>
> --
> Best Regards,
> Jasem Mutlaq
>
>
>
> On Tue, Nov 10, 2020 at 10:48 AM Wolfgang Reissenberger <
> sterne-jaeger at openfuture.de> wrote:
>
>> It wasn’t that bad. The problem was that KStars went to 100% CPU usage
>> and died (or I killed it, do not exactly remember). I’ll try to reproduce
>> it...
>>
>> Am 10.11.2020 um 08:45 schrieb Hy Murveit <murveit at gmail.com>:
>>
>> OK, well I believe it was fixed a week ago, so if you can still recreate
>> it, you should report it.
>> It should be fixed before release if it is still freezing the Pi.
>>
>> Hy
>>
>> On Mon, Nov 9, 2020 at 11:42 PM Wolfgang Reissenberger <
>> sterne-jaeger at openfuture.de> wrote:
>>
>>> OK, I have to check it. The problem occurred only a few days ago and I
>>> think I’m always on bleeding edge...
>>>
>>> Am 10.11.2020 um 08:38 schrieb Hy Murveit <murveit at gmail.com>:
>>>
>>> Wolfgang: I believe Rob and/or Jasem fixed the issue with parallel
>>> algorithm bringing down the RPi4 a while back.
>>> I have the solver on auto parallelism and load all indexes in memory,
>>> and it seems to work fine (and in parallel).
>>> Similarly, for star extraction, Jasem implemented a threaded extraction
>>> that also automatically determines how many threads to use and seems fine
>>> on the RPi4.
>>>
>>> Eric: I believe these parallel options are the defaults. Hopefully users
>>> won't need to configure things like this.
>>> For star detection, I don't believe you can turn it off.
>>> For star detection Jasem split the frame before detection (into at most
>>> num-threads parts--4 for the RPi4).
>>> For align, I'm not sure how Rob divided things.
>>>
>>> Hy
>>>
>>> On Mon, Nov 9, 2020 at 11:07 PM Wolfgang Reissenberger <
>>> sterne-jaeger at openfuture.de> wrote:
>>>
>>>> Hi all,
>>>> I think we are close to finishing the release. I personally would opt
>>>> to wait for another week and keep an eye stability.
>>>>
>>>> Maybe we should take another look if the default settings in the
>>>> StellarSolver profiles work a) for typical camera/scope combinations and b)
>>>> for all platforms.
>>>>
>>>> For example with my RPi, I needed to change the Parallel Algorithm to
>>>> „None“ because parallelity brought KStars down. Is the default setting
>>>> „None“ and I changed it somewhen? With all the new parameters I would
>>>> prefer having a robust setup and leave it to the user to optimize speed.
>>>>
>>>> @Jasem: please take a closer look to MR!122, since it fixed 4(!)
>>>> regressions I introduced with my capture counting fix MR!114. Hopefully now
>>>> we have at least a proper coverage with automated tests...
>>>>
>>>> Wolfgang
>>>>
>>>> Am 09.11.2020 um 22:04 schrieb Jasem Mutlaq <mutlaqja at ikarustech.com>:
>>>>
>>>> Hello Folks,
>>>>
>>>> So back to this topic, any major blockers to the KStars 3.5.0 release
>>>> now?
>>>>
>>>> 1. Remote Solver should be fixed now.
>>>> 2. StellarSolver Profiles are more optimized now.
>>>> 3. Handbook not updated yet, but we can probably work on this shortly.
>>>> 4. Couple of pending MRs to take care of.
>>>>
>>>> How about Friday the 13th?
>>>>
>>>> --
>>>> Best Regards,
>>>> Jasem Mutlaq
>>>>
>>>>
>>>>
>>>> On Thu, Nov 5, 2020 at 3:41 AM Robert Lancaster <rlancaste at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Eric,
>>>>>
>>>>> Ok so then we would be changing the way we do version numbering with
>>>>> this, right?
>>>>> I believe now we typically add features in each new iteration 3.4.1,
>>>>> 3.4.2, etc etc
>>>>> and when it is really big like StellarSolver, then we make it a big
>>>>> release like 3.5.0
>>>>>
>>>>> With this new paradigm, we wouldn’t put new features into the master
>>>>> of the main 3.5 branch
>>>>> But instead we would work on a new 3.6 branch, and then bug fixes
>>>>> would go into the 3.5 branch
>>>>> to make each new minor release, like 3.5.1, 3.5.2 etc.
>>>>>
>>>>> Do I have this correct?
>>>>>
>>>>> If this is right, then it would be longer before users see new
>>>>> features in the main branch, but the
>>>>> tradeoff is that the main branch would have a LOT more stability.  I
>>>>> see this as a big positive.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Rob
>>>>>
>>>>> > On Nov 4, 2020, at 5:54 PM, Eric Dejouhanet <
>>>>> eric.dejouhanet at gmail.com> wrote:
>>>>> >
>>>>> > Hello Hy,
>>>>> >
>>>>> > Version 3.5.0 is only the beginning of the 3.5.x series, with more
>>>>> > bugfixes on each iteration (and possibly, only bugfixes).
>>>>> > So I have no problem leaving unresolved issues in 3.5.0.
>>>>> >
>>>>> > For instance, the Focus module now has a slight and unforeseeable
>>>>> > delay after the capture completes.
>>>>> > The UI reflects the end of the capture only, not the end of the
>>>>> detection.
>>>>> > This makes the UI Focus test quite difficult to tweak, as running an
>>>>> > average of the HFR over multiple frames now has an unknown duration.
>>>>> > Right now, the test is trying to click the capture button too soon 2
>>>>> > out of 10 attempts.
>>>>> > But this won't block 3.5 in my opinion (and now that I understood the
>>>>> > problem, I won't work on it immediately).
>>>>> >
>>>>> > In terms of reporting problems, the official way is stil
>>>>> bugs.kde.org,
>>>>> > but there's quite a cleanup/followup to do there.
>>>>> > I'd say we can use issues in invent.kde.org to discuss planned
>>>>> > development around a forum/bugzilla issue or invent proposal (like
>>>>> > agile stories).
>>>>> > There are milestones associated with several issues (although I think
>>>>> > they should be reviewed and postponed).
>>>>> > And we can certainly write a punchlist: check the board at
>>>>> > https://invent.kde.org/education/kstars/-/milestones/3
>>>>> >
>>>>> > Le mer. 4 nov. 2020 à 22:38, Hy Murveit <murveit at gmail.com> a écrit
>>>>> :
>>>>> >>
>>>>> >> Eric,
>>>>> >>
>>>>> >> I would add to your list:
>>>>> >>
>>>>> >> - KStars Handbook (review update sections to reflect 3.5.0) and
>>>>> finally (perhaps manually if necessary) put the latest handbook online.
>>>>> >>
>>>>> >> - Review the extraction settings. I spent a bit of time looking at
>>>>> the default HFR settings, and based on some experimentation (truth be told,
>>>>> with a limited amount of data) adjust things a little differently than my
>>>>> first guess (which was basically focus' settings).
>>>>> >> Rob: My intuition is that I should adjust the default StellarSolver
>>>>> star-extraction settings for Focus and Guide as well in
>>>>> stellarsolverprofile.cpp. I don't know whether you've already verified
>>>>> them, and want to release them as they are, or whether they are a first
>>>>> shot and you'd welcome adjustment?
>>>>> >>
>>>>> >> Also, Eric, I suppose I should be adding these things here:
>>>>> https://invent.kde.org/education/kstars/-/issues
>>>>> >> Is that right? Sorry about that--ok, after this thread ;) But
>>>>> seriously, your email is a good summary, and from that link
>>>>> >> it doesn't seem as easy to see which are "must do by 3.5.0" and
>>>>> which are "nice to have someday".
>>>>> >> A 3.5.0 punchlist would be a nice thing to have.
>>>>> >>
>>>>> >> Hy
>>>>> >>
>>>>> >> On Wed, Nov 4, 2020 at 12:58 PM Eric Dejouhanet <
>>>>> eric.dejouhanet at gmail.com> wrote:
>>>>> >>>
>>>>> >>> Hello,
>>>>> >>>
>>>>> >>> Where do we stand now in terms of bugfixing towards 3.5.0?
>>>>> >>>
>>>>> >>> - StellarSolver has all features in, and 1.5 is finally out at
>>>>> Jasem's PPA.
>>>>> >>> - However Gitlab CI still complains about that lib package (see
>>>>> >>> https://invent.kde.org/education/kstars/-/jobs/75941)
>>>>> >>> - Unitary tests are being fixed progressively, mount tests are
>>>>> down to
>>>>> >>> ~20 minutes (yeees!)
>>>>> >>> - From my tests, the remote Astrometry INDI driver is not usable
>>>>> >>> anymore from Ekos.
>>>>> >>> - The issue raised with flat frames is confirmed fixed (at least
>>>>> by me).
>>>>> >>> - Meridian flip is OK (but I had not enough time to test TWO flips
>>>>> in a row).
>>>>> >>> - Memory leaks are still being researched in Ekos.
>>>>> >>> - There is an issue when duplicating an entry in a scheduler job,
>>>>> >>> where the sequence associated is copied from the next job.
>>>>> >>>
>>>>> >>> Could we get a 3.6 branch where we will merge development of new
>>>>> features?
>>>>> >>> And master for bugfixing 3.5.x until we merge 3.6 new features in?
>>>>> >>> (we'd still have to port bugfixes from master to 3.6)
>>>>> >>> I don't think the opposite, master for 3.6 and a separate living
>>>>> >>> 3.5.x, is doable in the current configuration (build, ppas,
>>>>> MRs...).
>>>>> >>>
>>>>> >>> --
>>>>> >>> -- eric.dejouhanet at gmail.com - https://astronomy.dejouha.net
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > -- eric.dejouhanet at gmail.com - https://astronomy.dejouha.net
>>>>>
>>>>>
>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201110/1d79d173/attachment-0001.htm>