User Tools

Site Tools


chara:tunable_beacons

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
chara:tunable_beacons [2022/10/20 16:44]
gail_stargazer
chara:tunable_beacons [2023/02/06 23:24] (current)
charaobs
Line 1: Line 1:
 ====== Tunable Beacons ====== ====== Tunable Beacons ======
  
-<font 14px/Arial,Helvetica,sans-serif;;black;;inherit>Tunable blue laser beacons have been installed on all telescopes</font>E1 <font inherit/inherit;;black;;inherit>blue</font>flux will remain low until the new fiber combiner arrives. +<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>Tunable blue laser beacons have been installed on all telescopes</font> . <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>The S2 blue</font> beacon is currently running on the red channel. So for now use the red buttons on S2 for controlling the bluebeacon.
- +
-<font 14px/Arial,Helvetica,sans-serif;;black;;inherit>The S2 blue</font>  <font inherit/inherit;;black;;inherit>beacon</font>is currently running on the red channel. So for now use the red buttons on S2 for controlling the <font inherit/inherit;;black;;inherit>blue</font><font inherit/inherit;;black;;inherit>beacon</font>.+
  
 <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>You can start the control GUI from a terminal on a CHARA computer by:</font> <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>You can start the control GUI from a terminal on a CHARA computer by:</font>
Line 16: Line 14:
 <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>At a setting of 10, the beacon is just visible on the labao at 100 fps. 13-14 gives better contrast., still without the star. Turning it to 13-17 after locking a star of mag V2.4 worked well to just suppress the starlight while not shining through to the TWFS. A star of mag V1.8 required settings from 20-30 and mag V4 required 13-16. Mag V5.2 was 11-14. I think these are at 40 fps on the labao. Mag V6 used settings of 10-13, about 2 clicks above where the starlight was seen. Mag V7.1 used the same 10-13.</font> <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>At a setting of 10, the beacon is just visible on the labao at 100 fps. 13-14 gives better contrast., still without the star. Turning it to 13-17 after locking a star of mag V2.4 worked well to just suppress the starlight while not shining through to the TWFS. A star of mag V1.8 required settings from 20-30 and mag V4 required 13-16. Mag V5.2 was 11-14. I think these are at 40 fps on the labao. Mag V6 used settings of 10-13, about 2 clicks above where the starlight was seen. Mag V7.1 used the same 10-13.</font>
  
-<font 14px/Arial,Helvetica,sans-serif;;rgb(0, 0, 0);;inherit>Turning the setting down until the starlight is just being seen and then back up by 2-3 seems to work well. Since the labao display has an auto gain, it will not look brighter as you turn the setting up, but will add light to the TWFS which is not taken out by the ZDARK. ​</font>+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>Turning the setting down until the starlight is just being seen and then back up by 2-3 seems to work well. Since the labao display has an auto gain, it will not look brighter as you turn the setting up, but will add light to the TWFS which is not taken out by the ZDARK. ​</font>
  
  
chara/tunable_beacons.1666298645.txt.gz · Last modified: 2022/10/20 16:44 by gail_stargazer