Welcome, Guest
Username: Password: Remember me
25 Jul 2018
Glad to announce of release of INDI Library v1.7.4 on 2018-07-25. A few drivers were added in this release as we continue to improve & stabilize existing drivers.
Read More...
  • Page:
  • 1

TOPIC: What's next for EKOS?

What's next for EKOS? 4 weeks 19 hours ago #27617

The platform has become very mature over the last year. Attention seems to be diverting towards EKOS Live. I'm wondering what are the next big features that EKOS still needs to support to continue advancing the platform?

From the forums I can tell there's still some development being put towards the scheduler, and refining it. Efforts are still going into better driver support. Are there really any big sets functionality left out at this point? What is the future direction of EKOS?
The following user(s) said Thank You: knro

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

What's next for EKOS? 4 weeks 14 hours ago #27626

From my own experience I am of the opinion that bug fixing and improving ease of use should receive most attention going forward, at least for a while. Even with 35 years experience in astronomy and computers there were quite a few things that prevented me from achieving what I wanted to achieve when I started using Indi/Kstars. Just as an example it took me days to figure out how to make the server side run multiple drivers (without Web Manager). Or, the driver for a Losmandy G-11 is named indi_lx200gemini but in Ekos you have to choose "Losmandy Gemini". Confusing, at least for me. What also caused confusion here is the two layers of configuration. Most settings are done in Indi whereas others are taken care of in Ekos. For a new user there is no way of knowing where to find it. He would expect to find all settings in one place.

I'm not complaining here. I became familiar with the software over time and am very happy with what I am now able to achieve. But if you're looking for ways to improve the software I am of the opinion we should focus more on ease of use and less on new features.
The following user(s) said Thank You: gbeaton

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

Last Edit: by Herrhausen.

What's next for EKOS? 4 weeks 13 hours ago #27629

Thanks for asking. I think the most important thing for me at least is more stability for INDI drivers. Next comes stability of Ekos + KStars, but Ekos is just one client out of many out there. So if drivers are working great, all clients would benefit equally.

For me personally, I'm currently spending a lot of time on EkosLive now. But my long term plans for Ekos is to make it suitable for scientific data acquisition & analysis. So photometry, variable stars, detection of objects...etc.
The following user(s) said Thank You: pcxz

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

What's next for EKOS? 4 weeks 13 hours ago #27630

Herrhausen wrote: From my own experience I am of the opinion that bug fixing and improving ease of use should receive most attention going forward, at least for a while. Even with 35 years experience in astronomy and computers there were quite a few things that prevented me from achieving what I wanted to achieve when I started using Indi/Kstars. Just as an example it took me days to figure out how to make the server side run multiple drivers (without Web Manager). Or, the driver for a Losmandy G-11 is named indi_lx200gemini but in Ekos you have to choose "Losmandy Gemini". Confusing, at least for me. What also caused confusion here is the two layers of configuration. Most settings are done in Indi whereas others are taken care of in Ekos. For a new user there is no way of knowing where to find it. He would expect to find all settings in one place.

I'm not complaining here. I became familiar with the software over time and am very happy with what I am now able to achieve. But if you're looking for ways to improve the software I am of the opinion we should focus more on ease of use and less on new features.


Thanks for the feedback!

1. Why did it take you several days to find how to start multiple drivers on an INDI server? Was it lack of documentation? If it was, can you please make a summary for new users on the procedure and we'll publish it here in the documentation?
2. Losmandy Gemini is the overall type.. we can't have Losmandy G-8, G-11...etc. as it would clutter the already cluttered menu.
3. Of course there would be two layers of configuration. Because you are using two separate software packages. If you used INDI with any other client (e.g. SkyCharts), it would have its own client-side configurations. INDI configurations are related to the actual driver.

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

What's next for EKOS? 1 week 1 day ago #28404

1. Why did it take you several days to find how to start multiple drivers on an INDI server? Was it lack of documentation? If it was, can you please make a summary for new users on the procedure and we'll publish it here in the documentation?


It was lack of documentation. At the time the popup help did not yet work as it does now. I did several search queries in the support forum but didn't find my question answered. I assume it is documented now but will check this later today. [Edit: Hmmm, again I wasn't able to find the info how to start multiple device drivers on the remote machine without using WebManager. If it is already documented, please let me know where! If it's not, I would try to do it. A few sentences should do as it isn't complicated at all.]


2. Losmandy Gemini is the overall type.. we can't have Losmandy G-8, G-11...etc. as it would clutter the already cluttered menu.


The fact that the device and their respective drivers are named differently did cause confusion

3. Of course there would be two layers of configuration. Because you are using two separate software packages. If you used INDI with any other client (e.g. SkyCharts), it would have its own client-side configurations. INDI configurations are related to the actual driver.


I believe that's the programmer's point of view. As a new user of Ekos I don't know what the underlying architecture looks like. Currently the first layer of configuration is in Ekos and sorted application wise while the second layer is found elsewhere (Indi) and is sorted device wise. This is different from what a user is used to and would expect. Imagine we could set *all* settings in Ekos (Ekos simply "forwarding" the Indi-related settings to Indi). The more important/prominent settings could reside in their respective application tabs (guiding, capturing, solving, etc.) while the less important ones would only appear in the same tab once an "ALL setttings" button is pressed much like it is done in VLC, for instance. Indi would remain unchanged and could continue to serve as the foundation for a whole suite of clients while Ekos users would find all settings in the "most logic" place. "Exposure time" as well as "Gain" in the capture tab. That's where I need it (and as a new user would expect it). Nobody would have to know the former is a true "Ekos settting" while the latter is an Indi based one.

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

Last Edit: by Herrhausen.

What's next for EKOS? 1 week 1 day ago #28406

Herrhausen wrote:

I believe that's the programmer's point of view. As a new user of Ekos I don't know what the underlying architecture looks like. Currently the first layer of configuration is in Ekos and sorted application wise while the second layer is found elsewhere (Indi) and is sorted device wise. This is different from what a user is used to and would expect. Imagine we could set *all* settings in Ekos (Ekos simply "forwarding" the Indi-related settings to Indi). The more important/prominent settings could reside in their respective application tabs (guiding, capturing, solving, etc.) while the less important ones would only appear in the same tab once an "ALL setttings" button is pressed much like it is done in VLC, for instance. Indi would remain unchanged and could continue to serve as the foundation for a whole suite of clients while Ekos users would find all settings in the "most logic" place. "Exposure time" as well as "Gain" in the capture tab. That's where I need it (and as a new user would expect it). Nobody would have to know the former is a true "Ekos settting" while the latter is an Indi based one.


This was my sentiment exactly when first using the application. There are core features (even in other Indi imaging apps) that need to be available on certain tabs. Gain and Offset are two that should be part of the capture tab. AstroImager includes these functions within it's main interface for capturing, not solely in the Indi control panel. Herrhausen is correct, that from a programmer point of view, this makes sense, but from an end user perspective it requires a learning curve since it's not the "norm". Otherwise I love what it offers.

The following user(s) said Thank You: Herrhausen, TallFurryMan

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

  • Page:
  • 1
Time to create page: 0.129 seconds

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica