![]() ![]() The client can configure it, disconnect and keep it running, doing its job and connect later to monitor the status or to take the results. Such an agent is independent of the connection to the client. We use term INDIGO agent for this code, acting on the server side and controlling the local devices on behalf of the client. The thin client running in a browser needs a much smarter backend than INDIGO server itself, it needs a server side application logic. The most important driver for the change was implementation of webGUI on INDIGO server. You can just use it.Īlthough INDIGO was always well prepared for a distributed computing, for many situations the traditional client/server is not the best approach. Each application contains embedded INDIGO Server together will all necessary drivers. If you don't want to, you don't need to care about INDIGO complexity and its distributed nature. INDIGO uses the same astronomical hardware abstraction as INDI, but removes some of its design limitations, dramatically improves its performance in some typical scenarios and overcomes license restrictions to allow both non-commercial and commercial use. You can consider it as a next generation of INDI, based on layered architecture and software bus. INDIGO is a system of standards and frameworks for multiplatform and distributed astronomy software development. The standalone versions are intended for advanced use and are not necessary in the most cases. Please note, that every core application contains an embedded server, control panel and script editor. Astrometry, the macOS port of substantial part of project.FITS Preview, the fast previewer for FITS, XISF and INDIGO RAW formats and. ![]() INDIGO Dashboard, the highly configurable dashboard for low level server control,.INDIGO Script Editor, the standalone INDIGO script editor,.INDIGO Control Panel, the standalone control panel,.INDIGO Server, the standalone server for building distributed systems,.INDIGO A1, all in one application containing AstroImager, AstroGuider and AstroTelescope in a single bundle with a single embeded server.AstroGuider, the application for controlling the guider camera and guider port of the mount and the front end for "Guider Agent" and.AstroTelescope, the application for controlling the dome and the mount and the front end for "Mount Agent",.AstroDSLR, a very similar application, but intended specifically for tethering DSLRs and another front end for "Imager Agent",.AstroImager, the application for controlling the main camera and the associated filter wheels, focusers and the front end for "Imager Agent",.There are five core applications and a couple of utility applications in our suite. The disadvantage is that you need to understand how the applications work to configure them to talk to each other properly. The major advantage is that you can select just tools you really need and use them only when you really need. This approach has some advantages and some drawbacks. Unlike the other similar systems, our suite is not a single monolithic application, we use standalone loosely coupled applications instead. We left the traditional client server approach and switched to multi-tier agent based architecture allowing even higher performance and reliability.Ĭore and utility applications of astrophotography suite In the latest generation we made so far the most radical change. ![]() Later we focused on the performance and reliability and transferred the whole development to INDIGO framework. AstroDSLR Getting started with the INDIGO agents based backyard astrophotography application suiteĪbout eight years ago we started to develop a software with the idea to make Apple macOS and iOS the first class platforms for backyard astrophotography.Īt the beginning, the most important task was to add as many hardware drivers as possible. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |