RCE < ATLAS/PUUKA

ATLAS/PUUKA Web>Tasks>Modules>RCE (2016-02-18, KennyWraight) (raw view)
---+ Glasgow !RCE Info

---+++ Set-up

See here for hardware set-up: RCESetUp

---++ Running the !RCE software

Make sure to have set-up symbolic link to !RCE area, i.e. <code>ln  -s /afs/phas.gla.ac.uk/group/atlas/rcepixel01/ibldaq/IBLDAQ-0-0-0 daq </code>
   * Navigate to the directory %GREEN% ~/daq/rce %ENDCOLOR% %BLUE% 
      * $ cd daq/rce %ENDCOLOR%
   * Open C shell %BLUE% 
      * $ tcsh %ENDCOLOR%
   * Run set-up script %BLUE%
      * $ source scripts/setup_rce-04-00-01.csh %ENDCOLOR%
   * Start servers %BLUE%
      * $ ipc_server &
      * $ rce_ipc_server &
      * $ rce_is_server & %ENDCOLOR%
   * You can check that the servers are running using the command %BLUE%
      * $ rce_ipc_ls %ENDCOLOR%
   * Load !RCE (!RCE ip address is 10.129.3.11) %BLUE%
      * $ rce_load 10.129.3.11 %ENDCOLOR%
   * Open GUI %BLUE%
      * $ calibGui %ENDCOLOR%
   * Further info on [[https://twiki.cern.ch/twiki/bin/viewauth/Atlas/RCEPixelLab][RCEPixelLab]]

---++ !RCE calibGui

!CalibGui is the software used to perform tunes, run scans and test devices.

---+++ Before running a scan

Once GUI is open…
   * In "Scan" tab
      * Set directory to save root files by clicking "Browse" button adjacent to "Data Dir" in "Global Module Configuration area", e.g. /afs/phas.gla.ac.uk/data/atlas/upgrade01/rce-tests/
      * Select Scan Type of scan from drop down list in "Scan Config" area
      * If required choose a Prim list by "Load Primlist" button in Prim List area
         * <b>NB</b> prim lists have priority over any selected scan. Also, prim lists must be cleared before loading a new list or running single scan.

   * In "Config Halfstave" tab (4 provided, choose whichever is appropriate) 
      * Choose a "Frontend: are and set parameters for communication with chip
      * Select config file from "Choose Config", and browse to file, e.g. /afs/phas.gla.ac.uk/data/atlas/upgrade01/rce-tests/KateRCE/THRESHOLDX/config
         * NB check references to masked directories in config file are to correct place (i.e. current directories)
         * for valid config rations the "Valid" check will be ticked
      * Set inlink/outlink to valid parameters, and correct !RCE (see map !ADD LINK LATER)
      * make sure the "Included" check is ticked, else the communication will not be attempted
	
   * In "Plots" tab 
      * The output of them most recent scan is viewable in GUI 
         * Usual root rules apply, i.e. zoom, right-click, etc. 

---+++ Running a scan

Basic checks
   * Is the chip powered?
   * Is the chip biased (do you want it biased?)?
   * Is the chip connected?

Select Scan/Primlist

View scan results in the "Plots" tab

---++Test/Scan Data

   * Occupancy plots and histograms can be viewed in the plots tab of the calibGui. %BLUE%

   * Data is saved in %GREEN% ~/calibData %ENDCOLOR% directory.  %ENDCOLOR%

   * There are root scripts in the %GREEN% ~/root_scripts %ENDCOLOR% directory for plotting and analysing analog, digital and threshold scan data. %BLUE%

   * To run the analysis ROOT script open file %GREEN%  run_analysis.C %ENDCOLOR% in an editor (emacs, geany). Change the run number for the Analogue, Digital & Threshold Tests on lines 5 to 7. Open ROOT in the calibData folder and run the %GREEN% run_analysis.C %ENDCOLOR% script. %ENDCOLOR%

---++ IV Scan %BLUE%

   * There is a c++ script for running an IV scan on the pixel detector using a Keithley 2410. The script is located in ~/Projects/IVProgram %ENDCOLOR%
   * To compile and link the IV scan script do: %BLUE%
      * sudo g++ -m32 main.cpp -o iv_scan /usr/local/natinst/ni4882/lib/cib.o -ldl %ENDCOLOR%
      * To run iv_scan do: %BLUE%
         * cd ~/projects/IVProgram
         * ./iv_scan %ENDCOLOR%

---++ !RCE calibGui

---++ FE-I4A Config Files

---++ Background Material


-- Main.AndrewStewart - 2013-07-04
Topic revision: r21 - 2016-02-18 - KennyWraight
ATLAS/PUUKA