Beam Line For Schools Run Shifter Instructions

This page is designed to help Run Control Shifter of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction.

The duties of the Run Control Shifter can be summarized as:

Checking Beam Status

Run Control shifter is responsible of checking the beam status and deciding on the to start and stop the new run according to it. There are two ways of checking the beam status.

From CPS Vistar Page

CPS stands for Cern Proton Synchrotron. You can observe the status of the CPS in all the experimental areas from CPS Vistar page. In big experiments like ATLAS and CMS, they are also using Vistar Pages to observe the status of the LHC Beam. Before staring and stopping a run and during your shift, check the monitor in the control room or the web page: You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"


There is beam if the value near EASTA_ should be ~30, and you should see a image with rising and falling signals as seen in above image.

You can find the detailed information in page:, if you would like to learn more.

From BL4S Vistar Page

For BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status".You will see a screen like:


You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values. The units used here is "cm" for the mean values. The mean values sould be a a couple of cms and the counts should be on the order of the number of events read for regular runs. Discuss any big change with the shift leader.

Run Control (DAQ)

The main responsibility of the run controller shifter is to start and stop the run. During the run you should watch the Error Report Service (ERS). In BL4S experiment, we are using the same data acqusition software that is used in ATLAS experiment. Here "Run" is defined as the data taking session. Once you changed the configation or beam status then you should stop the current run and start a new one. The Shit Leader will help you about when to start and stop the run.

To open the BL4S DAQ Software, you can click on the icon on your desktop.

Starting DAQ

(TODO: BL4S Logo here!) bl4s_logo.png

If you have troubles with openning the DAQ (Data Acqusition) software, you can ask shift leader for help. You will see a page like below:


Lets have a look at what we can change and observe on the software:

  • At the bottom, you will see Error Report Service (ERS). If there is any warning or error at the beginning or while taking data, first check the BL4SWhiteBoard then if you could not any information on the whiteboard, discuss it with the shift leader.
  • In the middle and on the right, you will see informations about the run segments, apps etc... You should not change anything here.
  • On the left, you will see in order:
    • Run Control State (will be explained in below in starting a run part)
    • Run control command (will be explained in below in starting a run part)
    • Beam Stable (should always be green)
    • Run Informations and settings
First checkthe "Settings" tab in "Run Informations & Settings" part on the left. It looks like:


Here we have seetings:

  • Max Events : If you are taking data, it should be zero which means infinite.
  • Run Type: You should select a run type here. It can be either "Physics" or "Calibration"
  • Beam Type: You select the beam type.
  • Beam Energy: You should write the beam energy you are using here in units of GeV.
  • Tier0 Project Name : Do not change it.
  • File Name Tag: you should write a proper file name tag here depending on the type on the run. For example: lgcalibration, dwccalibUD, PionDecay, CalorimeterTest etc.
  • Recording: You should "Enable" it!
After you adjust the settings press "Set Values Button".

At ERS in the botton you will see an information as "Run settings have been correctly updated". If not, it means that you are making something wrong like using forbidden characters in tag or foget to select something.

Starting a Run

Now you are ready to take data. After you finish the settings properly told above you can start a run using the "Run Control Commands" section on the left top part. At first the Run Control State should be NONE and only initialalize button is enabled. Then you should follow the following steps by pressing the buttons:

  1. INITIALIZE : Run Control State will be INITIAL (from NONE)
  2. CONFIG : Run Control State will be CONNECTED. A pop up will appear saying "Remember to check the Run settings before starting the run". It is the last time you can change the run settings. So it is advised to check the run settings once here!
  3. START : Run Control State will be RUNNING.

All the segments in run Control and Root Controller should be green now. Now you have a new run! Congragulations!

Never forget to check ERS while starting the DAQ. If there is an ERROR or WARNING check the BL4SWhiteBoard and discuss with the shift leader.


You can find run information on "Information" tab under "Run Information & Settings"

