The CHARA Array Wiki

User Tools

Site Tools

Trace:
chara:pavo_user_manual

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:pavo_user_manual [2020/08/18 19:21]
gail_stargazer 		chara:pavo_user_manual [2023/12/03 22:47] (current)
bflores [2 Cooling Down the PAVO Camera]
Line 75: Line 75:
 ===== 2 Cooling Down the PAVO Camera ===== ===== 2 Cooling Down the PAVO Camera =====
  
-The PAVO camera needs to be cooled down at the beginning of the run. Type the following command into the pavo server: > coolon -60\\ +The PAVO camera needs to be cooled down at the beginning of the run. Type the following command into the pavo server: > coolon -50\\ 
-This cools the camera to -60 C. You can read the current temperature from the pavo server. As of 2014, we are doing air cooling (PAVO is no longer hooked up to water cooling). Because of this, the minimum gain setting should be 170 for almost all targets (not 150). If you leave the pavo computer on and the camera plugged-in, then you don’t have to do anything until a PAVO run is over. At the end of the run, type "coolon 0" into the server and it will raise the temperature to 0 Celsius. Once it gets to about 0, it is "safe" to switch anything and everything off without damaging the CCD. +This cools the camera to -50 C. You can read the current temperature from the pavo server. As of 2014, we are doing air cooling (PAVO is no longer hooked up to water cooling). Because of this, the minimum gain setting should be 170 for almost all targets (not 150). If you leave the pavo computer on and the camera plugged-in, then you don’t have to do anything until a PAVO run is over. At the end of the run, type "coolon 0" into the server and it will raise the temperature to 0 Celsius. Once it gets to about 0, it is "safe" to switch anything and everything off without damaging the CCD.
-<code>+
  
 +<code>
 \\  Previous Notes: When PAVO was hooked up to the water cooling, the camera was cooled down to -70 C. [CCD Cool] had to be turned on through the power gui for this to work. The fan is also on, so nothing should break if CCD cool isn’t on; it will just stop at about -55C and not go any lower. The gain numbers in the current mode only apply to this temperature. \\  Previous Notes: When PAVO was hooked up to the water cooling, the camera was cooled down to -70 C. [CCD Cool] had to be turned on through the power gui for this to work. The fan is also on, so nothing should break if CCD cool isn’t on; it will just stop at about -55C and not go any lower. The gain numbers in the current mode only apply to this temperature.
  
