Changes
SHOC
,/* Change Log */
== Change Log ==
'''Most recent changes at the top'''
* '''Installation of "New" SHOC on the 74-inch, February 2024<br>'''
** Users should also familiarise themselves with these two wikis if they are using SHOC on the 74-inch after February 2024
** [https://topswiki.saao.ac.za/index.php/74%22_/_1.9m_-_%22Instrument_Selector%22 "Instrument Selector" wiki].
** [https://topswiki.saao.ac.za/index.php/%22New%22_SHOC "New" SHOC wiki].
* '''v1.4.4 Release date 5 December 2018<br>'''
or
ssh shoc40in@shoc40in.suth.saao.ac.za
or ssh shoclesedi@shoclesedi.suth.saao.ac.za When prompted for the password, use the password for the 74in or 40in or lesedi user.
** In the terminal, type
restart_services
** Return to the web browser, and reload the page, then try to start the camera again.
** It may be necessary to restart the services a few times before you can start the camera.
* '''Acquisition doesn't start:''' Check on the GPS tab that the trigger signal has been activated. If it has, but the camera is still not taking images, try stopping the camera, resetting the GPS trigger to a time in the near future, and try again. Sometimes, it appears that the GPS trigger signal is not being sent (despite the software reporting that it is). The current acquisition should be stopped and restarted (because when the acquisition is started, the time the POP signal will start is recorded and will apear appear in the fits headers - so stopping and starting the acquisition will ensure that the correct POP time is used). Note that the index willl be incremented when doing this. To avoid this, you can rewind the increment by 1, in the advanced tab. Make sure you have no data that will be overwritten. *''' Acquisition doesn't finish:''' Sometimes it appears that the camera does not ever leave the acquiring state (despite all images in the kinetic series having been obtained). It may in this case be neccessary necessary to restart the server, manually edit the FITS files to include the filter and timing informationsinformation, and to then copy them to their final destination. The server may be restarted running the command "restart_services" from a terminal. The data is spooled to a directory under /data/spool/, based on the date, the sequence number and the time the acquisition started. In this directory is the data file, data.fits, and file containing other acquisition parameters, info.txt. The latter may be used to update the FITS header. The procedure is as follows:
** Rescue your data using the data rescue utility, as described in the section Rescuing Data.
** Run the command to restart the webserver, as described above in the subsection "Camera won't switch on".
or
ssh shoc40in@shoc74in.suth.saao.ac.za
or
ssh shoclesedi@shoclesedi.suth.saao.ac.za
When prompted for the password, use the password for the 74in or 40in user. Then go to the directory containing the spooled files:
cd /data/spool
sudo rescue_data.py
and then answer the questions as prompted. You'll be prompted for a password, use the password for the user you logged in as.
* The telescope is the name of the telescope being used; either 40in or , 74inor lesedi.
* The instrument will be one of shocnawe (sha) or shocndisbelief (shd). These are used to create the directory and filename in the /data directory. The directory will be of the form /data/<telescope>/<lowercase_instrument>/<YYYY>/<MMDD>, and the file of the form <instrument>_<YYYYMMDD>.<index>.fits. From this, the instrument name can be determined. At the moment, SHA is the SHOC instrument mounted on the 74inch and SHD is on the 40in.
* You will be prompted for an index to use. NB: '''make sure there is no existing file with the same index that will be overwritten''' The script will scan the target directory and list the existing files. Choose and index which isn't used(one option is to use an index like 3a , if index 3 exists). In other words, if files such as SHA_20150403.0004.fits and SHA_20150403.0005.fits, choosing either index 4 or 5 will result in that file being overwritten. If you choose as index 4a or 5a, the files will not be overwritten.
|}
The shoc computer should be reachable by an '''alias''' containing the telescope name. Usually '''shoc74in''' is an alias to '''shocnawe''', and '''shoc40in''' is an alias to '''shocndisbelief'''. If, e.g. '''shocndisbelief''' is mounted on the '''74inch''' telescope, the alias '''shoc74in''' should be changed to point to '''shocndisbelief'''.
IT should '''ONLY''' change the '''CNAME record'''. The '''A records''' should '''NEVER''' change. Even if only one of the instruments is being moved to another dome, BOTH records must be switched or DNS resolution will be intermittent. Example of a switched DNS setup:
Both '''shocndisbelief''' and '''shocnawe''' machines move between the telescopes. The setup below is what needs to change when '''shocnawe''' is moved.
'''From'''
| 360
|}
==Run the shocboxswitch.sh script when SHOC is moved between telescopes==
