Difference: ShiftLeaderInstructions (1 vs. 4)

Revision 42015-03-19 - TimBrooks

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

Beam Line For Schools Shift Leader Instructions

Changed:
<
<
This page is designed to help the Shift Leader of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction.
>
>
This page is designed to help the Shift Leader of the BL4S experiment. Please be sure that you read the general shift instructions in page ShiftIntroduction.
  The duties of the Shift Leader can be summarized as:
Line: 10 to 10
 

General structure of the shifts

Changed:
<
<
The Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look above the shoulders of the shifters. You can see the duties of them from the page BL4SRunControlShifterInstructions and BL4SDetectorShifterInstructions.
>
>
The Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look above the shoulders of the shifters. You can see the duties of them from the page RunControlShifterInstructions and DetectorShifterInstructions.
  There is a BL4S E-Log where everything should be documented during runs.
Line: 22 to 22
 

Editing White Board

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

Vistar and Event Display

Line: 42 to 42
 

Running DAQ and Controlling HVs

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

Changing Configuration Files

Line: 54 to 54
  Configuration Files can be opened by clicking on the "Configuration files" on your desktop:
Changed:
<
<
ibus-engine.png
>
>
ibus-engine.png
  You can see pedestal data file here that you did before.

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

Changed:
<
<
cfg.png
>
>
cfg.png
  Be careful that there are different type of configuration files. We can categorize them as:
Line: 86 to 86
 
  • Double click on your new config file and you will see a page like on the left below.
  • Now find the channels that you changed and write the new values and then save and quit.
  • Make an e-log that you changed the config file, containing the new name of the config file and why you need change it.
Changed:
<
<
cfg_file.png geo_file.png
>
>
cfg_file.png geo_file.png
  If you changed anything about the geometry, you should create a new geometry file. You can do the following steps:
  • Find the most recent .cfg and .geo files.

Revision 32014-09-01 - SaimeSarikaya

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

Beam Line For Schools Shift Leader Instructions

Line: 8 to 8
 
Changed:
<
<

General Structure of the shifts

>
>

General structure of the shifts

 
Changed:
<
<
Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look behind the shoulders of the shifters. You can see the duties of them from the page BL4SRunControlShifterInstructions and BL4SDetectorShifterInstructions.
>
>
The Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look above the shoulders of the shifters. You can see the duties of them from the page BL4SRunControlShifterInstructions and BL4SDetectorShifterInstructions.
 
Changed:
<
<
There is a BL4S E-Log that everything should be documented during runs.
>
>
There is a BL4S E-Log where everything should be documented during runs.
  https://espace.cern.ch/project-blfs/bl4s-elog-2014/default.aspx
Line: 42 to 42
 

Running DAQ and Controlling HVs

Changed:
<
<
Shift Leader should also run the DAQ in monitoring mode for Error Report Service (ERS) (explained in BL4SRunControlShifterInstructions) and control the HVs (explained in BL4SDetectorShifterInstructions) and apply any name and voltage value change if needed.
>
>
The Shift Leader should also run the DAQ in monitoring mode for Error Report Service (ERS) (explained in BL4SRunControlShifterInstructions) and control the HVs (explained in BL4SDetectorShifterInstructions) and apply any name and voltage value change if needed.
 

Changing Configuration Files

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

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

Changed:
<
<
You should create a .cfg file if you change and channel on DAQ system (the channels on VME). The explanations of the variables are written in the file.
>
>
You should create a .cfg file if you change a channel in the DAQ system (the channels on VME). The explanation of the variables are written in the file.
 
  • First find the last config file. It will be named as example: 1407238700_T9_05082014.cfg
Changed:
<
<
  • Here the first number "1407238700" is unix time stamp. Unix time stamp means "system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC) on January 1 1970". Run numbers are also assigned with a unix time stamp.
>
>
  • Here the first number "1407238700" is unix time stamp. Unix time stamp means "system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC) on January 1 1970". Run numbers are also defined by a unix time stamp.
 
  • Second word "T9" is the tag. If you are making a special run with a special configuration like Calibration or Test, you can use that tag.
  • The last number "05082014" is the date as 05.08.2014.
  • Copy and Paste the most recent config file. Then rename it.
Line: 88 to 88
 
  • Make an e-log that you changed the config file, containing the new name of the config file and why you need change it.
cfg_file.png geo_file.png
Changed:
<
<
If you changed anything about the geometry, you should create a new geometry file. You can follow the following steps:
>
>
If you changed anything about the geometry, you should create a new geometry file. You can do the following steps:
 
  • Find the most recent .cfg and .geo files.
Changed:
<
<
  • Copy them and rename them as told above. (In the geometry file you do not need any unix time stamp).
>
>
  • Copy them and rename them as explained above. (In the geometry file you do not need any unix time stamp).
 
  • Open the new config file and change the "GEOMETRY FILE NAME" with the new geometry file name you created.
  • Save and quit the config file.
  • Open the new geometry file.

Revision 22014-08-27 - SaimeSarikaya

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

Beam Line For Schools Detector Shifter Instructions

>
>

Beam Line For Schools Shift Leader Instructions

 
Changed:
<
<
This page is designed to help Detector Shifter of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction.

The duties of the Detector Shifter can be summarized as:
>
>
This page is designed to help the Shift Leader of the BL4S experiment. Please be sure that you read the general shift instructions in page BL4SShiftIntroduction.

The duties of the Shift Leader can be summarized as:

 
Added:
>
>

General Structure of the shifts

Shift leader is supposed to help whenever the Run Control and Detector Shifters need help. You should look behind the shoulders of the shifters. You can see the duties of them from the page BL4SRunControlShifterInstructions and BL4SDetectorShifterInstructions.

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

https://espace.cern.ch/project-blfs/bl4s-elog-2014/default.aspx

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

https://espace.cern.ch/project-blfs/detlog/default.aspx

Editing White Board

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

Vistar and Event Display

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

goBL4Sopt
cd /afs/cern.ch/user/d/daquser/public/BL4S_DAQ/DataFlow/ROSMonitor
./x86_64-slc6-gcc47-opt/vistar -p part_BL4S -t ReadoutApplication -v 1 -c config_file_name.cfg

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

/afs/cern.ch/user/s/ssarikay/www/vistar/comments.txt

Running DAQ and Controlling HVs

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

 

Changing Configuration Files

Changed:
<
<
Configuration files are needed for analysis, event monitor and event display. So it is important to keep the configuration files up to date. It is advised to make any change in the configuration files with the shift leader.
>
>
P.S. This part was first written for the Detector Shifter but then revisited after the duty is given to the Shift Leader. That is why it is kept so simple.

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

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

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

Changed:
<
<
ibus-engine.png
>
>
ibus-engine.png
  You can see pedestal data file here that you did before.

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

Changed:
<
<
cfg.png
>
>
cfg.png
  Be careful that there are different type of configuration files. We can categorize them as:

File format Description Contains How/When to create Who is responsible
Pedestal folder The pedestal data files Pedestal data Created when pedestal program runs Detector Shifter
Changed:
<
<
.cfg files Main configuration files The DAQ Channels and relevant files like calibration and geometry. Necessary file paths Created when there is a change in DAQ channels or geometry Detector Shifter & Shift Leader
.geo files Geomerty File Geometry of the detectors and beam line Created when there is a change in geometry. Detector Shifter & Shift Leader
.calib files Calibration Files Calibration constants of the DWC and Lead Glass Calorimeters Once at the beginning of the experiment Shift Leader
.txt files Data File Names Names of the files with the relevant tags for analysis After each run Shift Leader
>
>
.cfg files Main configuration files The DAQ Channels and relevant files like calibration and geometry. Necessary file paths Created when there is a change in DAQ channels or geometry Shift Leader
.geo files Geomerty File Geometry of the detectors and beam line Created when there is a change in geometry. Shift Leader
.calib files Calibration Files Calibration constants of the DWC and Lead Glass Calorimeters Once at the beginning of the experiment DAQ Expert
.txt files Data File Names Names of the files with the relevant tags for analysis After each run DAQ Expert
  As you can see from the table you are only responsible from the .cfg and .geo files. Do not change or remove any other file.
Line: 46 to 86
 
  • Double click on your new config file and you will see a page like on the left below.
  • Now find the channels that you changed and write the new values and then save and quit.
  • Make an e-log that you changed the config file, containing the new name of the config file and why you need change it.
Changed:
<
<
cfg_file.png geo_file.png
>
>
cfg_file.png geo_file.png
  If you changed anything about the geometry, you should create a new geometry file. You can follow the following steps:
  • Find the most recent .cfg and .geo files.
Line: 57 to 97
 
  • Apply any change you made in geometry.
  • Save and Quit.
  • Make an e-log that you changed the config file and the geometry, containing the new names of the files and why you need change it.
Deleted:
<
<
It may seem you a little bit complicated. But you should not wotty about this too much and the Shift Leader will always be there to help you smile
  -- SaimeSarikaya - 26 Aug 2014

Revision 12014-08-26 - SaimeSarikaya

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

Beam Line For Schools Detector Shifter Instructions

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

The duties of the Detector Shifter can be summarized as:

Changing Configuration Files

Configuration files are needed for analysis, event monitor and event display. So it is important to keep the configuration files up to date. It is advised to make any change in the configuration files with the shift leader.

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

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

ibus-engine.png

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

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

cfg.png

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

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

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

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

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

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

  • Find the most recent .cfg and .geo files.
  • Copy them and rename them as told above. (In the geometry file you do not need any unix time stamp).
  • Open the new config file and change the "GEOMETRY FILE NAME" with the new geometry file name you created.
  • Save and quit the config file.
  • Open the new geometry file.
  • Apply any change you made in geometry.
  • Save and Quit.
  • Make an e-log that you changed the config file and the geometry, containing the new names of the files and why you need change it.
It may seem you a little bit complicated. But you should not wotty about this too much and the Shift Leader will always be there to help you smile

-- SaimeSarikaya - 26 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