User Tools

Site Tools


obs:123

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
obs:123 [2009/02/11 21:51] matesobs:123 [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
 +
 +
 ====== 1.23m telescope at Calar Alto ====== ====== 1.23m telescope at Calar Alto ======
  
-on 11. February 2009 we did our first visit to 1.23 at CAHA. Thanks to the great support of Ulli Thiele we got the basic info which is summarized further. +On 11. February 2009 we did our first visit to 1.23 at CAHA. Thanks to the great support of Ulli Thiele we got the basic info which is summarized further. 
  
 ===== General notes ===== ===== General notes =====
Line 10: Line 12:
  
 Good news is that the telescope is not willing to self destroy if incorrectly commanded. The low limit of pointing is at altitude of 10deg.  Good news is that the telescope is not willing to self destroy if incorrectly commanded. The low limit of pointing is at altitude of 10deg. 
 +
 +The pointing accuracy of the telescope is of the order of 30" and is expected to improve. 
  
 ==== Where to install the RTS2 ==== ==== Where to install the RTS2 ====
  
-The pointing accuracy of the telescope is of the order of 30" and is expected to improve. +{{ :obs:md123-ota.jpg?200|The 1.23m telescope of CAHA}}
  
 We discussed the possibility of installing our stuff on Solaris - it seems this would be the cleanest solution, This Solaris has a C and C++ compiler, but it may be painful to get all the libraries we need to use to run there. The extreme example case being the PSQL database. The obtained images are physically on this computer. We discussed the possibility of installing our stuff on Solaris - it seems this would be the cleanest solution, This Solaris has a C and C++ compiler, but it may be painful to get all the libraries we need to use to run there. The extreme example case being the PSQL database. The obtained images are physically on this computer.
Line 20: Line 24:
  
 This is, however, not a concern for the case of early testing. This is, however, not a concern for the case of early testing.
 +
 +//Update 20.iii.2009:// 
 +
 +We are definitively trying to get RTS2 working on Solaris ''ultra2.caha.es''. I managed to compile astrometry after some minor struggle with it. So here we go:
 +
 +  * The astrometric registration script is ''/disk-a/obs12/jelinek/ast123''. It contains no dark/flat correction as we still need to make clear how (and if) we are going to play with those things.
 +  * ''rtopera2'', the BOOTES astrometric package is in ''/disk-a/obs12/jelinek/rtopera2'', no binary installation has been performed (programs must be called from within there.
 +  * ''libnova'' is there, in ''/disk-a/obs12/kubanek/libnova-0.12.3/'', it does not support Lunar computations yet, for there were some problems compiling the source.
 +
 +The compilation problems against linux machines were the following:
 +  * ''asprintf()'' does not exist: generally replaced with ''malloc(1024);sprintf(...''
 +  * ''sinl()''. ''cosl()'' and similar are not present on Solaris - macros made
 +  * ''round()'' call does not exist - enabled a windows macro.
 +  * ''getopt_long()'' i did not find, header file ''#include <getopt.h>'' does not exist. ''getopt()'' may be used instead, losing the long options, however.
 +  * to get support for socket & hostname lookup in programs, one must link against ''-lsocket -lnsl''
  
 ==== Focusing and filters ==== ==== Focusing and filters ====
  
-There is a built-in focus/temperature self-correction to prevent frequent focusing during the operation. The focal offsets of various filters are not known and it is known that they are not treated within the existing solution. They are very likely to be small for the existing filter set, but may be of a concern if a custom filter is inserted. +<del>There is a built-in focus/temperature self-correction to prevent frequent focusing during the operation.</del> The focal offsets of various filters are not known and it is known that they are not treated within the existing solution. They are very likely to be small for the existing filter set, but may be of a concern if a custom filter is inserted. 
  
 There is a basic set of Bessel filters. Custom filters of 50x50mm may be inserted upon request. There is a basic set of Bessel filters. Custom filters of 50x50mm may be inserted upon request.
 +
 +We tested the focusing procedure, it's on ultra2:~/jelinek/focscr123, it works, produces images with columns of stars with different focuses. We have been told that within CAHA there is a program to tell the best focus out of such an image.
 +
 +When running this script we get a ''Warning: interrupt in select function'' at the graphical screen. Weird.
  
 ==== Presentation ==== ==== Presentation ====
 +
 +{{ :obs:md123-cam.jpg?200|The 2kx2k CCD camera}}
  
 The operation of RTS2 may, at present, appear chaotic to the responsible CAHA staff, especially in case of GRB alerts. We believe that care should be taken to inform people around about the actions the telescope is performing in a simple and accessible way. The operation of RTS2 may, at present, appear chaotic to the responsible CAHA staff, especially in case of GRB alerts. We believe that care should be taken to inform people around about the actions the telescope is performing in a simple and accessible way.
  
-==== EPIX database ====+==== EPICS database ====
  
 CAHA maintains a database of all available information (meteo/ccd info/telescope info/etc.) Practically anything can be taken there. Most importantly the imaging CCD properties and conditions, which cannot be taken with any //info// command on the command line. CAHA maintains a database of all available information (meteo/ccd info/telescope info/etc.) Practically anything can be taken there. Most importantly the imaging CCD properties and conditions, which cannot be taken with any //info// command on the command line.
 +
 +=== Update:  ===
 +
 +This is still a piece of magic for us. However, seemingly this may be the key to get a real grip to the telescope with RTS2. The calls provided to us for managing the CCD camera are in fact actually EPICS wrappers. 
  
 ===== Telescope control model ===== ===== Telescope control model =====
 +
 +{{ :obs:md123-dome.jpg?200|Tepescopes dome at Calar Alto}}
  
 This section contains the control model rewritten from the sheet Ulli Thiele gave us during our first visit to CAHA. Plus some notes regarding various points which were not in the original text. This section contains the control model rewritten from the sheet Ulli Thiele gave us during our first visit to CAHA. Plus some notes regarding various points which were not in the original text.
Line 41: Line 72:
 ==== Telescope ==== ==== Telescope ====
  
-These are commands to the mount and focuser. They are generally blocking commands which end when the requested action is finished. They return a single numeric value on a line to determine the exit status. (//We are missing examples of the output of each command at this moment.// The dome is entirely integrated with the telescope, there is no need to take care of it.+The telescope is controlled with the computer tecs12. To get the graphical interface go for   
 + 
 +''ssh tecs@tecs12'' 
 + 
 +''setenv DISPLAY ultra2:0.0'' //or another if the DISPLAY was created by ssh// 
 + 
 +''start''  //comes the famous window of tecs// 
 + 
 +there are 2 actions:  
 +  * ''start_tcs'' to restart the telescope control, normally not needed, but sometimes has to be tried more than once. If used, wait until the logging falling into the terminal ceases and then the other command may be run. 
 +  * ''start_gui'': starts the GUI.  
 + 
 +In GUI: 
 +  - Make sure the REMOTE is in GREEN, if it is red, it may be really not remote or you may need to ''start_tcs'' of the previous step 
 +  - Start the hydraulics with the button ''hydraulics'', it may take up to one minute and it may fail and need another try. 
 +  - Start the drives with ''drives'', this is normally short amd makes no problems. 
 +  - Manage the dome with the pull-down ''dome'', ''auto'' means to follow the telescope. 
 + 
 +=== scripting commands === 
 + 
 +The following scripting commands are executed at ''ultra2''
 + 
 +From what I have seen they are all scripts which can be studied (and not really used literally). The level of support of programs based on what has been found inside is, however, likely to be different than if we use them as they are. On the other hand, connecting rts2 to epics would bring a serious simplification. 
 + 
 +They are generally blocking commands which end when the requested action is finished. They return a single numeric value on a line to determine the exit status. (//We are missing examples of the output of each command at this moment.// The dome is entirely integrated with the telescope, there is no need to take care of it.
  
 As I (mates) understood, this set of commands, although old as the others, has been recently revisited by Ulli Thiele when the telescope has been repaired and could, theoretically, be retouched if there are some issues. But we should not expect Ulli or anybody else do much effort here.  As I (mates) understood, this set of commands, although old as the others, has been recently revisited by Ulli Thiele when the telescope has been repaired and could, theoretically, be retouched if there are some issues. But we should not expect Ulli or anybody else do much effort here. 
Line 49: Line 104:
 ''t_offset //d_RA d_DEC//'' sends the telescope the reqest for pointing offset. It is in units of 0.1arcsec. (//note: is this is an image offset of a pointing offset? To move the given amount of pixels, should we or shouldn't we multiply by cos(\delta)?//) ''t_offset //d_RA d_DEC//'' sends the telescope the reqest for pointing offset. It is in units of 0.1arcsec. (//note: is this is an image offset of a pointing offset? To move the given amount of pixels, should we or shouldn't we multiply by cos(\delta)?//)
  
-''t_afocus //focus_absolute value//'' (mm)+''t_afocus //focus_absolute value//'' (mm) //tried, works//
  
-''t_dfocus //focus_differential_value//'' (mm)+''t_dfocus //focus_differential_value//'' (mm) //seem that it does not work//
  
-''t_request'' is a query command - it returns alpha,delta,HA,AM,ST,UT,focus,casspos.+''t_request'' is a query command - it returns alpha,delta,HA,AM,ST,UT,focus,casspos. //tried, works//
  
 ==== CCD Camera ==== ==== CCD Camera ====
 +
 +{{ :obs:md123-sketch.jpg?200|An old sketch of the telescope}}
  
 ''camera_chip1_hbin //h_binning_factor//'' ''camera_chip1_hbin //h_binning_factor//''
Line 90: Line 147:
  
 ==== Filter wheel ==== ==== Filter wheel ====
 +
 +{{ :obs:md123-montage.jpg?200|Old image of the telescope being manufactured}}
  
 Filter wheel commands are not known to us at this moment. :!: Filter wheel commands are not known to us at this moment. :!:
obs/123.1234385516.txt.gz · Last modified: 2009/02/11 00:00 (external edit)