ideas:development_topics
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ideas:development_topics [2008/08/22 17:54] – pkubanek | ideas:development_topics [2009/01/06 19:11] – Link to current GUI pkubanek | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This section depicts what is missing inside RTS2. In states expected human (and other) investments and a brief description of the problem. If somebody will be interested in taking problem and solve it, we will move it to extra page under ideas: namespace and provide a link there. | + | This section depicts what is missing inside RTS2. In states expected human (and other) investments, profile of people doing that and a brief description of the problem. If somebody will be interested in taking |
====== Final integration of meteorite detection code to RTS2 ====== | ====== Final integration of meteorite detection code to RTS2 ====== | ||
Line 5: | Line 5: | ||
Expected costs: 1 student, 1-2 weeks | Expected costs: 1 student, 1-2 weeks | ||
- | I have meteorite detection code for RTS2, however it is not integrated in RTS2. The task of the student | + | Profile: image processing, C++, Subversion |
+ | |||
+ | I have meteorite detection code for RTS2, however it is not integrated in RTS2. The task of the student | ||
+ | |||
+ | The work may be extended so that it would take advantage of the WCS (pixel-> | ||
+ | |||
+ | |||
+ | ====== Transient pipeline ====== | ||
+ | |||
+ | Will be provided by Pi-of-the Sky, expected to be integrated by end of 2008. | ||
====== GUI ====== | ====== GUI ====== | ||
Line 11: | Line 20: | ||
Expected costs: 1-3 students, 2-6 months | Expected costs: 1-3 students, 2-6 months | ||
- | There is prototype implementation | + | Profile: GTK, PyGTK ideal, XML-RPC, Subversion, GUI design, user documentation |
+ | |||
+ | For description | ||
+ | |||
+ | As astronomers are strange beasts, it **must** be multiplatform (at least Windows + Linux, Mac highly recommended). We do not expect | ||
+ | |||
+ | What we expect: | ||
+ | |||
+ | * 3D telescope visualition, with interface to describe various system attached to the telescope and describe its status, failures etc.. | ||
+ | * plotting of history of selected variables (temperature, | ||
+ | * configurable interface | ||
+ | * display observations, | ||
+ | |||
+ | ====== | ||
+ | |||
+ | Expected costs: 1-3 students, 2-6 months | ||
+ | |||
+ | Profile: [[http:// | ||
+ | |||
+ | There is a prototype implementation of RTS2 web, which have some limited functionalities. I would like to see extension of this piece of software which should result in usable | ||
====== Comparsion of various XML-based interfaces for remote telescope ====== | ====== Comparsion of various XML-based interfaces for remote telescope ====== | ||
Expected costs: 1 student, 3 months | Expected costs: 1 student, 3 months | ||
+ | |||
+ | Profile: computer science theory, C++, Subversion | ||
We went through an interesting history none -> SOAP -> XML-RPC regarding external access to RTS2. I just recently read through Atom specification, | We went through an interesting history none -> SOAP -> XML-RPC regarding external access to RTS2. I just recently read through Atom specification, | ||
- | ====== | + | ====== |
+ | |||
+ | [[ideas: | ||
- | Expected costs: 1 student for 6 months | + | ====== Advanced scripting ====== |
- | I am currently working on making ultimate scheduling, which will answers all problems which we have in scheduling. Having somebody else working on some topics, but using different algorithms (I am using genetics algorithms as this is requirement) can be useful and possibly beneficial for both parties. | + | [[ideas: |
+ | ====== Database improvements ====== | ||
+ | We need to improve database design. Current summary is given at [[devel: | ||
ideas/development_topics.txt · Last modified: 2009/01/06 00:00 (external edit)