Difference: RunControlShifterInstructions (1 vs. 14)

Revision 142015-03-19 - TimBrooks

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools: Run Control Shifter Instructions

Changed:
<
<
This page is designed to help the Run Control Shifter of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping a run, etc.
>
>
This page is designed to help the Run Control Shifter of the BL4S experiment. Please be sure that you read the general shift instructions in page ShiftIntroduction. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping a run, etc.
  The duties of the Run Control Shifter can be summarized as:
Line: 15 to 15
 General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In the control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you have a problem that you could not solve, you can always call the on-call experts. Other than starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.

  • Check the beam status from vistar pages. Is there any stop of the beam? Are the numbers in BL4S Vistar Page steady?
Changed:
<
<
  • Check Error Reporting System (ERS) under the DAQ. Is there any Error or Warning other than the ones mentioned in BL4SWhiteBoard?
>
>
  • Check Error Reporting System (ERS) under the DAQ. Is there any Error or Warning other than the ones mentioned in WhiteBoard?
 
  • Check the "Counters" tab in "Run Information & Settings", Is it increasing when there is beam?
  • Check the DFPanel under "Run control Panel". Can you see the spills? If it is constant for a while, discuss with the shift leader.
  • Run the Event Display. Do the Events make sense? If you see any anormality discuss with the Detector Shifter.

Revision 132014-09-05 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools: Run Control Shifter Instructions

Line: 38 to 38
 

From BL4S Vistar Page

Changed:
<
<
For the BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:
>
>
For the BL4S experiment, we have our own vistar page at http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=T9_CPS_EAST. You will see a screen like:
  vistar_bl4s.png
Changed:
<
<
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes in the mean and sigma values of all three DWC. The units used here are [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
>
>
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes in the mean and sigma values of all three DWC. The units used here are [cm] for the mean and sigma (standard deviation) values. The mean values should be +/-40mm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
 

Run Control (DAQ)

Line: 144 to 144
  As you can realize from the event displays, it is much more easier to understand the tracks and the energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.
Changed:
<
<
In our project we have out our 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.
>
>
In our project we have out our Event Diplay. You can open it by clicking on the icon at your desktop "BL4S Event Display". Please check with Shift leader that there was no change in the geometry.
 
Changed:
<
<
xfce4_xicon1.png
>
>
event_disp3.png
  Then, you will see the following screen:
Changed:
<
<
Screenshot-5.png
>
>
event_disp2.png
 
Changed:
<
<
With your mouse wheel, you can zoom in and out. By clicking and holding 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.
>
>
  • When the event display opens, from menu go to Detector->Download Geometry
  • Then to load the next event, click Download Event, or press F5.

The camera controls are explained in the program on the right.

  -- SaimeSarikaya - 12 Aug 2014 -- CenkYildiz - 20 Aug 2014
Line: 170 to 173
 
META FILEATTACHMENT attachment="BeamlineCERN.jpg" attr="" comment="" date="1408706274" name="BeamlineCERN.jpg" path="BeamlineCERN.jpg" size="74374" user="joos" version="1"
META FILEATTACHMENT attachment="BL4S_DAQ_openning.png" attr="" comment="" date="1409137663" name="BL4S_DAQ_openning.png" path="BL4S_DAQ_openning.png" size="74864" user="ssarikay" version="1"
META FILEATTACHMENT attachment="pilot.jpg" attr="" comment="" date="1409141817" name="pilot.jpg" path="pilot.jpg" size="371164" user="ssarikay" version="1"
Added:
>
>
META FILEATTACHMENT attachment="event_disp3.png" attr="" comment="event display icon" date="1409919845" name="event_disp3.png" path="event_disp3.png" size="50454" user="cyildiz" version="1"
META FILEATTACHMENT attachment="event_disp2.png" attr="" comment="" date="1409920669" name="event_disp2.png" path="event_disp2.png" size="76701" user="cyildiz" version="1"

Revision 122014-09-01 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Changed:
<
<

Beam Line For Schools Run Control Shifter Instructions

>
>

Beam Line For Schools: Run Control Shifter Instructions

 
Changed:
<
<
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. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping run, etc.
>
>
This page is designed to help the Run Control Shifter of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping a run, etc.
  The duties of the Run Control Shifter can be summarized as:
Line: 12 to 12
  pilot.jpg
Changed:
<
<
General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you face with a problem that you could not solve, you can always call the on-call experts. Other that starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.
>
>
General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In the control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you have a problem that you could not solve, you can always call the on-call experts. Other than starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.
 
  • Check the beam status from vistar pages. Is there any stop of the beam? Are the numbers in BL4S Vistar Page steady?
Changed:
<
<
  • Check ERS under the DAQ. Is there any Error or Warning other than the ones mentioned in BL4SWhiteBoard?
  • Check the "Counters" tab in "Run Information & Settings", Is it increasing when there is a beam?
>
>
  • Check Error Reporting System (ERS) under the DAQ. Is there any Error or Warning other than the ones mentioned in BL4SWhiteBoard?
  • Check the "Counters" tab in "Run Information & Settings", Is it increasing when there is beam?
 
  • Check the DFPanel under "Run control Panel". Can you see the spills? If it is constant for a while, discuss with the shift leader.
Changed:
<
<
  • Run the Event Display. Does the Events make sense? If you see any abnormality discuss with the Detector Shifter.
  • Check the BL4S E-Log if there is any update from other desk.
  • If there is any problem you face, make an e-log about.
>
>
  • Run the Event Display. Do the Events make sense? If you see any anormality discuss with the Detector Shifter.
  • Check the BL4S E-Log if there is any update from the other desk.
  • If there is any problem you have, make an e-log about.
 
  • Have Fun!

Checking Beam Status

Changed:
<
<
Run Control shifter is responsible of checking the beam status and deciding on when to start and stop a run. There are two ways of checking the beam status.
>
>
The Run Control shifter is responsible for checking the beam status and deciding on when to start and stop a run. There are two ways of checking the beam status.
 

From CPS Vistar Page

Changed:
<
<
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 (tv) in the control room or the web page: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status".
>
>
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 starting and stopping a run and during your shift, check the monitor (tv) in the control room or the web page: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status".
  cps.png
Changed:
<
<
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.
>
>
There is beam if the value near EASTA_ is ~30, and you should see an image with rising and falling signals as shown in the image above.
  If you would like to learn more about the CPS vistar page, you can find the detailed information in page: https://espace.cern.ch/be-dep/OP/PS/Applications%20Documentation/CPS%20Vistar.aspx.

From BL4S Vistar Page

Changed:
<
<
For BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:
>
>
For the BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:
  vistar_bl4s.png
Changed:
<
<
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of all 3 DWC. The units used here is [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
>
>
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes in the mean and sigma values of all three DWC. The units used here are [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
 

Run Control (DAQ)

Changed:
<
<
The main responsibility of the run controller shifter is to start, stop and observe the run. During the run you should watch the Error Report Service (ERS), explained below. In BL4S experiment, we are using the same data acquisition software that is used in ATLAS experiment. Here "Run" is defined as the data taking session. Once you changed the configuration or beam status then you should stop the current run and start a new one. The Shift Leader will help you about when to start and stop the run.
>
>
The main responsibility of the run controller shifter is to start, stop and observe the run. During the run you should watch the Error Report Service (ERS), explained below. In the BL4S experiment, we are using the same data acquisition software that is used in ATLAS experiment. Here "Run" is defined as the data taking session. Once you changed the configuration or beam status then you should stop the current run and start a new one. The Shift 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.
Line: 54 to 54
  BeamlineCERN.jpg
Changed:
<
<
If you have trouble with openning the DAQ (Data Acqusition) software, you can ask the shift leader for help. You will see a page like below:
>
>
If you have trouble with opening the DAQ (Data Acquisition) software, you can ask the shift leader for help. You will see a page like below:
  BL4S_DAQ_openning.png
Changed:
<
<
Lets have a look at what we can change and observe on the software:
>
>
Let`s have a look at what we can change and observe on the software:
 
  • At the bottom (red box), 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 find any information on the whiteboard, discuss it with the shift leader.
  • In the middle and on the right (orange box), you will see expert/advanced features(segments, root controller etc.)... You do not need to change anything here.
  • On the left (blue box), you will see in order:
Changed:
<
<
    • Run Control State(yellow) (will be explained below in starting a run part)
    • Run Control Commands (purple) (will be explained below in starting a run part)
>
>
    • Run Control State(yellow) (will be explained below in the Starting a Run part)
    • Run Control Commands (purple) (will be explained below in the Starting a Run part)
 
    • Beam Stable(cyan) (should always be green)
    • Run Information & settings (green)
First check the "Settings" tab in "Run Information & Settings" on the left. It looks like:
Line: 106 to 106
 
  • The run number
  • The file_tag_name you selected
  • Run Type
Changed:
<
<
  • The Trigger type: you should learn it from the Detector and DAQ shifter.
>
>
  • The Trigger type: you should get 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.
Line: 122 to 122
  daq_counters.png
Changed:
<
<
You can also check the rate by loading DFPanel. Simply click 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 also check the rate by loading DFPanel. Simply click DFPanel under "Load Panels" on the top. Another tab will appear on the Run Control Panel. Select the DFPanel then select tick L1 as in the screen below.
  df_panel.png
Line: 138 to 138
 

Running event display

Changed:
<
<
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:
>
>
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

Revision 112014-08-27 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Changed:
<
<

Beam Line For Schools Run Shifter Instructions

>
>

Beam Line For Schools Run Control 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. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping run, etc.
Line: 10 to 10
 

General Duties and Checklist

Changed:
<
<
pilot.jpg
>
>
pilot.jpg
  General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you face with a problem that you could not solve, you can always call the on-call experts. Other that starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.
Line: 30 to 30
  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 (tv) in the control room or the web page: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status".
Changed:
<
<
cps.png
>
>
cps.png
  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.
Line: 40 to 40
  For BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:
Changed:
<
<
vistar_bl4s.png
>
>
vistar_bl4s.png
  You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of all 3 DWC. The units used here is [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
Line: 52 to 52
 

Starting DAQ

Changed:
<
<
BeamlineCERN.jpg
>
>
BeamlineCERN.jpg
  If you have trouble with openning the DAQ (Data Acqusition) software, you can ask the shift leader for help. You will see a page like below:
Changed:
<
<
BL4S_DAQ_openning.png
>
>
BL4S_DAQ_openning.png
  Lets have a look at what we can change and observe on the software:
  • At the bottom (red box), 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 find any information on the whiteboard, discuss it with the shift leader.
Line: 68 to 68
 
    • Run Information & settings (green)
First check the "Settings" tab in "Run Information & Settings" on the left. It looks like:
Changed:
<
<
daq_settings.png
>
>
daq_settings.png
  Here we have these seetings:
  • Max Events : If you are taking data, it should be zero which means infinite.
Line: 91 to 91
 
  1. START : Run Control State will be RUNNING.
NOTE: When you have clicked on a button wait until the system has completely settled before you continue.
Changed:
<
<
BL4S_DAQ_running.png
>
>
BL4S_DAQ_running.png
  All the segments in run Control and Root Controller should be green now. If not, check the BL4SWhiteBoard and discuss with the Shift Leader. Now you have a new run! Congratulations!

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.

Changed:
<
<
daq_information.png
>
>
daq_information.png
  You can find run information on "Information" tab under "Run Information & Settings"
Line: 120 to 120
  You can directly click the "Counters" tab in "Run Information & Settings". Here "Rate" should be going up to 1-5 KHz, then dropping to 0 every few seconds. At the same time the Number should be increasing. If the rate is lower than 1kHz, or number is not increasing, check the beam status in Vistar Page. If the beam is fine, then there may be a problem in data taking and you should immediately take action with the Shift Leader.
Changed:
<
<
daq_counters.png
>
>
daq_counters.png
  You can also check the rate by loading DFPanel. Simply click 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.
Changed:
<
<
df_panel.png
>
>
df_panel.png
  You can see the spills during the run on this panel. If there is no beam it will look straight.
Line: 140 to 140
  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:
Changed:
<
<
ATLAS_higgs_candidate.png CMS_higgs_candidate.png
>
>
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 energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.

In our project we have out our 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.

Changed:
<
<
xfce4_xicon1.png
>
>
xfce4_xicon1.png
  Then, you will see the following screen:
Changed:
<
<
Screenshot-5.png
>
>
Screenshot-5.png
  With your mouse wheel, you can zoom in and out. By clicking and holding 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.

Revision 102014-08-27 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 10 to 10
 

General Duties and Checklist

Changed:
<
<
pilot.jpg
>
>
pilot.jpg
  General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you face with a problem that you could not solve, you can always call the on-call experts. Other that starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.
Changed:
<
<
  • Check the beam status from vistar pages. Is there any stop of the beam? Are the numbers in BL4S Vistar Page steady?
>
>
  • Check the beam status from vistar pages. Is there any stop of the beam? Are the numbers in BL4S Vistar Page steady?
 
  • Check ERS under the DAQ. Is there any Error or Warning other than the ones mentioned in BL4SWhiteBoard?
  • Check the "Counters" tab in "Run Information & Settings", Is it increasing when there is a beam?
  • Check the DFPanel under "Run control Panel". Can you see the spills? If it is constant for a while, discuss with the shift leader.
Line: 30 to 30
  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 (tv) in the control room or the web page: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status".
Changed:
<
<
cps.png
>
>
cps.png
  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.
Line: 40 to 40
  For BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:
Changed:
<
<
vistar_bl4s.png
>
>
vistar_bl4s.png
  You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of all 3 DWC. The units used here is [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
Line: 52 to 52
 

Starting DAQ

Changed:
<
<
BeamlineCERN.jpg
>
>
BeamlineCERN.jpg
  If you have trouble with openning the DAQ (Data Acqusition) software, you can ask the shift leader for help. You will see a page like below:
Changed:
<
<
BL4S_DAQ_openning.png
>
>
BL4S_DAQ_openning.png
  Lets have a look at what we can change and observe on the software:
  • At the bottom (red box), 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 find any information on the whiteboard, discuss it with the shift leader.
Line: 68 to 68
 
    • Run Information & settings (green)
First check the "Settings" tab in "Run Information & Settings" on the left. It looks like:
Changed:
<
<
daq_settings.png
>
>
daq_settings.png
  Here we have these seetings:
  • Max Events : If you are taking data, it should be zero which means infinite.
Line: 91 to 91
 
  1. START : Run Control State will be RUNNING.
NOTE: When you have clicked on a button wait until the system has completely settled before you continue.
Changed:
<
<
BL4S_DAQ_running.png
>
>
BL4S_DAQ_running.png
  All the segments in run Control and Root Controller should be green now. If not, check the BL4SWhiteBoard and discuss with the Shift Leader. Now you have a new run! Congratulations!

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.

Changed:
<
<
daq_information.png
>
>
daq_information.png
  You can find run information on "Information" tab under "Run Information & Settings"
Line: 120 to 120
  You can directly click the "Counters" tab in "Run Information & Settings". Here "Rate" should be going up to 1-5 KHz, then dropping to 0 every few seconds. At the same time the Number should be increasing. If the rate is lower than 1kHz, or number is not increasing, check the beam status in Vistar Page. If the beam is fine, then there may be a problem in data taking and you should immediately take action with the Shift Leader.
Changed:
<
<
daq_counters.png
>
>
daq_counters.png
  You can also check the rate by loading DFPanel. Simply click 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.
Changed:
<
<
df_panel.png
>
>
df_panel.png
  You can see the spills during the run on this panel. If there is no beam it will look straight.
Line: 140 to 140
  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:
Changed:
<
<
ATLAS_higgs_candidate.png CMS_higgs_candidate.png
>
>
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 energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.

In our project we have out our 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.

Changed:
<
<
xfce4_xicon1.png
>
>
xfce4_xicon1.png
  Then, you will see the following screen:
Changed:
<
<
Screenshot-5.png
>
>
Screenshot-5.png
  With your mouse wheel, you can zoom in and out. By clicking and holding 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.

Revision 92014-08-27 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Changed:
<
<
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.
>
>
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. You should always be in contact with the Shift Leader and the Detector Shifter for starting, stopping run, etc.
  The duties of the Run Control Shifter can be summarized as:

Added:
>
>

General Duties and Checklist

pilot.jpg

General duties of the Run Control Shifter is to start the run, to stop the run and to observe the beam. You should always be in contact with the Shift Leader. In control room, you are most like a pilot of a car and the Shift Leader is like a copilot giving directions. If you face with a problem that you could not solve, you can always call the on-call experts. Other that starting and stopping a run as explained below, you should always check the beam status and error reporting service during your shift. You should also check the event display and if you see something strange, discuss it with the Shift Leader and the Detector Shifter. To help you during a run here is a checklist, you should go over at least once in an hour.

  • Check the beam status from vistar pages. Is there any stop of the beam? Are the numbers in BL4S Vistar Page steady?
  • Check ERS under the DAQ. Is there any Error or Warning other than the ones mentioned in BL4SWhiteBoard?
  • Check the "Counters" tab in "Run Information & Settings", Is it increasing when there is a beam?
  • Check the DFPanel under "Run control Panel". Can you see the spills? If it is constant for a while, discuss with the shift leader.
  • Run the Event Display. Does the Events make sense? If you see any abnormality discuss with the Detector Shifter.
  • Check the BL4S E-Log if there is any update from other desk.
  • If there is any problem you face, make an e-log about.
  • Have Fun!
 

Checking Beam Status

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

Line: 11 to 25
 

Checking Beam Status

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

Added:
>
>
 

From CPS Vistar Page

Changed:
<
<
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: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"
>
>
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 (tv) in the control room or the web page: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status".
 
Changed:
<
<
cps.png
>
>
cps.png
  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.
Changed:
<
<
You can find the detailed information in page: https://espace.cern.ch/be-dep/OP/PS/Applications%20Documentation/CPS%20Vistar.aspx, if you would like to learn more.
>
>
If you would like to learn more about the CPS vistar page, you can find the detailed information in page: https://espace.cern.ch/be-dep/OP/PS/Applications%20Documentation/CPS%20Vistar.aspx.
 

From BL4S Vistar Page

Changed:
<
<
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:
>
>
For BL4S experiment, we have our own vistar page! You can navigate through your browser toolbar for "BL4S status" or the link .You will see a screen like:

vistar_bl4s.png

 
Changed:
<
<
vistar_bl4s.png
>
>
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of all 3 DWC. The units used here is [cm] for the mean and sigma (standard deviation) values. The mean values should be a couple of cm and the count should be on the order of the number of events read for regular runs. You can also see the signals of the first DWC. Discuss any big change with the shift leader.
 
Deleted:
<
<
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of 3 DWC. The units used here is [cm] for the mean values. The mean values should be a a couple of cm 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)

Changed:
<
<
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 Shift Leader will help you about when to start and stop the run.
>
>
The main responsibility of the run controller shifter is to start, stop and observe the run. During the run you should watch the Error Report Service (ERS), explained below. In BL4S experiment, we are using the same data acquisition software that is used in ATLAS experiment. Here "Run" is defined as the data taking session. Once you changed the configuration or beam status then you should stop the current run and start a new one. The Shift 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

Changed:
<
<
BeamlineCERN.jpg
>
>
BeamlineCERN.jpg
  If you have trouble with openning the DAQ (Data Acqusition) software, you can ask the shift leader for help. You will see a page like below:
Changed:
<
<
BL4S_DAQ_openning.png
>
>
BL4S_DAQ_openning.png
  Lets have a look at what we can change and observe on the software:
Changed:
<
<
  • 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 find any information on the whiteboard, discuss it with the shift leader.
  • In the middle and on the right, you will see expert/advanced features(segments, root controller etc.)... You do not need to change anything here.
  • On the left, you will see in order:
    • Run Control State (will be explained below in starting a run part)
    • Run Control Commands (will be explained below in starting a run part)
    • Beam Stable (should always be green)
    • Run Information & settings
>
>
  • At the bottom (red box), 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 find any information on the whiteboard, discuss it with the shift leader.
  • In the middle and on the right (orange box), you will see expert/advanced features(segments, root controller etc.)... You do not need to change anything here.
  • On the left (blue box), you will see in order:
    • Run Control State(yellow) (will be explained below in starting a run part)
    • Run Control Commands (purple) (will be explained below in starting a run part)
    • Beam Stable(cyan) (should always be green)
    • Run Information & settings (green)
 First check the "Settings" tab in "Run Information & Settings" on the left. It looks like:
Changed:
<
<
daq_settings.png
>
>
daq_settings.png
  Here we have these 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.
Changed:
<
<
  • Beam Energy: You should write the beam energy you are using here in units of GeV.
>
>
  • Beam Energy: You should write the beam energy you are using here in units of GeV.
 
  • Tier0 Project Name : Do not change it.
Changed:
<
<
  • 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.
>
>
  • 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 the "Set Values" button.
Line: 65 to 81
 After you adjust the settings press the "Set Values" button.

At ERS in the bottom you will see a message such as "Run settings have been correctly updated". If not, it means that you are doing something wrong like using forbidden characters in the tag or you forgot to select something.

Added:
>
>
 

Starting a Run

Changed:
<
<
Now you are ready to take data. After you finish the settings as explained 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 the "initialalize" button is enabled. Then you should follow these steps by pressing the buttons:
>
>
Now you are ready to take data. After you finish the settings as explained 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 the "initialize" button is enabled. Then you should follow these 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.
NOTE: When you have clicked on a button wait until the system has completely settled before you continue.
Changed:
<
<
BL4S_DAQ_running.png
>
>
BL4S_DAQ_running.png
 
Changed:
<
<
All the segments in run Control and Root Controller should be green now. Now you have a new run! Congratulations!
>
>
All the segments in run Control and Root Controller should be green now. If not, check the BL4SWhiteBoard and discuss with the Shift Leader. Now you have a new run! Congratulations!
  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.
Changed:
<
<
daq_information.png
>
>
daq_information.png
  You can find run information on "Information" tab under "Run Information & Settings"
Line: 93 to 110
 
  • Beam Type/Status/Intensity : From vistar page
You can find an example new run log at the BL4S E-Log.
Added:
>
>
When the run is finished, come back to the same e-log, edit it and add; * The stop time * Number of events read. You can find it under "Information" tab under "Run Information & Settings".
 

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:

Changed:
<
<
You can directly check the "Counters" tab in "Run Information & Settings". Here Rate should be going up to 1-5 KHz, then dropping to 0 every few seconds. At the same time the Number should be increasing. If the rate is lower than 1kHz, or number is not increasing, check the beam status in Vistar Page. If the beam is fine, then there may be a problem in data taking and you should immediately take action with the shift Leader.
>
>
You can directly click the "Counters" tab in "Run Information & Settings". Here "Rate" should be going up to 1-5 KHz, then dropping to 0 every few seconds. At the same time the Number should be increasing. If the rate is lower than 1kHz, or number is not increasing, check the beam status in Vistar Page. If the beam is fine, then there may be a problem in data taking and you should immediately take action with the Shift Leader.
 
Changed:
<
<
daq_counters.png
>
>
daq_counters.png
 
Changed:
<
<
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 also check the rate by loading DFPanel. Simply click 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.
 
Changed:
<
<
df_panel.png
>
>
df_panel.png
  You can see the spills during the run on this panel. If there is no beam it will look straight.
Added:
>
>
 

Stopping a Run

Changed:
<
<
When we want to change beam parameters or trigger logic or detector configuration, we should stop the run first. The Shift Leader will tell you when you should stop the run. Before stopping the run, open the e-log you madefor the new run and edit it. Add the number of events recorded and the stop time to your log. Then go through the steps;
>
>
When we want to change beam parameters or trigger logic or detector configuration, we should first stop the run. The Shift Leader will tell you when you should stop the run. Before stopping the run, open the e-log you made for the new run and edit it. Add the number of events recorded and the stop time to your log. Then go through the steps;
 
  1. STOP
  2. UNCONFIG
  3. SHUTDOWN
Line: 119 to 140
  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:
Changed:
<
<
ATLAS_higgs_candidate.png CMS_higgs_candidate.png
>
>
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 energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.

In our project we have out our 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.

Changed:
<
<
xfce4_xicon1.png
>
>
xfce4_xicon1.png
  Then, you will see the following screen:
Changed:
<
<
Screenshot-5.png
>
>
Screenshot-5.png
  With your mouse wheel, you can zoom in and out. By clicking and holding 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.
Line: 137 to 158
 
META FILEATTACHMENT attachment="cps.png" attr="" comment="cps vistar" date="1408375615" name="cps.png" path="cps.png" size="11628" user="ssarikay" version="1"
META FILEATTACHMENT attachment="vistar_bl4s.png" attr="" comment="bl4s vistar page" date="1408378309" name="vistar_bl4s.png" path="vistar_bl4s.png" size="176661" user="ssarikay" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="BL4S_DAQ.png" attr="" comment="" date="1408536440" name="BL4S_DAQ.png" path="BL4S_DAQ.png" size="70090" user="ssarikay" version="1"
 
META FILEATTACHMENT attachment="BL4S_DAQ_running.png" attr="" comment="" date="1408535886" name="BL4S_DAQ_running.png" path="BL4S_DAQ_running.png" size="66692" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_information.png" attr="" comment="" date="1408535917" name="daq_information.png" path="daq_information.png" size="4072" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_counters.png" attr="" comment="" date="1408535917" name="daq_counters.png" path="daq_counters.png" size="2940" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_settings.png" attr="" comment="" date="1408535917" name="daq_settings.png" path="daq_settings.png" size="4948" user="ssarikay" version="1"
META FILEATTACHMENT attachment="df_panel.png" attr="" comment="" date="1408535917" name="df_panel.png" path="df_panel.png" size="66836" user="ssarikay" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="BL4S_DAQ_openning.png" attr="" comment="" date="1408536544" name="BL4S_DAQ_openning.png" path="BL4S_DAQ_openning.png" size="70090" user="ssarikay" version="1"
 
META FILEATTACHMENT attachment="ATLAS_higgs_candidate.png" attr="" comment="" date="1408545259" name="ATLAS_higgs_candidate.png" path="ATLAS_higgs_candidate.png" size="4685722" user="ssarikay" version="1"
META FILEATTACHMENT attachment="CMS_higgs_candidate.png" attr="" comment="" date="1408545258" name="CMS_higgs_candidate.png" path="CMS_higgs_candidate.png" size="296076" user="ssarikay" version="1"
META FILEATTACHMENT attachment="xfce4_xicon1.png" attr="" comment="" date="1408548723" name="xfce4_xicon1.png" path="xfce4_xicon1.png" size="4000" user="ssarikay" version="1"
META FILEATTACHMENT attachment="Screenshot-5.png" attr="" comment="" date="1408548808" name="Screenshot-5.png" path="Screenshot-5.png" size="26233" user="ssarikay" version="1"
META FILEATTACHMENT attachment="BeamlineCERN.jpg" attr="" comment="" date="1408706274" name="BeamlineCERN.jpg" path="BeamlineCERN.jpg" size="74374" user="joos" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BL4S_DAQ_openning.png" attr="" comment="" date="1409137663" name="BL4S_DAQ_openning.png" path="BL4S_DAQ_openning.png" size="74864" user="ssarikay" version="1"
META FILEATTACHMENT attachment="pilot.jpg" attr="" comment="" date="1409141817" name="pilot.jpg" path="pilot.jpg" size="371164" user="ssarikay" version="1"

Revision 82014-08-22 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 36 to 36
 

Starting DAQ

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

Revision 72014-08-22 - MarkusJoos

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 10 to 10
 

Checking Beam Status

Changed:
<
<
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.
>
>
Run Control shifter is responsible of checking the beam status and deciding on when to start and stop a run. 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: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"

Line: 36 to 36
 

Starting DAQ

Changed:
<
<
(TODO: BL4S Logo here!) bl4s_logo.png
>
>
BeamlineCERN.jpg
 
Changed:
<
<
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:
>
>
If you have trouble with openning the DAQ (Data Acqusition) software, you can ask the shift leader for help. You will see a page like below:
  BL4S_DAQ_openning.png

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

Changed:
<
<
  • 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.
>
>
  • 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 find any information on the whiteboard, discuss it with the shift leader.
 
  • In the middle and on the right, you will see expert/advanced features(segments, root controller etc.)... You do not need to change anything here.
  • On the left, you will see in order:
Changed:
<
<
    • Run Control State (will be explained in below in starting a run part)
    • Run Control Commands (will be explained in below in starting a run part)
>
>
    • Run Control State (will be explained below in starting a run part)
    • Run Control Commands (will be explained below in starting a run part)
 
    • Beam Stable (should always be green)
Changed:
<
<
    • Run Informations & settings
First check the "Settings" tab in "Run Informations & Settings" part on the left. It looks like:
>
>
    • Run Information & settings
First check the "Settings" tab in "Run Information & Settings" on the left. It looks like:
  daq_settings.png
Changed:
<
<
Here we have seetings:
>
>
Here we have these 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.
Changed:
<
<
  • 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.
>
>
  • 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!
Changed:
<
<
After you adjust the settings press "Set Values Button".
>
>
After you adjust the settings press the "Set Values" button.
 
Changed:
<
<
At ERS in the bottom 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 forget to select something.
>
>
At ERS in the bottom you will see a message such as "Run settings have been correctly updated". If not, it means that you are doing something wrong like using forbidden characters in the tag or you forgot to select something.
 

Starting a Run

Changed:
<
<
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:
>
>
Now you are ready to take data. After you finish the settings as explained 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 the "initialalize" button is enabled. Then you should follow these 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.
Added:
>
>
NOTE: When you have clicked on a button wait until the system has completely settled before you continue.
 BL4S_DAQ_running.png

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

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

Stopping a Run

Changed:
<
<
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. Then go through the steps;
>
>
When we want to change beam parameters or trigger logic or detector configuration, we should stop the run first. The Shift Leader will tell you when you should stop the run. Before stopping the run, open the e-log you madefor the new run and edit it. Add the number of events recorded and the stop time to your log. Then go through the steps;
 
  1. STOP
  2. UNCONFIG
  3. SHUTDOWN
Line: 121 to 124
  As you can realize from the event displays, it is much more easier to understand the tracks and the energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.
Changed:
<
<
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.
>
>
In our project we have out our 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.
  xfce4_xicon1.png
Line: 146 to 150
 
META FILEATTACHMENT attachment="CMS_higgs_candidate.png" attr="" comment="" date="1408545258" name="CMS_higgs_candidate.png" path="CMS_higgs_candidate.png" size="296076" user="ssarikay" version="1"
META FILEATTACHMENT attachment="xfce4_xicon1.png" attr="" comment="" date="1408548723" name="xfce4_xicon1.png" path="xfce4_xicon1.png" size="4000" user="ssarikay" version="1"
META FILEATTACHMENT attachment="Screenshot-5.png" attr="" comment="" date="1408548808" name="Screenshot-5.png" path="Screenshot-5.png" size="26233" user="ssarikay" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BeamlineCERN.jpg" attr="" comment="" date="1408706274" name="BeamlineCERN.jpg" path="BeamlineCERN.jpg" size="74374" user="joos" version="1"

Revision 62014-08-20 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 27 to 27
  vistar_bl4s.png
Changed:
<
<
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.
>
>
You can see the counts of the detectors, daily plan and ongoing runs from here. Observe sharp changes on the mean and sigma values of 3 DWC. The units used here is [cm] for the mean values. The mean values should be a a couple of cm 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)

Changed:
<
<
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.
>
>
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 Shift 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.
Line: 44 to 44
  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.
Changed:
<
<
  • In the middle and on the right, you will see informations about the run segments, apps etc... You should not change anything here.
>
>
  • In the middle and on the right, you will see expert/advanced features(segments, root controller etc.)... You do not need to change anything here.
 
  • On the left, you will see in order:
    • Run Control State (will be explained in below in starting a run part)
Changed:
<
<
    • Run control command (will be explained in below in starting a run part)
>
>
    • Run Control Commands (will be explained in below in starting a run part)
 
    • Beam Stable (should always be green)
Changed:
<
<
    • Run Informations and settings
>
>
    • Run Informations & settings
 First checkthe "Settings" tab in "Run Informations & Settings" part on the left. It looks like:

daq_settings.png

Line: 64 to 64
 
  • Recording: You should "Enable" it!
After you adjust the settings press "Set Values Button".
Changed:
<
<
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.
>
>
At ERS in the bottom 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 forget 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:

Line: 74 to 74
 
  1. START : Run Control State will be RUNNING.
BL4S_DAQ_running.png
Changed:
<
<
All the segments in run Control and Root Controller should be green now. Now you have a new run! Congragulations!
>
>
All the segments in run Control and Root Controller should be green now. Now you have a new run! Congratulations!
  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.
Line: 97 to 97
  You should also check the counts during a run. You can check it in two places:
Changed:
<
<
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 directly check the "Counters" tab in "Run Information & Settings". Here Rate should be going up to 1-5 KHz, then dropping to 0 every few seconds. At the same time the Number should be increasing. If the rate is lower than 1kHz, or number is not increasing, check the beam status in Vistar Page. If the beam is fine, then there may be a problem in data taking and you should immediately take action with the shift Leader.
  daq_counters.png
Line: 108 to 108
 You can see the spills during the run on this panel. If there is no beam it will look straight.

Stopping a Run

Changed:
<
<
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;
>
>
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. Then go through the steps;
 
  1. STOP
  2. UNCONFIG
Changed:
<
<
  1. SHOTDOWN
After you make the changes needed you can start a new run.
>
>
  1. SHUTDOWN
After you make the necessary changes 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

Changed:
<
<
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.
>
>
As you can realize from the event displays, it is much more easier to understand the tracks and the energy measurements by eye. However, we still need what we call "offline analysis" to understand the physics in our experiment and calculate results.
  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.
Line: 129 to 129
  Screenshot-5.png
Changed:
<
<
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.
>
>
With your mouse wheel, you can zoom in and out. By clicking and holding 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.
 
Changed:
<
<
-- SaimeSarikaya - 12 Aug 2014
>
>
-- SaimeSarikaya - 12 Aug 2014 -- CenkYildiz - 20 Aug 2014
 
META FILEATTACHMENT attachment="cps.png" attr="" comment="cps vistar" date="1408375615" name="cps.png" path="cps.png" size="11628" user="ssarikay" version="1"
META FILEATTACHMENT attachment="vistar_bl4s.png" attr="" comment="bl4s vistar page" date="1408378309" name="vistar_bl4s.png" path="vistar_bl4s.png" size="176661" user="ssarikay" version="1"

Revision 52014-08-20 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 15 to 15
  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: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"
Changed:
<
<
cps.png
>
>
cps.png
  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.
Line: 25 to 25
  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:
Changed:
<
<
vistar_bl4s.png
>
>
vistar_bl4s.png
  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)

Line: 36 to 36
 

Starting DAQ

Changed:
<
<
(TODO: BL4S Logo here!)
>
>
(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:
Changed:
<
<
BL4S_DAQ_openning.png
>
>
BL4S_DAQ_openning.png
  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.
Line: 52 to 52
 
    • Run Informations and settings
First checkthe "Settings" tab in "Run Informations & Settings" part on the left. It looks like:
Changed:
<
<
daq_settings.png
>
>
daq_settings.png
  Here we have seetings:
  • Max Events : If you are taking data, it should be zero which means infinite.
Line: 72 to 72
 
  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.
Changed:
<
<
BL4S_DAQ_running.png
>
>
BL4S_DAQ_running.png
  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.

Changed:
<
<
daq_information.png
>
>
daq_information.png
  You can find run information on "Information" tab under "Run Information & Settings"
Line: 93 to 93
 

Counters and ERS during run

Changed:
<
<
daq_counters.png
>
>
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.
 
Changed:
<
<
df_panel.png
>
>
You should also check the counts during a run. You can check it in two places:
 
Added:
>
>
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.

daq_counters.png

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.

df_panel.png

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

 

Stopping a Run

Added:
>
>
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
  2. UNCONFIG
  3. SHOTDOWN
After you make the changes needed you can start a new run.
 

Running event display

Added:
>
>
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.

xfce4_xicon1.png

Then, you will see the following screen:

Screenshot-5.png

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

META FILEATTACHMENT attachment="cps.png" attr="" comment="cps vistar" date="1408375615" name="cps.png" path="cps.png" size="11628" user="ssarikay" version="1"
Line: 112 to 142
 
META FILEATTACHMENT attachment="daq_settings.png" attr="" comment="" date="1408535917" name="daq_settings.png" path="daq_settings.png" size="4948" user="ssarikay" version="1"
META FILEATTACHMENT attachment="df_panel.png" attr="" comment="" date="1408535917" name="df_panel.png" path="df_panel.png" size="66836" user="ssarikay" version="1"
META FILEATTACHMENT attachment="BL4S_DAQ_openning.png" attr="" comment="" date="1408536544" name="BL4S_DAQ_openning.png" path="BL4S_DAQ_openning.png" size="70090" user="ssarikay" version="1"
Added:
>
>
META FILEATTACHMENT attachment="ATLAS_higgs_candidate.png" attr="" comment="" date="1408545259" name="ATLAS_higgs_candidate.png" path="ATLAS_higgs_candidate.png" size="4685722" user="ssarikay" version="1"
META FILEATTACHMENT attachment="CMS_higgs_candidate.png" attr="" comment="" date="1408545258" name="CMS_higgs_candidate.png" path="CMS_higgs_candidate.png" size="296076" user="ssarikay" version="1"
META FILEATTACHMENT attachment="xfce4_xicon1.png" attr="" comment="" date="1408548723" name="xfce4_xicon1.png" path="xfce4_xicon1.png" size="4000" user="ssarikay" version="1"
META FILEATTACHMENT attachment="Screenshot-5.png" attr="" comment="" date="1408548808" name="Screenshot-5.png" path="Screenshot-5.png" size="26233" user="ssarikay" version="1"

Revision 42014-08-20 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 15 to 15
  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: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"
Changed:
<
<
cps.png
>
>
cps.png
  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.
Line: 25 to 25
  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:
Changed:
<
<
vistar_bl4s.png
>
>
vistar_bl4s.png
  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.
Changed:
<
<

Starting and Stopping a Run

>
>

Run Control (DAQ)

 
Changed:
<
<
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 confugation 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.
>
>
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!)

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:

Changed:
<
<
BL4S_DAQ.png
>
>
BL4S_DAQ_openning.png

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:

daq_settings.png

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.
BL4S_DAQ_running.png

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.

daq_information.png

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

daq_counters.png

df_panel.png

Stopping a Run

 

Running event display

Line: 44 to 105
 
META FILEATTACHMENT attachment="cps.png" attr="" comment="cps vistar" date="1408375615" name="cps.png" path="cps.png" size="11628" user="ssarikay" version="1"
META FILEATTACHMENT attachment="vistar_bl4s.png" attr="" comment="bl4s vistar page" date="1408378309" name="vistar_bl4s.png" path="vistar_bl4s.png" size="176661" user="ssarikay" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="BL4S_DAQ.png" attr="" comment="BL4S DAQ" date="1408380237" name="BL4S_DAQ.png" path="BL4S_DAQ.png" size="63167" user="ssarikay" version="1"
>
>
META FILEATTACHMENT attachment="BL4S_DAQ.png" attr="" comment="" date="1408536440" name="BL4S_DAQ.png" path="BL4S_DAQ.png" size="70090" user="ssarikay" version="1"
META FILEATTACHMENT attachment="BL4S_DAQ_running.png" attr="" comment="" date="1408535886" name="BL4S_DAQ_running.png" path="BL4S_DAQ_running.png" size="66692" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_information.png" attr="" comment="" date="1408535917" name="daq_information.png" path="daq_information.png" size="4072" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_counters.png" attr="" comment="" date="1408535917" name="daq_counters.png" path="daq_counters.png" size="2940" user="ssarikay" version="1"
META FILEATTACHMENT attachment="daq_settings.png" attr="" comment="" date="1408535917" name="daq_settings.png" path="daq_settings.png" size="4948" user="ssarikay" version="1"
META FILEATTACHMENT attachment="df_panel.png" attr="" comment="" date="1408535917" name="df_panel.png" path="df_panel.png" size="66836" user="ssarikay" version="1"
META FILEATTACHMENT attachment="BL4S_DAQ_openning.png" attr="" comment="" date="1408536544" name="BL4S_DAQ_openning.png" path="BL4S_DAQ_openning.png" size="70090" user="ssarikay" version="1"

Revision 32014-08-18 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Beam Line For Schools Run Shifter Instructions

Line: 8 to 8
 
Deleted:
<
<

Changing Beam Parameters and Dumping the Beam

 

Checking Beam Status

Added:
>
>
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: http://op-webtools.web.cern.ch/op-webtools/vistar/vistars.php?usr=CPS. You can also directly navigate through the bookmarks from your browser toolbar for "CPS status"

cps.png

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: https://espace.cern.ch/be-dep/OP/PS/Applications%20Documentation/CPS%20Vistar.aspx, 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:

vistar_bl4s.png

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.

 

Starting and Stopping a Run

Added:
>
>
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 confugation 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.

(TODO: BL4S Logo here!)

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:

BL4S_DAQ.png

 

Running event display

-- SaimeSarikaya - 12 Aug 2014

Added:
>
>
META FILEATTACHMENT attachment="cps.png" attr="" comment="cps vistar" date="1408375615" name="cps.png" path="cps.png" size="11628" user="ssarikay" version="1"
META FILEATTACHMENT attachment="vistar_bl4s.png" attr="" comment="bl4s vistar page" date="1408378309" name="vistar_bl4s.png" path="vistar_bl4s.png" size="176661" user="ssarikay" version="1"
META FILEATTACHMENT attachment="BL4S_DAQ.png" attr="" comment="BL4S DAQ" date="1408380237" name="BL4S_DAQ.png" path="BL4S_DAQ.png" size="63167" user="ssarikay" version="1"

Revision 22014-08-12 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Added:
>
>

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:

Changing Beam Parameters and Dumping the Beam

Checking Beam Status

Starting and Stopping a Run

Running event display

 -- SaimeSarikaya - 12 Aug 2014 \ No newline at end of file

Revision 12014-08-12 - SaimeSarikaya

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="BeamLineForSchools"
-- SaimeSarikaya - 12 Aug 2014
 
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