Associated Wikis
(privileges may be required)
Associated Wikis
(privileges may be required)
This is an old revision of the document!
Last updated 04/26/2025
Any major updates made to the wiki, please send an email to the gsu “charaengineering” email list summarizing new changes.
Link for Old Operating Procedures Page
Observing Procedures
Supplemental Links
Discussion of Alignment Procedures
New Alignment Procedures - no longer updated - see alignment sections on this page
Night-time POP Changes - includes how to trouble shoot pop not moving
Remote Observing
Shutting Down prior to a Power Outage
Recovering from a Power Outage
Trouble Shooting
Text Commands for CHARA GUIs
Daily Alignment Check Procedure
Co-phasing with the CHARA phase reference
Cophasing with the New ChanCam
Instructions for using the Six Telescope Simulator (STS)
Six Telescope Star Tracker (STST) Manual
Tip-tilt Splitters Change
E1 HuT and Cooler Communications Recovery
Coude alignment procedure - Updated 2021Jun01
Telescope Horizon Limits
Restarting Servers
Daily Aberration Plots
Backup Remote Observing
ADAPTIVE OPTICS DOCUMENTATION
Tunable beacons
Tuning the AO Systems
E2 AOB Dichroic Recovery Document
Using Labao with Starlight
Telescope AO User Manual - an engineering manual, not for observing
WFS TT Alignment and Usage
TWFS Faint Object Instructions
Telescope Adaptive Optics Calibration Procedure
LabAO Alignment Procedure
INSTRUMENTS
Instrument Manuals and Observing Logs
Recent fringe offsets
Recent glass offsets
Software setup for specific instruments
Classic Faint Object Procedures
Check the current conditions and weather forecast for Mount Wilson before opening any of the domes or telescope covers. The telescopes can be closed in about 5 minutes from the control room. With this in mind, don’t open up the telescopes if conditions can change for the worse rapidly enough that you don't have time to close down safely.
Weather stations are installed at each bunker; readings are listed on the weathergtk. The HPWREN cameras are also useful in monitoring local conditions. However, nothing beats going outside for a gander and giving the sky a good old fashioned assessment.
Weather variations do exist from telescope to telescope, as much as 20% in RH at times. Most of the time this just means something is blowing through and opening is not a good idea. These circumstances need to be dealt with cautiously depending on the given weather conditions. Allowing extra time to close is advised in case of any problems.
Other humidity warning signs are: 1) water dripping off the OPLE building (or wet spots on the asphalt straight down from the eaves); 2) cold, clammy feel to metal objects such as railings; and 3) dew forming on the parked cars. It is important to note that the humidity can rise from 50% to 80% in as little as 10 minutes, so keep a close eye on the rate of change of the humidity plots. It can also rain or hail from small, passing clouds when the humidity is quite low, even 30% RH or lower. Operators have been surprised before by small puffy clouds in unsettled air with low humidity. If in doubt, stay closed. The HPWREN webcams are a good resource to view the bottoms of clouds. If there is any virga, the clouds are holding moisture and try to rain out. Stay closed if you see anything streaming below the clouds.
First thing to check are the purple air particulate sensors. There are three (S1E1W1) and will give a fairly good representation of the number of particulates in the area. The default is PM2.5 EPA AQI. We are still working on the shutdrown numbers, however, during the fires in September 2024, the numbers were above 100 when smoke could be detected on the mountain. Use caution and check other methods if the number is over 50-100. Consider closing mirror covers and domes if the number is above 100, especially if damp weather is coming soon. Please find the map at the following link and click the legacy link to display the map if the browser is unsupported.
https://map.purpleair.com/1/mAQI/a10/p604800/cC0#15.07/34.22297/-118.05484
Gauging the airborne dust and pollen can be problematic because you need a bright light and a relatively dark night. In general, you want to look in the bottom 0.5 meter of the light column. There will be a diffuse column lit up by the beam – don’t worry about it, just follow the dust glints. If you can count the dust glints, the conditions are safe to observe. If it looks like a blizzard, close up. If any of the dust glints shine with an orange or a peach hue, or the dust glints look abnormally large, the dust is probably ash – close up immediately. Ash seriously degrades bare aluminum coatings. Dust and wind go together. But, just because it is calm, the dust conditions might still be bad. If it was windy a few days earlier, it could have kicked up a lot of dust, which can take several days to settle. Finally, during late spring to early summer, conifer tree pollen can be problematic. If particulates are borderline please email the CHARA day staff so they can clean the optics as soon as possible.
Wind will degrade the seeing and kick up dust. The wind effects are amplified in the tunnel between the OPLE building and the office building, so look for other places to gauge the wind conditions. The intersection of the road and the trail to the eastern telescopes is a good place to gauge conditions. If you can hear the gusts from your desk, whistling from the light pipe supports, or the chain banging, it is too windy to observe. Occasionally you will hear the wind rustling the tops of the tall trees, but it is calm at ground level. This is a symptom of chaotic wind conditions, and almost always happens during windy episodes (Santa Anas, onshore flows, etc.), during which you shouldn’t observe – the seeing will be bad anyway. Be cautious about opening if wind gusts are above 15-20 kph; winds this high are usually correlated with bad seeing and poor data quality. Telescopes and domes should be closed if the wind gusts get up to 30 kph. This will protect the optics from branches and debris that can be blown in from the surrounding trees.
If there is snow stuck to the telescope dome itself, don’t open up. If there is snow still on the trees and branches procede with caution and make a visual assessment.
Cold temperatures around freezing also can be problematic. Several components are not rated to operate at freezing temps. The DM is temperature sensitive with a 5° C lower limit. Do not open unless it is above freezing and keep an eye on the temps if they are still dropping.
[Outdated] Here are limits for observing close to freezing:
A high-powered infrared laser is used for the delay line metrology. This is an eye hazard, so before entering the lab check to make sure the red light above the door is not on. If the laser is activated, you must wear IR-protective goggles. Please note that the METLAS gui or OPLESystem Controller gui may not show the correct state of the laser. Hit reopen on the METLAS gui if it does not agree with the others.
Lab booties/shoe covers must be worn inside the lab. Throw out booties that have holes in them. The traction tape on the steps are particularly rough on booties so examine them before and after using them. Proper clothing is also important. Loose hanging jackets or garments can snag on mirrors or other exposed equipment and are better left outside of the lab. Please be alert and move slowly and cautiously. When entering the lab make sure to walk across the sticky floor mat. If the mat isn’t sticky, remove the top layer. If this is close to the final layer please notify the staff.
Minimize the number of people in the lab, especially if within a few hours before observing time. Many bodies can create unwanted atmospheric effects. With too many people, it is too easy to bump into each other and the equipment. If you bump, hit, move or just tap anything in the slightest way, let staff know. Never touch anything you have not been trained to use. If ever in any doubt, leave it alone and get someone who knows. Any unusual sounds, sights, movement of equipment, etc., should be noted. You must know the path of the laser beams, metrology or alignment.
When leaving the lab any time of the day, remember to turn off all lights (fluorescent and incandescent). Lights left on generate unnecessary heat in the lab.
Ask in the discord if it's okay to start opening the domes to make sure opening doesn't interfere with any tests. Begin opening telescope domes and cylinders at least two hours before sunset (when the sun is below 40º).
Currently, only S2 and W1 can have the lower cylinders opened.
Before opening the domes, make sure to check the current weather conditions and the forecast to make sure conditions are safe to open and are likely to be stable as you wait for it to get dark.
To vent the domes (open partially, usually during Summertime):
To open the dome slit fully:
To open the cylinders:
Day time staff will align the lab during the week, but operator is responsible for alignments on the weekends.
Before doing alignments, if using SPICA or PAVO, home LDC's as they will be in.
If alignments have been done, check the following:
Pavo does not need IR target alignments.
If the observer will be observing bright targets and requires the use of the aperture wheels, the power cord needs to be plugged in.
NOTE: If using W2 E2 S2 for Classic or PAVO, then W1 E1 S1 ople computers have to be turned on as well in order to turn on the electronics for the pair, even if you don't plan to use them.
There are six computer screens. Top Left is screen 1, bottom left is screen 2, top middle is screen 3 and so on. Window layouts can be saved and reloaded to suit each operator. Use the third icon from the left in the toolbar (Operator Layout) to open a window to save or load a layout.
Let the domes cool at least an hour to do M10 and red beacon alignments, otherwise things will drift as the temperature changes and will need to be realigned. Alignments can get started before ople system controller is on and before UT 0 because the scope servers are always on. Will need labao servers (after UT 0) to do labao alignments. Remember to restart scope servers. Ople system controller is needed for the carts, not alignments
Servers can be opened from the black menu at bottom of screen 1
See also Night-time POP Changes which includes trouble shooting notes if a pop mirror does not move.
Check that pops are set as the same pops as the setup request email before homing the carts or after homing and sending them back to 20m.
Make sure to send M7 to default, and that STS VIS is out.
Manually Moving PoPs during Popperi movement
Make sure the carts are not near the front (0-5 meters) when performing these alignments or the labao alignments will be off.
Set defaults on Obsgtk,
Red Beacon Alignment:
Blue Beacon Alignment:
Focus beacons:
If SPICA does STS at the start of the night, red beacons have to be turned off.
Check higher order terms - look at abberation plots or at terms displayed on the telaogtk.
Checks to make sure beacons are aligned properly to TWFS:
Aberration plots: Keep aomon open during the night to montior the aberration terms. If twfs terms get large, do the ZERO CENT procedure.
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 boxes are for starlight and the green boxes 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 save the beacon position after the STST alignment. 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.
We use the Six Telescope Star Tracker (STST) to align the IR starlight in the lab.</font>
Can either align STST during the first slew (see Alignment Sequence for IR Combiners) or with STS (see below).
Before the start of the night, use the Six Telescope Simulator (STS) to set the reference boxes on the Six Telecope Star Tracker (STST). Here are brief instructions:
(see STST manual for more details)
If the STST camera is already running, you can open a second GUI by typing “ststrtd_gtk” in a terminal and click the “Start RTD” button to start the display. You can adjust the contrast of the display by changing the number in “Flux” box in the upper right of the GUI.
It is typically dark enough to lock on your first star roughly 25 minutes after sunset or the time of twilight reported by Cosmic Debris.
If the first science target/calibrator is faint in V-band, slew to a brighter star to initialize the telescopes, make flats, and do STST alignments.
Slewing to a Target Using Cosmic Debris
Locking on a star involves aligning the beacons, locking the star on tiptilt and tel AO, and locking the blue beacon on labAO. TelAO performs fast correction to compensate for atmospheric turbulence. LabAO performs slow correction to compensate for non-common path length errors along the beam path from the telescope to the lab.
The path of the visible and IR light into the lab is different because of atmospheric refraction and dispersion in the AO dichroic. Below we outline alignment steps separately for visible and IR combiners. For IR combiners we use the Six Telescope Star Tracker to align the IR light in the lab.
While tracking on a star, labao will offload X,Y tilt to M7 to keep the the blue beacon centroids aligned to labAO WFS. There are two methods for doing this:
Old method: DMTILT is gray (reconstructor ignores tilt). M7AUTO will adjust M7 to keep blue beacon centroids aligned to labAO WFS.
New method: DMTILT is green (uses tilt when computing reconstructor - “Not ignoring tilt”). DMAUTO will use labao DM to correct for tilt and offload to M7 to avoid reaching its tilt limit.
STOP A: If needed, the 3 STOP A buttons on obsgtk will stop any alignment sequences in progress.
The path of the IR light will be different from the visible light because of dispersion in the AO dichroic and atmospheric refraction. The starlight will also be offset from the blue beacon that is used for locking labAO. This offset will rotate on the sky as the telescope moves in azimuth. To compensate for this offset, we misalign the beacon flat mirror to center the IR light from the star on the Six Telescope Star Tracker (STST).
SPICA uses MIRC-X as a fringe tracker and MYSTIC as a fringe finder. During SPICA observing runs, data are often collected in all three combiners simultaneously (SPICA, MIRC-X, and MYSTIC). A new alignment has been adopted for SPICA:
Therefore, we now have a uniformed alignment sequence for visible and IR combiners.
For Silmaril, NIRO will be transformed into an IR star tracker called Strider. If Strider is in use, then STST should be out of the beam.
For CLASSIC, it might be useful to align the star using STST so that the alignment into CLASSIC stays consistent between the calibrator and science target. However, check with the Observer to find out if they want to use STST. The faintest targets observed with CLASSIC are probably not visible on STST, so in these cases, it would be better to observe without STST in the beam.
With TipTilt now being performed at the telescope instead of in the lab, there is no longer a stable reference position for PAVO, and the star will often drift out of the PAVO mask holes over the course of an observation. If the PAVO stars are bright enough to see on STST in the IR, then it might be useful center the star on STST and turn on STST guiding. There will still be an offset between the IR and visible light, but after the visible light is aligned to PAVO using the PAVO optics, this strategy might stabilize the star position. Ask the PAVO observer whether they might want to use STST guiding in the IR. If not using STST, then skip the STST steps in the following sequence.
Selecting a Bright Star for Initial STST Alignment
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:
[ALN BCN], Align red beacon to the 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.
If using STST, then keep the beacon misaligned relative to the WFS boxes on subsequent slews.
LABAO section, [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
When beacon is in the boxes, then [ALN M7]
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).
- Set a new ref cart position using [Opt Delay]. For CLASSIC and PAVO, do NOT move the reference cart between the calibrator and science target. 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.
- 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.
- 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 alignment button on obsgtk 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.
- Set a new ref cart position using [Opt Delay]. For CLASSIC and PAVO, do NOT move the reference cart between the calibrator and science target. 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. ==== Trouble Shooting - AO Performance ==== If AO performance is bad try these steps in the following order: * Check aberration plots. If X/Y terms are not going to zero, try stopping servo loops, recentering alignment, and turning back on servo loops. * Turn off the blue beacon and check the centering of the star on the ACQ hole. Adjust box positions to center star (ADJ popup on obsgtk). Hint - zoom in on ACQ display. * Look at red beacon on tel WFS and try zeroing the centroids using ZCEN on obsgtk. Note if you are using IR combiner, then align red beacon to blue starlight boxes (not the offset green beacon boxes) before clicking ZCEN. Align beacon back to STST reference after. * Check alignment of blue/red beacon on labao - make sure they are aligned properly with labao boxes. Use red beacon to find center of pattern then turn on blue to be sure the spots are in correct boxes. If not, move M7 to center with correct boxes. Note that the blue/red beacons are offset by about half a box. * If IR flux is low or spots are maps are poor on MIRCX/MYSTIC, then go to bright IR star and check beacon alignment again with STST. * Go back to stow and check the full beacon/dichroic alignment using the start of the night procedure. Remember to load all defaults before doing the alignment. * If X/Y and higher order terms are still not going to zero after checking alignment, making a new flat, and zeroing centroids, then this likely means a new reconstructor needs to be made. Notify charatech (maybe try taking onsky reconstructor). ==== Trouble Shooting - Locking TT and AO Loops ==== - If not locking, make sure red beacon is off, make sure on blue boxes, load def flat or last flat, make sure no clouds - If not locking, make sure DM current is low or around 1.2 - If not, Obsgtk, main tab, LD DEF
- if star is flaring and really bright, - lower the gain, may need to go lower than 100, maybe even 30 or lower. Lower until star is no longer flaring and spot is compact.
- After TT DM, Zdark if gain is not 300 ===== Optimizing AO Performance ===== ==== Recommended Settings for TelAO using IR dichroics: ==== |Star Magnitude |Exposure Time (msec) |Gain | |5.4 |1 |300 | |6.8 |1 |800 | |7.0 |2 |300 | |8.5 |2 |600 | |9.0 |2 |800 | |10.4 |10 |800 | For the VIS dichroics, the WFS gets only 20% of the light, but 1 msec should still get to magnitude 5.0. ==== Setting Threshold for WFS ==== If the starlight is missing from the boxes on the TWFS on S2, you might be able to improve performance on by applying a threshold to ignore the TWFS boxes without flux This is likely caused by an alignment problem at the telescope/AOB, so notify charatech if you apply a threshold. Here are the steps to try this approach again on sky: - If light is missing in some of the TWFS boxes, set a threshold to ignore those boxes. - Open: wfs_gtk S2 - The threshold is set on the WFS/TT tab. Enter a number in the box to the left of the THRESHLD button. Then click THRESHLD to set. - A threshold of 0.5 to 1.0 seems to work well. - Look at DM tab to make sure the edge actuators are not at or close to 1. If they are, try iterating between the default flat and new sky flat so that the edge values are not saturated. - The thresholding is based on the standard deviation across the full frame (with starlight). The statistics might be better if you make a dark for the WFS. Note that darks should be made after the sky is fully dark, otherwise the dark will include residual sky light. - NOTE: The thresholding works by setting everything below the threshold to<font 11pt/inherit;;inherit;;inherit>zero, so if it is too high it will black out the TWFS. You wantthe threshold to be as low as possible while still actually helping out. ==== Offloading Telescope Aberrations ==== Theo added a routine to offload aberrations from the telescope WFS on to the labAO DM. This could help remove static aberrations that are not corrected by telAO. Follow these instructions: - Open an engineering version of the telescope wfsgtk: - wfsgtk -E W2 &
- Clicking [ADDAB] will apply the correction to the terms with non-zero gain. - Clicking [ZEROAB] will zero out the corrections that were added to the labao DM.
===== Guiding with STST ===== For stars that are bright enough to see on STST, we can actively guide to keep the IR flux centered in the lab. This will minimize the number of fiber maps that are needed to keep the light centered on mircx/mystic. Check with the PI to ask if they want active guiding. There are three methods for keeping starlight aligned on STST: * STST ALIGN: The [STST] button on obsgtk takes the star offset (delX, delY) from STST and applies it to the BEACON-FLAT and M7 in a single move (open loop). During this operation, the auto-guiding of M7 is turned off to avoid conflicts. This command is very fast, a few seconds. * STST GUIDING using obsgtk: The [GUIDE] button on obsgtk is a continuously running background process that runs every 10 seconds. It takes the star offset from STST and moves the BEACON-FLAT in small increments of 400 units. This method relies on the Labao M7 auto-guiding corrections against the BEACON-FLAT moves (closed loop). This mode added more short-term variations to the flux trend plots because of backlash/overshooting of the beacon flat. We need a more precise way to control the beacon flat for this guiding mode to work. * STST GUIDING using ststrtd_gtk: The [GUIDING] button on ststrtd_gtkmoves the labao WFS boxes to keep the star centered on STST. In turn, the DMAUT/M7AUT tracking will move M7 to keep the beacon centered in the labao boxes. The motion of the labao boxes can be controlled more precisely than the moving the beacon flat. This is the preferred method for guiding with STST. If using this mode on sky, make sure to send labao boxes to default before slewing to the next star, otherwise the labao reconstructor might fail if the labao boxes move too much. Follow this procedure to use active guiding with STST: * Move the beacon flat M7 using the [STST]button on obsgtk to center the star close to the STST reference pixel. This step cannot correct the STST error below 5 pixels. * After the star is centered on STST, click the boxes next to the active scope (S1 S2 E1 E2 W1 W2) and turn on the [GUIDING] button on ststrtd_gtk. This will move the labao boxes to keep the star centered on STST. You can unclick the box to turn off guiding for a particular telescope. * The STST-LABAO-BOXES guiding will correct errors above 5 pixels and any slow beam drift. * If the LABAO boxes move too much, the LABAO reconstructor can have problems (tests show that it can remain stable for over 30 minutes). If you see flux dropping on mircx/mystic, it might mean that the LABAO-BOXES have moved too far. To fix this, switch off guiding, load default labao boxes, correct the STST error with the beacon M7 button (STST button on obsgtk), and then restart the STST-LABAO-BOXES guiding. Narsi will try to automate that by checking the difference between the labao default boxes and the current boxes – if they too much difference, stop the guiding offload to the beacon flat. * IMPORTANT: Turn off GUIDING when sky shutters start. After the the data/shutter sequence is complete, load the default labao boxes BEFORE slewing to the next star. ===== The Next Slew - Avoid Triggering AZ Limit Switches: ===== Always pay attention to the AZ you are slewing from or to, to avoid passing the sensors incorrectly and dealing with scopes getting stuck near 90° or 270°. Az Limit Switch Near 0º: There are two sensors negative and positive near AZ 0. It is okay to slew completely past AZ 0 in either direction. However, if you slew close to zero from the west or away from zero to the east, it is possible you will hit just one sensor. * If your next slew is continuing past zero in the SAME direction that you came from, both switches will get hit, and all is fine. * If your next slew is going back away from zero, you will not hit the second limit switch and will run into problems later. * before going to your next slew away from zero, slew to a different star past zero to hit the second limit switch. * can use obsgtk, [Find *] * Az: ~355 or 5º, keep el the same, mag 6
If you don't pay attention and only hit one sensor at AZ 0, some or all telescopes will continue to stall near 90 or 270 degrees and it is a pain to fix. Will have to trip the limit switch at the telescope.
TCS Az limit beyond -90 and 450º:
On the telescope server, keep an eye on the TCS az to not go beyond -90º and 450º. If you are getting close, telescopes will have to go the other way around to avoid hitting the limit.
Got to Troubleshooting, “Azimuth Limit Switches” Section
If you need to send a telescope to a different star while keeping the others at their current position:
Initialize the pointing of the telescopes on your first target by going to the MAIN tab on the obsgtk and clicking the red [INIT] button. Make sure you are on the correct star before initing the scopes or you will have problems. This may have to be repeated if the pointing drifts during the night. This will allow more consistent and accurate pointing for this part of the sky. You can also INIT during the SKY frames on MIRCX and MYSTIC since the star is in a good spot for finishing a slew.
or - Hit reopen on CD after data sequence/before shutter foregrounds end - Sometimes data acquired will show after shutter sequence finishes
When running MIRCX/MYSTIC, the operator may want to have the windows open to follow the fiber mapping, scanning for fringes and data recording. The windows can be opened with the command mircx_launch_all_guis on a desktop terminal. It will open 5 windows for each combiner, but they do not need to all be open. Close what you don't want to monitor. The fiberexplorer, gdt, rtd, and super_gtk windows are most helpful.
==== Acquisition Laser Alignment if the star does not lock in Tiptilt (Rarely used) ==== - Set VISBEAMS to correct beams. - Laser Filter on ND 3.0 - If the beacon and fiber covers are open, use the SHUTTERS GUI to open the laser shutter and the corresponding B1-B6 shutters. - You can also put in the corner cube with the [CCIN] button. - You will see at least two stars and two laser spots in the ACQ window. There is a reflection, hence two images of each. The desired spots are the right ones. - Use the “ORIGIN” paddle on the ADJUST Tab of the Telescope GUI or obsgtk to align the TV cross-hairs to coincide with the laser spot. - Close the laser shutter and the B1-B6 shutters. - * Move the corner cube out with the [CCOUT] button on the Main tab or Control tab on the telescope gui if you used it. - It will take about 10 seconds to move out of the the beam.
- Lock Tiptilt as shown above. Maintain the ACQ laser alignment during the night by adjusting the crosshairs to the star after locking Tiptilt. ==== Changing Ref Cart position: ==== - Manually - Take difference of the Targets pos and Laser position for cart farthest to the back (~44.2 m) or closest to the front (-1.2 m) - If w1 is close to front also, adjust w1, then the next farthest one. - Then make up the difference on the ref
- If W2 get's dropped from observations but is the ref cart (ex. going from 6T to 5T with no W2): - keep W2 in the config - turn cart off when its near the back - set ref between 44-70 to get delay on other carts.
- Star acquired
- Visbeams, go to beams you want, Laser filters, ND 0.3 or OPEN - Popperi, turn on power to pops you want to change, change first pop - turn off pop when it finishes on popperi
- When finished aligning, open M5, ACQ - Turn off Laser, close beam shutters, - If using SPICA, do [SPICA PERI IN] - If staying on the same star, turn off labao servo and load the default flat first. ==== Changing Beam Configuration During the Night ==== If you need to realign the lab dichroic or the IR mirror on the beam sampler stage during the night, make sure to remove STST stage (using the shutter gtk) before doing any alignments. Put STST back in the path after you are finished with the lab alignments and are ready to go on back on sky. STST gets the beam information from the telemetry server. Try clicking RECONNECT button on ststrtd_gtk. Also try resending the updated configuration from Cosmic Debris and the OPLE GTK (yes try both!). If that doesn't work try restarting the telemetry server by typing the following into ctrscrut: * killall telemetry_server * bootlaunch_master Reopen Cosmic Debris and resend configuration again. If that doesn't work then try killing and restarting mircx_stst_server on spooler@stst and running mircx_bootLaunch_master with N option (don't restart all servers - it will mess up mircx/mystic observer). ==== Locking Lab Tiptilt (only used in special cases) ==== With the star aligned with the acquisition ticks, check to make sure there are counts on the TipTilt server or the white plots in the TT windows have condensed. - Obsgtk, Main Tab, [TIP/TILT] under the Pointing Servo menu. - If this button is not pressed, then the green dots on the tiptilt windows will drift and eventually drop TT lock. - The [STAR ACQUIRED] button on Cosmic Debris also starts the Tiptilt servo for all active scopes with one push of a button. - On the Tiptilt Servo Control GUI, turn tiptilt [ON] for each telescope or use the [TT ON] button on Cosmic Debris to perform this function for all active scopes.
The End Night sequence on Cosmic Debris can be used to end observing and stow the telescopes, carts, and domes and close the mirror covers. It will only stow the active scopes, carts, and domes, so if there are other scopes open, make them active in the Configure tab of CD or stow them manually with the procedure below.
- Does NOT: - close the dome slits - send inactive scopes or carts back. - Update the configuration with any inactive scopes to make sure those carts can be sent back manually as well. - Doesn't close M5, M7, fiber, beacon, led (red), or laser (blue) laser beacons, - Doesn't disable scopes, shut off powers, turn off labao camera,
- Obsgtk, CONTROL→ close M7 and M5, FINDER (if used). - Obsgtk, MAIN→ TWFS Gain 100, [USBOFF], Labao [STOP], [OFF] - Obsgtk, CONTROL→ turn off Red, Fiber, Beacon. - Beacon Laser Control → Turn off red and blue beacons - Obsgtk, WFS → SHUTTERS OFF, DM POWER OFF - Never do camerlink off - Only do COOLING OFF when notified by daytime staff (e.g., during hot summer months) otherwise keep it on.
- For now, the daytime alignment is done without STST in the path so it is important to remove STST at the end of the night.
- Close slits after M1 fully closes (ON, SPY 2 to check). - Visually check all telescopes in the spycams 1&2 to make sure all covers and slits are closed. - make sure finder lid closed all the way (sometimes doesn't).
- Ople server →Double check carts are at the backswitch, once they are, Ople GUI, [OFF], close ople server - Shut down the ople control system - Close ople server - Press the shutdown button on the OPLE System Control gui, wait until all 6 dots are grey. - Press the Metro button, and wait until it is grey. - Close the gui on Wazoo. - Turn off the metrology laser (METLAS → Laser Power)
- Turn off [NIRO CPU], and [CLS-DITH], on the POWER gui. - Close CLIMB/CLASSIC GUIs and CLIMB/CLASSIC servers (type CTRL C, then Y)
- You can close Cosmic Debris after you have sent out the Observing Report.
At the end of the night, write a tech report detailing any issues that happened throughout the night. Helpful to keep an open email draft to note issues as they happen instead of waiting until the end of the night to write everything down.
- Finder CLOSE - W2 and E1 finder covers need a second click to close - Use SPY2 to make sure mirror covers close properly. - Check the Scope Monitor for mirror cover status. ==== Shutting down the Lab ==== - Close the vacuum valves for all telescope lines - Go to pump shack, close valve, shut off the pump. - Note any unusual noises or excessive oil temps (above 54 C) reported by the thermometer. Let Craig, Victor or Steve know of any concerns. Lock the padlock.
- Check for Any signs on the ople power controllers indicate power was left on. - E1 computer is usually on. - Push the Off button to turn off the component that is on. - Scroll left and right using the UP/DOWN buttons to move to each sign. Make sure all doors are closed as you leave. ==== Back in the Control Room: ==== - If you run into any problems during the shutdown procedures, send an email to charamnt or directly to Craig and Steve so that they can work to resolve any problems that need to be resolved promptly. - Please feel free to record any details in the Observers Notebook. - Email a Tech Report if you have other technical information to send out that is not related to the nightly observing runs. - Lock front and side doors of Operations Center if you are the last one in the building. - Close OPLE building doors; they tend to stick open, please push firmly. ===== Useful Commands for Errors ===== Labao server: - “oscope” - Type in Labao server - For hut and labao error. Reconnects labao with hut.
Scope Server
- “otcs” - Type in Telescope server - Opens telescope control system, use when “NO DOME SERVER” error in scope server, esp. after dome server restart
Ople Server
- “oo” - Open ople - Use if ople server crashes or if you open ople before ople system controller
Generic
- ctrl-L - Clears server error messages that block display
- if problem persists, restart ople system controller. - On Ople System Controller, restart the ople computer for the cart. - When its done, rehome and check the cart. Issue should go away. === Hut Error === Obsgtk: “Hut….Error: Relative move error -12” If you start to notice that buttons aren't doing anything (usually on E2) such as moving the beacon or turning on the red beacon, try doing one ~1100 step move to the beacon. If you get a “Hut….Error: Relative move error -12”, need to recycle the aob and restart hut. - Power Gui, turn off the AOB power (ex. E2WFS → AOB) - Obsgtk, Ajust tab, [RESTART PIC] old way: - Recycle AOB power, - open terminal, 'Tel'wfs (ex. E2wfs) - bootlaunch_master - kill hut twice to make sure it no longer exists.
On obsgtk, if the telescope wfs goes black, the wfs server has crashed.
- on Main tab, wait for cooling to reach -50. Will need to reopen to see it update. - once cooled, turn on the beacon, press STAND, and pres REDON.
- if “no route to host” message after shh'ing, need to go to dome - turn off raspberry pi and unplug both cables (black and orange) - plug back in and turn back on - ssh 'tel'zwo on computer - bootLauch_master - kill beacontune - bootLaunch_master
Sometimes S2 unlocks and won't move in elevation. Will notice star will only move side to side and drift diagonally and never be able to move straight to acquisition hole. Try the following to get it to move in elevation again:
- Restart dome server - open terminal, type “S2” - bootlaunch_master, kill dome_S2 PID, bootlaunch_master twice