×
INDI Library v1.8.1 Released (09 Sep 2019)

Monthly maintenance release INDI v1.8.1

Artificial Horizon hiccups

2 months 3 days ago 2 months 3 days ago by jnowat. Reason: yeesh my grammar
jnowat
Senior Boarder
Senior Boarder
Posts: 45
Karma: 1
More
Topic Author
Artificial Horizon hiccups #44407
I'm in KStars Build: 2019-10-03T08:23:19Z on my desktop right now. On my laptop (build in signature, more frequently used), I have my artifical horizon functioning just fine. I can't save it, however, because I get the wonderful invalid polygon error. I surely must have succeeded in the first place with it by luck, because I can't recreate it in my desktop without getting the invalid error, whether by manually typing out the points or drawing it, or even drawing some random would-be restricted area.

When I try to create another one on my laptop, it doesn't even mind that my new drawing is probably going to fail, it's concerned with the old polygon name (which displays perfectly and doesn't touch the horizon at all, nor does it end with a zero, it only begins with a zero in the altitude).

Further, when I was typing in some of the points, for instance I could type "39" and then hit space- the cursor would not advance for two lines of points and only in altitude (azimuth was fine with spacebar), but on the third it went back to normal behavior. I saw this in the laptop as well, when I first attempted to type them in, then succeeded by drawing.


Now I don't know if the whole "first and last points must be on the horizon" just happens to be required to allow the function to exist, but I'm drawing the thing in the first place because I don't see a horizon where my scope stands, at all, and I'm even further restricted by trees and buildings, so of course that requirement was odd in my perspective from the beginning, but there must be some way by which that requirement can be ousted? I mean, my art.horiz which is actually working doesn't come close to the horizon, so why require two points to be as such? I'm sure it's technical, so I assure you the question is rhetorical.

I didn't find a video on the process, but I think it would be a quick and valuable addition to the tutorial video lineup. The KStars Handbook (pg.48 of who knows what version- could use a version/date on the first page) directions for art.horiz doesn't really reflect the issues I have personally seen with the tool, and so I've listed them here.

Tired and a little cranky (probably much of the moon and cloud effects), but thought it useful to list out the issues I've seen with this tool over the past week. Can I even incorporate it into Ekos? I don't think so, and if not, consider it a point on the wishlist for sure.

The cool thing is, I somehow have it working on the machine I use the most- I don't know how. The lame thing is, I can't do anything else with it or duplicate it or further understand it.

CS
Jacob

Losmandy G11, Gemini II, Custom 10" f/3.8 Newt (Ostahowski Optics),
TV Paracorr-2, 2" Starlight FT, HSM20, Pegasus UPBv2,
ASI1600MM Pro, ASI174MM Mini, ZWO LRGB, EFW, & OAG, StellarMate on my RPi3
KStars Build 2019-09-30T08:25:45Z on Win10 (don't click while loading anything!)
Indi ver....

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

2 months 3 days ago
Spartacus
Senior Boarder
Senior Boarder
Posts: 56
More
Artificial Horizon hiccups #44410
Hi Jacob,
I also have had this exact problem in the past. I have 1 machine where it works well (Odroid running ubuntu) but I have failed to get it to work on Windows PC running KStars. Like you, the invalid polygon error message pops up despite the data points being exactly the same as the one that works. I gave up on it 6 months ago so have not checked again if it has been fixed. It would also be nice to have some way to transfer the point or the model between machines to save the time taken to add each point manually.
Hopefully someone who has cracked this will reply :)

Mike

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

2 months 2 days ago
fenriques
Expert Boarder
Expert Boarder
Posts: 139
More
Artificial Horizon hiccups #44455
I usually follow 3 rules to get rid of the polygon error :
- enter the point manually, preferably every 5/10 deg AZ
- first and last point should be both Az=0 and alt=0
- Always draw the base of the polygon (see attached image).

ferrante
Attachments:
The following user(s) said Thank You Spartacus

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

2 months 1 day ago
Spartacus
Senior Boarder
Senior Boarder
Posts: 56
More
Artificial Horizon hiccups #44492
Hi Ferrante,

I had another go and it all works. I had previously done exactly the process that you use and kept getting the error. Now it works!
Many thanks

Mike

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

2 months 19 hours ago
jerry
Expert Boarder
Expert Boarder
Posts: 130
Karma: 1
More
Artificial Horizon hiccups #44502
Is there a directionality to the polygon? I've created what it indicates is a correct polygon, but I assume that the coloured polygon in the centre of the screen represents the viewable area, but I would have expected it not to be shaded (less readable)

Is this the correct behaviour?


10" Meade SCT on Celestron CGEM DX HC: GEM 5.29.7137 MC: 6.50 6.50,
QHY-5L-II-M 1280x960 3.75um guiding,
Nikon Z7 8256 x 5504, 35.9 x 23.9mm 4.34 um pixel size.
StellarMate OS on RPI4 using kstars-bleeding and Kstars on Odroid-N2.
Attachments:

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

2 months 17 hours ago
Spartacus
Senior Boarder
Senior Boarder
Posts: 56
More
Artificial Horizon hiccups #44504
Hi Jerry,

The shaded area on mine is the non viewable area.

Mike

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

2 months 16 hours ago
jerry
Expert Boarder
Expert Boarder
Posts: 130
Karma: 1
More
Artificial Horizon hiccups #44506
Thanks I figured that must be the case. I'll tweak my coordinates.

10" Meade SCT on Celestron CGEM DX HC: GEM 5.29.7137 MC: 6.50 6.50,
QHY-5L-II-M 1280x960 3.75um guiding,
Nikon Z7 8256 x 5504, 35.9 x 23.9mm 4.34 um pixel size.
StellarMate OS on RPI4 using kstars-bleeding and Kstars on Odroid-N2.

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

Time to create page: 0.667 seconds