DOC Tasks

Essential Instructions

  • Please keep an eye on detector temperatures and note any unexplained increases--they could be the result of a clogging pneumatic valve control line

The essential webpages (needs tunnelling) for monitoring are:

Open the DCS Panel (instructions in the "Beginning of every shift" session)
  • LV & HV Current for Pixel Barrel and Pixel Endcap
    • in the PixelBarrel tab or PixelEndcap Tab respectively ->Plot: Select command
    • LV channels->Monitored current
    • HV channels->Monitored current
  • Temperature for Pixel Barrel and Pixel Endcap
    • in the PixelBarrel tab or PixelEndcap Tab respectively ->Plot: Select command
    • PLC Probes->All temperatures on silicon below
    • PLC Probes->All temperatures on liquid below
  • to move them around press Alt and move them with the mouse

Open RCMS: RCMS web interface: http://cmsrc-pixel.cms:17000/rcms/gui/servlet/FMPilotServlet?groupID=9270&ACTION=Refresh

Choose: PixP1_TCDS_DCS_XDAQ14_GLOBALCALIB, then click create and initialize

Pixel DAQ Finite State Machine: choose Readbacker at the bottom of possible configurations, then click configure and then Start

(you need to provide user/passwd credentials for booking a Global Run, ask for it)

Now back to RCMS once completed and destroy

The following calibrations need to be done regularly, once every week :

The procedure for doing the calibration

# It is done while the detector is in local (DAQ)! First, setup the machine and become a pixeldev

ssh yourusername@srv-s2b18-37-01
# To connect from outside do the following 
# ssh yourusername@cmsusr
# ssh srv-s2b18-37-01 
sudo -u pixeldev -H bash -l 

#Source the environment and run the software:

export curdir=$PWD; cd ~/TriDAS; source; cd $curdir
cd /pixel/users/ph1commissioning/bpix/

#The script will keep running in the background as you run the calibration from the web browser:

# After running the software, open Pixel DAQ Finite State Machine from the web browser for the given machine (srv-s2b18-37-01)


Click on XDAC

Click on Initialize

# On the right side of seen table in the web browser, the list of calibration types are given. Follow the instructions below:

  • Choose the calibration that you are interested in
  • Start configuration - configure - (when the configuration done, it will provide you a "Run Number")
  • Save the run number for the specific calibration
  • Then, start the calibration - start -
  • When it is done, you will see the following information, which is not related to the current calibration steps:
    • The current calibration: "CalibrationType" produced the following configuration data:
    • Insert data for dac: Yes/No
    • Update the any of the following aliases:
    • Default: Yes/No
    • LowPower: Yes/No
    • BBTest: Yes/No
    • Don't do anything about it, and halt the calibration process for further studies by the experts - halt -
  • The calibration is completed!
  • Now, you can kill the running software from the tmux session of the "POS" target. This will close the open session in the web browser (Pixel DAQ Finite State Machine). Detach the tmux sessions that you attached via "ctrl d"
  • Write an elog specifying the type of calibration(s) and the corresponding run numbers, and also mention that full BPix is selected for the calibration.

Approximate time needed to complete some BPIX calibrations

Another way:

# open a tmux session for "POS" target

 tmux att -t POS  
# tmux ls  => shows the available sessions 

# The calibration can be done for different sectors of BPix, the given calibrations need to be done with full BPix. In order to check the config, open another tmux session for "config" target

 tmux att -t config   

# The config file should include the full BPix. In order to check it, one can compare the number of lines in the config file used in the calibration ("detectconfig.dat") with the ones in the config file for full BPix ("detectconfig.dat_bfix" : 18945 modules in total). The number of lines corresponds to the number of modules in the considered sector.

 wc -l detectconfig.dat
 wc -l detectconfig.dat_bfix 
# If those are equal to each other, continue with the calibration.

# In the first tmux session for target "POS", run the software

 ./ /pixel/users/ph1commissioning/bpix/multi.xml 
# Keep this screen open to follow the progress, if there is an error the program will crash.

During physics fills: pixel and strip HV turn on automatically once STABLE BEAMS is declared. See here for a description of the beam background numbers and switch-on criteria.

All other times: DCS action matrix ( and choose PIXEL in the "select detector" drop-down menu) is to be followed. When there is no beam in the machine, the cDCS shifter can decide to turn on the pixel HV (e.g. for a cosmic run), or the pixel DOC can decide to turn on the pixel HV (e.g. for calibrations).

Daily tasks

  • Runs must have DT, TRACKER and PIXEL in and a reasonable high number of events
  • How to get HV details:
    • go to -> RunSummary
    • insert run number -> Submit -> Lumi Sections
    • check BPix and Fpix columns: different colors = CHANGING, green = ON, red = OFF
  • How to get the key:
    • ssh -Y
    • login on a cms machine, for example srv-c2f38-15-01 (a list is here:
      cd ../pixelpro/TriDAS 
      cd $POS_OUTPUT_DIRS 
      cd Run_313000/Run_313916 #This is just an example for run 313916
    • cat PixelConfigurationKey.txt 
    • read the key value (4607 in this example): now you can get all the other values:
    • grep -A20 4607 configurations.txt #4607is the key! 

  • The report has to be made by following the instructions in the above link
  • create the plots by following exactly the "What to do" description for each plot
  • check the plots for problems
  • to save the images as .png files remember to Actions-> Convert to Png or View Plot Image (depending on the page) before right click to save it
  • note that some plots are quite heavy, do one at the time and be patient
  • to check the value (instruction on how to Login in the DCS Panel are in the next section):
    • Min/Max/Mean Temperatures: follow the link in the explanation-> Actions -> Show -> Last Value Table
    • Sniffer dew points: from the DCS Panel -> View (Select command) -> Sniffer racket
    • Dry Gas Source: from DCS Panel, find the Dry Gas Source in the subsystem, double click on Dry Gas Source to open the "Dry Gas State" tab to find more values. Make sure to follow the correct diagram.
    • PixelPlants and CO2 from DCS Panel, here you will find also the cavern dewpoint
    • Plant Status from DCS Panel, in the Cooling tab
  • Once all the information are collected write an E-log
    • E-log should be submitted under "Tracker" with Type: Monitoring report - morning and Subject: Tracker Daily Monitoring
    • an example is here example eLog

At the beginning of every shift

  • Read the most recent E-log entries
  • Talk to the previous shifter
  • Read the Messages to the Shifter section
  • Read the ToDo List section

  • At P5
    • use the tracker2 PC of the PixelInfrastructure in the P5 control room
    • double-click on the Desktop "" (default) or "" (in case the DCS expert tells you)
    • log in using your NICE username and password and select the correct role
  • Remotely
    • connet to lxplus: ssh -X
    • start the remote desktop: rdesktop -g 90% -P -z -x l -u username -d CERN (replace username by your NICE username)
    • login with using your nice user name and password
    • double-click on TrackerDCS icon
    • log in using your NICE username and password and select the correct role

The pixel shift desk has four monitors dedicated to Data Acquisition (DAQ) and two monitors dedicated to the Detector Control System (DCS). These pages need to be open at all times

At the end of every shift

  • If you are in control of the pixel detector on the DCS FSM, you should Release control (do NOT choose Release All!).
  • After you release control, you should ask the central DCS shifter to take control.
  • Only after releasing control, you may log out.

Please write a Shift Summary E-log.

Go to subsystems -> Tracker -> Pixels to write an elog (note: for the daily report shared with the tracker DOC go to tracker instead).

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2018-07-17 - BenediktVormwald1
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

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