Kirrily Rule 2013-04-09 16:47 To start running Gumtree, double click on the icon on the desktop. Two windows will automatically open and you will be logged in as “Manager”. (Why manager, why not user???) This quick start guide assume SICS is configured for your experiment, and that it is running. If it is not, go to the section

Open one of the previous batch files by double clicking on a .tcl file in the Project Explorer window. This will appear in the Tree View panel above. You can edit this and save it with a new file name (File -> Save as). To run this file, drag it into the Buffer Queue. You can either press Play, or Validate to check the file. All commands listed with > should be typed into the SICS command line in Gumtree, or in the black sicsclient window opened via PuTTy (Taipan ICS profile). Either of these will drive the instrument. Only those commands executed from Gumtree will be printed into the Log file.

In the Scripting control window, choose Load Script -> analysis -> live data to show a live plot as the counts are taken. In this window, you can tick (or untick) autofit (for a Gaussian fit), and normalise (which normalises to time) You can also change which detector you wish to see the counts in: bm1_counts = monitor bm2_counts = detector You can also control the fitting range in this window You can add past data sets to the Plot 2 window (beneath the liveplot window). Highlight the plots you wish to add, be sure you have the correct detector choice and x-axis parameter selected, then click on the button “Import Data Files to Plot2”. These can also be removed for the plot. There is currently no fitting procedure for Plot2. At any time, to interrupt SICS you can click on the red button, or type >>INT1712 3 Before you can control the instrument, there are 2 programs that need to be running, SICS and Gumtree. SICS should already be configured and running by the local contact. This procedure allows you to check this. On the Microsoft Windows computer in the instrument cabin, find the putty program.

Choose the ICS computer from the list of Saved Sessions Load and open Use your NBI username and password, supplied by the Bragg Institute User Office You will now have a command prompt to a Linux operating system Normally SICS will be running. You can check if SICS is running by using the PuTTy window and at the Linux operating system command prompt type > runsics status If the status shows that SICS is not running, or if there is a change in the SICS configuration files e.g. a piece of sample environment has been added, you should contact your local contact. If the local contact has confirmed it is OK to restart SICS, then in the PuTTy window type > runsics stop > runsics start In the previous section, you logged into the ICS (instrument control server) computer using putty. At the Linux operating system command prompt, you will run a program that will give you a sics command prompt. For most cases, you won't have to do this. A SICS command prompt is available in Gumtree. At the Linux operating system command prompt type > sicsclient You should see OK on the screen. You now have a SICS command prompt. It may look strange since the cursor will be on a blank line. You will not have access to the Linux operating system command prompt until you log off. Next step is to login to sics by typing > user password where user is literally the word "user" and the password will be supplied by the local contact You can replace user with spy. The spy login provides read-only access to SICS.

