6 replies to this topic

[gordtulloch]

Hi there:

 

I've been working on a project for a while and would like to bounce it off the community to see what functions people might want in an observatory management software package. This would be an open-source package (likely with a supported "Pro" version to make me filthy rich during my retirement lol) that would run in Linux environments and operate on top of a KStars/EKOS/INDI ecosystem. No Windows/ASCOM version is possible or contemplated - go buy one. 

 

 

Features - Initial release scope is as follows:

• Web browser based user interface (Django) augmented with Python scripts
• Multinode support for seperate telescope and observatory computers
• Support for multiple workload types, all from the same code base
• Support for automated science and astrophotography imaging using KStars/EKOS on Linux
• Automatic collection of data into data repositories including FITS file metadata
• Automated cloud detection from any allsky camera that can produce a current image on disk
• Support for rain detectors to automatically park the telescope and close the dome/roof of the observatory
• Support for weather stations to determine if the weather is suitable for imaging operations
• Support for Smoke and Aurora forecasts to assist in determining whether imaging operations can proceed
• Automated calibration, stacking, and processing of images and generation of thumbnails or data summaries

So the workflow would be to select targets and download their info via Simbad (or upload a list eventually) - this is the "stuff I want to observe list":

 

 

The targets would have some basic info, plus a sized image to assist in framing and selection of an instrument. Rise set and so on would be included in a graph (this still needs some work):

 

 

 

(continued)

Edited by gordtulloch, 08 November 2024 - 05:04 PM.

[gordtulloch]

When you want to queue up a target for observation you can add it to the "Observe this when possible" list and specify what the equipment config should be (so observations are only scheduled when the required equipment is set up in the current config) - in my case I have two telescopes on the same mount so that needs to be accommodated:

 

 

This would result in the object being added to a schedule, which would be uploaded to an EKOS instance that runs the telescope. I already have Python scripts, one for the observatory computer that detects when the roof can roll back (including AI cloud detection, smoke forecasts, aurora forcecasts, rain detection etc.) and unparks the scope, and one that runs on the scope computer that detects when the scope is unparked and runs KStars/EKOS via Dbus to execute the schedule. This might be an iterative process with the script parking the scope, closing the roof, opening, unparking etc. all night. Don't care, I'm sleeping!

 

Once the data has been collected it's sucked into the repository, renamed appropriately and put in a directory structure that seperates calibration images and lights, seperates different telescopes, imagers, filters, etc etc. Corrections to the FITS header are done at the same time, for example WCS entries are set properly. Highlights of the FITS header is copied to a database so there's a master index of whats been done that can be referred back to the observation request. Every morning an email is sent to the operator with a list of what data was collected along with thumbnails with links to calibrated and stacked images of that data, or light curve info, or whatever is appropriate for a particular target.

 

 

(Continued)

Edited by gordtulloch, 08 November 2024 - 05:02 PM.

[gordtulloch]

Calibration is done automatically with light image subs sorted into sequences so they can be matched with calibration sequences. Master flats, darks, and bias images are created and recorded for the sequence. You can download an entire sequence including calibration images and masters from the repository as a ZIP file when you want to load everything up in your processing software of choice (structure will be in SIRIL friendly format). You can browse through the repository and do preliminary culling of images to get them out of the repo before you download the sequence for processing.

 

 

The targets are tagged with what type of processing they need, so eventually in addition to calibrating the image and doing a sample stack so you can see what the image looks like so far, I would also like to do photometry on images so I can automate the process of generating variable star and exoplanet data.

 

For an instance thats running on the observatory computer I'm setting up plugins so I can run the various power bars and stuff from the same interface, thats whats in the "Operations" tab. 

 

So thats kind of what I'm working on. If you could add your wishlist, what would it be?

Edited by gordtulloch, 08 November 2024 - 05:08 PM.

[TheStarsabove]

Wow, I didn’t know you were working on this!!! This looks so much easier than using Ekos and a bunch of other software!!! I would certainly like to try this out once I get my observatory up and running! How much would the Pro version be, do you think?

 

BTW, I love the  idea of the smoke/aurora/cloud detectors options as well as the automatic stacking/calibration of the images!!!

 

 

Edit: Just refreshed the page. I would add: Is it possible to automatically transfer to the home computer (like my MacBook Air)? Also, you might want to add a moon-phase/illumination calendar, as well as a moon altitude graph.

Edited by TheStarsabove, 08 November 2024 - 04:53 PM.

[gordtulloch]

Wow, I didn’t know you were working on this!!! This looks so much easier than using Ekos and a bunch of other software!!! I would certainly like to try this out once I get my observatory up and running! How much would the Pro version be, do you think?

 

BTW, I love the  idea of the smoke/aurora/cloud detectors options as well as the automatic stacking/calibration of the images!!!

 

 

Edit: Just refreshed the page. I would add: Is it possible to automatically transfer to the home computer (like my MacBook Air)? Also, you might want to add a moon-phase/illumination calendar, as well as a moon altitude graph.

The pre-requisite, of course, is that KStars and EKOS are 100% working in a completely automated way or just dumping schedules to a non-working system isn't getting you too far!

 

I imagine the Pro version would be cheap, as in $100. I was thinking a similar model to Stellarmate with appliance based turnkey observatory systems, or the software seperate to roll your own. Seems a shame to dump all this work into my dinky little micro-observatory and not create something other people can buy if they lack the tech skills to implement it themselves. I was also thinking of pre-fab micro-observatories too as a retirement business, since I'm looking for something to do in a few years.

 

As for image transfer I was thinking of automatically transmitting repo updates to a Master computer (in my case my workstation in my home office where I do my image processing) so it would probably be doable to install the Master instance of the software on your Mac and the repo updates would be uploaded to your computer as they happen. Similarly I was thinking about website versions where stacked images could be auto-uploaded to my website so as to have a "now imaging" display plus a repository of stacked images as an image library for public consumption, much like the indi-allsky or TJ sites for allsky cameras.

 

The physical files are stored in the file system with intelligent names so things are easy to find or you could just ask for the entire sequence to be downloaded for you which would match calibration frames to lights and dump everything in a ZIP file to transmit to you. I guess that means supporting Mac and Windows for a Master node but thats not too bad, Django/Python works anywhere.

 

I can add the moon to the graph on the target screen I think, it needs more work anyways. Thanks!

Edited by gordtulloch, 08 November 2024 - 05:44 PM.

[TheStarsabove]

 

I imagine the Pro version would be cheap, as in $100. I was thinking a similar model to Stellarmate with appliance based turnkey observatory systems, or the software seperate to roll your own. Seems a shame to dump all this work into my dinky little micro-observatory and not create something other people can buy if they lack the tech skills to implement it themselves. I was also thinking of pre-fab micro-observatories too as a retirement business, since I'm looking for something to do in a few years.

 

As for image transfer I was thinking of automatically transmitting repo updates to a Master computer (in my case my workstation in my home office where I do my image processing) so it would probably be doable to install the Master instance of the software on your Mac and the repo updates would be uploaded to your computer as they happen. Similarly I was thinking about website versions where stacked images could be auto-uploaded to my website so as to have a "now imaging" display plus a repository of stacked images as an image library for public consumption, much like the indi-allsky or TJ sites for allsky cameras.

 

The physical files are stored in the file system with intelligent names so things are easy to find or you could just ask for the entire sequence to be downloaded for you which would match calibration frames to lights and dump everything in a ZIP file to transmit to you. I guess that means supporting Mac and Windows for a Master node but thats not too bad, Django/Python works anywhere.

 

I can add the moon to the graph on the target screen I think, it needs more work anyways. Thanks!

 

Well, I think that it is really cool that you posted it for public use, even if you make money off of it . I like the idea of selling pre-configured devices, like StellarMate, as an option. As for me, I would get the software since I have the RPI5. 
 

I had another thought: So, Ekos Live now has the option where you can rent-out your observatory when you aren’t using it. I think that a lot of people will be using it, so is there a way to implement this software into Ekos Live? I don’t know if you would need to talk to the developers or not, so maybe my idea is a little crazy.

Edited by TheStarsabove, 08 November 2024 - 06:18 PM.

[gordtulloch]

While I don't think I can get an XML file from Obsy into the Ekos Live data stream certainly when this is a completed project (loooong way away) I'll be talking to Jasem about possible partnerships since he's already got the supply chain in place. It wouldn't take much to alter a Stellarmate appliance to include some relays for opening closing the roof and some switches to detect status for a turnkey observatory controller...