Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by:
Lock expires at: 2025/09/02 23:37 (15 min)

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

====== ESA Summer of Code in Space 2016 - Idea List ======

[[en:start|MLAB]] is [[http://en.wikipedia.org/wiki/Open_source_hardware|open-source hardware]] and [[http://en.wikipedia.org/wiki/Open_source_software|open-source software]] project which makes effortless design and construction of various measurement devices available for scientific purposes. There already exist several space and astronomical measuring instruments in MLAB project. The [[http://www.astro.cz/|Czech Astronomical Society]] is also involved due to the quality of data captured by our instruments and sets up a data storage server space.astro.cz for data collection from measuring stations.
We want to improve our designs by software development supported by European Space Agency.

===== Main goals =====

* Design algorithms and implement innovative technologies for robotic telescope control system.
  * Create customizable graphical user interface (GUI) for simple and full control.
  * Expand hardware support.
  * Create communication protocol for multi-site and multi-modal observatory cooperation.

Although robotic telescope systems are in development for more than ten years ((http://www.astro.physik.uni-goettingen.de/~hessman/MONET/software.html))((http://www.rotse.net/equipment/docs/rotsedocs.pdf)) The currently most advanced Robotic telescope system [[http://www.rts2.org/|RTS2]] lacks a technology which allows a large scale deployment on multiple observation sites. Therefore reimplementation of existing robotic system software for use in autonomous telescope network is needed.

===== Robozor network =====

Robozor project is network of robotic telescopes which can communicate together and plan observation with best conditions. Robozor network is controlled by [[https://github.com/Robozor-network|AROM software]].

==== AROM software ====

AROM (autonomous robotic observatory manager) is set of programs (nodes) for control instruments of autonomous telescopes as mount, camera, spectroscope, meteo station, roof, switches and etc. All software should be programmed in Python or C++. Knowledge of these programming languages is a necessity for participation in this project.

Today the main control platform is web. Web is the most common interface. AROM control center now offers the ability to control hardware or real-time data visualization. It uses web-sockets messages for communication with AROM system.

Software includes shared object database. Database is ready to support the moving object (comets, asteroids, Planets, meteors, satellites and etc.) and static objects (stars).

AROM software involve [[http://www.ros.org/|ROS]] (Robotics Operation System) which provides useful tool for developing and testing whole system like messaging system between nodes, shared parametric server or sharing data trough network. The structure of AROM nodes (drivers or control programs) is shown in the following figure.

{{ :cs:designs:arom:arom_node_hierarchy.png?600 | AROM structure}}

Main goal of this software is provide comfortable platform to observer which allows telescope control without solving problems with software or hardware.

r===== Tasks for SOCIS participants =====

There are several tasks for SOCIS participants in the summer 2016 you can choose one. There are brief description of problems and description of initial task for qualifying of you for these tasks. If you are interested in the tasks presented here please do not hesitate to contact us at bolidozor@googlegroups.com, we will send you a technical details or we will help you with your deal.

==== Task: Observation scheduler ====
Observation scheduler should be used for optimal distribution of the observation time with depends on weather, site, equipment or other object parameters. The scheduler could run in muli-site observation mode in which the object observation time could be spread over whole network depending on local observation limits of individual nodes.

=== Qualification task ===
The student has to adopt AROM’s simple one-site scheduler which will be choosing target by Altitude. Observer only say “I want observe these objects”. System must reorganise targets in target list with highest altitude at given observation time. Target could be any of above mentioned astronomical and space objects. 
This task will determinate students basic astronomical and programming skills.

=== Project details ===
Advanced scheduler is useful for fully autonomous mode. That will be distribute observing time according to target altitude, weather or time range (e.g. for variable stars observing). Advanced scheduler should be shared between multiple stations which are in stand-by mode and all other condition allows to start robotic observation. Target list is stored in shared database. Every target has there prescribed observation conditions.

=== Expected results ===
Expected result is AROM node which will optimally organizes observation list and it will synchronize target database between AROM systems in Robozor network.

==== Task: Camera drivers ====
Camera is one of the most common instrument in optical astronomy. Therefore AROM needs quality drivers for various cameras.

=== Qualification task ===
The student has to create AROM driver (node) for getting data from meteostation with open-source [[http://www.weewx.com/|WeeWX]] software which could simulate a meteorological station. 
This task will determinate students basic programming skills. Student should have experience with calibration and processing of astronomical images.

=== Project details ===
Driver must be a ROS node. AROM scheduler (or observer trough web AROM control center) sends a standard message and camera driver should execute it. This node will also be responsible for control built-in camera accessories or external accessories with own driver (node).

=== Expected results ===
AROM node which can handle astronomical cameras from various brands. Preferred cameras are DSLRs (Canon, Nikon, Sony), or special astronomy cameras like Moravian instruments, Atik, Andor, SBIG, FLI. The driver also can handle with camera accessories as filter wheel, focuser or field anti-deformers.

==== Task: Video guiding ====
Video guiding is method for increase star tracking accuracy. It usually uses second camera with smaller resolution and shorter expositions.

=== Qualification task ===
The student has to create software for fast recognition stars in FITS fields (images). A third-party open source library could be used, but student must show his own knowledge and code contribution to the existing solution.

=== Project details ===
Video guiding AROM node will request image from camera driver and it will calculates position and delta error (vector of movement from last image) of the stars. For absolute mount calibration or accurate slewing image can be processed with astrometry.net or similar software.

=== Expected results ===
Telescope will accurately track stars and it will choose the best target to tracking. After slewing or after losing of target it measure position with using of astrometry and it will correct differences.

===== Contact =====
For further information we strongly recommend to contact the project coordinator Jan Chroust (jacho@mlab.cz)

Please fill all the letters into the box to prove you're human. Q᠎ M B U I Please keep this field empty:

Edit summary

Note: By editing this page you agree to license your content under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International