Normally, Gumtree will be connected to SICS, as in the figure above. In Gumtree you reconnect to SICS if you restart SICS. This is done by clicking on the little man at the bottom of the Gumtree screen and log in to SICS. He will be standing still, and you will see the word Disconnected when not connected. He will be running when connected as in the figure. You will then need to start a new Sics terminal in Gumtree. From the left screen, in the project explorer window, Right click on SICS and choose the option to start a new “SICS telnet terminal”. Reconnection won't work properly if SICS has changed configuration e.g. you've added a piece of sample environment. In this case, when you restart SICS you should also restart Gumtree When using the 12T magnet on TAIPAN, you must work in fixed Ki mode, as the magnet is too heavy to move M2. Consider the energy transfer range required to determine the appropriate Ei for these experiments. After discussing your instrument preferences with your local contact, they will align the spectrometer in the following way: Drive the spectrometer to the required incident energy (for elastic mode) = e.g. 14.87meV Drive the analyser arm to the straight-through position (s2=0, a1=0, a2=0, atrans=19) Visually check the straight-through arm and change any motors accordingly Place the Ni sample on the sample stage, and Borated Al sheets over the analyser collimator. (the detector saturates at ~35,000 counts/sec) Check M1 alignment with a rocking scan Check S2=0 alignment with a rocking scan Check A2=0 alignment with a rocking scan Remove the Al attenuator and insert collimators if they need changing Perform the Ni powder calibration, using 5 peaks From the least squares fitting of these peaks, update the new M1 offset, M2 offset and S2 offset. With the spectrometer at S2=-50, and atrans=0 (to view the Vanadium incoherent peak from the Ni sample can), perform an A1 scan and an A1/A2 scan around the elastic position. Perform an En scan (where Ei will move if Ef is fixed). Here the FWHM of the peak will give you the resolution of your instrument. At the beginning of an experiment load the “Experimental setup” script (in the scripts window, right screen) to list the most important configuration identifiers for the experiment. These should appear in the header lines in your data files. For instance, these include: Proposal number and title User’s name, and research team present Local contact’s name Sample information including number of samples and sample environment requirements Particular instrument setup features (scattering sense, collimation, filters, slits etc) Next the UB matrix needs to be set. To do this, you need to input the cell parameters and at least 2 reflections which will define your scattering plane. These can be calculated for your system using the file “/home/taipan/calculatedDspaceTAIPAN.xls” or something similar, such as the ICSD website. > tasub listub shows the current UB matrix, cell parameters and reference peaks > tasub cell a b c alpha beta gamma input new lattice parameters > tasub addref qh qk ql adds a new reflection to the list when Taipan is at the reflection > tasub addref qh qk ql a3 a4 sgu sgl ei ef adds a new reflection from a calculation > tasub addauxref qh qk ql adds a new reflection where S2 is calculated from the lattice parameters only. This will also calculate the relative S1 positions > tasub del num deletes one of the previously stored reflections > tasub listref lists the reflections that have been input > tasub makeub 1 2 calculates new UB matrix from reflections 1 and 2 > tasub calcang qh qk ql ei ef calculates reflection from UB matrix – be careful when changing lattice parameters, as this command won’t use them! Output: M2 S1 S2 sgu sgl A2 For Ei = Ef = 14.87 meV > tasub cell 5.011 5.85 10.353 90 92.4 90 > tasub calcang 1 0 0 14.87 14.87 (calculated S2 = 27.1) > tasub calcang 1 1 0 14.87 14.87 (calculated S2 = 35.9) > tasub calcang 0 2 0 14.87 14.87 (calculated S2 = 47.3) Drive the instrument to the calculated S2 value of a particular peak. The other motor positions are not correctly set at this point. This will also give you a relative s1 position between the peaks. Scan S1 until you find the peak. > bmonscan clear > bmonscan add S1 -10 0.2 (motor name, starting point, step size) > bmonscan run 60 timer 5 (scans 60 points, for a time of 5 seconds per point) OR > runscan s1 -10 0 101 time 5 (motor, start, stop, # pts, time (the mode in secs)) (this does not work for multiple motors yet) (This step should hopefully be replaced by the differential scan, or the rate-meter) Once the peak position (S1) has been optimised, scan sgu and sgl > runscan sgl -10 10 21 time 1 > runscan sgu -10 10 21 time 1 Once the peak has been optimised with SGU and SGL (and you are sitting at the peak position!!) you can set this as one of your reference peaks, where the current motor values define the peak position. > tasub addref 1 0 0 Calculate the values of S1 and S2 for the next peak – use the > tasub calcang qh qk ql ei ef command to see the relative values of S1 and S2 as calculated from the lattice parameters! Repeat for at least one other peak, preferably one orthogonal to the first. > tasub addref 0 0 1 > tasub listref (to see the observed peaks in your list (e.g. number 4 and 5)) > tasub makeub 4 5 (this used peaks 4 and 5 to calculate the UB matrix) > tasub update > tasub listub Once this has been set, then you should be able to drive your spectrometer to any accessible qh, qk, ql and en. At the end of each change, be sure to type > tasub update Once your sample has been aligned, add the PG filter to the instrument. You could test the effectiveness of the filter by scanning a peak that will display higher order scattering – e.g. (½ 0 0) which does not exist except from higher order scattering from the (1 0 0 ). Sometimes you might want to add an additional filter. Finally you can scan your slits to reduce the background scattering. > runscan pa_left -15 -2 27 time 1 (scans 27 points, for a time of 1 seconds per point) After this, consider if you need to add more shielding to the detector drum or any other part of the instrument (e.g. manual slits on analyser arm, additional PG filters). When the sample temperature has stabilized at the required temperature, the low temperature lattice parameters can be checked. For example, a tetragonal system in the ab-scattering plane can be optimized as follows: > drive qh 5 qk 0 ql 0 en 0 > runscan qh 4.985 5.015 31 time 5 The centre of this scan should be close to 5, but could be shifted. This will be the fit value from the scan. Then you can change the a lattice parameter accordingly in tasub anew=aold(peakcalculated/peakcentre from scan) replace with jpg of equation??? MathML doesn't transform to pdf using oxygen xslt. > tasub cell a b c alpha beta gamma The next peak can be aligned in the same way > drive qh 0 qk 3 ql 0 en 0 > runscan qk 2.985 3.015 31 time 5 Find the centre of this scan then you can change the b lattice parameter accordingly in tasub. Also, while sitting on the peak, perform the > tasub addref 0 3 0 If your sample is cubic (and remains cubic at low temperatures) and you are in the HK0 scattering plane, then the lattice parameters are best set with a peak that involved both H and K – for instance the 110 peak. Make sure after you have changed your lattice parameters, and both peaks have been added to the reference list that you remake your ub matrix! Batch files are stored in /usr/local/nbi/sics/taipan/batch and are just text files with the extension .tcl. You can edit these in a text editor, or the editing panel of the left window. Your file, filename.tcl can be run by dragging and dropping into the Buffer Queue and then run by pressing the “Play” button. You can also queue additional files to run by dragging and dropping them into Batch Queue window. These will then be run sequentially. Files can be removed and edited or replaced as desired from the Batch Queue window. Once the file has been read into the buffer, it can no longer be edited. For this reason it is recommended that multiple short files are created. These can be run multiple times if necessary. To check your script, you can validate it using the Validation tab in the Buffer Queue. Drag your file into the Validate window and click on Validate. Information about your file will scroll through the log screen. Use this to see if any errors or motor limits have been reached. # This is a comment and will not be executed drive qh 2.5 qk 0 ql 3.5 en 32 bmonscan clear bmonscan add qh 2.5 0.1 bmonscan run 31 monitor 1000000 # This is another comment with important information drive qh -2.5 qk 0 ql 3.5 en 32 bmonscan clear bmonscan add s2 -55 -0.1 bmonscan run 31 monitor 1000000 clientput [m2 absenc] # (prints out the m2 absolute encoder value) There are new log files written for each experiment. These are located in: J:\data\current\reports\exp#\LogFile.txt on the Microsoft Windows DAV computer. These will be updated as the experiment progresses and should include both commands from the command line window and the batch file. Use a program such as WinSCP to transfer files to your computer. The files will be in /experiments/taipan/data/current/reports/exp#/LogFile.txt. These files are archived to a proposal directory at the end of each cycle e.g. /experiments/taipan/data/proposal/proposal#/reports/exp#/LogFile.txt The typical closed cycle cryo-furnace used on Taipan is cryo-furnace #1 (CF1). This uses a Lakeshore 340 controller. SICS is capable of reading and driving the temperature on this device. The Moxa box must be installed, and connected to the Lakeshore hardware. In the future, the Lakeshores will have a dedicated Moxa box. > tc1_driveable2 shows the sample temperature from channel A > run tc1_driveable 200 drives the regulation temperature (B) to 200K > wait 600 shows wait in seconds > drive tc1_driveable 200 drives the regulation temperature (B) to 200K and waits for it to be within 1K of this value before continuing to the next command >sct_ls340_tc1 send "RANGE?" this will query the heater power range – 0 = off, 5 = 100W >sct_ls340_tc1 send "RANGE 1" this will set the heater power range. Set to a value between 0-5 The fine control of the temperature parameters, such as tolerance, heater power range, etc, can be adjusted by clicking on the SIC Server tree view. Alternatively you can use certain commands listed below in a batch file: Check the heater power range of the closed cycle. To heat the sample relatively quickly you need to have the heater range to 5. To reach base temperature (10K or less), the heater range should be set to 4 or lower.

These detailed commands can be used (also in batch files) to control the temperature parameters: > hlist –val /sics/tc1/sensor shows set points and sensors etc > hget /sics/tc1/sensor/setpoint1 to show the temperature > hset /sics/tc1/sensor/setpoint1 200 to set the temperature to 200K – there is no blockage of the drive functions when this command is used > > hset /sample/tc9/Loop1/setpoint 200 to set the temperature of the 12T magnet to 200K > hget /sample/tc9/Loop3/sensor to read the temperature of the 12T magnet > hset /sics/tc1/heater/heaterRange 5 for 100W power, or 4 for 10W power > hset /sics/tc1/control/tolerance 1 5 to set the tolerance of 5K to reach desired temperature Sics and gumtree can also control the high voltage rig which is also set up on CF1. The following commands will be useful > pulseron turn on HV > pulseroff turn off HV > getvolt > setvolt 100 sets the voltage to 100V Once you have set your slits, turn the motion control OFF (on the same box as the shutter control) and unplug the 4 cables. Turn the motion control ON again. The slits are now in a safe mode for driving the field. To perform field ramps safely (without risk of quenching), you should put the beam stop down. To do this, turn the motion control OFF (on the same box as the shutter control), ramp the field into persistent mode and then turn the motion control ON again. Once you have reached your new field, drive to a new Q-E position to ensure that all the motors still behave correctly after the motion OFF. If not, you might have to reset particular motors: > m1 send RS (this will reset the m1 motor controller) To keep the beam stop down Turn off motion control Close valve located at the base of the beam stop Turn on motion control There are two parameters you will need for driving the s1 via the sample stick. vs1 drives the motor from the command line, while dummy_s1 is in the UB matrix and scan parameters. So use these in the following way: > drive vs1 30 (in the command line – this drives the motor to a value) > runscan dummy_s1 25 35 101 time 1 > runscan qh When running a powder sample in the magnet, fix dummy_s1 > dummy_s1 fix 1 (> dummy_s1 fix 0 to unfix) On ics1-taipan, you'll be editing SICS configuration files so that SICS will load the driver for a device. The editor is vim. This process will be done through a graphical interface in the future. :colorscheme ron Change the color scheme. This make editing easier /tasub This searches for the string “tasub” i insert mode. Add text. r replace. Replace a character. x delete ESC key escape out of the current mode When using the Lakeshore 340, various things need to be changed in the configuration files. This should only be done by the local contact. > cd /usr/local/nbi/sics/taipan/ > vim extraconfig.tcl Remove both the # in the following four lines #catch #add_sct_… # hsetprop #}msg Save and quit by typing :wq > runsics stop > runsics start When using the High voltage setup, various things need to be changed in the configuration files. This should only be done by the local contact. > cd /usr/local/nbi/sics/taipan/ > vim extraconfig.tcl Remove both the # in the four lines # Make AsyncP… # Make AsyncP… # pulser delay # pulser timeout Save and quit by typing :wq Make sure that the IP on the function generator is set to the following: 137.157.203.149 Get an electrician such as Dan Bartlett to confirm the setup is safe! > runsics stop > runsics start When using the 12T magnet, various things need to be changed in the configuration files. This should only be done by the local contact. Turn on the magnet laptop – check that the Ethernet cable and grey cable are connected. Click on “SICS oxford instruments” to bring up the front panel. Click on ITC503 Front Panel open a Putty terminal > cd /usr/local/nbi/sics/taipan/server > sudo vim taipan_configuration.tcl On line 59, remove the # from # fileeval ../aerotech.tcl On line 61 is s1 in the TASUB command. Change this to vs1. Save and quit by typing :wq If you made a mistake, quit without changing by typing :q! and start again. > cd config/motors/ > sudo vim motor_configuration.tcl /magnet Search for the string “magnet” The following {0} should change to {1} for the magnet: If {0}{ # Convert magnet angle to s1 angle VarMake vs1speed float user vs1speed 1 … } } Save and quit by typing :wq > cd /usr/local/nbi/sics/taipan/ > vim extraconfig.tcl #--------------- # 12T magnet #--------------- Remove the # in the following lines (choose which temp controller method you require – running with the Mercury, or as Legacy mode) #add_oxford_magnet "magnetic" 137.157.203.153 #add_oxford_mercury "tc9" 137.157.203.151 7020 2.0 "\r" #add_itc500 tc1 137.157.203.151 7020 2.0 "@8" This is for running in Legacy Mode (to look like ITC500) Save and quit by typing :wq > runsics stop > runsics start When using the 3He setup, various things need to be changed in the configuration files. This should only be done by the local contact. When using the 3He setup, you need to switch to the appropriate speeds and accelerations for the elongated instrument. To do this, in the PuTTy window, go to > cd /usr/local/nbi/sics/taipan/ > vim taipan_setup.txt Change the 0 to 1 to turn on this file Save and quit by typing :wq > runsics stop > runsics start Alerts the user to known operational problems What to do if things go wrong