After you start a run make an e-log (with the run number at the subject) about the new run, containing information:

  • The start time.
  • The run number
  • The file_tag_name you selected
  • Run Type
  • The Trigger type: you should learn it from the Detector and DAQ shifter.
  • Beam Type/Status/Intensity : From vistar page
You can find an example new run log at the BL4S E-Log.

Counters and ERS during run

During a run observing the system is very important. You should check the ERS from time to time. If any ERROR not indicated in BL4SWhiteBoard appears immediately discuss it with the Shift Leader and make an e-log or add the error message on the run log about it.

You should also check the counts during a run. You can check it in two places:

You can directly check the "Counters" tab in "Run Information & Settings". Here rate should be around a couple of KHz (?) and the number should increase. If the rate is lower or the number is not increasing, Check the beam status in Vistar Page. If the beam is fine, then there is a problem in data taking and you should immediately take action with the shift Leader.


You can also check the rate by loading DFPanel. Simply select DFPanel under Load Panels on the top. Another tab will appear on the Run Control Panel. Select the DFPanel then select tick LV1 as in the screen below.


You can see the spills during the run on this panel. If there is no beam it will look straight.

Stopping a Run

When we want to change beam parameters or trigger logic or detector configuration, we should stop the run before. The Shift Leader will tell you when you should stop the run. Before stopping the run, open the e-log you make for a new run and edit it. Add the number of events recorded and the stop time to your log. The go through the steps;

  1. STOP
After you make the changes needed you can start a new run.

Running event display

While taking data, we would like to see how the events look like. Event Display is the sofware that is used to see the signals on the detectors. All the experiments have their own event displays to understand the events taken during the experiment. You can see the event display of ATLAS and CMS for higgs candidate events below:

ATLAS_higgs_candidate.png CMS_higgs_candidate.png

As you can realize from the event displays, it is much more easier to understand the tracks and the enegy measuremets by eye. But to understand and observe new physics, with only event displays for high rates.

In our project we have out own Event Diplay. You can open it by clicking on the icon at your desktop "BL4S Event Display". Before starting event display, please ask the Shift Leader for the configuration.


Then, you will see the following screen:


With your mouse wheel, you can zoom in and out and by hold on your mouse wheel you can shift the display. You can also enable and disable the events and see only detectors. To open a new event, close the two open windows and click on the BL4S Event Display icon once more.

-- SaimeSarikaya - 12 Aug 2014

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng ATLAS_higgs_candidate.png r1 manage 4575.9 K 2014-08-20 - 16:34 UnknownUser  
PNGpng BL4S_DAQ.png r1 manage 68.4 K 2014-08-20 - 14:07 UnknownUser  
PNGpng BL4S_DAQ_openning.png r1 manage 68.4 K 2014-08-20 - 14:09 UnknownUser  
PNGpng BL4S_DAQ_running.png r1 manage 65.1 K 2014-08-20 - 13:58 UnknownUser  
PNGpng CMS_higgs_candidate.png r1 manage 289.1 K 2014-08-20 - 16:34 UnknownUser  
PNGpng Screenshot-5.png r1 manage 25.6 K 2014-08-20 - 17:33 UnknownUser  
PNGpng cps.png r1 manage 11.4 K 2014-08-18 - 17:26 UnknownUser cps vistar
PNGpng daq_counters.png r1 manage 2.9 K 2014-08-20 - 13:58 UnknownUser  
PNGpng daq_information.png r1 manage 4.0 K 2014-08-20 - 13:58 UnknownUser  
PNGpng daq_settings.png r1 manage 4.8 K 2014-08-20 - 13:58 UnknownUser  
PNGpng df_panel.png r1 manage 65.3 K 2014-08-20 - 13:58 UnknownUser  
PNGpng vistar_bl4s.png r1 manage 172.5 K 2014-08-18 - 18:11 UnknownUser bl4s vistar page
PNGpng xfce4_xicon1.png r1 manage 3.9 K 2014-08-20 - 17:32 UnknownUser  
Edit | Attach | Watch | Print version | History: r14 | r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r5 - 2014-08-20 - unknown
    • 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback