Differences

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

--- howto:focus [2009/05/02 20:52] – Added variable description pkubanek
+++ howto:focus [2009/07/12 20:29] – mates
@@ Line 1: / Line 1: @@
 ====== Focuser API ======
-Focuser present to end user various variables. On first look they might look confusing, so there is a small description. You will find it also in //man rts2-focusd//.
+Focuser presents various variables to the end user. They may look confusing on a first look, so here is a small description. You may find it also in //man rts2-focusd//.
   * **FOC_POS** This variable show actual focuser position. If set, it will cause focuser to move to set position. If focuser is moved to position, it shows the actual focuser position.
@@ Line 52: / Line 52: @@
 A working solution is to set up the object detection (with ''detect.advanced'' ) so that it tries to determine the optimum aperture and stores it in the fits image keyword ''DET_APE''. ''detect.advanced'' normally does this, so just make sure that it is used. If you use ''detect.sexonly'' to gain speed, you may restrict detect.advanced only to the focusing target.
-Automatic focusing in RTS2 is solved using a combination of a observation scripts and observation processing. In particular, there is a special target which needs to be executed in order to (re)focus the telescope.
+Automatic focusing in RTS2 is solved using a combination of observation scripts and observation processing. In particular, there is a special target which needs to be executed in order to (re)focus the telescope.
 === Getting the minima ===
@@ Line 121: / Line 121: @@
   * the way of feeding back the computed position is not definitively solved
-  * there was bug related to scheduling of a command to move the focuser, which resulted in incorrect values in the fits headers. (i have no idea if this is already solved or it just happens randomly)
+  * there was a bug related to scheduling of a command to move the focuser, which resulted in incorrect values in the fits headers. (i have no idea if this is already solved or it just happens randomly)
   * we do not care if the astrometry is successfull, but obsproc mechanism by default does and does not provide a way to give us all images without complications. Disabling the astrometry and performing only object detection would improve the speed and overall processing.  -> disable the astrometry in the processing script? -> How many things would this break?