Beam Line For Schools Shift Leader Instructions

This page is designed to help the Shift Leader of the BL4S experiment. Please be sure that you read the general shift instructions in page ShiftIntroduction.

The duties of the Shift Leader can be summarized as:

General structure of the shifts

The Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look above the shoulders of the shifters. You can see the duties of them from the page RunControlShifterInstructions and DetectorShifterInstructions.

There is a BL4S E-Log where everything should be documented during runs.

You can also check the BL4S Detector & DAQ Sharepoint to search for any kind of problem that may be solved before.

Editing White Board

The Shift Leader is responsible to update the WhiteBoard especially in the morning shift. You should update the name of the shifters for that day,

Vistar and Event Display

Vistar and Event Display data is provided by Online Monitoring software. As "daquser" you can start to generate events and calculate the DWC mean values in vistar change.

cd /afs/
./x86_64-slc6-gcc47-opt/vistar -p part_BL4S -t ReadoutApplication -v 1 -c config_file_name.cfg

Be sure that you use the right config file which you can find in White Board or E-Log. You can also change the comments section in Vistar Page by changing the file:


Running DAQ and Controlling HVs

The Shift Leader should also run the DAQ in monitoring mode for Error Report Service (ERS) (explained in RunControlShifterInstructions) and control the HVs (explained in DetectorShifterInstructions) and apply any name and voltage value change if needed.

Changing Configuration Files

P.S. This part was first written for the Detector Shifter but then revisited after the duty is given to the Shift Leader. That is why it is kept so simple.

Configuration files are needed for analysis, event monitor and event display. So it is important to keep the configuration files up to date.

IMPORTANT: Never delete or change config files directly. Always create a new copy and rename it properly and make any change on the new file.

Configuration Files can be opened by clicking on the "Configuration files" on your desktop:


You can see pedestal data file here that you did before.

If you click on the icon, the browser following browser will pop up:


Be careful that there are different type of configuration files. We can categorize them as:

File format Description Contains How/When to create Who is responsible
Pedestal folder The pedestal data files Pedestal data Created when pedestal program runs Detector Shifter
.cfg files Main configuration files The DAQ Channels and relevant files like calibration and geometry. Necessary file paths Created when there is a change in DAQ channels or geometry Shift Leader
.geo files Geomertry File Geometry of the detectors and beam line Created when there is a change in geometry. Shift Leader
.calib files Calibration Files Calibration constants of the DWC and Lead Glass Calorimeters Once at the beginning of the experiment DAQ Expert
.txt files Data File Names Names of the files with the relevant tags for analysis After each run DAQ Expert

As you can see from the table you are only responsible from the .cfg and .geo files. Do not change or remove any other file.

You should create a .cfg file if you change a channel in the DAQ system (the channels on VME). The explanation of the variables are written in the file.

  • First find the last config file. It will be named as example: 1407238700_T9_05082014.cfg
  • Here the first number "1407238700" is unix time stamp. Unix time stamp means "system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC) on January 1 1970". Run numbers are also defined by a unix time stamp.
  • Second word "T9" is the tag. If you are making a special run with a special configuration like Calibration or Test, you can use that tag.
  • The last number "05082014" is the date as 05.08.2014.
  • Copy and Paste the most recent config file. Then rename it.
  • While renaming delete "(copy)" at the end.
  • You can check the current unix time stamp from the site: . Then remove the time stamp in the copy file and copy the time stamp from this website instead.
  • Change the date at the end.
  • Now you have a brand new config file.
  • Double click on your new config file and you will see a page like on the left below.
  • Now find the channels that you changed and write the new values and then save and quit.
  • Make an e-log that you changed the config file, containing the new name of the config file and why you need change it.
cfg_file.png geo_file.png

If you changed anything about the geometry, you should create a new geometry file. You can do the following steps:

  • Find the most recent .cfg and .geo files.
  • Copy them and rename them as explained above. (In the geometry file you do not need any unix time stamp).
  • Open the new config file and change the "GEOMETRY FILE NAME" with the new geometry file name you created.
  • Save and quit the config file.
  • Open the new geometry file.
  • Apply any change you made in geometry.
  • Save and Quit.
  • Make an e-log that you changed the config file and the geometry, containing the new names of the files and why you need change it.
-- SaimeSarikaya - 26 Aug 2014
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2015-03-19 - TimBrooks
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    BL4S All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback