Thank you everybody for your input. Yes using astroberry.local:444/ does work.
I found more in depth discussion on cloudynights here www.cloudynights.com/topic/785514-new-al...oftware-indi-allsky/
Cant wait to try it out.... Bruce

I have just released v4.0 of indi-allsky which includes meteor/line detection for the images.

All in all, the detection works very well. On the very first night of testing, I managed to capture a meteor and the line detection flagged the image. Detection works slightly better with a monochrome camera, but I have been surprised by how accurate the detection works across all of my cameras.

The only weak point in the detection is "clouds". Just like our imaginations can see objects in clouds, the edge detection can be thrown off when clouds are arranged certain ways.

The detection is also very fast, taking a mere 0.1s to analyze a 1920x1080 image on Raspberry Pi hardware.

I have created a timelapse video to show the star and line detection abilities in indi-allsky. Hopefully, this can demystify what is going on in the background.

I added a new option to highlight the detected stars (red circles) and lines detected (green lines) within the detection area. If you look carefully, you can see there are some false positives for both. Defraction/reflection artifacts from the dome can be detected as stars. Same for lines. Also, the edges of clouds can sometimes be detected as lines.



Startrails:


Note: There are some dark areas center left. This my oldest allsky camera (sv305) and a couple of years in the sun have caused some striations to develop in the plastic dome.

I really like indi-allsky, and have been using it for several months now. As a minor issue, does anyone else have problems with the lunar and solar orbs positions? Mine seem to be out by 180 degrees, despite no image flipping. Times and locations are all correct, and I cannot see any way to adjust the positions. It makes no difference to the utility of indi-allsky, but it niggles my OCD! Any ideas how to correct it?
Regards
Tim

Hello Tim, what is your configured latitude and longitude and where do you live? I just want to double check the logic.

Can you upload an image here so I can see what you are seeing?

The orbs are drawn on the image after any flipping is done, so that should not affect anything.

Hi Aaron. Thanks for all your work on indi-allsky.
My Lat and Long are +50.98, -2.67. The current picture is attached. North is top(ish), East is left. Time is UTC+1, Moon should be at Az 72 El -32, Sun at Az 122, El43 according to Ekos. Indi-Allsky shows correct Elevations in status window.
Kind regards.
Tim

I need to add another screenshot in my project regarding the orbs. The orbs do not reflect the altitude or azimuth, but the local hour angle of the sun and the moon. 12o clock on the local hour angle (top center of the image) should be when the sun/moon reaches the meridian in the sky. The notches on the side are the hour angles for the sun when -6 (civil twilight), -12 (nautical twilight), and -18 (astronomical twilight) below the horizon.

Hi Aaron, thank you. Now I understand. I thought that they indicated the solar and lunar azimuths when those bodies are not visible. My mistake. Thanks again for all your work.
Kind regards
Tim

I considered a few different modes for the orbs, but eventually settled on the hour angle.

I suppose I did pick an "earth centric" view rather than observer centric. I can see how Alt/Az could be helpful.

Tell you what, I will take your post as a request for the ability to change the orbs to show Alt/Az.

Thanks Aaron. I think an alt/az approach would be useful, especially when using indi-allsky to monitor sky conditions for observing.
Kind regards
Tim

I just merged support for two additional modes for the orb rendering. You can now choose from:

• Hour Angle
• Azimuth
• Altitude

Let me know how this works.

The Orbs seem to work in Az, thank you. But I now have a permanent SOI rectangle and focus rings on the stars, whatever the focus settings.
Thanks
Tim