Artificial Horizon

[Hy Murveit]

Sorry, don't understand your last line--What is #7?

Also, why would people make scripts when nothing makes use of it? Do users
find enough added value just marking up the sky? (I'm new to this and don't
really understand it's current value--happy to be educated. I'm really just
using my imaging point-of-view).

FWIW, I played with it this evening, and found editing regions buggy. For
instance, if you define two regions, and then delete one of them, the one
you didn't delete loses its last point and becomes "not closed".

When defining the polygons, it's necessary to be very exact when clicking
the last point (it needs to exactly match the first one). I'd like to be
simpler--e.g. the system could easily close the polygon itself.

Don't think we shoudl constrain the polygons to start (and end) on the
horizon--the instructions say one needs to do this. For instance, my
telescope's "horizon" never touches the real horizon at any azimuth.

The UI, though, with the addition of Terrain makes it straight-forward to
define a horizon. If the buggy-ness, and the issues with what's inside the
polygon and what's outside it were resolved, this could be a reasonable
thing to integrate with the scheduler.

Hy


On Wed, Mar 24, 2021 at 11:00 PM Eric Dejouhanet <eric.dejouhanet at gmail.com>
wrote:

> I don't think any other feature is using AH. It is slightly tedious to
> create and to edit. Some forum users created database scripts to generate
> it. #7 is registered in gitlab to make use of it in Scheduler.
>
> eric.dejouhanet at gmail.com - https://astronomy.dejouha.net
> *De:* murveit at gmail.com
> *Envoyé:* 24 mars 2021 22:50
> *À:* eric.dejouhanet at gmail.com
> *Répondre à:* hy at murveit.com
> *Cc:* kstars-devel at kde.org
> *Objet:* Re: Artificial Horizon
>
> Thanks. I'll take a look at rendering, or perhaps add an "invert" option,
> if I can't improve the logic.
> Does anything outside of the skymap use the artificial horizon?
>
> On Wed, Mar 24, 2021 at 2:39 PM Eric Dejouhanet <eric.dejouhanet at gmail.com>
> wrote:
>
>> 1. For various reasons, your horizon may be rendered "from the outside".
>> That's why you don't want to do a single 360 polygon.
>>
>> 5. Scheduler does not make use of AH. It's been in my pipe for some time,
>> but it's trickier than it seems. The first step would be to have two
>> altitude restrictions, one for setting objects (the current one we have)
>> and one for rising objects.
>>
>> 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/20210324/9c6ad64b/attachment-0001.htm>