Differences

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

--- chara:archived_procedures [2020/02/04 18:23]
charaobs
+++ chara:archived_procedures [2025/06/13 17:46] (current)
gail_stargazer
@@ Line 4: / Line 4: @@
 {{:chara:files:s2_new_finder_camera-r1.docx|New S2 Finder Instructions}}  command line instructions for the first finder camera installation.
+===== Bootlaunch for servers =====
+Here are the available bootlaunch scripts as of June 2017:\\
+\\
+gps computer:
+  * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2.
+  * bootlaunch_zaber – Starts the ZABER_2 server.
+ \\ telescope bunker computers are now using bootlaunch_master to start each of the servers listed below.
+  * bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from.
+  * bootlaunch_rpc – Starts the RPC_E1, RPC_E2, RPC_S1, RPC_S2, RPC_W1, or RPC_W2 server, depending on the machine it's launched from.
+  * bootlaunch_weather – Starts the E1_WEATHER, E2_WEATHER, S1_WEATHER, S2_WEATHER, W1_WEATHER, or W2_WEATHER server, depending on the machine it's launched from.
+  * bootlaunch_lower – Starts the E1_Lower, E2_Lower, S1_Lower, S2_Lower, W1_Lower, or W2_Lower cylinder server, depending on the machine it's launched from.
+  * bootlaunch_upper – Starts the E1_Upper, E2_Upper, S1_Upper, S2_Upper, W1_Upper, or W2_Upper server, depending on the machine it's launched from.
+===== Manually restarting the dome server =====
+To manually start the dome server:
+. Make sure the power to the drives is OFF.
+. Login to the relevant computer as observe. For example, type "s1" to log on to S1.
+. Work out the process ID number (PID), either with the command
+(s1:1001) tsockman get dome_S1 \\ Name : dome_S1 \\ Machine : s1.chara-array.org \\ PID : 29953 \\ Commands : -1 \\ Data : -1 \\ Message : 4002 \\ Restart : /usr/local/bin/dome_server -A33.7441 S1 \\  \\ or with \\ (s1:1003) ps aux | grep dome \\ theo 4473 0.0 0.0 61188 748 pts/3 S+ 10:45 0:00 grep dome \\ observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 /usr/local/bin/dome_server -A33.7441 S \\  \\ It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. \\  \\ So in this case the PID is 29953. \\  \\ 4. Try and stop the server gracefully: kill -2 29953
+. You should then check that the server has indeed stopped: \\  \\ [s1:600] tsockman get dome_S1 \\ Name : dome_S1 \\ Machine : s1.chara-array.org \\ PID : 15635 \\ Commands : -1 \\ Data : -1 \\ Message : 2008 \\ Restart : /usr/local/bin/dome_server -A41.0166 S1 \\  \\ If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1
+. Restart the dome server by copying the command at the end of the /etc/rc.local file:
+[s1:602] more /etc/rc.local \\ <<< Press space bar or enter to scroll through file>>> \\  \\ #Run the dome server \\  \\ /usr/local/bin/tsockman remove dome_S1 \\ /usr/local/bin/dome_server -A41.0166 S1 & \\  \\ (Note: the part of the command that saves information to /var/log/dome_S1.log has been removed.)
+. Turn the power to the drives back on.
+. Hit REOPEN and ENABLE on the domegtk, and type "otcs" in the telescope server.
+===== Tiptilt Server: =====
+[[:chara:old_lab_tiptilt_server|Instructions for old lab tiptilt server]] (these sections apply to the old lab tiptilt system retired in April 2021).
+From the Observing Procedures page:
+(This section is obsolete with the retiring of the old lab tiptilt) \\ Establish connection between tiptilt and the telescopes. On the Control Tab on Cosmic Debris, click on [TIPTILT COMM]. Click [START JOB QUEUE] on CD to continue the Tiptilt Communication sequence. After several seconds, the telescope servers will indicate that the Socket (SOC) connection is established and turn on the tiptilt rate display. Cosmic Debris will usually display a lower rate, such as 42Hz, to indicate tiptilt is running. The servers will display 158Hz to show a proper functioning of the tiptilt system. If the connection is not established the first time, try again until CD shows rates for each telescope used. If a telescope server will not display a TT signal rate, you may need to shut it down and restart it. Once the telescope WFS's are used for tiptilt, these steps for the lab tiptilt will not be used. \\ Finish setting up tiptilt GUIs. Click re-open on the Tiptilt GUI. This will update the TT labels on the TT viewing screens from B1,B2,etc to the telescope names. Click on the [SERVO CONTROL] tab on the tiptilt GUIto bring up a second window and move to screen 5 with the telescope guis. The Servo Control GUIallows you to turn ON the servo for the TT loop and make biases for individual beams (DBIAS and ZBIAS)
+The tiptilt server controls the CCD based tiptilt detection system. \\  \\ Before you start the tiptilt server, you must ensure that the power to the cooling system and the CCD iteslf is on. It is extremely important that the cooler be running before you turn on the CCD and is only turned off if you are sure the CCD is NOT running. You can start the server from the X windows menu or with the command xtiptilt. \\  \\ Note that there are background counts and read noise to deal with. Whenever you change the frame rate, please ensure that the bias frame is OK. The server will attempt to load an old bias frame that should work, but if things are not working, try making a new bias frame by ensuring that the detector is in the dark and typing "mkbias" into the tiptilt server. \\  \\ In the tiptilt GUI windows, the white dots represent the starlight while the green dots represent the motion applied to telescope's secondary mirror to keep the starlight centered. When tiptilt is locked the white dots will be brought to the center of the tiptilt window. The green dots should be mostly centered also. W2 and E2 telescopes have a small oscillation that show as back and forth plots of the green dots.
+==== Tiptilt server complains about the CCD ====
+Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, which should return with no errors. Try this command a few times, but if it still fails, there is a more serious problem. Turn off the CCD and reboot the tiptilt computer. If it still fails, I am afraid you are in more serious trouble. \\  \\ Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command "testclock" on a tiptilt command line. If this says the clock is working do not reboot the machine. \\  \\ Also note that cycling the power on the CCD can cause harm so be sure you need to do it before trying it. Also, it is important to wait for at least 20 seconds after turning off the power before turning it on again.
+==== Tiptilt doesn't seem to be talking to the telescopes ====
+Sometimes the telescope server will not show that TT is running. It will show 0Hz for a signal rate for TT. Running TIPTILT COMM will not get it started while other scopes do show it starting. Close and restart any telescope servers that won't connect after two tries of TIPTILT COMM. \\ Note: There is more info in the software manual on this topic, but I wasn't sure if it was still relevant.
+==== Tiptilt server says the clock isn't running ====
+First check whether the clock itself is running and the other machines receive the clock signal. Look at the clock cards at the back of other computers in the rack. The clock cards have three LEDs, one yellow and two greens. If the computer is receiving the clock signal properly all three LEDs should blink, but at a different rate. If the LEDs on all the clock cards are solid then reboot the GPS computer. When the GPS computer is down, it is best to cycle the power also on the box right above the GPS computer. \\  \\ If the clock appears to be working properly on other machines and not on the tiptilt now it is time to reboot tiptilt. \\  \\ [There is a bug in the real time part of the CCD code. It is caused by the clock in the tiptilt system either not running at all or having been set to a time very different from the last time the CCD ran.] \\  \\ For the time being the only solution is to reboot tiptilt, but do so from the lab. Power OFF the CCD, then reboot the tiptilt machine and go into the BIOS. Make sure that interrupt 11 has been set to ISA legacy, save the BIOS and reboot. When the clock card LEDs in the tiptilt machine indicate proper clock signal, turn the CCD back on and start the tiptilt server. \\  \\ Also, sometimes Serial Port 3 grabs IRQ 11 which stops the clock from running. Since there is no serial port 2 it's safe to disable this in the BIOS. This problem normally comes up when there has been a power outage. \\  \\ Sometimes syncing the clock can also cause this problem, but that should be fixed soon. If it does, exit the tiptilt server, log in as root, and reload the tiptilt model using the following commands: \\ /sbin/rmmod tiptilt_rt \\ /sgin/insmod /usr/local/modules/tiptilt_rt.o \\  \\ Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command "testclock" on a tiptilt command line. If this says the clock is working do not reboot the machine.
+==== Tiptilt is not locking on a star or locks, but lets the star drift away ====
+  * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.]
+  * Has TIPTILT COMM been run from Cosmic Debris?
+  * Check the ACQ alignment to make sure the tick marks are centered on the laser.
+  * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris.
+  * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover.
+  * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope's beam. This will show in the TT server as much lower counts than the other locked stars, but still high enough to lock TT. Use the laser to find the correct position to lock TT.
+  * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1.
+  * Are the TIPTILT buttons turned on from the POWER GUI?
+==== Tiptilt servo oscillates ====
+You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/horizontal motion indicates an oscillation in both directions. Motion from the upper right to lower left corresponds to elevation axis while motion from the upper left to lower right corresponds to the azimuth axis. (I think you can check direction by typing sin into telescope server to send sine waves to the telescope.) There are a few ways you can try to correct the oscillation manually tuning the servo:
+  * Type "tune" into the tiptilt server. Select the appropriate telescope. Turning the gain down normally helps.
+  * Type "tune" into the appropriate telescope server. The default value for the proportional term is -0.5 and differential term is 0.0. Adjust these values between -0.2 to -1.0 for proportional and 0.0 to 0.2 for differential.
+  * Read section on adjusting the Telescope Tracking Gain using the Dome Server GUI (ref).
+==== Tiptilt is saturating ====
+  * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts.
+  * Set the TT exposure time on Cosmic Debris in the box for "Tiptilt (mS)". This will set the TT exposure time when slewing to a new target.
+  * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt frequency (in Hz) changes on the tiptilt server after changing the exposure time. If the frame rate doesn't change, then set the exposure time back to the old value and try entering the new value again. You might have to do this a few times to actually get the frame rate to change.
+  * Frame rates for given exposure times:
+      * ExpTime = 5 msec, Frame Rate = 157 Hz
+      * ExpTime = 2 msec, Frame Rate = 299 Hz
+      * ExpTime = 1 msec, Frame Rate = 427 Hz
+==== Tiptilt counts are way too low ====
+Try using a slower frame rate or increasing the NSUM. Also ensure that the acquistion is properly aligned with the laser. To change the frame rate, click the [EXP] button on the tiptilt GUI and enter a longer integration time. Remember to change "Tiptilt (mS)" on Cosmic Debris to keep the same exposure time when slewing to the next target.
+==== Tiptilt counts are negative ====
+The bias frame is bad. Get a new one or turn it off.
 ===== 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:
-  *
 cosmic_fluor -F -o2 (for a secondary program using secondary ople)
+====   ====
+===== HISTORICAL NOTES ON ALIGNMENT SEQUENCES =====
+==== Beacon Alignments at Stow ====
+**IMPORTANT NOTE:**  There are now two sets of boxes on the TWFS.
+The **blue boxes**  are for locking on starlight and are the default reference position. \\ The **green boxes**  can be offset from these to save the beacon positions after the STST alignment.
+At the beginning of the night, the **red beacon**  must be **aligned to the blue**  starlight boxes with the telescope **at stow**. You can zero out any offsets between the green beacon boxes and the blue starlight boxes on the telescope WFS using [ZERO] on obsgtk or [ZERO BCN] on wfsgtk.
+==== Aberration Terms ====
+==== Check higher order terms - look at abberation plots or at terms displayed on the telaogtk ====
+  - If the astigmatism and coma terms reported by the telescope WFS are high
+      - obsgtk, main tab, [ZCEN] to update the relative box positions for the red beacon obsgtk to zero out higher order terms
+        - or [ZERO_CENT] button on telescope wfsgtk -E for engineering version.
+      - Only perform the ZERO CENT function when the X,Y and focus terms have been brought to near zero.
+==== Alignment Sequence for Visible Combiners: SPICA and PAVO ====
+For the visible combiners the red beacon and starlight will be coaligned, so you only need to use the blue starlight boxes on the telescope WFS.
+<del>**Obsgtk, **main tab, **[ZERO BCN]**  at the start of the night to clear any offset between the position of the beacon boxes and the starlight boxes to avoid any confustion</del>
+For **SPICA**, make sure to do “**useldc **on” in ople server if you haven't done so already.
+  - Slew to star.
+  - Main tab, turn on **[M7AUTO] **to hold the blue beacon during the slew and avoid drifting. It will turn off at the end of the slew.
+  - CD, **[Star Acquired],**  and set new ref pos with **[Opt delay]**
+      - **FOR PAVO: **Do **//NOT //**  hit **[Star Acquired] **before aligning for PAVO, only do **[STAR ACQUIRED]**  after alignment is finished.
+  - Obsgtk, use **[BEACON] **preset for beacon alignment.
+  - Make sure **[DMTILT]**  is off.
+  - **[ALN BCN], **Align red beacon to the blue starlight boxes on the telescope WFS using the beacon flat.
+      - Wfs tab, Use beacon buttons if needed on W1 if beacon gets out of the boxes
+      - or hit RIGHT with 500 stepsize to get them back in.
+  - LABAO section, **[ALN M7], **Align blue beacon to lab WFS using M7.
+      - WFS tab, use the yellow M7 buttons to get centered if beacon is not in boxes, then **[ALN M7]**
+      - 150,000 step size moves 1 full row. Directions are normal.
+  - LABAO section, **[FOCUS] **blue beacon on labao WFS if the focus term is high (moves beacon parabola).
+  - TELWFS section, **[FOCUS] **red beacon on TWFS if focus term is high
+  - **[RED OFF] **Turn off red beacon.
+  - Click **[MOVE]**  button then click on star in ACQ window. This will move star into ACQ hole.
+  - Turn off blue beacon and lock star on **[TT].**
+      - Wait a few seconds to let the star fill up the wfs.
+  - Lock star on telescope AO servo (**[****DM]**  button on obsgtk). Both TT and DM servos should be on now.
+  - If needed, move TWFS boxes (use popup from **ADJ**  button on obsgtk) to** get star centered and evenly illuminated on ACQ hole.**  (Note: you might need to close DM AO loop during this step.)- Turn on the blue beacon
+  - Make sure **DMTILT is green**
+      - Stays off during alignments and when locked on star using M7AUTO
+      - Stays on when locked on a star using DMAUTO.
+      - The message from DM tilt “NOT Ignoring DM tilt…” when it is on. (This may take 2 clicks to confirm this message.)
+      - NOTE: The **DMTILT**  button changes whether the x, y numbers at the bottom of obsgtk show box centroids (DMTILT gray) or zernike terms (DMTILT green). The automatic alignment sequences now correctly use the correct x,y calculations regardless of whether DMTILT is green/gray (centroids for aligmments and M7AUTO; zernike terms for DMAUTO).
+  - Turn on **DM AUTO**, **LABAO**.
+  - Align STST for IR
+      - obsgtk, **[STST]**
+      - once centered, turn on guiding
+  - **For PAVO: **make sure carts are in position, then hit **[STAR ACQUIRED**] once alignments are finished. Star acq. starts the camera on pavo.
+  - **For SPICA (no longer do extra spica ipdet alignment)**:
+      - **ip_det_gtk **  (blue chara menu)
+      - **[Start ACQ] **
+      - can adjust display with 200 - 2000 in the max, then hit **[SET]**.
+      - press **[BF/M7 CONTROL] **to open pop up control to align.
+        - use step size of about 32 if on the edge to bring to center. Directions are normal (ex. right is right)
+      - Use **STST **as a reference, if spots are far on ipdet display, stst is probably really off too. Use stst to bring spots close to center and it should help bring spots close to center on ipdet, then use BF/M7 to finish aligning.
+        - use the printed azimuth wheel to get directions of the buttons for SPICA.
+      - let SPICA team know, they may or may not want you to turn on FTT/SERVO.
+      - Once aligned, on STST GUI, press **[CenBox]**  to mark new reference position to monitor any drift.
+      - Make sure data acquired line comes in on CD, otherwise do **[DATA ACQ]. **
+        - or make sure to **[REOPEN]**  CD during shutters
+  - If the coma and astigmatism terms are high on the aberration plots, create a new sky flat
+      - Turn off **[DM]**, **[SV FLT]**, **[FLATEN]**, then relock the **[DM]**
+      - If the signal is good on the tel WFS, it is a good idea to make a new sky flat on every star.
+  - **Check aberration plots.**  If X/Y terms are not going to zero, try stopping servo loops, recentering alignment, and turning back on servo loops. If X/Y and higher order terms still not going to zero after checking alignment and making a new flat, then this likely means a new reconstructor needs to be made.
+  - SPICA uses MIRCX as a fringe tracker and MYSTIC as a fringe finder so having the STST open to monitor the IR beam quality is helpful even if you will not be doing the additional STST beacon flat alignment.
+      - Center the star flux in the Crop boxes with the CenBox button and use the drift from center, along with SPICA team input, to make beacon flat corrections as requested.
+  - At times, Mircx will have such poor flux that a beacon flat correction to align to the STST reference position will be needed. This will occur on **E1 pop 4 ****and 5**  and **S1 pop 5**  due to their extreme distances from the telescope to the lab.
+      - Follow the SPICA team guidance in making this correction to improve the flux to keep Mircx usable as a fringe tracker with those baselines.
+==== Alignment Sequence for IR Combiners: MIRC-X/MYSTIC, CLASSIC/CLIMB, SILMARIL ====
+The path of the IR light will be different from the visible light because of dispersion in the AO dichroic and atmospheric refraction. To compensate for this offset, we have **two sets of boxes**  on the telescope WFS.
+The **__blue boxesu are for starlight** and the **__  green boxesu are for aligning the red beacon**. The offset between these sets of boxes will change depending on the azimuth and elevation of the target.
+The green beacon boxes help keep track of the offset red beacon motion. These are defined as an offset to the starlight position, so if you move the starlight boxes, the beacon boxes will also move. If you move the beacon boxes only they will move.
+Before the start of the night clear any offset between the position of the beacon boxes and the starlight boxes on the telescope WFS using the “ZERO BCN” button on obsgtk.
+Faint stars (H > 5 mag) will not be easily visible in STST. Therefore, before slewing to the first star of the night or when slewing to a different region of the sky, slew to to a nearby bright IR star to align the beacon flat and set the beacon box offset on the TWFS. Then slew to faint star, keeping the red beacon at the same fixed position.
+**NOTE:**  The STST centroiding/servo'ing now works for longer exposure times. If you change exposure time, you need to: stop the camera, config the camera, restart the camera, and retake backgrounds.
+For **H=6 mag**, try changing coadds to 5 or 10 for 1 sec integration.
+For **H=8 mag,**  centroiding has been shown to work using 50 sec exposure (1 coadd).
+*Please update here* if you determine settings that work good for the using the auto STST alignments at different magnitudes.
+**Aligning the scopes before STST:**
+  - On shutters GUI, make sure **[STST]**  is in.
+  - Slew to a star of Hmag 5 or brighter (or adjust exposure time/coadds on STST as needed to see fainter stars).
+      - The Find IRC function on CD can do this quickly.
+      - Enter the target on a empty line, press **[HD]**  once (or appropriate designation), and **[Find IRC] **
+      - will automatically give you a bright star nearby.
+  - Close IR shutters as needed to avoid saturating the combiners.
+  - **[M7AUTO]**  can help keep the blue beacon aligned during the slew.
+  - Obsgtk, use **[BEACON] **preset for beacon alignment.
+  - Make sure **[DMTILT] **is off while aligning. This will display x, y centroids at the bottom of obsgtk.
+  - On the first slew only,
+      - **[ALN BCN], **align red beacon to the __blue star boxes__  on the telescope WFS using the beacon flat.
+  - On subsequent slews,
+      - if the star is bright enough to see in STST (Hmag 5 or brighter), then go to step **12 **
+      - if you can't see the star on STST, then align red beacon__ to the __offset green beacon boxesu (only after green boxes have been set using STST - see below).
+  - **[ALN M7] **Align blue beacon to lab WFS using M7.
+      - If beacon is not in boxes, use the yellow M7 buttons on the WFS tab to get centered
+      - 150,000 step size moves 1 full row. Directions are normal.
+  - Labao section,** [FOCUS]**  blue beacon If focus term is high
+  - TWFS section,** [FOCUS]**  red beacon If focus term is high
+      - (ONLY DO THIS STEP IF RED BEACON IS ALIGNED TO STARLIGHT BOXES - e.g., first slew)
+  - **[RED OFF]**. Make sure you have the blue starlight boxes on telescope WFS.
+  - Click **[MOVE]**  button then click on star in ACQ window. This will move star into ACQ hole.
+  - Turn off blue beacon and lock star on **[TT]**  only.
+  - Lock star on telescope AO servo (**DM**  button on obsgtk). Both TT and DM servos should be on.
+  - If needed, move TWFS boxes (use popup from **ADJ**  button on obsgtk) to** get star centered and evenly illuminated on ACQ hole.**
+      - (Note: you might need to close DM AO loop during this step.)
+  - Turn on the blue beacon.
+  - Turn on DMTilt (will turn green).
+      - stays off during slews
+      - the message from DM tilt will say “NOT Ignoring DM tilt…” when it is on. This may take 2 clicks to confirm this message.
+  - Turn on **DM AUTO**, **LABAO servo**.
+  - If the coma and astigmatism terms are high on the aberration plots, create a new sky flat
+      - Turn off **[DM]**, **[SV FLT]**, **[FLATEN]**, then relock the **[DM]**.
+      - **If the signal is good on the tel WFS, it is a good idea to make a new sky flat on every star.**
+**Aligning STST:**
+  - With the star locked, move the beacon to align the starlight on STST.
+  - On STST GUI, use either Full or Crop view.
+      - The green cross marks the center of the box and is your target, the red cross marks the centroid of star.
+      - If the star is within the STST reference box,
+        - **obsgtk**, main tab, very bottom, click **[STST]**  to automatically move the beacon and M7 simultaneously to align the star to STST. You can do all six at the same time.
+      - If the star is outside of the STST reference box,
+        - Try increasing the size of the STST reference boxes or move the beacon manually using the WFS tab.
+          - Use the azimuth rotation matrix wheel printout on the desk to know which way to move for IR.
+            - point arrow to the objects azimuth.
+            - the direction on the printout corresponds to the direction you want to move on stst.
+            - the direction printed on the wheel is the beacon button to press on obsgtk wfs tab.
+            - So if 'LEFT' is pointed up, press the left button to move stst up.
+          - The first few clicks may not move at all due to hysteresis in the actuators. Do this process slowly, as the labao DM TILT will offload to M7 slowly to compensate for the beacon shift and keep the blue beacon aligned to labao.
+          - If the IR flux did not move when clicking the beacon flat, click again as it was taking up slack in the movement. the labao DMTilt can handle up to 3 units of tilt to offload to the M7.
+          - If the tilt values reported on the obsgtk labao tilt are lower than 2 units, you can click again. Steps of 333-500 are typical for the first moves.
+            - If the required move is large, ~1000 steps on the beacon flat, or about 25 pixels on STST, it may help to turn the Labao Servo and DM AUTO off and manually move the blue beacon with M7 back to center on labao until the flux is closer to the STS center. AUTO M7 can also be used for medium sized moves, ~333-500 steps or so of the beacon flat.
+  - **If this is the first STST alignment star,**  then set the offset position of green beacon boxes on TWFS.
+      - When the star is aligned on STST
+        - turn off the DM servo and TT
+        - move the star away with NEXT
+        - turn on the Red Beacon.
+        - Turn on the boxes
+        - Click “TOGG” on obsgtk (or “TOG BEACON” on WFS gtk) to toggle from the blue starlight boxes to the green beacon boxes on telescope WFS.
+        - Click “SET” button on obsgtk (or “ALIGN BOXES” on WFS gtk) to move the green beacon boxes to the position of the red beacon. This will center the boxes over the beacon and save the new beacon flat positions in a few seconds. Watch the X,Y values of the twfs go to zero. Alternatively, you can use the buttons on the obsgtk ADJ tab pop up window to manually move them.
+        - TOGG back to blue starlight boxes when finished.
+  - **If you will record fringes on this star**
+      - turn off the red beacon
+      - toggle back to the starlight (blue) boxes
+      - MOVE the star to center on ACQ
+      - Turn on **TT**  and **DM**  servo for TWFS.
+      - Turn on **DM AUTO, DMTILT, **and **LABAO**  servo.
+  - **If this is an STST alignment star only**
+      - slew to the first target and align as needed there, which shouldn't be much or at all.
+  - **Check aberration plots. **If X/Y terms are not going to zero, try stopping servo loops, recentering alignment, and turning back on servo loops. If X/Y and higher order terms still not going to zero after checking alignment and making a new flat, then this likely means a new reconstructor needs to be made.
+  - **When slewing to the subsequent stars:**
+      - If you will see the star on STST, then align red beacon using **STST**  auto-alignment button after locking the star.
+      - If you won't see the star on STST, then align the red beacon using the new positions for the green beacon boxes (not the blue starlight boxes), then switch to the starlight boxes when locking starlight. If the slew is close on the sky, you can use the beacon alignment from the previous star. Go back to a nearby bright star if you need to check the beacon alignment on STST (e.g. if flux is lower or fibermaps have degraded on Mircx/Mystic
+      - Always lock the star using the blue star boxes.
+  - When you finish slewing and locking the star on TT, telAO, labAO, then click **[STAR ACQUIRED]**  on Cosmic Debris.
+For programs with bright IR stars, skip align beacon, but do the M7 and labao focus alignments. Then lock the star on the blue boxes and use the STST to fine tune any misalignment of the beacon flat. Check the beacon focus on the twfs occasionally to make sure it stays near zero, every 2-3 stars.

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools