Extension number: 9109 (to phone from within the observatory)
<!--To phone the dome from outside: 023 100 0 0230 (+27 23 100 0 0230 from outside South Africa)
-->
# If you are not on the SAAO network (i.e. not on site at SAAO in Cape Town), enable your SAAO VPN.
# '''Check the weather conditions [https://suthweather.saao.ac.za/ here]'''. If windspeed <60km/h and T-T<sub>dew</sub> > 1.5 (see [[#Observing limits|observing limits]]), continue with step 23.
# Open a Chrome or Chromium browser, navigate to the [https://unifivideo.suth.saao.ac.za:7443/cameras Unifi webcam], click "Live Feed" and check your volume level so you can hear sounds from the dome.
# In another tab, open this [httpshttp://10.2.50.12 webcam] which gives a wider view of the observing floor.
# Open another browser window and navigate to the TCS (URL, username & password in the Lesedi User Resources google doc).
# Navigate to the "Advanced" tab of the TCS, and in the central "Dome" section, turn the Slew Lights ON and check the webcam to see if observing floor is clear (if not, call the standby technician). Switch the Slew Lights OFF.
'''1.''' Follow the facility [[#Start-up recipes|start-up procedure]].
'''2.''' Check that the selected target is within the [[#Telescope pointing limits|pointing limits]]. If you're not sure, or want to find out the exact altaz of when your targetis visible, you can enter the coordinates into the input boxes on the upper left panel of the Controls tab, then click "Visibility...". This brings up a panel that shows the altitude and azimuth of the target at that moment, and the times at which the target rises and sets at the 30° altitude limit.
Then/or, either:
'''3(a)''' In the TCS '''Controls''' tab , in the boxes on the upper left panel, enter the RA, and Dec in sexagesimal (you can use not degrees). Use spaces for delimiters, i.e. hh mm ss (though colons will work too) - '''don't include any decimals''') and . Then enter the Equinox into , e.g. 2000 (don't include the boxes on the upper left panel "J") and click '''Go'''.
or:
'''3(b)''' In the TCS '''Controls''' tab click on the box labelled '''Targets''', then select the desired object from the dropdown list. To populate the dropdown list, see the [[#Target Creating a target catalogue| catalogue instructions]].
The telescope will slew to the target, and its movement will be plotted in red dots on the schematic in the right-hand panel. The "Go" button will become a "STOP" button, which you can click if you need to stop the telescope. Once it reaches the target coordinates, the telescope will start to track and yellow dots will show the track progress on the visibility plot. If nothing happens, the target is probably outside the observing window - return to step 2.
'''4.''' The telescope will track the target until you click '''STOP''', or until it reaches the lower altitude limit (note that the TCS will not warn you if this happens, so keep an eye on the visibility plot).
'''5.''' Lesedi's pointing is excellent, so your target should land very close to the centre of the image. The Due to cable wrap limits that preclude a 360° instrument rotation, the '''image orientation''' will vary between North up, East to the left, ; and North down, East to the right, due to cable wrap limits that preclude a 360° instrument rotation.
To adjust the pointing (e.g. to position a target and comparison star in the field), in the TCS Controls tab, click on the three dots beside "RA offset" (to shift the image horizontally) or "Dec offset" (for a vertical shift), enter the size of the required offset in arcsec, then click on the North, South, East or West button to move the telescope in the desired direction. When you're done, clicking the three dots again will hide the offset boxes.
'''6.''' The focus position is reported in the central status panel on the Controls tab. A reasonable starting point for Mookodi focus (imaging with clear filter) is ~2380μm; ~1700μm for Sibonise. Once you're close to focus, a reasonable increment for small adjustments is ~10μm. Focus the telescope using the '''Adjust Focus...''' button, which brings up a box in which you can enter the focus increment in microns, then click '''+''' or '''-''' to add or subtract e.g. 10μm to the focus position.
=== Creating a target catalogue ===
If you will be observing many targets during your run, or revisiting the same targets repeatedly, it would be helpful to create a target catalogue so that you don't have to type the coordinates into the TCS every time. There are two ways to do this:
# '''Add each target to the catalogue the first time you observe it.''' To do this, click "Catalogue..." enter the target, coordinates and equinox into the boxes and click "Add Target". You can then select the target from the dropdown "Targets" list above the Catalogue button.
# '''Create a catalogue file.''' Create a text file on the PC that is running the browser TCS (e.g. if you are in the dome, this will be lesedi-nuc). The file should consist of one line per target, with RA, Dec, target name & equinox as comma-separated variables, e.g.
11 12 13,-14 15 16,J1112-1415,2000
22 23 24,-25 26 27,J2223-2526,2000
Save the catalogue with an easily identifiable filename, e.g. myname.txt, then on the TCS, click "Catalogue..." and "Import". Navigate to the appropriate directory and select your catalogue file.
If you are observing from the dome, using lesedi-nuc, and have created your catalogue file on your own PC, you will need to upload it using:
scp myname.txt ccd@lesedi-nuc.suth.saao.ac.za:~/Targets
then on the TCS, click "Catalogue..." then "Import" and select your file from /home/ccd/Targets.
If you then click on the dropdown Targets list above the Catalogue button, your targets will be available for you to select, then click "Go" to point.
== Autoguiding ==
As of February 2021, there is a web browser interface to the backend autoguider control GUI, so users no longer need to access the backend ([[#Backup autoguiding procedure|unless you have problems]]). Note that the original autoguider software does need to be running on ioserver1 in order to operate the guider, but you shouldn't need to interact with it directly. The procedure for autoguiding via the browser is described below.
Open a web browser and navigate to:
10.2.2.32:5001
'''Make sure that there is only ever one autoguider window open at a time, or you will have problems.'''
The autoguider control interface looks like this:
<br clear=all>
The autoguider camera image is displayed on the top right, with the finderchart image below. There will be a green "Online" indicator at the top left if all is well; if it's red ("Offline") the autoguider control software might not be running on ioserver1. If it looks ok, continue reading this section, otherwise - and if you run into trouble with any of the steps below - skip to the [[#Backup autoguiding procedure|next section]]call a technician.
To acquire a guide star, do the following:
# Click "Stop Continuous" to stop exposing.
# Click "INITIALISE" to return the XY-slides to the home position.
# In the terminal running the web server, press CTRL-C to kill the process. === Backup autoguiding procedure === Users have occasionally encountered repeated loss of connectivity that makes it difficult to use Close the browser control for autoguiding. In this case, you can interact directly with the backend software by following the instructions below. # Connect to ioserver1 via remote desktop, e.g. for Linux use the Remmina client, set the server to ioserver1.suth.saao.ac.za and enter the username and password from the Lesedi User Resources Google document.# Once connected to ioserver1, the autoguider software should be running. If it isn't, or if it fails to respond, follow [[#Autoguider troubleshooting|these instructions]]. '''To start guiding''': # On the main autoguider GUI, if using Mookodi select Slide 0; or Slide 1 for Sibonise.# If the status of any of the error codes (Err, XLL, XUL, YLL or YUL) is 1, click RESET, then INITIALISE. "FAKE" should always be a green "Fake is OFF" button while guiding - this is a test function for engineering purposes. # To start continuous exposures with the autoguider Lodestar camera, enter a number (~2 seconds) in the box on the right, and click CONTINUOUS. Binning should be set to 2x2. To get a workable look-up table, on the left-hand side of the main autoguider GUI, move the uppermost vertical slider ~1/6 of the way from the bottom. Leave the other two sliders in their default positions (lower vertical slider halfway up; lower horizontal slider all the way to the left; upper horizontal slider all the way to the right).# Enter the target coordinates (using spaces as delimiters, e.g. 12 34 56 -76 54 32) in the separate GS_FC window and click "Set".# Check that a finder chart loads showing your field. Guide stars are to be selected from outside the green box in the finder chart image. When North is Up in the Mookodi/Sibonise image, click on a star in the upper half of the image to use as a guide star.<!--, with X<20000 and Y<15000. As Y increases it begins to vignette the Mookodi field, so try to choose a guide star at low Y.--># On the XY Slide Control section of the main GUI, click "Goto GS". This will send the XY slides to the position you clicked on the finder chart. <!--If it doesn't, read the coordinates of the guide star off the image and enter them manually; when the position is reached click "Pick guide star" and click on your chosen star in the guide camera image.--># Click the "Pick G_Star" button in the "Guiding" panel, which will turn dark blue to indicate that it's ready to receive your guide star selection. # Choose a star in the Lodestar image and click on it. The "Pick G_Star" button will turn green if it recognises the star. If the button turns grey, your selection has been unsuccessful and you will need to click the "Pick G_Star" button again and then try clicking on a different star.# Click the red GUIDE button - it should turn green to indicate that it has started guiding. '''If guiding fails''' at any point during a track (e.g. due to cloud), the button will turn red. Try increasing the exposure time (change the value and click "CONTINUOUS") and click GUIDE if the star is sill near the box. If the star has drifted, you can either offset the telescope to bring it back to its original position and then click GUIDE, or if it is not important to you to keep the target in the original position on the science image, you can repeat the guide star selection procedure to resume guiding in the post-drift position. '''To stop the autoguider:''' # Click "GUIDE" to stop guiding.# Click "STOP CONT." to stop exposing.# Click "Initialize" to return the XY-slides to the home position. === Autoguider troubleshooting === If the autoguider GUI isn't already running (or is not responding), open a terminal, log in to lesedis2 (username & password in the Lesedi Resources google doc) and check for any autoguider jobs already running: ssh -Y observer@lesedis2.suth.saao.ac.za ps aux | grep readPLCIf there are outstanding jobs, the result will be something like: root 1310 99.8 0.1 39384 13016 ? R Jun21 5284:08 python readPLCandLesediV1.py root 14103 0.0 0.1 39384 13040 pts/11 S+ 14:41 0:00 python readPLCandLesediV1.py root 20411 99.9 0.1 39384 13092 ? R Jun23 1187:37 python readPLCandLesediV1.py observer 25808 0.0 0.0 14224 1032 pts/12 S+ 17:49 0:00 grep --color=auto readPLCThese processes remain "hanging" if the software was not closed properly using the EXIT button. You need to kill them using their IDs given above, e.g. in this case: sudo kill -9 1310 14103 20411Then in the same terminal, check that the Lodestar cameras are connected: observer@sa1:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 079: ID 1278:0507 Starlight Xpress Lodestar autoguider Bus 001 Device 081: ID 1278:0507 Starlight Xpress Lodestar autoguiderThere is one Lodestar camera each for Mookodi and Sibonise. If you see one Starlight Xpress in the list it might just be the one you need, so try the next steps. If you do not see any Starlight Xpress listed then the cameras are not detected on the USB ports and the icron devices probably need power cycling (call electronics standby). Once any rogue processes are killed and the cameras are connected, start the autoguider GUI: cd /home/observer/src/xyslides2ports sudo ./main_prog -depth 24 You are now ready to continue [[#Autoguiding|running the autoguider from the browser]]. However, if for some reason you need to run the guider from the backend software, you will need to start the finder chart software. Open a new terminal on ioserver1 (or preferably a new window in the same terminal with Ctrl-Shift-T) and log in again to lesedis2: ssh -Y observer@lesedis2.suth.saao.ac.za cd /home/observer/GS_FC python genfinderLesediFeb2020.py This brings up a finder chart and a coordinates box. You're now ready to [[#Backup autoguiding procedure|guide use the backend autoguider software]]. '''If the autoguider camera image does not update''' after selecting continuous exposures, you will need to press the turquoise "Power Cycle Cameras" button on the backend GUI, then EXIT the software with the red button and restart it as above.
== Shutdown recipes ==
# Click the '''SHUTDOWN''' button on the bottom right of the TCS screen. This will close the mirror & baffle covers, close the dome shutters, and park the telescope and dome. A blue progress circle will rotate on the button while all the commands are executed; it will disappear once the shutdown procedure is complete.
# Turn on the slew lights on the "Advanced" tab and check on the Mobotix webcam that telescope and dome are closed and parkedand closed.
# On the central panel of the TCS "Controls" tab, check for grey or orange indicators showing the status of each subsystem: telescope Tracking = Off (grey); Mirror covers = Closed (orange); Dome (orange) Tracking = Off (grey) and Shutters = Closed (orange) [the arc indicating the shutters on the schematic will also turn red and settle in the West].
# On the left-hand panel of the Controls tab, there should be a message in orange stating "Unpark telescope to slew", indicating that the telescope is parked.
# If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
# '''Logout''' of the TCS and close the webcam browser windowswindow.# Stop the autoguider exposures and , initialise the XY slidesand close the autoguider browser window.# Close the webcam browser windows.
# Make sure the instrument (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.
# On the Controls tab of the TCS check for grey or orange indicators showing the status of each subsystem: telescope Tracking = Off (grey); Mirror covers = Closed (orange); Dome (orange) Tracking = Off (grey) and Shutters = Closed (orange) [the arc indicating the shutters on the schematic will also turn red].
# If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
# '''Logout''' of the TCS and close the webcam browser windowswindow.# Stop the autoguider exposures and , initialise the XY slidesand close the autoguider browser window.# Close the webcam browser windows.
# Make sure the instrument (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.
== Troubleshooting ==
The table below describes some problems you might encounter. Some can be tackled by the observer (see column 4). If the suggested steps to be followed by an observer fail, please call a technician.
{| class="wikitable" border="1"
| Mechanical or electronic standby.
|-
| The telescope spontaneously shut down (mirror covers closed, dome closed, telescope parked).| The facility was shutdown by the LCU, either due to bad weather or a loss of connection to the TCS.| Check the weather: if it's bad you must leave the telescope closed. Check the TCS: if there is a message stating that the connection has been lost, reload the page. If the weather is good, press Startup and resume observing.| Observer|-| The dome didn't open on startup, or closed by itself and won't reopen.
| There may be a dome comms problem.
| Call a technician to remedy.