Changes

== SHOC User Manual ==* '''Observation planning tools:''' There is now a SHOC [http://shoc.saao.ac.za/SHOCsnr.html signal-to-noise ratio, exposure time, and limiting magnitude calculator]. * NOTE: THIS PAGE REFERS TO THE LINUX- and WEB-BASED SOFTWARE (AS OF MARCH, 2015). For the original, manufacturer-based software and instrument commissioning details, please refer to the manual at http://shoc.saao.ac.za/Documents/ShocnHelpful.pdf.*'' If you have found this webpage already loaded on the browser, please refresh to ensure that it is current!!''==SHOC Call Out list = Introduction ='''Instrument software issues:''' Carel van Gend **050 (0768181312)  '''Telescope software issues:''' standby **113 (0212015178) or 9118 '''Electronics Issues:''' standby **103 (0212015179) or 9117 '''Mechanical Issues:''' standby **104 (0212015180) * Please report any problems on [https://faultreports.saao.ac.za/ the fault reports page]. == Introduction ==The SHOC systems consist of a filterwheel unit (with one or two filterwheels), a GPS unit for providing accurate timing triggers, an Andor iXon camera, and a control PC. Currently there are 2 full SHOC systems (shocnawe & shocndisbelief), and 1 development system running a different camera (shocnhorror). As of March 2015, the control software is web-based. Users point their browser to the instrument location, and separate tabs appear to allow control of the camera, GPS, and filter wheel. SHOC can be mounted on the 1.9- and , 1-m and Lesedi telescopes. We have tried to make the usage telescope specific, so please confirm but it is very useful to know which SHOC system instrument is mounted on your the telescope so that you know where to point the browser! are using. Details on instrument operation are below.

[http://marissa.saao.ac.za Dr. Marissa Kotze] has written some [http://marissashoc.saao.ac.za/SHOCpipelinePipeline/ pipeline] software which may help with reduction of SHOC databut due to IRAF dependency the SAAO will no longer provide support for this pipeline from August 2020 onward. Users are now encouraged to use [https://bitbucket.org/DominicBowman/tea-phot/src/master/ TEA-phot] developed by Dominic Bowman and Daniel Holdsworth. [[TEA-phot|Here]] are some installation instructions and basic "how-to" tips. If you use the TEA-Phot code to produce results for a scientific publication, we ask that you please adhere to the citation requests of the developers that are on their main repository page.

=== Quick Start IMPORTANT NOTES===* '''CONSIDER DECREASING DETECTOR TEMPERATURE IF TAKING LONG EXPOSURES''' Reports in 2016 indicated that the dark current is higher than expected (by a factor of ~ 100; more information to follow). This is most noticeable for long (>=10 minute) exposures. The camera is automatically cooled to -50C. It can be cooled down to -70 C; however, if the ambient temperature is high, the cooler will be stressed and cannot reach minimum temperatures. If you do adjust the temperature to -60, -65 or -70, please listen carefully so that if the temperature alarm triggers (a high-pitched, continuous beep) you can stop cooling and prevent hardware failure. March 2017* '''THE NEW SOFTWARE HAS DIFFERENT FILE NAMES AND HEADER KEYWORDS THAN PREVIOUS DATA.''' If you use this information in your analyses, you will have to update it. The filename format has been standardized to <Instrument>_YYYYMMDD.####.fits, where the instrument is sha (shocnawe), shd (shocndisbelief), or SHH to designate which SHOC box is being used. Please check the header of a new data file or the wiki [http://topswiki.saao.ac.za/index.php/SHOC#FITS_Header_Keywords FITS header keywords] (the "new" keywords are directly from the Andor iXon camera under Linux). March 2015* '''THE FILE SIZE IS NO LONGER LIMITED TO 2 GB. ''' This means that if you take large data cubes, the file size has ''no limit'' (this is because we are no longer on a Window-based, 32-bit, operating system). If you end up with a very large file, data analysis can be difficult. We are working on an efficient method to automatically split files into smaller sizes, but for now users need to be aware that requesting a large number of images in one file could return a very large file size (and if you mistakenly delete your file, you have lost alot of work!). It is recommended that multiple files be manually taken. ''If you have any questions or problems with the data, feel free to contact carel@ saao.ac.za.'' March 2015

* (1) Connect to the web browser. '''Go to http://shoc40in.suth.saao.ac.za:5000 or http://shoc74in.suth.saao.ac.za:5000 depending on which telescope you are using.'''== Change Log ==* (2) Initialize the filter wheel and select your filter. '''You must initialize both filter wheels whenever Most recent changes at the webservice is started.top'''* (3) Click on camera tab: turn on the camera and confirm that it is cooling.* (4) If using the GPS to trigger data frames, click on GPS tab: check that the GPS has valid time and can be set.* (5) Click on camera tab: set parameters on the camera and start previewing and taking data.* (6) Transfer data from the instrument to your local machine or the SAN.* (7) Turn OFF the camera before you leave!!

* '''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>'''** Bug: Camera user interface works without any filter wheels** Feature: Display filter wheel names on the user interface * '''v1.4.3 Release date 25 July 2018<br>'''** Bug: Fixed GPS antenna reference "off" bug by assigning per-telescope locations** Feature: Added a button to set GPS start time 30 seconds into the future (uses web browser operating system's time so make sure that your time zone is SAST) * '''v1.4.2 Release date 3 January 2018<br>'''** Feature: Better error reporting** Feature: TCS info now available when mounted on the 40-inch * '''v1.4.0 Release date 23 November 2016<br>'''** Bug: Camera interface doesn't revert to "manual mode" when reloading the page while it's in scripting mode** Feature: Upgraded to JS9 v1.10 ([https://github.com/ericmandel/js9/releases/tag/v1.10 Release Notes])** Feature: Display and plot total counts for active regions on image display * '''v1.3.5 Release date 16 November 2016<br>'''** Feature: GPS driver now has access to a general-purpose SHOC config file** Feature: GPS antenna delay is now set from the config file  * '''v1.3.4 Release date 19 October 2016<br>'''** Bug: Default image display orientation. The image shown on-screen in conventional mode should now be correctly oriented. * '''v1.3.3 Release date 17 August 2016<br>'''** Bug: EM amplifiers are not selectable** Bug: 74" GPS antenna reference off (CLI only)** Bug: Fixed bug where start button says 'Start' instead of 'Stop'** Feature: GPS static and dynamic mode options (CLI only)** Feature: Shorter exposure times for kinetic series =1 * '''v1.3.2 Release date 4 May 2016<br>'''** Bug: Filterwheel sometimes doesn't initialise on the first try.** Bug: Plot 1 point per exposure on analysis tab.** Feature: Turn off GPS pulses at restart_services.** Feature: Configurable audio signal when exposures are complete. * '''v1.3.1 Release date 6 April 2016<br>'''** Bug: If the output amp is switched, x should be flipped to the opposite of what it was.** Bug: Ambient temperature keword is now ENVTEM. No longer clobbers CCD temp keyword (TEMP).** Bug: TCS related keywords were not always correctly updated.** Bug: The SHOC cameras were referred to by the usual instruments to which they were attached. Now use serial number.** Bug: Fix to allow ampersand characters in additional header fields.** Bug: Scripting should now be working as expected.** Feature: Use logrotate to prevent log files from getting too big * '''v.1.3.0 Release date 10 February 2016<br>'''** Bug: Camera freezes up, requiring restart_services** Bug: When acquisition is stopped before first trigger is received, counter is nevertheless incremented.** Bug: Controller doesn't know about GPS when running in external mode** Bug: TCS information not appearing in FITS headers** Bug: Temperature reported as "N/A" when reloading camera interface** Feature: Swap "move" and "initialize" buttons on filter interface** Feature: Add additional binning options for scripting * '''v1.2.2 Release date: 14 October 2015<br/>'''** Bug: Subframe parameters will automatically adjust to allowable values based on binning configuration.** Bug: Fixed JS9 Zscale bug.** Feature: Basic authentication from within the web interface.** Feature: Scripts can be repeated by entering a value in the "script iterations" field from the advanced tab. * '''v1.2.1 Release date: 15 July 2015<br/>'''** Bug: Camera properties are looked up in a table, in the controller, so the driver no longer needs to query the camera each time for these.** Bug: Directories for saved data are now lowercase e.g. sha not SHA (this now follows SAAO standards).** Feature: Filter wheel ID and slot number are now included in the FITS headers. * '''v1.2.0 Release date: 17 June 2015<br/>'''** Bug: Incorrect counts displayed on analysis page** Feature: Only display one filter wheel interface when only one wheel is configured** Feature: [[#Automated_Data_Acquisition_.28Scripting.29|Scripting capabilities]] * '''v1.1.3 Release date: 13 May 2015<br/>'''** Bug: Some of the input fields on the camera form don't get disabled when acquiring data * '''v1.1.2 Release date: 4 May 2015<br/>'''** Bug: Counts in display appear to be negative when they exceed ~30,000 * '''v1.1.1 Release date: 29 April 2015<br/>'''** The following changes have been affected:<br/>*** Data is copied from the spool directory to the final directory _before_ the supplementary FITS header keywords are added. * '''v1.1 Release date of 1.1: 18 April 2015<br/>'''** From v1.0 released 25 March 2015, the following changes have been affected<br/>*** Images were horizontally flipped and shouldn't be (SHA; 20150325)*** Filter keywords in FITS header are now the colour, not number*** Exposure label on interface now reset when changing from external to internal mode*** Exposure time now set to 0 in external mode*** A header [http://topswiki.saao.ac.za/index.php/SHOC#FITS_Header_Keyword_Conversion keyword conversion script] from the old headers (prior to v1.1) to the new headers (v1.1) to be able to run old data through [http://shoc.saao.ac.za/Pipeline/ Marissa's updated pipeline].*** New data entry under the ''Camera'' -> ''Advanced'' -> ''Additional'' Header Keywords for astronomer to enter header keywords related to target/RA/Dec/additional information*** specifically for the 74in telescope, addition of FITS header keywords from the TCS. NOT AVAILABLE IN THE 40in TELESCOPE*** DATE-OBS field contains decimal part twice fixed*** At 16:30 daily, the restart_services will be run from cron*** sudo adjusted to be able to run all services needed including restart_services, rescue_data.py and ....?????? == Quick Start == # Connect to the web browser. '''Go to http://shoc40in.suth.saao.ac.za:5000 or http://shoc74in.suth.saao.ac.za:5000 or http://shoclesedi.suth.saao.ac.za:5000 depending on which telescope you are using.'''# If you are prompted to log in, use the shoc74in or shoc40in or shoclesedi username and password, depending on which telescope you are using (passwords are the same as those used in the data transfer section, and should be obtained during startoff)# Initialize the filter wheels and select your filter. '''You must initialize both filter wheels whenever the webservice is started.'''# Click on camera tab: turn on the camera and confirm that it is cooling.# If using the GPS to trigger data frames, click on GPS tab: check that the GPS has valid time and can be set.# Click on camera tab: set parameters on the camera and start previewing and taking data.# Transfer data from the instrument to your local machine or the SAN.# Make sure to turn OFF GPS trigger pulses when you are done with them.# Turn OFF the camera before you leave!! ==Filter wheel===* <span style="color: red">'''(1)'''</span> Point your browser at shoc40in.suth.saao.ac.za:5000 or shoc74in.suth.saao.ac.za:5000 or shoclesedi.suth.saao.ac.za:5000

[[File:filterwheelFilterwheel.png|1000px|left]]<br clear=all>

===GPS===

* Set the Programmed Output Pulse (POP) parameters (mode <span style="color: red">'''(3)'''</span>, pulse width <span style="color: red">'''(4)'''</span>, start date <span style="color: red">'''(5)'''</span>, start time <span style="color: red">'''(6)'''</span>(<strong>NOTE</strong>: the "now + 30 seconds" button uses your browser's time so make sure your operating system is set to local time), trigger interval <span style="color: red">'''(7)'''</span>) and click apply <span style="color: red">'''(8)'''</span>. The status should change to pending <span style="color: red">'''(9)'''</span>.* The recommended default pulse width is 10 microseconds.

===Camera===

* Set the trigger type <span style="color: red">'''(6)'''</span>, exposure <span style="color: red">'''(7)'''</span> and kinetic series <span style="color: red">'''(8)'''</span> parameters. Note that an entry of "0" in the Exposure field <span style="color: red">'''(7)'''</span> will default to the minimal possible exposure time.

===Acquiring data===

:: '''<telescope>''' is 40in or 74inor lesedi,:: '''<INSTR>''' could be SHD shd for shocndisbelief, SHA sha for shocnawe or SHH shh for shocnhorror,

:: '''<filename>''' is the instrument abbreviation in uppercase (SHA or , SHDor SHH) followed by the date in YYYYMMDD format and the number of the acquisition.* An example is /data/74in/SHAsha/2015/0325/SHA_20150325.0001.fits

===Automated Data TransferAcquisition (Scripting)===* To transfer data directly to your computer from the SHOC instrument, use the command line. Copy the data using the following command, depending on the telescope: rsync -avzP shoc74in@shoc74in.suth.saao.ac.za:/data/74in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath rsync -avzP shoc40in@shoc40in.suth.saao.ac.za:/data/40in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath

NOTE: Data are moved When running a series of exposures on the same target with different filters itcan be useful to make use of the SAN automated acquisition mode on the plateau every morning at 9:30amcamera tab. However, if you're wanting to get your data to the SAN (and from there to the servers in Cape Town sooner than 9''NOTE:30am) you MUST have run the shocdatacopy.sh script in order to get the data to the SAN. You can then obtain the data from astro.suth.saao.ac.za (or astro.cape.saao.ac.za if youSCRIPTING ALWAYS USES THE INTERNAL TRIGGER'''re back in Cape Town). See Data Transfer information under the advanced guide below for details on how to transfer to the SAN.

[[File:scripting_1.png|1000px]] <span style="color: red;">'''(1)'''</span> You can switch between the conventional "Manual" acquisition mode and automated mode by clicking on the option menu to the right of the tabs on the camera interface.  [[File:scripting_2.png|1000px]]<br> <span style="color: red;">'''(1)'''</span> Opening the menu will display a list of existing scripts as well as an <span style="color: red;">'''(2)'''</span> option for creating new ones.  [[File:scripting_3.png|1000px]]<br> When you click the "New script" option a dialog will appear giving you <span style="color: red;">'''(1)'''</span> a text field to enter a name for your new script. You can then enter any name and click the <span style="color: red;">'''(2)'''</span> "Create Script" button to create a new one. ''NOTE: Please ensure that your script has an easily identifiable name for the observer and run, e.g. Sickafoose_20150617Script1. All scripts are currently being stored in the drop-down web interface -- this means you will see other people's scripts and will have to look there for your own in order to load the script in subsequent observing runs.''  [[File:scripting_4.png|1000px]]<br> <span style="color: red;">'''(1)'''</span> This will then display a new, empty section where you can add a sequence ofacquisitions.  [[File:scripting_5.png|1000px]]<br> You can add as many line items as required by entering the appropriate valuesand clicking the <span style="color: red;">'''(1)'''</span> "Add Item" button.  [[File:scripting_6.png|1000px]]<br> If you make any mistakes while adding items, you can remove individual ones byclicking the <span style="color: red;">'''(1)'''</span> cross icon next to it. Once you're happy with the sequence,clicking the <span style="color: red;">'''(2)'''</span> "Start" button will start your automated acquisition.  [[File:scripting_7.png|1000px]]<br> Unless you click the <span style="color: red;">'''(1)'''</span> "Stop" button while the acquisition sequence is inprogress, the sequence will run to completion.  [[File:scripting_8.png|1000px]]<br> Scripts can also be repeated by clicking the repeat button, entering the number of times the script should be repeated and clicking the <span style="color: red;">'''(2)'''</span> "Start" button. ==Data Transfer== There is an automatic transfer of data from the instrument to the file servers in Sutherland and Cape Town, every morning at 7:30. So you should not need to worry about the security of your data. However, you'll still need to access your data! We describe here how to do this. There are two ways to get the data: (1) directly from the instrument PC or (2) from the SAAO storage area network (SAN).  To use method (1):** Open a shell on your local PC (Putty if you're using Windows or a bash/tcsh/sh if on Mac or Linux)** Copy the data using the following command, depending on the telescope: rsync -avzP shoc74in@shoc74in.suth.saao.ac.za:/data/74in/sh?/<YYYY>/<MMDD>/*.fits /LocalFilePath rsync -avzP shoc40in@shoc40in.suth.saao.ac.za:/data/40in/sh?/<YYYY>/<MMDD>/*.fits /LocalFilePath ---- where sh? is a wildcard that will point to the correct instrument mounted on the telescope for that night and "/LocalFilePath" is the location on your local machine ---- the password is that for the shoc74in or shoc40in accounts* NOTE: if the rsync command fails, try it WITHOUT the wildcard (*). Some rsync programs apparently do not support this function.* ANOTHER NOTE: if the rsync command fails, try it with the data path in quotations, e.g.: rsync -avzP shoc40in@shoc40in.suth.saao.ac.za:"/data/40in/shd/2016/0503/*.fits" /LocalFilePath  To collect your data from the SAN, you'll have to secure copy it from '''astro.suth.saao.ac.za'''. The usernames for this are '''ccd40''' and '''ccd74''' depending on your telescope. Ask for the password. Data are in the path /data/telescopedata/<TELESCOPE>/sh?/<YYYY>/<MMDD> rsync -avzP ccd74@astro.suth.saao.ac.za:/data/telescopedata/74in/sh?/<YYYY>/<MMDD>/*.fits /LocalFilePath rsync -avzP ccd40@astro.suth.saao.ac.za:/data/telescopedata/40in/sh?/<YYYY>/<MMDD>/*.fits /LocalFilePath ---- where SH? is a wildcard that will point to the correct instrument mounted on the telescope for that night; YYYY is the year; MMDD is the month and day; and "/LocalFilePath" is the location on your local machine * Useful: **On the SHOC computers, the 'tree' command will assist you in trying to look at what folders and files are under that directory.** For information on the script, a logfile is produced that will be in /var/log/<TELESCOPE>DataCopyLog<MMDD>-<NUM> where <TELESCOPE> is 40in or 74in <MMDD> MonthDay <NUM> the Nth time this script has been run NOTE: Data are moved to the SAN on the plateau every morning at 9:30am. However, if you're wanting to get your data to the SAN (and from there to the servers in Cape Town sooner than 9:30am) you MUST have run the shocdatacopy.sh script in order to get the data to the SAN. You can then obtain the data from astro.suth.saao.ac.za (or astro.cape.saao.ac.za if you're back in Cape Town). ==Advanced users guide ======= Web interface====

* Point your browser at http://shoc74in.suth.saao.ac.za:5000 or http://shoc40in.suth.saao.ac.za:5000or http://shoclesedi.suth.saao.ac.za:5000* If you are prompted to log in, use the shoc74in or shoc40in accounts depending on which telescope you are using.

====Filter wheel ====

====GPS (optional: to be used for accurately-timed images)====

====Camera====

** By moving the subframe to the bottom of the CCD, the kinetic cycle time can be reduced slightly (IN the order of a few hundredths of a second) as compared to when it is placed at the top.* Below this, the readout speed and preamp gain may be set. Higher readout speeds allow for shorter exposure times* Below this, but at the expense of noisier datareadout speed and preamp gain may be set.* The last setting is the Electron Multiplying (EM) gain. <span style="color: red">NOTE: DO NOT USE ELECTRON MULTIPLYING MODE UNLESS YOU HAVE SPECIFICALLY OBTAINED PERMISSION FROM DR AMANDA GULBIS SICKAFOOSE TO DO SO, AND YOU UNDERSTAND HOW AND WHEN TO USE IT. PERMANENT DAMAGE TO THE SENSOR CAN RESULT FROM INCORRECT USAGE. If you are using EM mode, choose the EM output amplifier, and then select a gain. BEGIN WITH LOW GAIN VALUES, BECAUSE IF THERE IS TOO MUCH SIGNAL''' YOU CAN DAMAGE THE CAMERA.'''</span>* When setting the horizontal shift speed, preamp gain and (if using EM mode, the EM gain), note the following: Higher readout speeds allow for shorter exposure times, but at the expense of noisier data, while higher electron to ADU gain values decrease the dynamic range. Read noise and electron to ADU gain values for each mode are provided in the PDF manual. In addition to this, it should be noted that as it takes about 6 milliseconds for the top-most pixel in the frame to be shifted to the storage area and SHOC does not have a shutter. The top row of pixels in each frame will have an exposure time of about six milliseconds longer than the bottom row. Consequently although it is possible (with enough subframing and binning) to expose for less than a hundredth of a second, this is inadvisable for the above reason. Finally, as indicated above, the 1MHz CON and EM modes are both 16bit. What this means is that the mode will reach saturation at 2^16 = 65536 counts. On the other hand, the 3 MHz CON and EM and 5,10 MHz EM modes are all 14-bit modes and saturate at 2^14 = 16384 counts. As the saturation limits of each mode will also depend on the electron to ADU gain, tables in the printed manual give the saturation limit in both counts and electrons for each mode.

====Real-time image display====

* Menu items above the image allow users to change the image zoom level, scaling and colour. * It is also possible to select regions of the graph for further analysis, notably a real-time display of counts: (i) while taking images using the Preview mode, click on the "Analysis" tab in the camera GUI; (ii) Select the "Region" menu at the top of the js9 image display and select a box or circle or whatever shape you like; (iii) Click on the region (in the image) and the right side of the screen will show a plot of the counts within the region and numbers for various parameters below; (iv) The region can be moved and enlarged realtime, and the display updates accordingly; (v) Multiple regions can be added to the plot, and the display reports whichever region is current selected. (vi) The regions will continue to appear on the display under the "Controls" GUI tab. Selecting "Region" -> "Delete Regions" will remove all of the regions shown on the frame.[[File:RealTimeSHOC.jpg|800px|left]]<br clear=all>

====Data TransferTotcounts and bscounts ====Totcounts are the total counts in the box region, while bscounts has the calculated background (see below) subtracted from the total.

There are two ways to transfer data: (1) directly to your computer or (2) onto the SAAO storage area network (SAN). ==== Background and Noise ====The data background and noise are automatically copied to obtained from the server every morning (at 9:30am).* (1) To transfer data directly to your computer, use outer 4 pixel-wide perimeter of the command lineselected region.** Open a shell on your local PC (Putty if you're using Windows or a bash/tcsh/sh if on Mac or Linux)** Copy the data using the following command, depending on the telescope: rsync -avzP shoc74in@shoc74in.suth.saao.ac.za:/data/74in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath rsync -avzP shoc40in@shoc40in.suth.saao.ac.za:/data/40in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath ---- where SH? The background value is a wildcard that will point to the correct instrument mounted on the telescope for that night median value of this area and "/LocalFilePath" is the location on your local machine ---- the password noise value is that for the shoc74in or shoc40in accountsRMS.

* (2) To move data to the SAN on the Sutherland plateau (from which you can access it ==== Centroid ====The centroid is obtained by connecting to locating the SAAO server), there is a data copy script on brightest 9 pixel box and computing the SHOC computer. ** From a command line, connect to the instrument computer. As appropriate for your telescope, use either centroid of the following commands: ssh shoc74in@shoc74in.suth.saao.ac.za ssh shoc40in@shoc74in.suth.saao.ac.za ---- When prompted for the password, use the password for the 74in or 40in user.**Run the shocdatacopy.sh script. Options can be: shocdatacopy.sh -d yesterday # to transfer yesterday's background subtracted data shocdatacopy.sh -d YYYYMMDD # to transfer data from some specified date ---- Without parameters, it will try to transfer today's data.** To collect your data from the SAN, you'll have to secure copy it from '''astro.suth.saao.ac.za'''. The usernames for about this are '''ccd40''' and '''ccd74''' depending on your telescopepoint. Ask for the password. Data are in the path /data/telescopedata/<TELESCOPE>/SH?/<YYYY>/<MMDD> rsync -avzP ccd74@ astro.suth.saao.ac.za:/data/telescopedata/74in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath rsync -avzP ccd40@ astro.suth.saao.ac.za:/data/telescopedata/40in/SH?/<YYYY>/<MMDD>/*.fits /LocalFilePath ---- where SH? is a wildcard that will point to the correct instrument mounted on the telescope for that night; YYYY is the year; MMDD is the month and day; and "/LocalFilePath" is the location on your local machine

* Useful: ==== FWHM ====**On The FWHM is estimated from the SHOC computers, image moments about the 'tree' command will assist you in trying to look at what folders and files are under that directory.** For information on the scriptcentroid, assuming a logfile is produced that will be in /var/log/<TELESCOPE>DataCopyLog<MMDD>-<NUM> where <TELESCOPE> is 40in or 74in <MMDD> MonthDay <NUM> the Nth time this script has been runGaussian distribution.

==== Recue Data=FITS Header Keywords===The FITS information is mostly drawn from the Andor camera. We have added additional keywords added to contain information on target (which can be entered by the user under the "advanced" tab in the web interface), the GPS settings, and from the telescope (when available -- currently only for the 74 inch). We have retained the raw state of Andor's keywords in order keep things as simple and straightforward as possible.

Under normal operation, the system automatically updates the {| border="1" cellpadding"5" cellspacing="0" class="wikitable"!|Keyword and comments (example) !| Notes|-|SIMPLE = T / file does conform to FITS standard |-|BITPIX = 16 / number of bits per data pixel |-|NAXIS = 3 / number of data axes |-|NAXIS1 = 128 / length of data axis 1 |-|NAXIS2 = 128 / length of data axis 2 |-|NAXIS3 = 10 / length of data axis 3 |-|EXTEND = T / FITS dataset may contain extensions |-|COMMENT FITS cube header with supplementary information (filterFlexible Image Transport System) format is defined in 'Astronomy|-|COMMENT and Astrophysics', external trigger parametersvolume 376, telescope pointing information etcpage 359; bibcode: 2001A&A.) and the moves the cube ..376..359H |-|BZERO = 32768 / offset data range to that of unsigned short the permanent (for the night) storage area|-|BSCALE = 1 / default scaling factor |-|HEAD = 'DU8201_UVB' / Head model |-|ACQMODE = 'Frame Transfer' / Acquisition mode |-|ACT = 1. From 11592 / Integration cycle time to |-|KCT = 1.11592 / Kinetic cycle time |-|NUMACC = 1 / Number of integrations |-|NUMKIN = 10 / Series length |-|READMODE= 'Image ' / Readout mode |-|IMGRECT = '1, it may 1024, 1024, 1' / Image format |-|HBIN = 1 / Horizontal binning|-|VBIN = 1 / Vertical binning|-|SUBRECT = '897, 1024, 128, 1' / Subimage format|-|DATATYPE= 'Counts ' / Data type|-|XTYPE = 'Pixel number' / Calibration type |-|XUNIT = 0 / Calibration units |-|RAYWAVE = 0. / Rayleigh Wavelength | This seems to be neccessary irrelevant, since we are not taking spectra.|-|CALBWVNM= 0 / Wave calibration | This seems to do this manuallybe irrelevant, using the rescue_data toolsince we are not taking spectra. In particular|-|TRIGGER = 'Internal' / Trigger mode|-|CALIB = '0, if 1,0,0 ' / Calibration|-|DLLVER = '2.97.30005.0' / Software Version|-|EXPOSURE= 1.10916 / Total Exposure Time|-|TEMP = 23. / Temperature| The CCD temperature. If the system has frozen at temperature is not yet stabilized, this will be -999. Then UNSTTMP gives the end unstabilized CCD temperature.|-|READTIME= 1.0E-06 / Pixel readout time| This corresponds to the 1, 3, 5, or 10 MHz readout amplifier.|-|OPERATN = 4 / Type of an acquisitionsystem |-|GAIN = 0 / Gain|-|EMREALGN= 0 / EM Real Gain |-|VCLKAMP = 0 / Vertical Clock Amplitude|-|VSHIFT = 6.5E-06 / Vertical Shift Speed|-|OUTPTAMP= 'Conventional' / Output Amplifier |-|PREAMP = 1. / Pre Amplifier Gain | This corresponds to the 1, but before fixing ~2.5x, or ~5x gain setting.See keyword SNTVTY or the header camera spec sheets at http://shoc.saao.ac.za/Documents/iXon.X5982.SpecSheet.pdfand moving http://shoc.saao.ac.za/Documents/iXon.X6448.SpecSheet.pdf.|-|SERNO = 6448 / Serial Number | The serial number of the datra filecamera. |-|UNSTTEMP= -35.764 / Unstabilized Temperature|If camera temp is stabilized, it this will be neccessary -999and the temperature will be under keyword "TEMP".|-|BLCLAMP = F / Baseline Clamp|-|PRECAN = 0 / Prescans |-|FLIPX = 1 / Horizontally Flipped |-|FLIPY = 0 / Vertically Flipped |-|CNTCVTMD= 0 / Count Convert Mode|-|CNTCVT = 1 / Count Convert|-|DTNWLGTH= 500. / Detection Wavelength| A misleading keyword: the camera has no information about filters!|-|SNTVTY = 3.82 / Sensitivity| The e/ADU conversion.|-|SPSNFLTR= -5551 / Spurious Noise Filter Mode| A keyword that we are still trying to perform this proceduredecipher.There are multiple camera * Open a terminalsettings, and they result to values ofeither 0 or -5551. Find your Setting 0 returns  normal-looking data , but returns this -5551 value.|-|THRSHLD = 0. / Threshold|-|PCNTENLD= 116 / Photon Counting Enabled |A keyword that we are still trying to decipher.When this camera setting is "off" the value of 116 is listed in the spool directoryheader. It's stored in a directory named When the setting is "on" the value is 0. |-|NSETHSLD= 0 /dataNumber of Photon Counting Thresholds |-|PTNTHLD1= 0. /spoolPhoton Counting Threshold 1|-|PTNTHLD2= 0. /<CCYYMMDD><index>Photon Counting Threshold 2 |-|PTNTHLD3= 0.<HHMMSS> / Photon Counting Threshold 3 |-|PTNTHLD4= 0. / Photon Counting Threshold 4 |-|AVGFTRMD= 0 / Averaging Filter Mode |-|AVGFCTR = 1 / Averaging factor |-|FRMCNT = 1 / Frame Count|-|PORTMODE= 0 / Port Readout Mode |-|LSHEIGHT= 0 / Exposure Window Height |-|LSSPEED = 0. / Line Scan Speed |-|LSALTDIR= 0 / Alternating Readout Direction |-|LSCTRL = 0 / Scan Speed Control |-|LSDIR = 0 / Readout Direction |-|FKSMODE = 0 / Fast Kinetics Storage Mode |-|FKTMODE = 0 / Fast Kinetics Time Scan Mode |-|USERTXT1= ' ' / User text|-|USERTXT2= ' ' / User text|-|USERTXT3= ' ' / User text|-|USERTXT4= ' ' / User text|-|DATE = '2015-04-17T14:34:28' / file creation date (where index YYYY-MM-DDThh:mm:ss) |-|FRAME = '2015-04-17T14:34:28.000' / Start of Frame Exposure | This comment is incorrect. It is the indextime at the ''end'' of the first frame for internal mode, CCYYMMDD and the time "start" is pressed for external triggering mode.|-|ESHTMODE= 0 / Electronic Shuttering Mode | |-|HIERARCH PREAMPGAINTEXT = ' ' / Pre-Amplifier Gain|-|HIERARCH SPECTROGRAPHSERIAL = ' ' / Spectrograph Serial |-|HIERARCH SHAMROCKISACTIVE = 0 / Shamrock is active |-|HIERARCH SPECTROGRAPHNAME = ' ' / Spectrograph name |-|HIERARCH SPECTROGRAPHISACTIVE = 0 / Spectrograph is active |-|HIERARCH IRIGDATAAVAILABLE = 0 / IRIG Availability |-|IRIGDATA= ' ' / IRIG Timestamp| This is the date last keyword of those coming straight from the Andor Ixon camera. |-|AIRMASS = 'NA ' / The airmass (sec(z)) | Starting with this keyword, everything here and HHMMSS is below has been added in the SAAO software. Airmass comes from the TCS.|-|DATE-OBS= '2015-04-17T14:34:26.446239' / The time the acquisition starteduser pushed start (UTC). For example| Note that during external triggering mode, this does not correspond to any specific timing for the images. The camera started waiting at this time for a trigger from the GPS.|-|DOMEPOS = 'NA ' /dataThe dome position| Read from the TCS.|-|ENVTEM = '26.65 ' /spoolThe average ambient temperature| This is the temperature on the plateau|-|FILTERA = ' ' /201503250002The active filter in wheel A| This should be a human-readable name for the filter in wheel A|-|FILTERB = ' ' / The active filter in wheel B | This should be a human-readable name for the filter in wheel B|-|GPS-INT = ' ' / GPS trigger interval (msec)| Set by the user on the GPS tab of the web interface.141026This is the cadence at which GPS pulses are sent. Each pulse triggers a readout on the camera.|-|GPSSTART= ' ' / GPS start time (UTC; external)| Set by the user on the GPS tab of the web interface. Go This is the time that the first GSP pulse was sent, which corresponds to this directory:the readout ssh shoc74in@shoc74inof the first GPS image.suth  We typically toss the first two images in a GPS triggered sequence because the first is nothing  (before the first pulse) and the second has slightly inaccurate timing.saao|-|HA = 'NA ' / The telescope hour angle | Read from the TCS.ac|-|INSTANGL= 'NA ' / The instrument angle| Read from the TCS.za |-|INSTRUME= 'SHD ' / The SHOC instrument name|-|INSTSWV = '1.0 ' / The SHOC software version|-|OBJDEC = ' ' / Declination of object| From the user- or entered information on the advance tab of the web interface.|-|OBJECT = ' ' / IAU name of observed object ssh shoc40in@shoc74in| From the user-entered information on the advance tab of the web interface.suth|-|OBJEPOCH= ' ' / Object coordinate epoch| From the user-entered information on the advance tab of the web interface.saao|-|OBJEQUIN= ' ' / Object coordinate equinox | From the user-entered information on the advance tab of the web interface.ac|-| OBJRA = ' ' / Right ascension of object | From the user-entered information on the advance tab of the web interface.za |-|OBSERVER= ' ' / Observer who acquired the data | From the user-entered information on the advance tab of the web interface.|-|OBSTYPE = ' ' / Observation type | From the user- When prompted for entered information on the password, use advance tab of the password for web interface.|-|POSA = '7 ' / The slot position of wheel A | The numerical slot position of wheel A |- |POSB = '8 ' / The slot position of wheel B | The numerical slot position of wheel B |-|TELDEC = 'NA ' / The telescope declination | Read from the TCS. Currently only on the 74in or !|-|TELESCOP= '40in user ' / The telescope name|-|TELFOCUS= 'NA ' / The telescope focus | Read from the TCS.ssh shoc74in@shoc74inCurrently only on the 74in!|-|TELRA = 'NA ' / The telescope right ascension | Read from the TCS.suthCurrently only on the 74in!|-|WHEELA = '011 ' / The ID of wheel A | The numerical ID of wheel A|-|WHEELB = '100 ' / The ID of wheel B | The numerical ID of wheel B|-|ZD = 'NA ' / The telescope zenith distance | Read from the TCS.saaoCurrently only on the 74in!|- |AIRMASS = 'NA ' / The airmass (sec(z)) |-|HUMIDIT = '9.ac86 ' / The average humidity |-|RELSKYT = '49.za57 ' / The relative sky temperature (average cloud cov cd |-|SEEING = 'Unknown ' /dataThe curent seeing |-|TMTDEW = '34.44 ' /spoolDifference between current and dew-point temper ls |-l cd <CCYYMMDD><index>|WIND = '39.<HHMMSS>73 ' / The average wind speed ls |-l* There should be |END|-|} ===FITS Header Keyword Conversion=== With the release of the new, web-based software there have been changes in the naming of some of the FITS keywords. The keywords are documented in the table below: {| border="1" cellpadding="5" cellspacing="0" class="wikitable"!|Old Keyword!|New Keyword|-|HIERARCH EMREALGAIN|EMREALGN|-|HIERARCH COUNTCONVERTMODE|CNTCVTMD|-|HIERARCH COUNTCONVERT|CNTCVT|-|HIERARCH DETECTIONWAVELENGTH|DTNWLGTH|-|HIERARCH SENSITIVITY|SNTVTY|-|HIERARCH SPURIOUSNOISEFILTER|SPSNFLTR|-|HIERARCH THRESHOLD|THRSHLD|-|HIERARCH PHOTONCOUNTINGENABLED|PCNTENLD|-|HIERARCH NOTHRESHOLDS|NSETHSLD|-|HIERARCH PHOTONCOUNTINGTHRESHOLD1|PTNTHLD1|-|HIERARCH PHOTONCOUNTINGTHRESHOLD2|PTNTHLD2|-|HIERARCH PHOTONCOUNTINGTHRESHOLD3|PTNTHLD3|-|HIERARCH PHOTONCOUNTINGTHRESHOLD4|PTNTHLD4|-|HIERARCH AVERAGINGFILTERMODE|AVGFTRMD|-|HIERARCH AVERAGINGFACTOR|AVGFCTR|-|HIERARCH FRAMECOUNT|FRMCNT|} A [https://bitbucket.org/api/2.0/snippets/saao/L5Xp/7c7ce9a54b8b55127f1893037fc5f5cb7dba86e0/files named /convert_keywords.py script] is provided to convert back and forth between the two versions of the keywords. This is useful when working with a datapipeline that is still based on the old version of the keywords or to make old data compatible with a new data pipeline. The script can be used as follows from a command line terminal:  $ convert_keywords.py mydatacube.fits and info This will convert the keywords in an old data cube to the new version.txtTo convert the keywords back to the old version, run the script with the "revert" option:* The info $ convert_keywords.txt py --revert mydatacube.fits In both cases the program will try to save the updated cube to a file contains with the supplementary informationsame name, but postfixed with "_converted".* Change So, "mydatacube_converted.fits" in the examples above. If the file already exists, you will be asked if you want to this directoryoverwrite the file.* Run If you do not want to overwrite the rescue utilityfile you will be given the opportunity to enter a different file name. Multiple files can be converted at once by providing a list of them when running the program: type rescue_data  $ convert_keywords.py cube1.fits cube2.fits cube3.fits '''NOTE:''' The conversion script makes use of [http://astropy.org Astropy]. See the official documentation for [http://astropy.readthedocs.org/en/stable/install.html installation instructions]. ===LED timing tests===''This functionality should be available on the 74", the 40" and then answer Lesedi. It has only been tested on the questions as prompted74".''* The telescope idea is to take a long, GPS-triggered data cube with SHOC at high cadence, while running the name of LED at 1 PPS (which has a longer pulse on the telescope being minute and can thus be used; either 40in or 74into test absolute timing accuracy).* The instrument will dome and mirror covers must be one of shocnawe OPEN for this test to work. (SHAThe GPS needs to get satellite signal, and the LED must be seen through the light path.) or shocndisbelief  *There is an LED mounted in the telescope optical path that can be used to independently verify SHOC timing. Log into the following website:  http://10.2.55.5:4000/timepulse Ask the Electronics standby for username and password. This website allows selection of LED pulses of different cadence (SHD1, 2, 5, 10, 100 Hz and 100kHz), see the image below. These '''Note that the pulse must be switched off when you are used to create done, otherwise it will continue blasting photons into the directory telescope!'''  [[image:74inLEDPulseWebsite.jpg|500px]] * Check that the LED is visible by turning on a pulse and filename seeing if it is apparent in the /data directorypreview images. The directory will be of For example, take 0.2-s exposure and set the form LED to 1 PPS, then look for increased counts/flashes on the display every 5th frame.* '''To take a timing data/cube:''' ** start the LED at 1 PPS** in preview mode, increase the SHOC binning and readout speed to reach the desired exposure cadence (<telescope>/<instrument>/<YYYY>/<MMDD0.05s). ** set SHOC to external timing, select >=10000 frames, and start the file of GPS with repeated pulses at the form <instrument>_<YYYYMMDD>chosen cadence ** REMEMBER TO TURN OFF THE LED PULSES WHEN DONE.<index>* '''Analysis:''' you are free to analyze your own timing data! Otherwise, an analysis pipeline has been written by Marissa Kotze and is supported by Carel van Gend.fits Carel can assist with data analysis. From this* Download the SHOCpipeline.tar and PULSEtiming.tar software. Create a directory for the software (e.g. timingtests) and extract the software to that directory: mkdir timingtests cd timingtests tar -xvf ../SHOCpipeline.tar tar -xvf ../PULSEtiming.tar * In the README file, follow the instrument name can be determinedinstructions on setting up iraf. * You will be prompted Then make a further subdirectory for an index the testdata: mkdir testdata * Copy the data cube to usethis directory, and run the testPULSEtiming. NBpy script: make sure there is no existing cd testdata python testPULSEtiming.py <SHOC fits file with the same index that name> * The software will be overwritten (one option is to use an index like 3a examine the header, if index 3 exists)ask the user for confirmation of a few values, and then verify the timing. A report is printed out at the end.

=== In-depth Information =======Characteristics and Properties====

====Choosing an Observing Method====

=== User's troubleshooting guide=====Camera Issues===* '''Camera won't switch on:''' If the camera display times out when trying to switch on, you will need to restart the services. To do this:** Open a terminal. This is available from the top menu or side menu of the thin client in the warm room. If the web browser is full screen, push 'F11', and you should then see the top menu bar. Once the terminal window appears, ssh to the instrument by running the command ssh shoc74in@shoc74in.suth.saao.ac.zaor 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_servicesYou will again be prompted for the password. The various services comprising the instrument will then restart. This lasts a few seconds a few seconds.** 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 stoppingthe 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:** Open a terminal and ssh to the instrument, running the command ssh shoc74in@shoc74in.suth.saao.ac.za. When prompted for the password, use the password for the 74in user.

** Run the command to restart the webserver: restart_services . This will take a few seconds to complete. The web server should be accessible again, as described above in the subsection "Camera won't switch on".

*** The filter wheel needs to be reinitialized. Go to the filter wheel tab, click the initialize button under the active wheel(s).esh the camera tab in the browser window*'''Camera tab is frozen:''' Occasionally (often at the start of the night) the first acquisition causes the camera tab to become unresponsive and 'freeze up'. The solution to this is to restart the services, as described above, then refresh the browser window and try again to restart the camera. This may need to be repeated several times before the camera starts.*'''Camera overheats:''' Should the camera over heat (this normally results from the air outlets being blocked), an alarm will sound from the camera. Unfortunately no indication or reason for the alarm will be given on the control software. In the case of this happening please shut the instrument down and contact electrical support immediately. THE CAMERA MAY NOT BE USED WHILE THE ALARM IS SOUNDING. ===GPS Issues===* '''The GPS time is not valid:''' If the GPS reports that the timing is not valid, check that it is able to see at least a few satellites, and that the signal quality is acceptable. Click on the Receiver Status button on the GPS tab, and a pop-up should appear, displaying the signal quality of the visible satellites. If each signal quality bar is zero, check that the dome is open; the antenna can't detect the satellites if it's closed. If there are a number of satellites visible, each with a reasonable signal, you might need to wait for a while for the GPS to rgister this and for the time to become valid. Normally this happens quite quickly, but for reasons we don't entirely understand, sometimes this can take five or ten minutes. It may also help to put the GPS into dynamic mode. Usually the GPS is set to operate in static mode, where the known position of the telescope is used. In dynamic mode, the GPS will first locate itself before getting a lock on the time. It may be that doing this will help to get a lock on the time. To put the GPS into dynamic mode, or to return it to static mode, use the command line interface described below. (One can also return the GPS to static mode by doing a "restart_services" call. To use the command line interface:** Fire up a terminal** $ ssh <user>@<shocndisbelief|shocnawe>.suth.saao.ac.za** $ shoc-gps-cli** The commands in the cli are help, status, pop, mask, bias, timing_mode and location. Use "help <command>" for more information.** The timing_mode option makes the GPS use static or dynamic mode.** The status option prints out all the current status reported by the GPS. If the command line tool reports an error while updating the status, simply try again until it works.** type "q" to exit the interface === Dealing with large FITS files===When taking very large data cubes, the file sizes may grow unmanageably large. On older 32-bit systems, FITS files were automatically truncated at 2GB and rolled over, but on the new 64-bit systems we use, this does not happen. Consequently, very large FITS files may be generated. To cope with these, there is a utility called split_fits.py. This script prompts for the name of a FITS file to split, and the number of chunks into which it should be split. It then splits the large file into this number of smaller files. The FITS header is identical in each of the resulting files.  The script split_fits.py is installed on both astro.cape and astro.suth, in the directory /usr/local/saao/bin. To run it, type split_fits.pythen when prompted enter the filename and number of chunks to produce. The output files are put in the same directory as the input file. === Rescuing Data===N. B. It is NOT normally necessary to run the data rescue script described below; the problem we had with the interface freezing up and acquisitions not being completed is now solved. Under normal operation, the system automatically updates the FITS cube header with supplementary information (filter, external trigger parameters, telescope pointing information etc.) and the moves the cube to the permanent (for the night) storage area. From time to time, it may be necessary to do this manually, using the rescue_data.py tool. In particular, if the system has frozen at the end of an acquisition, but before fixing the header and moving the data file, it will be necessary to perform this procedure. ''This procedure does NOT need to be done when stopping an acquisition; only if the interface hangs and you cannot do anything do you need to run this script.''* The procedure is to open a terminal and find your data in the spool directory on the instrument computer. It's stored in a directory named /data/spool/<CCYYMMDD><index>.<HHMMSS> (where index is the index, CCYYMMDD is the date and HHMMSS is the time the acquisition started). For example, /data/spool/201503250002.141026/ . * Caution: the date is the actual date valid when the acquisition was begun. If this was after midnight, the date will be incremented by one day. This is NOT the same as for the final FITS files; the final FITS file names are based on the date which was valid at the start of the night. Bear this in mind if you go back and try to rescue data which was acquired on previous night!* The procedure is done by using ssh to connect to the SHOC host computer: ssh shoc74in@shoc74in.suth.saao.ac.zaor ssh shoc40in@shoc74in.suth.saao.ac.zaor ssh shoclesedi@shoclesedi.suth.saao.ac.zaWhen 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 ls -l cd <CCYYMMDD><index>.<HHMMSS> ls -l* There should be files named data.fits and info.txt* The info.txt file contains the supplementary information.* Run the rescue utility: type 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, 74in or 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. = Technician's guide = '''IMPORTANT: If a SHOC machine is swapped out and installed on a different telescope, the website aliases (shoc74in and shoc40in) and data storage paths will be *incorrect*. Please notify the IT standby person before trying to use them. Currently, shocnawe is tied to the 74in and shocndisbelief is tied to the 40in.'''

== Technician's guide =====Mounting SHOC ===

===Testing the components ===

===Configuring the SHOC computer (not the web interface!)===

*** Use the up and down arrows to view each line of the file. Change the telescope name to the name of the currently used telescope: 74in or 40in. The instrument name should already be set to SHA sha or SHD shd (for shocnawe or shocndisbelief) and the log level should be info (not debug). In the editor, to remove a character type x . To add a character type a followed by the character to add, then hit esc to stop inserting. To exit, type :wq .

**Under /home/ccd/programming/shoc/bin/, type the following: ./restart_services ==Switching the SHOC computer to a new telescope==  Notify the IT standby person, so that the DNS records can be altered - they should use the information below. '''Normal Setup''' {| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shocnawe.suth.saao.ac.za| A| 10.2.2.89| 86400|-| shocndisbelief.suth.saao.ac.za| A| 10.2.2.88| 86400|-| shoc40in.suth.saao.ac.za| CNAME| shocndisbelief.suth.saao.ac.za| 360|-| shoc74in.suth.saao.ac.za| CNAME| shocnawe.suth.saao.ac.za| 360|-| shoclesedi.suth.saao.ac.za| CNAME| shocndisbelief.suth.saao.ac.za| 360|}  The shoc computer should be reachable by an '''alias''' containing the telescope name. 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: '''Instrument switched setup'''{| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shocnawe.suth.saao.ac.za| A| 10.2.2.89| 86400|-| shocndisbelief.suth.saao.ac.za| A| 10.2.2.88| 86400|-| shoc40in.suth.saao.ac.za| CNAME| shocnawe.suth.saao.ac.za| 360|-| shoclesedi.suth.saao.ac.za| CNAME| shocndisbelief.suth.saao.ac.za| 360|}  Both '''shocndisbelief''' and '''shocnawe''' machines move between the telescopes. The setup below is what needs to change when '''shocnawe''' is moved.  When e.g. the '''shocnawe''' machine is moved from the '''40inch''' to the '''74inch''', '''only''' change the '''40''' to '''74''' like below: '''From'''{| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shoc40in.suth.saao.ac.za| CNAME| shocnawe.suth.saao.ac.za| 360|} '''To'''{| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shoc74in.suth.saao.ac.za| CNAME| shocnawe.suth.saao.ac.za| 360|}  '''When you ssh after the CNAME change'''  Note: This change will result in a warning if someone tried to SSH into the machine - this is safe to accept. ssh ccd@shoc40in.suth.saao.ac.za Warning: the ECDSA host key for 'shoc40in.suth.saao.ac.za' differs from the key for the IP address '10.2.2.89' Offending key for IP in /Users/simon/.ssh/known_hosts:283 Matching host key in /Users/simon/.ssh/known_hosts:317 Are you sure you want to continue connecting (yes/no)? yes '''Possible CNAME changes'''  With the CNAME setup below, both the shocndisbelief and shocnawe can be connected in Lesedi. Please ask the IT standby person to help you with this DNS setup. Either SHOC instrument may be mounted on any of the three telescopes. '''How to configure'''{| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shoclesedi.suth.saao.ac.za| CNAME| shocndisbelief.suth.saao.ac.za| 360|} '''Can be added if required'''{| class="wikitable" border="1"|-! Name! Type! Content! TTL|-| shoclesedi.suth.saao.ac.za| CNAME| shocnawe.suth.saao.ac.za| 360|} ==Run the shocboxswitch.sh script when SHOC is moved between telescopes==  Run the script shocboxswitch.sh. The default option reverts to the standard mapping between SHOC computers and telescopes. If the default is not chosen, you'll be prompted for the name of the telescope the SHOC computer is being mounted on.* Check the log entry to make sure the configuration was changed to the telescope you chose. In a terminal type:  less /var/log/shoc-camera.log [[image:Camera-log.png|500px]] * Check and make sure that the configuration file points to the telescope name that you chose. In a terminal type:  less /etc/init/shoc-camera.conf * Take test data to make sure the data is written to '''/data/<telescope_name>/<instrument_name>/YYYY/MMDD/'''. ==Unmounting SHOC==* Before physically unmounting the instrument from the telescope, the SHOC control computer should be powered down. To do this: ssh ccd@shocnawe.suth.saao.ac.zaor ssh ccd@shocndisbelief.suth.saao.ac.za Then sudo shutdown -h now * Once the operating system has powered down, the power may be switched off and the instrument removed from the telescope.

===Technician's Troubleshooting guide ===

** Check that the location settings are correct. Click on 'receiver status' in the GPS tab and look at the latitude and longitude. The Sutherland Latitude is ~32 22 S while Cape Town is 33 56S. If the location is not corrrectcorrect, then the GPS will not find satellites and the correct location needs to be updated as described in the Configuring SHOC section.

*** change into directory /home/ccd/programming/shoc /bin and type the following: ./restart_services. It may be neccessary to do this a few times.*** If that does not work, under /home/ccd/programming/shoc /bin type the following to stop and start in separate steps: