300 likes | 312 Views
A comprehensive guide for ECAL shifters, providing information on detector monitoring, trigger pedestals, slow control, and more.
E N D
Federico Pilo Gabriele Bigongiari Marco Incagli Sylvie Rosier Armand Fiasson Valerio Vagelli Giovanni Gallucci Mercedes Paniccia Laurent Basara Roman Kossakowski Franco Spinella Corinne Goy ECAL DAQ experts ECAL cell @JSC +1 321 720 0191
ECAL structure • necessary to know the meaning of (x,y) view, ECAL trigger, … • more information in https://twiki.cern.ch/twiki/bin/view/AMS/ECAL
As a general rule … • ECAL is a simple and reliable detector: immediate actions have to be taken only in 2 circumstances (details later): • noise in some ECAL trigger channels causing an increase of AMS dead time • temperature becomes too high (->switch off electronics) or too low (->enable heaters, eventually switch off electronics) • Always write an entry in the ECAL tab of the AMS Elog • Legenda: • notify an expert = if it’s 3AM no need to wake up... • call an expert = call!
ECAL shifter training: start up In ECAL POC station (currently pcpoc72) login as user ecal (usually it’s already done!) - relecant workspaces are: ECALMONandSlowControl - if the monitor is not running open a Terminal Window Terminal Window click to open Workspace click to change
ECAL monitoring • Detector monitoring: • Cell occupancy • Trigger bits • Pedestals • Slow Control: • Temperature • Data size • Trigger rate • Low Voltage Power consumption • At switch on/reboot • HV values
Occupancy Plots ECAL Trigger Pedestals Part 1: Detector Monitoring
ECMON is the main ECAL Monitoring software package Current release: /pocchome/ecal/ECAL/ECMON (v1.00-NASA) More details on the TWIKI page: https://twiki.cern.ch/twiki/bin/view/AMS/Monitoring The package includes two main monitoring tools: CFGMon - detector housekeeping and configuration monitor Mom - data quality and calibration monitor Monitoring tools are based on ROOT files created by: bin2root – raw data decoder AMS standard 1 minute root files: standard AMS rples with a fraction (~1/5-1/10) of all events Detector Monitoring 8
bin2root – shifter duties 1/3 During SCIENCE Ops. two different instances* of bin2root must be always running: both MOM and CFGMon will not work if bin2root is stopped *(one for HK, CFG and temperature decoding, the other for CAL, SCI and CFG) • Check that bin2root is running: • Open a new shell (from pcpoc72 – ECAL pocc computer) • Type: ps aux | grep bin2root • Check that two instances of bin2root are running: • ./bin2root -D /Data/BLOCKS/SCIBPB/RT -S “0x05|4|0x06|1|0x07|1|0x08|1|0x19|0|” 0015807 999999 • ./bin2root -D /Data/BLOCKS/HKLR/CDP -S “0x05|0|0x06|0|0x07|1|0x08|1|0x19|1|” 0027932 999999 9
bin2root – shifter duties 2/3 • Check bin2root decoding status: • Open a new shell (from pcpoc72 – ECAL pocc computer) • Type: • For HK, CFG and temperatures decoding: • tail –f /pocchome/ecal/ECAL/data/log/bin2root_SCIBPB_RT.log • For HK, CFG and temperatures decoding: • tail –f /pocchome/ecal/ECAL/data/log/bin2root_SCIBPB_RT.log • In the log files, bin2root reports the elapsed time since the last analyzed BF or a summary of the decoding • [bin2root - INFO] Waiting for a new Block File from 50 seconds ... • [bin2root - INFO] Booking a new Tree h1 • [WARNING] DeBlock read one word: end of file reached • Node ID Found DATA bit Bld Cond Err Bld Err Cum Node Stat Process Mode Int Struct bit • JINJ-0 23999 0 0 0 0 23999| 0| 0 23999| 0 • JINJ-2 23999 0 0 13 0 23999| 0| 0 23999| 0 • JLV1-A 23999 23999 0 0 0 0| 23999| 0 0| 23999 • ETRG-0-A 23999 23999 0 0 0 0| 23999| 0 0| 23999 • ETRG-1-A 23998 23998 0 0 0 0| 23998| 0 0| 23998 • JINF-E-0-A 23999 23999 0 0 0 0| 23999| 0 23999| 0 • JINF-E-1-A 23999 23999 0 0 0 0| 23998| 0 23999| 0 • EDR-0-0-A 7107 7107 0 0 0 0| 7107| 0 0| 7107 • EDR-0-1-A 6945 6945 0 0 0 0| 6945| 0 0| 6945 • …. • If the log files are no more updated or any error (i.e.: [bin2root – ERROR]) or crash is reported, bin2root instances must be killed and restarted 10
bin2root – shifter duties 3/3 • Restart bin2root instances if not running (or an instance has been killed): • Open a new shell (from pcpoc72 – ECAL pocc computer) • Change directory to ECMON directory: cd /pocchome/ecal/ECAL/ECMON • Set ECMON environment variables: source set_environment.sh • Change directory to bin2root directory: cd bin2root • Run a new bin2root instance: • For HK, CFG and temperatures decoding: • ./bin2root -D /Data/BLOCKS/HKLR/CDP -S “0x05|0|0x06|0|0x07|1|0x08|1|0x19|1|” 0016744 999999 >> ../data/log/bin2root_SCIBPB_RT.log • For SCI, CAL and CFG decoding: • ./bin2root -D /Data/BLOCKS/SCIBPB/RT -S “0x05|4|0x06|1|0x07|1|0x08|1|0x19|0|” 0006000 999999 >> ../data/log/bin2root_HKLR_CDP.log • COMMAND Syntax: • ./bin2root -D /Data/BLOCKS/SCIBPB/RT -S “0x05|4|0x06|1|0x07|1|0x08|1|0x19|0|” 0015807 999999 >> ../data/log/bin2root_HKLR_CDP.log Block Files directory Pre-scaling Factors First-Last Block Files 11
Program bin2root is running if … …a colored meter, which updates every second, is shown with block file number being reconstructed… …or a message saying “Waiting for a new file…”, updated every 30 seconds, is displayed at screen bottom.
bin2root – call an expert if … • bin2root is stopped and it can not be restarted • bin2root has frequent crashes or error reports in the logs • Block files start to be downloaded on different directories respect to the “official ones” (i.e.: /Data/BLOCKS/SCIPBP/RT and /DATA/BLOCKS/HKLR/CDP) • bin2root decoding on SCI data is very slow (i.e.: the progress bar reports decoding time much greater than 1 min. while bin2root is running on /Data/BLOCKS/SCIPBP/RT) 13
Start Monitoring • open the monitoring program as follows: • cd ~/ECAL/ECMON/Mom • source ../ECAL_setup.sh • ./Mom& • A Graphical User Interface (GUI) is opened
Open LAST DATA or CALIBRATION ROOT data file: select LAST DATA or LAST CLB button Depending on the type of file you open, only the commands marked in green work.
The plots that a SHIFTER has to look at are listed under this section of the monitor window. The basic concept is: occupancy plots have to be flat! Shifter has to look for: DEAD channels (holes) HOT channels (peaks)
OccupancyX and OccupancyY : DEAD cell If you see 1 or (few) more dead cells: • check in the ELOG, or in the paper LOG, or asking around, if this is a known problem • ask the DAQ shifter to STOP the run, perform configuration and restart • even if the problem persists, data taking can continue • write an entry in the ELOG and notify an expert dead cell If you see a full group of dead cells: normally this is a problem of HV; default HV values are reloaded at configuration, so the actions to be taken are: • ask the DAQ shifter to STOP the run, load configuration and restart • if the problem persists, ask the DAQ shifter to switch on the ERPD B side (if A side is on) : however this must be coordinated with RICH, since this action will also have impact on this system! • call an expert
OccupancyX and OccupancyY : HOT cell If you see 1 or (few) more HOT cells: • check in the ELOG, or in the paper LOG, or asking around, if this is a known problem • ask the DAQ shifter to STOP the run, perform configuration and restart • if the problem persists, check the trigger occupancy to see if this is causing a lot of trigger hits • check with the DAQ shifter if the ECAL contribution to trigger rate is too high (see next slide) hot cells The DAQ shifter must remove ECAL from the trigger logic write an entry in the ELOG and call an expert NO YES If this is not the case, then data taking can continue write an entry in the ELOG and notify an expert
Checking anomalous trigger rate In this window (JLV1-1) you see the contribution of different sub-triggers to Level-1 ECAL used in SubTrigg. 4 (“electron trigger”) and 5 (“photon trigger”). Typical ECAL trigger rates are ~10% of total trigger; if this number is much larger, causing an increase in dead time, ask DAQ to remove ECAL from trigger and call expert
Occupancy HG 2D(HG=HighGain) 324 PMTs each one with • 4HG (High Gain) anodes • 4LG (Low Gain) anodes • 1 dynode • 1 trigger (only 2/3 of cells) for a total of 3024 channels Useful to spatially localize • a spike from a HOT photomultiplier (red box) • a hole from a DEAD photomultiplier (white box)
Trigger occupancy - Only 6/9 superlayers are used in ECAL trigger (see AMSnote-2003_08_01.pdf) - again SHIFTER must look for HOLES and SPIKES -> the SHIFTER has mostly to look for anomalous peaks in the distributions; if this occurs, take the same actions described before in slide Checking anomalous trigger rate
Trigger Occupancy 2D Useful to spatially localize anomalous triggering PMTs.Only 3 Superlayers are used in each view.
MEAN and RMS ALL CELLS 1. Open CALIBration file 2. Pedestal values peak around 100-200 3. RMS values are all below 5 4. if you see an overflow in one of these distributions: 0 - check ELOG if this is a know problem 1 - if you are looking at data in real time (no delay in data to ground) ask DAQ to stop and restart the run (=perform a calibration) 2 - notify an expert
Temperature Data size Trigger rate Power consumption (of LV) High Voltage (only at switch on) Part 2: SlowControl
SlowControl - general • all programs should run in workspace SlowControlof ECAL console (currently PCPOC09) • all windows must be opened from the directory ~/ECAL/SlowControl > cd ~/ECAL/SlowControl
1. ECAL temperatures (thermal shifter should also check this) launch GTSN-3-M and press ECAL button a long list of temperatures is shown if T>upper_operative_limit switch off electronics (=ERPD)! if T<0o check with DAQ that heaters are enabled if T<lower_operative_limit switch off electronics (=ERPD)!
2. Data Size • Launch with command: • ESCM & • Normally this window is (should be) checked also by DAQ • ECAL event dimension ~400B ECAL window
3. Trigger rate (JLV1-M) Total Fast trigger: must be <10% of AMS level 1 Fast trigger Y view Fast trigger X view Angular trigger X view Angular trigger Y view AMS level 1
4. Power Consumption launch program with: > cd ~/ECAL/Slowcontrol > PDS-M 2 2 & The ERPD currently switched on (A/B) should read ~3.5A The other must stay at 0A, with fluctuations <0.3A accepted
5. HV settings • This operation must be done ONLY at restart, AFTER power step 2 (check with DAQ) and BEFORE run start • Brick-5 eas:HOSC pcposj0 & • Check with DAQ what side of EHV is on • Read all EHV-A/B : they should all be 850Volts