Line 86: Line 86:
  
 Next: [[#aligning_pavo_in_the_lab|Aligning PAVO in the Lab]], Previous: [[#cooling_down_the_pavo_camera|Cooling Down the PAVO Camera]], Up: [[#top|Top]] [[#table_of_contents|Contents]] [[#index|Index]] Next: [[#aligning_pavo_in_the_lab|Aligning PAVO in the Lab]], Previous: [[#cooling_down_the_pavo_camera|Cooling Down the PAVO Camera]], Up: [[#top|Top]] [[#table_of_contents|Contents]] [[#index|Index]]
 +
  
 ===== 3 Overview of Alignment Steps ===== ===== 3 Overview of Alignment Steps =====
Line 94: Line 95:
   - Daily alignment of visbeams, dichroics, and M10. The green laser is now bright enough for these steps to be done using the standard CHARA procedures. LDCs should be in place and homed for all telescopes being used by PAVO. It is recommended that the IR beams be aligned to CLIMB on Beams 1-3, in case CLIMB is needed to help search for fringes.   - Daily alignment of visbeams, dichroics, and M10. The green laser is now bright enough for these steps to be done using the standard CHARA procedures. LDCs should be in place and homed for all telescopes being used by PAVO. It is recommended that the IR beams be aligned to CLIMB on Beams 1-3, in case CLIMB is needed to help search for fringes.
   - On-sky alignment of image and pupil planes. This should be done when switching to a new target/calibrator set in a different part of the sky. Details of the on-sky alignment are given in [[#on-sky_alignment|On-sky Alignment]].   - On-sky alignment of image and pupil planes. This should be done when switching to a new target/calibrator set in a different part of the sky. Details of the on-sky alignment are given in [[#on-sky_alignment|On-sky Alignment]].
 +<code>
  
-  Note: The alignment on Beams 1, 2, and 3 are done using VisBeams 1&2 and VisBeams 2&3. All beam pairs should be aligned to the targets on the east-end table (1&2-1, 1&2-2, 2&3-2, 2&3-3).+Note: The alignment on Beams 1, 2, and 3 are done using VisBeams 1&2 and VisBeams 2&3. All beam pairs should be aligned to the targets on the east-end table (1&2-1, 1&2-2, 2&3-2, 2&3-3). 
 + 
 +</code>
  
 ---- ----
Line 121: Line 125:
   * Open the PAVO server and PAVO gui. Check the current temperature from the pavo server. If it is not cooled, then type “coolon -60” into the pavo server to cool the camera.   * Open the PAVO server and PAVO gui. Check the current temperature from the pavo server. If it is not cooled, then type “coolon -60” into the pavo server to cool the camera.
   * Home the PAVO motors by typing "zzero" into the pavo server - only do this if there has been a power outage or if it has been a long time since PAVO was last aligned. You can check the zaber positions on the engineering gui to see if the motors need to be homed ([[#pavo_engineering_gui|PAVO Engineering GUI]]). The zzero command will set the motors to the last recorded positions after homing. Visually check to make sure the PAVO optics are moving during the homing sequence. As of December 2015, please see the trouble shooting note in [[#homing_the_lenslet_stage_motor_1|Homing the lenslet stage (motor 1)]].   * Home the PAVO motors by typing "zzero" into the pavo server - only do this if there has been a power outage or if it has been a long time since PAVO was last aligned. You can check the zaber positions on the engineering gui to see if the motors need to be homed ([[#pavo_engineering_gui|PAVO Engineering GUI]]). The zzero command will set the motors to the last recorded positions after homing. Visually check to make sure the PAVO optics are moving during the homing sequence. As of December 2015, please see the trouble shooting note in [[#homing_the_lenslet_stage_motor_1|Homing the lenslet stage (motor 1)]].
-  * After homing the PAVO motors, check the PAVO Zaber Engineering GUI to make sure the last two stages (B1 Split and B2 Split) go back to their last positions.  The last stage has been getting stuck at 0 and needs to be set manually.  The current position of B1 Split is 62421 and B2 Split is 105025 (as of 2020Aug18).+  * After homing the PAVO motors, check the PAVO Zaber Engineering GUI to make sure the last two stages (B1 Split and B2 Split) go back to their last positions. The last stage has been getting stuck at 0 and needs to be set manually. The current position of B1 Split is 62421 and B2 Split is 105025 (as of 2020Aug18).
   * Put the PAVO beam splitters into the beam path. The mounts are at the edge of the Classic table.   * Put the PAVO beam splitters into the beam path. The mounts are at the edge of the Classic table.
   * Align Visbeams using pico 3 (B1&2-1, B1&2-2, B2&3-2, B2&3-3) using the visbeams target on the East table.   * Align Visbeams using pico 3 (B1&2-1, B1&2-2, B2&3-2, B2&3-3) using the visbeams target on the East table.
Line 314: Line 318:
   * DTIME - damping time   * DTIME - damping time
  
-  Below this panel, provides information on fringe tracking and cart positions:+<code> 
 +Below this panel, provides information on fringe tracking and cart positions: 
 + 
 +</code>
  
   * Left-side panel - Baseline Information   * Left-side panel - Baseline Information
Line 346: Line 353:
 === Figure 5.2 === === Figure 5.2 ===
  
-{{:chara:files:pavo_gui.jpg|pavo_gui}}  The PAVO GUI used to control the instrument. Green indicates that a button is active. In this screenshot, autosave is turned on and the B1, B2, B3 shutters are open. The camera is off; the [GO/STOP] button will turn green when the camera is on. The mask is in (the [MASK OUT] button will turn green when the mask is out.+{{:chara:files:pavo_gui.jpg|pavo_gui}}The PAVO GUI used to control the instrument. Green indicates that a button is active. In this screenshot, autosave is turned on and the B1, B2, B3 shutters are open. The camera is off; the [GO/STOP] button will turn green when the camera is on. The mask is in (the [MASK OUT] button will turn green when the mask is out.
 <code> <code>
  
Line 381: Line 388:
 === Figure 5.3 === === Figure 5.3 ===
  
-{{:chara:files:pavo_maskin.jpg|pavo_maskin}}{{:chara:files:pavo_maskout.jpg|pavo_maskout}}  PAVO camera display when viewing the image plane on-sky. The three spots show the star light from Beam 1, 2, and 3, respectively from top to bottom. The colored boxes mark the position of each mask hole and are placed by clicking the TARGETS button on the PAVO GUI. The panel on the left shows the image plane with the mask in. The panel on the right shows the image plane with the mask out.+{{:chara:files:pavo_maskin.jpg|pavo_maskin}}{{:chara:files:pavo_maskout.jpg|pavo_maskout}}PAVO camera display when viewing the image plane on-sky. The three spots show the star light from Beam 1, 2, and 3, respectively from top to bottom. The colored boxes mark the position of each mask hole and are placed by clicking the TARGETS button on the PAVO GUI. The panel on the left shows the image plane with the mask in. The panel on the right shows the image plane with the mask out.
  
 === Figure 5.4 === === Figure 5.4 ===
  
-{{:chara:files:pavo_lenslet.jpg|pavo_lenslet}}  PAVO camera display when viewing the lenslet on-sky. The pupil is segmented by the lenslet array (appearing as vertical bands). Each lenslet band is dispersed by the prism with wavelength going from left to right in each band. The dark spot in the center is the central obscuration from the telescope.+{{:chara:files:pavo_lenslet.jpg|pavo_lenslet}}PAVO camera display when viewing the lenslet on-sky. The pupil is segmented by the lenslet array (appearing as vertical bands). Each lenslet band is dispersed by the prism with wavelength going from left to right in each band. The dark spot in the center is the central obscuration from the telescope.
  
 === Figure 5.5 === === Figure 5.5 ===
  
-{{:chara:files:pavo_labfringes_beam12_2016may19.jpg|pavo_labfringes_beam12_2016may19}}  {{:chara:files:pavo_labfringes_beam23_2016may19.jpg|pavo_labfringes_beam23_2016may19}}  Lab fringes on PAVO in a narrow bandpass. The two panels show the fringes at different frequencies on Beams 1&2 (left) and Beams 2&3 (right).+{{:chara:files:pavo_labfringes_beam12_2016may19.jpg|pavo_labfringes_beam12_2016may19}}{{:chara:files:pavo_labfringes_beam23_2016may19.jpg|pavo_labfringes_beam23_2016may19}}Lab fringes on PAVO in a narrow bandpass. The two panels show the fringes at different frequencies on Beams 1&2 (left) and Beams 2&3 (right).
  
 === Figure 5.6 === === Figure 5.6 ===
  
-{{:chara:files:pavo_fringes.jpg|pavo_fringes}}  PAVO waterfall display with fringes on Baseline 2.          —- Previous: [[#pavo_gui|PAVO GUI]], Up: [[#description_of_pavo_server_and_gui|Description of PAVO Server and GUI]] [[#table_of_contents|Contents]] [[#index|Index]]+{{:chara:files:pavo_fringes.jpg|pavo_fringes}}PAVO waterfall display with fringes on Baseline 2. —- Previous: [[#pavo_gui|PAVO GUI]], Up: [[#description_of_pavo_server_and_gui|Description of PAVO Server and GUI]] [[#table_of_contents|Contents]] [[#index|Index]]
  
 ==== 5.3 PAVO Engineering GUI ==== ==== 5.3 PAVO Engineering GUI ====
Line 401: Line 408:
 === Figure 5.7 === === Figure 5.7 ===
  
-{{:chara:files:pavo_eng.jpg|pavo_eng}}  PAVO Engineering GUI.+{{:chara:files:pavo_eng.jpg|pavo_eng}}PAVO Engineering GUI.
 <code> <code>
  
Line 416: Line 423:
   * Sync the time on the PAVO computer. Open a terminal window and type "rsh pavo" to log into the pavo computer. Then type "psync" to sync the time on pavo.   * Sync the time on the PAVO computer. Open a terminal window and type "rsh pavo" to log into the pavo computer. Then type "psync" to sync the time on pavo.
   * Run PAVO using primary OPLE and primary Cosmic Debris. Otherwise, there might be problems with the PAVO communications - see [[#using_pavo_with_secondary_ople_and_secondary_cosmic_debris|Using PAVO with Secondary OPLE and Secondary Cosmic Debris]].   * Run PAVO using primary OPLE and primary Cosmic Debris. Otherwise, there might be problems with the PAVO communications - see [[#using_pavo_with_secondary_ople_and_secondary_cosmic_debris|Using PAVO with Secondary OPLE and Secondary Cosmic Debris]].
-  * Open PAVO server from pull-down menu (Servers → PAVO). If this doesn’t work, then try "ssh -X pavo" and type "run_pavo". Note that for now (Oct 2008) it is OK to do this from ROCS/AROC, although there have been times where there seems to be fewer communication issues if the server is run from the mountain.+  * Open PAVO server from pull-down menu (Servers → PAVO). If this doesn’t work, then try "ssh -X pavo" and type "run_pavo". If observing remotely using the Atlanta VNC, connect with the shortcut "pavo" before running "run_pavo".
   * If the server is being run from the mountain during a remote observing run, then the remote observer should open a terminal window and type "speak pavo" to communicate directly with the PAVO server. All commands that are usually entered into the PAVO server can be entered into the speak pavo session. Use CTRL-C to exit out of the speak session, do NOT type exit (that will close down the server).   * If the server is being run from the mountain during a remote observing run, then the remote observer should open a terminal window and type "speak pavo" to communicate directly with the PAVO server. All commands that are usually entered into the PAVO server can be entered into the speak pavo session. Use CTRL-C to exit out of the speak session, do NOT type exit (that will close down the server).
   * Open PAVO GUI from pull-down menu (GTK → PAVO)   * Open PAVO GUI from pull-down menu (GTK → PAVO)
Line 776: Line 783:
 ==== 12.3 Can’t See Starlight on Dectector ==== ==== 12.3 Can’t See Starlight on Dectector ====
  
-Check the PAVO server to make sure the gain is set properly. If it is 0, then re-enter the gain setting using the PAVO gui. If light is still not reaching the detector, then go into the lab, put in the corner cubes, and make sure the laser light is reaching the PAVO table.+Check the PAVO server to make sure the gain is set properly. If it is 0, then re-enter the gain setting using the PAVO gui. 
 + 
 +The red beacon from the AO board can be seen on the PAVO camera.  Check to see if it is visible.  If it is not, the starlight is likely not visible as well. 
 + 
 +Check if the labao shows starlight when the blue beacon is turned low or off on a bright star, Vmag 3 or brighter.  If it is not visible, the dichroic may be misaligned and not sending starlight to the lab.  Confirm the dichroic position with the green laser, especially if it is the first night of a run. 
 + 
 +If light is still not reaching the detector, then go into the lab, put in the corner cubes, and make sure the laser light is reaching the PAVO table. Look for laser light on the splitters, M1 mirrors above the CLIMB table and L1 lenses facing the PAVO table.  Use a white card to see the laser light as it goes into the PAVO table cover slot.
  
 ---- ----
chara/pavo_user_manual.1597792885.txt.gz · Last modified: 2020/08/18 19:21 by gail_stargazer

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki