This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
chara:instruments [2018/06/27 17:36] 127.0.0.1 external edit |
chara:instruments [2018/11/20 20:54] jones |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Instruments ====== | ====== Instruments ====== | ||
- | \\ | + | |
- | ===== __**INSTRUMENT MANUALS**__ ===== | + | ===== INSTRUMENT MANUALS ===== |
- | \\ PAVO User Manual: Available in [[/ | + | |
- | ===== __OBSERVING LOGS__ | + | \\ |
- | [[/ | + | PAVO User Manual: Available in [[: |
- | ===== __USEFUL | + | |
- | [[/ | + | MIRCX:\\ |
- | ===== __**SOFTWARE SETUP FOR TELESCOPE OPERATORS**__ ===== | + | (A) Instrument user manuals (1) [[https:// |
- | \\ Below we describe the software that needs to be started for each instrument at the beginning of the night. Follow the [[/ | + | (B) [[https:// |
+ | (C) [[: | ||
+ | \\ | ||
+ | [[https:// | ||
+ | \\ | ||
+ | {{: | ||
+ | |||
+ | ===== OBSERVING LOGS ===== | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | [[https:// | ||
+ | |||
+ | ===== USEFUL | ||
+ | |||
+ | [[: | ||
+ | {{: | ||
+ | |||
+ | ===== SOFTWARE SETUP FOR TELESCOPE OPERATORS ===== | ||
+ | |||
+ | \\ | ||
+ | Below we describe the software that needs to be started for each instrument at the beginning of the night. Follow the [[: | ||
===== CLASSIC and CLIMB: ===== | ===== CLASSIC and CLIMB: ===== | ||
- | Open the CLASSIC/ | + | |
+ | Open the CLASSIC/ | ||
+ | \\ | ||
+ | [[: | ||
+ | [[: | ||
===== PAVO: ===== | ===== PAVO: ===== | ||
- | Open the PAVO server and GUI using the menu on zoot. Typically the observer runs the PAVO server from their location. However, if network speed becomes an issue during a remote run, the operator can open the PAVO server on the mountain and the observer can type commands into PAVO by using a "speak pavo" session. The [Status] button on the PAVO GUI will bring up a display of the server.\\ \\ PAVO uses the LDCs. Bring up the LDC GUIs using the menu on zoot (under ESP Controllers). It's a good idea to home the LDCs at the start of the night. To home the LDCs, turn on the power button for the relevant telescope (the button will turn from red to green). Set the velocity to a non-zero number like 50 and click the [VEL] button. Then click the [HOME] button. You will see the position of the LDC go to 0.0. If the position gets stuck at "<>", | + | |
+ | Open the PAVO server and GUI using the menu on zoot. Typically the observer runs the PAVO server from their location. However, if network speed becomes an issue during a remote run, the operator can open the PAVO server on the mountain and the observer can type commands into PAVO by using a "speak pavo" session. The [Status] button on the PAVO GUI will bring up a display of the server.\\ | ||
+ | \\ | ||
+ | PAVO uses the LDCs. Bring up the LDC GUIs using the menu on zoot (under ESP Controllers). It's a good idea to home the LDCs at the start of the night. To home the LDCs, turn on the power button for the relevant telescope (the button will turn from red to green). Set the velocity to a non-zero number like 50 and click the [VEL] button. Then click the [HOME] button. You will see the position of the LDC go to 0.0. If the position gets stuck at "<>", | ||
+ | \\ | ||
+ | If you need to home the LDC glass during the night, then follow this procedure: | ||
* Type " | * Type " | ||
Line 19: | Line 50: | ||
* After the LDC glass homes, then type " | * After the LDC glass homes, then type " | ||
* Click [Ref] on Cosmic Debris to send the LDCs back to the correct positions. | * Click [Ref] on Cosmic Debris to send the LDCs back to the correct positions. | ||
- | \\ If the PAVO server doesn' | + | |
+ | \\ If the PAVO server doesn' | ||
===== MIRC: ===== | ===== MIRC: ===== | ||
- | After the ople server and tiptilt servers are opened and tiptilt comm are established (TT COMMS button on cosmic debris), you can tell the MIRC observer to follow the mirc6T_memo.txt notes on the wolverine desktop to start the MIRC server (astropci), spooler, and GUIs. These are all run from the MIRC computer. Note that the beam order will not be correct on the MIRC gdt_control gui unless TT COMMS is established before that gui is opened.\\ \\ | + | |
+ | After the ople server and tiptilt servers are opened and tiptilt comm are established (TT COMMS button on cosmic debris), you can tell the MIRC observer to follow the mirc6T_memo.txt notes on the wolverine desktop to start the MIRC server (astropci), spooler, and GUIs. These are all run from the MIRC computer. Note that the beam order will not be correct on the MIRC gdt_control gui unless TT COMMS is established before that gui is opened. | ||
===== VEGA: ===== | ===== VEGA: ===== | ||
- | Open all CHARA servers and GUIs as usual. The VEGA team will open their servers and software from the VEGA computer.\\ \\ If VEGA is running with CLIMB, then LDCs will need to be used. Bring up the LDC GUIs using the menu on zoot (under ESP Controllers). It's a good idea to home the LDCs at the start of the night. To home the LDCs, turn on the power button for the relevant telescope (the button will turn from red to green). Set the velocity to a non-zero number like 50 and click the [VEL] button. Then click the [HOME] button. You will see the position of the LDC go to 0.0. If the position gets stuck at "<>", | + | |
+ | Open all CHARA servers and GUIs as usual. The VEGA team will open their servers and software from the VEGA computer. \\ \\ If VEGA is running with CLIMB, then LDCs will need to be used. Bring up the LDC GUIs using the menu on zoot (under ESP Controllers). It's a good idea to home the LDCs at the start of the night. To home the LDCs, turn on the power button for the relevant telescope (the button will turn from red to green). Set the velocity to a non-zero number like 50 and click the [VEL] button. Then click the [HOME] button. You will see the position of the LDC go to 0.0. If the position gets stuck at "<>", | ||
===== FLUOR: ===== | ===== FLUOR: ===== | ||
- | Nic can add instructions here, but it probably consists of opening the JuFlu server and GUI. There was a time when we had to open up a special Cosmic Debris for FLUOR by typing the following command into a terminal window:\\ | + | |
+ | Nic can add instructions here, but it probably consists of opening the JuFlu server and GUI. There was a time when we had to open up a special Cosmic Debris for FLUOR by typing the following command into a terminal window: | ||
* cosmic_fluor -F -o2 (for a secondary program using secondary ople) | * cosmic_fluor -F -o2 (for a secondary program using secondary ople) | ||
- | \\ | + | |
===== ===== | ===== ===== | ||
+ | |||
+ |