Note
This document describes the procedures for observing with the auxiliary telescope in the early stages of system integration and commission. The procedures are likely to change very rapidly in these stages so it is recommended that users keep a close eye on the document before doing any observations. Here we will also document some troubleshooting to commonly found issues. In case of questions contact the document authors.
1 Introduction¶
It is important to emphasize that this document focus on early operations of the Auxiliary Telescope, with a significant part of the hardware and software still in need of considerable advancements. For instance, we are still in the process of obtaining and validating the telescope pointing model and optical alignment.
There is also some significant distinctions in the way we operate the telescope at this early stages and the way we plan to operate during commissioning and, even more, during normal operations. At this point we maintain a “low-level” kind of operations, both due to the need to be in full control of all the components and simply because the lack of high level operation software available. In fact, we are in the process of developing high level software that will improve considerably the user experience as well as pave the way for the development of “SAL Scripts” that ultimately will power the observatory Script Queue.
Furthermore, some issues pointed in this document may have been corrected in the meantime so it is very likely that the document will contain some outdated information. We will make an effort to document corrections as they occur but be aware that changes may happen faster then we are able to update this document. Users may want to check for more updated versions in the edition navigation page or check the github repository for any pending pull requests.
2 Network architecture and connectivity¶
From the user perspective, the summit network can broken down into two main systems; the campus and the control network. Regardless if you are at the summit, the base or in Tucson if you are connected to the LSST network (e.g. LSST-WAP) you will have access to the summit network. The control network on the other side is only accessible from bastion computers on the summit. These bastions are connected to both the campus network and the control network, thus giving users access to the control network through ssh tunneling.
Attention
An important aspect of the control network is that it does not have access to the internet. This does create some issues, for instance, to update software on computers connected solely to the control network on the fly.
A list of the host computers IP address can be found here.
2.1 Useful ssh Tunneling rules¶
Paste the following rules to ~/.ssh/config on the computer you plan on using for the
observations.
This is to access a jupyter notebook.
Host chile-jupyter
Hostname 139.229.162.118
User <username>
LocalForward 8885 192.168.1.2??:8885
This is to enabled wget on GenericCamera.
Host chile-wget
Hostname 139.229.162.118
User <username>
LocalForward 8001 192.168.1.216:8000