Differences

This shows you the differences between two versions of the page.

--- ideas:development_topics [2008/11/07 14:29] – pkubanek
+++ ideas:development_topics [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 10: / Line 10: @@
 The work may be extended so that it would take advantage of the WCS (pixel->world) calibration to provide direct 3D resolved result if observed from more than a single camera.
+====== Transient pipeline ======
+Will be provided by Pi-of-the Sky, expected to be integrated by end of 2008.
 ====== GUI ======
@@ Line 17: / Line 22: @@
 Profile: GTK, PyGTK ideal, XML-RPC, Subversion, GUI design, user documentation
-There is prototype implementation of GUI, however I do not have time to finish it. It is in [[http://www.pygtk.org|PyGTK]], uses [[http://www.xmlrpc.com|XML-RPC]] to communicate with RTS2. Code is at SVN [[http://rts-2.svn.sf.net/viewsvn/rts-2/trunk/pyrts2]], to get it and run it execute:
+For description of XML-RPC interface, please see [[code:xmlrpc|XML-RPC wiki page]]. Also see description of current [[doc:gui|GUI]] there.
-<code bash>
+As astronomers are strange beasts, it **must** be multi-platform (at least Windows + Linux, Mac highly recommended). We do not expect it will be feasible to code all as Web application - standalone application is preferred. The application might integrate various programmes (image display,..) with [[http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/SampDoc|SAMP]]. We expect various team members will pick different areas.
-user@host:~$ svn co https://rts-2.svn.sf.net/svnroot/rts-2/trunk/pyrts2
-user@host:~$ cd pyrts2
-user@host:~/pyrts2$ ./pyrts2.py
-</code>
-You will need python-gtk2 installed:
+What we expect:
-<code bash>
+  * configurable interface to display (using various fancy displays - bars, gauges,..) and change variables, display events, notification and warnings, and display and modify scheduling database.
-user@host:~$ sudo apt-get install python-gtk2
+  * 3D telescope visualisation, with interface to describe various system attached to the telescope and describe its status, failures etc..
-</code>
+  * plotting of history of selected variables (temperature,..), similar to what [[http://finance.google.com|Google]] provides for finance or [[http://meteo.othello.ch|Meteo]] provides for meteo data display
+  * display observations, images related to observations,..
-And you need to have rts2-xmlrpcd running.
 ====== RTS2 Web ======
@@ Line 55: / Line 55: @@
 ====== Advanced scripting ======
-The current scripting model proved too difficult to maintain. Hence we are looking for new scripting part of RTS2. It shall be fully integrated. It should provide language specification, so we can easily extend language with new features.
+[[ideas:Advanced scripting]]
-The language must provides constructs for:
-  * loops (for, while,..)
-  * blocks which execution is based on some external factors (if acqusition is sucessfull, telescope error drop bellow some amount,..)
-  * manipulation devices variables
-  * executing and possibly queuing commands to devices
-  * waiting for system to reach some state (exposure possible,..) with possible timeout
-  * procedures and functions with parameters
-  * functions to perform various system tasks (copy files, call external programs in background,..)
-  * including of "libraries"
-  * calls to generate exceptions, which will be catched by RTS2 and resulted in script premature end
-  * logging calls to log script progress
-  * comments inside scripting language
-The idea is that the language will provide variables manipulation routines (including creating customs variables). The variables can be some "strange" astronomical quantities, e.g. error introduced either in degrees, arcminutes or arcseconds - distinguished by d, ', and " suffix.
-Input of the processor is string stream containing script. Its output is a binary sequence of commands, which will be executed by RTS2. There is an example of definition command to execute exposure:
-<code>
+====== Database improvements ======
-int exposure (camera, length)
-{
-       waitforSystemState(EXPOSURE_POSSIBLE);  // will wait for system to reach state when exposure is possible
-       camera.EXPOSURE = length;               // set camera variable EXPOSURE
-       camera.executer("exposure");            // execute command on camera
-}
-</code>
-and there is a call which include library, and call 10 seconds exposure:
+We need to improve database design. Current summary is given at [[devel:database_structure|there]]. Database was originally developed as a quick hack, and the project grows of the original scope. It is clear that we will need to improve our current design. The work should provide summary of a current state, and should try to draw a new design.
-<code>
-include exposureLibrary;
-exposure (C0, 10)
-</code>